Hello, magicspam-plesk stopped working with the following errors in the maillog... Oct 14 16:12:34 plesk6 magicspam-plesk[30859]: lm_file.c:106 ERROR lm_open(): Too many open files Oct 14 16:12:35 plesk6 magicspam-plesk[30859]: lm_file.c:106 ERROR lm_open(): Too many open files We're using Plesk 11....

Is this still the best method for the latest version of MaginSpam for Plesk? I'm using Plesk 11.0.9 w/ Postfix on CentOS 6.4. If upgrading, does the previous version of MagicSpam need to be removed, first? From the command line or via the Plesk Extensions GUI (or does it matter)? Settings will still...

Hello, We use Magicspam (1.0.6-1.3) for Plesk 11.0.9 with Postfix on CentOS 6.4. Is the "valid_from_domain" test intended to also reject mail from the null sender in addition to invalid domains? As I understand it, that violates RFCs, so I wanted to confirm that this is the intended behavi...

Hello, We use MagicSpam on Plesk 11 with CentOS 6 and Postfix. Recently, e-mail messages generated by Cron have been rejected by MagicSpam. See below... - - - - - From: root@plesk.example.com (Cron Daemon) To: root@plesk.example.com Subject: Cron <root@plesk> /usr/local/psa/libexec/modules/watchdog/...

So, in your opinion, or estimation, would you consider this rule (check_reverse_dns_list) to be less likely to have false positives than the check_dynamic_reverse_dns rule that blocks any dynamic looking reverse DNS (which is quite common for non-spam senders)? I'm looking for an alternative to chec...

Hello, I'm looking for additional details or a better description of what this rule is (check_reverse_dns_list). Is it a more forgiving version of check_dynamic_reverse_dns that only matches very specific patterns instead of all generic reverse DNS? Can you provide an example of a pattern that it is...

Hello, We use MagicSpam on Plesk 11 (CentOS 6) with Postfix. We only use IPv4 addresses on the server. I have noticed that messages sent from Mailman mailing lists (coming from the local machine) have been blocked. I had previously added 127.0.0.1 to the IP whitelist because other locally generated ...