Nicolas Letellier wrote: > 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? > > Thanks. > > > The best way to disable a rule, is to add a score statement for it setting it's score to 0 in your local.cf
score MSGID_MULTIPLE_AT 0 and yes, that does disable it. SA won't even evaluate a rule explicitly set to zero sc0re
