> Time to ask to spamassassin developers?
Solved.
The ipp2p (p2p block) firewall rules were active on localhost and
blocking connection to spamd via socket on port 783 for that
particular mail.
Sorry for the noise.
--
Ciao,
Filippo
> The mail has only two body lines, the first is very long. Here it is:
...
> If I cut that line after Code)" the mail arrives to spamd, if I don't
Please, read: if the line is more than 311 chars long, spamd doesn't receive it.
I modified the spamassassin plugin duplicating each print to SPAMD
s
Filippo Carletti wrote:
The symptoms are:
1. spam mail is not recognized as spam, no tests match (X-Spam-Status:
No, hits= required= tests=)
2. spamd logs:
warn: spamd: timeout: (300 second timeout while trying to SYMBOLS)
at /usr/bin/spamd line 2016, line 19.
3. qpsmtpd logs have a 5 minute
I think I'm experiencing the same problem described here:
http://www.nntp.perl.org/group/perl.qpsmtpd/2006/11/msg5815.html
Environment is the same, behavior identical.
But I'm able to reproduce the problem at will, I have a mail that is
sent partially to spamd.
The symptoms are:
1. spam mail is n
