Well, I notice that the only mail that comes in with the incorrect time is spam, and about 5 or so emails from servers that are misconfigured and use the beginning of the epoch as their time. While probably not necessary due to the incredibly low volume of false positive (1:5000?), perhaps a "WhiteTime" could be used to score less harshly for servers that are innocently incorrect versus 4 years in the future incorrect.
Jean-Pierre van Melis wrote: > I don't think it's a bad idea to give the mail some penalties for having a > date too much in the future or too long ago in the past. Some IP's could be > whitelisted and (optionally?) have their timestamp replaced with the moment > it is received by ASSP. Adding an extra header with the original timestamp > and no info is lost. > > I just wonder how much spam is getting stopped this way. > Personally I don't use any of the filters that scan the contents (besides > viruses), so any good idea is welcome. > ------------------------------------------------------------------------- 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 Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
