On Sun, 29 Sep 2002, Marc MERLIN wrote:
[...]
> Otherwise, see:
> http://bugzilla.spamassassin.org/show_bug.cgi?id=444
> for my patch
OK; as a quick fix, I have manually applied the patch
http://bugzilla.spamassassin.org/showattachment.cgi?attach_id=181
into the production copy of PhraseFreqs.pm
After restarting the daemons, it seems to have done the trick.
The offending mail has now been zapped, and a copy of it captured
for inspection.
It turns out that our spamassassin had been trying to reject a remote
spamassassin rejection report for a message whose sender address had
been counterfeited to be a remote user who has set his forwarding
address to his account with us. How's that....
> PS: I try to keep current on this list, but sometimes I have to do fast
> reading, so make sure you Email the sa-exim list if you want to make sure I
> see your message :-)
Understood, but I'm afraid I was initially confused as to whose
code was at the sharp end of this particular problem. Many thanks
for the clue!
