> -----Original Message----- > From: Nicolas Letellier [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 02, 2008 2:59 PM > To: users@spamassassin.apache.org > Subject: Re: problem with MSGID_MULTIPLE_AT > > On Tue, 02 Sep 2008 08:47:18 -0400 > Matt Kettler <[EMAIL PROTECTED]> wrote: > > Well, it's obvious what the problem is. There's clearly two @ signs > in > > the message-id, which is illegal, but it's what Microsoft is doing > anyway. > > > > There's also a bug already open on this. > > > > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5707 > > > > We might need to convert that rule to a meta and ignore it when the > MUA > > is outlook 12.0 unless we can figure out that the outlook in question > > has some weird hack that causes it, and normal outlook 12 doesn't > cause > > the problem.. Although I personally feel makers (and knowing users) > of > > broken tools should suffer, I don't think SpamAssassin is the best > spot > > to implement that. :-) > > Hello Matt, > > But today, I can't leave this option actived (or not patched). It's > important for my business, and too many clients use Outlook 12.0 (I > can't force them to use another mail client). > > For waiting, is it possible to disable the MSGID_MULTIPLE_AT check? And > how?
Put this in your /etc/spamasassin/local.cf: score MSGID_MULTIPLE_AT 0 Giampaolo > > Thanks. > > > -- > -Nicolas.