On Mon, 23 Jun 2008 06:09:21 +0900, Jason Haar <[EMAIL PROTECTED]> wrote:
> Mike Tedder wrote: >> I reverted back to qs-2.02 a few days ago, and so far all mails are >> coming in with the Message-ID in the header intact. So the problem is >> indeed with qmail-scanner, and not SpamAssassin. >> > > I was going to say "did you read the CHANGES file" but I now see I never > wrote in there what I'm about that say :-/ Actually, yes I did, and I noticed this particular change. :) > So I removed it. Now if a message hits QS without a Message-ID, QS > passes that to SA without the added "faked" Message-ID - and SA can > score it correctly. Then after the scoring has been done, QS will add a > Message-ID to it (if one isn't present) - just as it used to. I originally thought that this might have been the case, but I confirmed that the Message-ID was indeed coming from the remote client by using tcpdump on the SMTP connection. I posted the dump in the first mail to the list. Also, the format of QS's "faked" Message-IDs is not what I'm seeing in my mail client when I'm using qs-2.02. Finally, even if the Message-ID was not there to begin with, QS isn't adding a Message-ID at all. The mails received by my mail client don't have any Message-ID in the header with qs-2.04. So I think we're discussing a different problem here. I'll be doing the upgrade to 2.03 today, so let's see what happens. One last thing: I am using perl-5.10.0. Is there any known problems with this, perhaps? -- - breakpoint / brainstorm ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Qmail-scanner-general mailing list Qmail-scanner-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
