Our Spam mail filter has been modified to correctly support the whitelisting of SMTP-AUTH authenticated mail on our servers. Therefore, sending mail using 'smtp.umbc.edu' and authenticating to it using SMTP AUTH will allow your mail to bypass our spam flagging (and filtering.) This was the behaviour in our pre-January mail environment, and was an oversight when converting to our new system.
Basically, in the old system, you authenticated to the 'smtp.umbc.edu' relay machines, and then your mail was forwarded on to the 'mxin.umbc.edu' cluster for filtering and delivery. At that time, there was a Received: header in the message that advertised that this message was had an authenticated sender, so Spam Assassin could trigger on this to "whitelist" the message.
In our new environment, the outgoing relays and mail delivery machines are one in the same, and since the incoming message hadn't yet been blessed with a "Received:" header, Spam Assassin had nothing to trigger off of, and would simply treat the message as it usually would. MilterMonkey, and the Spam filtering module have been augmented to read the {auth_authen} macro from sendmail, and do the right thing bypassing the filtering engine. Messages that have been processed as such will have an X-Spam-Status header similar to:
X-Spam-Status: hits=0 rating= tests=AUTHENTICATED_USER(banz)
Comments (1)
Rob,
Makes sense, but I still have whitelisted addresses getting flagged as spam and sent to my spam folder.
John
Posted by John | February 7, 2006 11:30 AM
Posted on February 7, 2006 11:30