Hello all, I have been off the list for awhile but have been using SA. With the recent upgrade to 2.31 I have discovered a couple of rules that don't always work:
DATE_IN_FUTURE_03_06 FAKED_UNDISC_RECIPS FORGED_JUNO_RCVD Has there been any discussion on these? (Geocrawler is so difficult to search thru archives!). Here is what I found: DATE_IN_FUTURE_03_06: This rule misfired on an email that one of my customers sent. Her date was set using Pacific Time while being in Eastern time so her clock was set 3 hours ahead to correct the date. From my experience with novice users and PC clocks this is very common especially since MS Windows always defaults to Pacific time so I imagine that alot of East coast PCs are set like this. I myself have seen several. Perhaps this rule should be left out of the mix. FAKED_UNDISC_RECIPS: This rule misfired on a few emails that were legitimately sent BCC. FORGED_JUNO_RCVD: This one has caused alot of pain. With a large score of 4.4 it had better work flawlessly. I have helped a few customers with this one who did receive legitimate messages from Juno customers. I personally looked thru the headers and all of the Recieved headers appeared fine but they were still tagged as forged. Unfortunately, I do not have any copies of these emails to help with the discussion but am hoping that others have seen this and have some input. Thanks, Ed. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
