Another lightweight test you might want to consider is scoring a message for how much the Date: header deviates from Delivery-date or Received date.
I get a lot of spam that is dated a few days/weeks in the future, and also a few years in the past. This almost never happens with legitimate email. Occasionally, there will be the legitimate automated email from a server that is misconfigured and thinks it is 12/31/1969 6:00pm, but that is rare. A difference of more than 24-48 hours is more than likely not a drifting clock or misconfigured server, but rather a spam message attempting to gain attention by either floating to the top of the email list, or forcing a user to hunt through their email to clear the "new mail" flag. http://www.hoax-slayer.com/future-date-spam.shtml It would be nice for ASSP to be aware of this trick and penalize against it, but would it also be possible for ASSP to correct the time received header on emails coming in with clearly incorrect time? I switched from Outlook to Thunderbird a little while ago, and one thing I really miss is that Outlook would either normalize the received time or just sort by a different header to reflect when the message was actually received, which allowed me to check my ccSpam folder and find messages more accurately, instead of wading through messages from 4 years to 4 weeks in the future. Is normalizing the time the job of ASSP, the MTA or the email client? ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
