From: "Kjetil Kjernsmo" <[EMAIL PROTECTED]>
On Sunday 23 July 2006 00:52, jdow wrote:We still need to know how SpamAssassin is invoked. Could you give an anatomical description of your "mail goes in here and comes out there" message digestion process with each tool that gets invoked along the way at least named?Yup, all that was in my original mail. I figured I'd try to be terse this time! :-) spamd is running on a host robin (since then renamed to eeyore). It is called by qpsmtpd 0.32 with remote spamd capabilities. Since qpsmtpd is Perl-based, I'd be surprised if the calling code isn't essentially identical to the code in spamassassin itself. It is very simple, no amavisd or anything.
Spamd is "called" via spamc which is a C language thing.
It would also help to know how the daemon starts for spamd,It is a Debian system, it has its own ways of launching things, but ps x shows this:/usr/sbin/spamd --ip-address --allowed-ips=192.168.2.0/24 --username spamd --create-prefs --max-children 5 --helper-home-dir /var/opt/spamd -d --pidfile=/var/opt/spamd/pidI'm sure there isn't a permissions problem either, since it does run most of the time.
Before jumping onto qpsmtpd, I had been running Exim4 for several years. I had seen occasional unscanned messages, say once a month. I thought I had some kind of misconfiguration, so I didn't investigate further (often, it were things that had come through e.g. my CPAN address). This setup was not capable of using SA 3.1 like I wanted, so I split off spamd but retained Exim4 at first. It pretty much had the same symptoms, but I couldn't get Exim to give me any logs for debugging. Anyway, I suspect this is independent of the caller, since the same symptoms have been observed with Exim and qpsmtpd.
Regarding infrequent unscanned messages do they just happen to coincide
with a rules update time? That is the current unscanned messages problem.
I think 3.1.3 would have the fix for the PerMsgStatus.pm version of
unscanned messages.
I had the impression you were experiencing the cited problems with every
message. Having it happen with infrequent messages is a whole different
kettle or earthworms, most of which have been solved and the remainder of
which you can work around IF you can briefly tell qpsmtp to hold mail
for 3 or 4 minutes while the RDJ update is done. This should be QUITE
rare, however.
Another possible problem uniquely comes from the two machine configuration
if one or both machines have a firewall active on the interface net. There
are some ports that seem to get blocked for any use due to their frequent
appearance in nasty trojans. That could be causing you the upset.
{^_^}
