magicSpam interrupts on debian 5 64bit, plesk 9.x, postfix

[andi]

hello,

on our debian 5 64bit plesk 9 nodes, magicSpam was working fine, while we were using qmail MTA. - since some weeks, we changed MTA to postfix (inlucding postfix-policyd) and since then, we are facing the issue on several servers, that checking messages by magicSpam stops sometimes. if this happens, magicSpam is shown as activated, but no one message will be scanned. also, i was never able to restart scanning - only uninstall / reinstall of magicSpam (magicspam-plesk-1.0.5-3.1-lenny64-postfix.amd64.deb) did the trick.

what could be the reason for this issue and what can be done agains?

regards,
andi

[magicspam]

Hello Andi,

That's a little disturbing indeed...

Are all of these nodes still Plesk 9 - just running with Postfix MTA or were they upgraded to the 10.x series?

Also.. the postfix-policyd package - is that from Parallels or is that a 3rd party (or rather linux distribution native) one?

And finally, could you verify the exact version of MagicSpam that is running on those servers? We released a mini patch release for the postfix specific packages a while back to work around an issue that may or may not be related...

Thanks!

[andi]

hi,

all servers are plesk 9.5.4 servers on debian 5 64bit with postfix MTA.
postfix-policyd: http://www.policyd.org/
magicSpam: magicspam-plesk-1.0.5-3.1-lenny64-postfix.amd64.deb (i think, this is the latest version)

thank you,
andi

[magicspam]

Hello Andi,

We've taken a quick look at the policyd software.. we do need to point out that interoperability with that software with Parallels Panel is likely to experience issues. The fact is that Parallels software itself, upon updates and some other triggers we haven't fully identified yet - have a tendency to behave badly with added entries in the smtpd_restrictions = configuration line that policyd is normally configured to use.

Further to that, there is a possibility that the triggered act of configuration rebuild may also end up rebuilding the full configuration as opposed to the individual setting. Our own software links in (now) using the smtpd_milter configurations. During those periods in which service is noted as interrupted, would you be able to capture the output of the command:

postconf | egrep "^(smtpd_milters|smtpd_recipient_restrictions).*"

To confirm?

Thanks!

[andi]

hi,

i just detected a node, where magicSpam does not scan the messages:

# postconf | egrep "^(smtpd_milters|smtpd_recipient_restrictions).*"
smtpd_milters = inet:127.0.0.1:12345
smtpd_recipient_restrictions = permit_mynetworks, check_client_access pcre:/var/spool/postfix/plesk/no_relay.re, permit_sasl_authenticated, reject_unauth_destination

but:
# cat /etc/magicspam/control/enabled | grep 1
1


disabling / enabling protection did not change this output and situation, messsages are still not scanned.

after de-/reinstallation and enabling protection of magicSpam, i still get the sam output, but magicSpam is scanning the incomming messages again:

# postconf | egrep "^(smtpd_milters|smtpd_recipient_restrictions).*"
smtpd_milters = inet:127.0.0.1:12345
smtpd_recipient_restrictions = permit_mynetworks, check_client_access pcre:/var/spool/postfix/plesk/no_relay.re, permit_sasl_authenticated, reject_unauth_destination


thank you,
andi

[magicspam]

Thank you Andi, that helps.


It looks as if everything is integrating fine, and MagicSpam should be able to coexist with the policyd fine as well (though our previous warning about Parallels Plesk updates still applies.)

When this 'interruption' is next noticed, can you check please to see if there is a running process: /usr/share/magicspam/bin/magicspam-milter ?

The command:

ps fauxww | grep magicspam-milter

should do the trick for finding it.

If it is not, then see if starting the service again:

/etc/init.d/magicspam-milter start

does the trick.

In either case, please let us know.

Thanks!

[andi]

i got one and checked according to your advices:

magicspam-milter seems to be up and running:
# ps fauxww | grep magicspam-milter
root 27958 0.0 0.0 3876 600 pts/0 S+ 09:30 0:00 \_ grep magicspam-milter

# postconf | egrep "^(smtpd_milters|smtpd_recipient_restrictions).*"
smtpd_milters = inet:127.0.0.1:12345
smtpd_recipient_restrictions = permit_mynetworks, check_client_access pcre:/var/spool/postfix/plesk/no_relay.re, permit_sasl_authenticated, reject_unauth_destination

# cat /etc/magicspam/control/enabled | grep 1
1

last log seems to have been created 2011/10/31:

# ls -la /var/log/magicspam
total 2052
drwxr-xr-x 2 magicspam magicspam 4096 Nov 4 00:00 .
drwxr-xr-x 17 root root 4096 Nov 4 08:49 ..
-rw-r--r-- 1 magicspam magicspam 500 Jan 31 2011 .counter.dat.01
-rw-r--r-- 1 magicspam magicspam 500 Feb 28 2011 .counter.dat.02
-rw-r--r-- 1 magicspam magicspam 500 Mar 31 2011 .counter.dat.03
-rw-r--r-- 1 magicspam magicspam 500 Apr 30 2011 .counter.dat.04
-rw-r--r-- 1 magicspam magicspam 500 May 31 23:57 .counter.dat.05
-rw-r--r-- 1 magicspam magicspam 500 Jun 30 23:56 .counter.dat.06
-rw-r--r-- 1 magicspam magicspam 500 Jul 31 23:59 .counter.dat.07
-rw-r--r-- 1 magicspam magicspam 500 Aug 31 23:54 .counter.dat.08
-rw-r--r-- 1 magicspam magicspam 500 Sep 30 23:59 .counter.dat.09
-rw-r--r-- 1 magicspam magicspam 500 Oct 31 22:33 .counter.dat.10
-rw-r--r-- 1 magicspam magicspam 500 Dec 31 2010 .counter.dat.12
-rw-r--r-- 1 magicspam magicspam 766068 Oct 31 22:33 mslog.4
-rw-r--r-- 1 magicspam magicspam 371117 Oct 30 23:58 mslog.5
-rw-r--r-- 1 magicspam magicspam 416558 Oct 29 23:56 mslog.6
-rw-r--r-- 1 magicspam magicspam 470831 Oct 28 23:58 mslog.7

last entries in mslog.4 are from 22.33 PM:

# cat mslog.4 | tail -1
2011-10-31 22:33:34 magicspam-milter[18624]: HAM: mua=0,ip=[***.***.**.***:***.***.***],helo=<***.***.***>,from=<***.***@***.**>,rcpt=<***@***.***>


disabling / enabling magicSpam did not the trick,
so i uninstalled / reinstalled magicSpam, now messages are checked again.

regards,
andi

[magicspam]

Apologies for the delayed response Andi. Our developers are looking into this issue and trying to determine possible causes. In the meantime, the following commands may be quicker for you than uninstall / reinstall:

/etc/init.d/magicspam-milter stop
/usr/share/magicspam/bin/register -i
/etc/init.d/magicspam-milter start
/usr/share/magicspam/bin/register -a

We hope this at least saves some time and will let you know as soon as we have further information on what may be causing this...

Thanks!