Carl Brewer wrote:
It's a known problem. Dan Nelson (spamass-milter maintainer) says it's not spamass-milter :
But, it's broken -somewhere-, and the change was made in spamassassin. Any chance of reverting the change in spamassassin so spamass-milter works again?
Can you provide me with three copies of an affected message in a tarball: - the original, unscanned message - the original message after it has gone through spamass-milter - the original message after it has gone through spamc, not spamass-milter Be sure to use appropriate redirection and not copy-and-paste. Thanks, Daryl