Hi,
I had the same problem where an update from spamass-milter seemd to
cause spamassassin milter stop working and give the same error messages
in /var/log/maillog:
Milter (spamassassin): local socket name
/var/run/spamass-milter/spamass.sock unsafe
Milter (spamassassin): to error state
I
that as well. So John, thanks for mentioning
that as well.
I would assume though that Spamassassin would only look at the topmost
X-Greylist header.
If I do get it to work I think I will keep it till I start noticing an
increase in spam due to X-Greylist headers being spoofed.
Regards,
Arjun
Hi,
I have milter-greylist running on top of spamass-milter and spamassassin.
when milter-greylist detects a user that has passed SMTP AUTH - it does not
delay it and adds a header:
X Greylist: Sender succeeded SMTP Authentication, not delayed by
milter-greylist 0.3
Now, how do I add a rule to
