Hello WolfgangP, Thank you for posting to the forums. To answer your questions / observations - Not much we can tell you about the MBS message (possibly related to BMS?) that you saw without further information. Is your server configured to also store such information to log files as well or just co...

Greetings user7549, First, it should be noted that MagicSpam is not a 'filtering' service and as such it is not a case of 'releasing' a caught message. The message itself was blocked directly at the SMTP layer and as such the sender should have received a notice complete with a web URL to visit or f...

PostFix and most other systems 'can' be configured/modified to perform some of the actions that MagicSpam performs. However, most platforms are *not* configured that way out of the box. Aside from the MagicSpam 'special' features that maybe you cannot do, even for the items you can do with Postfix o...

Greetings, This sounds like a case where the sender's email server is only parsing the last line of the extended rejection notice. MagicSpam operates on a basis of multi-line rejection (which is permitted as per RFC specifications) whereas a series of "550" lines are issued. A proper compl...

Greetings, Log files should be accessible in the easiest sense by simply using the interface 'search logs' and 'view last 50 log entries' items on the main page. This stated, the logs should indeed be located /var/log/magicspam. The fact that the directory is empty is indicative of one of two things...

NOTE: this has been resolved via Email: Simply click on 'Modules / Magicspam' after downloading and installing the MagicSpam module specific to your OS / Plesk Version combination.

At this time bulk IP blocking (or exemption) support is not supported. The core reason is that there are many ways to specify ranges (be it CIDR notation, netmasks, dash dot ranges...etc) and is very very easy for one to make a wrong entry that could cause damage / harm to production services. This ...

The updater uses two ports:

443
and..
80

That is an interesting viewpoint indeed. We won't spend time arguing for / against, but simply point out that as part of Email Server Best Practice standards, a public Email service should have a proper conforming in-addr.arpa entry in place in order to properly identify itself. We have had customer...

Unfortunately no, MagicSpam for Plesk (on *Windows*) cannot be managed via the Plesk interface. Plesk has not provided a means to do this, which is why that functionality is not there. Our versions for Linux are capable of doing exactly what you're looking for, and they can be installed via the modu...