Search results

Hi, I have a legacy server running Debian 9.13 with Plesk version18.0.44-3 (the last one available for the OS), and this morning I got this email: 2023-03-29 06:25:13 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-03-29 06:25:16 ERROR: E:The repository...

If I'm not mistaken, the spam filter blacklist identifies emails from those subdomains as SPAM, but it is to the individual mailboxes filters to either reject SPAM, move it to the SPAM folder or just mark it as such on the subject but still deliver it to the inbox.

Sorry for bumping the thread as it is indeed Resolved. It turns out, for my particular case, the rotated mail.info files had the data I needed. Just a FYI if anyone is in the same position.

Perfect. Thanks!

Well, that's too bad. How can I increase the number of log files for maillog? This is my current /usr/local/psa/etc/logrotate.conf (OS: Debian 10): /var/log/maillog.processed { missingok rotate 3 size 10M compress nocreate } With that I have up to...

Hi, I'm having the same problem. I need to access an older version of maillog and can't find it on a full -no excluded log files- server backup. Anyone can confirm in which tzst file inside a full backup the maillog files are? Thanks.

I think this is an important observation. In an ideal world all of our servers would be up to date but in the real world some customers don't want or, most likely, can´t afford the costs of redesign a website they've already paid for, so many companies are forced to maintain at least one...

Thanks Peter!

I might need to do that in the near future due to unsupported OS, it will be helpful to know Plesk team's response time so I can schedule a timetable for the migration.

Hi, a client has mistakenly deleted the logs directory of a subscription. A full subscription backup, with the log files included (I downloaded the backup and checked they're there), did not recover the directory. Is there a way to regenerate these logs inside the subsciption directory...

Thanks, that is extremely helpful. The "new server with trial license -> plesk migration tool -> shutdown old server -> move license to new server" route was the way I dealt with unsupported OS as I prefer it to the risks of a dist-upgrade. I'm glad that option is still available.

Oops! I meant SpamAssassin custom rule and fail2ban custom filter, one for logging and the other for blocking based on the logged entry.

That's to me the main problem of the firewall, that it doesn't log anything. Several customers complain about the relatively minor spam attacks they get without knowing the ammount of stuff that doesn't get through, and we can't present them with any evidence otherwise. Sadly I dont' have an...

According to the docs, the dist-upgrade has a downtime "of one to three hours". Since I can't afford that ammount of downtime the "new server -> plesk migration tool -> switch DNS" has been the way I've updated my Plesk when the OS goes unsupported. In a couple of days everything is migrated and...

Related question to the original: changing root password via ssh changes the plesk root password as well?

Hi, I think this maybe related to Plesk dropping support for Debian 9: Change Log for Plesk Obsidian, more than to the manually installed PHP 5 version, because I have a development server with debian 9 and PHP 7 and 8 and got the same message. Since it won't receive more PHP updates...