>From reading the code: * just noticed Mail::SpamAssassin::Conf::add_to_addrlist() where it's converting the glob-patterns to regexs as it reads them in. Missed that in previous scans of the code. * before I changed it yesterday, the comparison was between the lowercased addr from the email and the unmodified string from the whitelist_from entry, in other words:
From: [EMAIL PROTECTED] ... whitelist_from *@PASSPORT.COM would try to compare passport.com with /.*@PASSPORT.COM/ and so would fail. I've since added a /i to the end of that match, so it should be case-insensitive now (which is more RFC compliant). The version in CVS should now work doing case-insensitive glob-pattern matches. C On Mon, 2002-02-04 at 10:52, Andrew Kohlsmith wrote: > LAST UPDATE (I hope!) > > The whitelist matching *IS* glob-type. .*@domain.dom is wrong. Lots of > debugging confirms this. > > Also, more debugging confirms that the whitelist_from entries *ARE* being > taken from SQL. It appears that it's not matching for some other reason. > (maybe because the passport "From" field is in block capitals?... testing.. > yes that is why.) > > So now... is this a bug in SpamAssassin or are these mailers broken? > > Regards, > Andrew > > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
