> Big subject line but what the heck. > > When I send email from SquirrelMail to friends who use spamassassin > it gets marked as spam.
> 2.0 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS > [xx.xx.xx.xxx listed in dnsbl.sorbs.net] > 2.5 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address > [xx.xx.xx.xxx listed in dnsbl.sorbs.net] I think, users will get same scores, if they use regural programs from their broadband/dialup machines. SM 1.5.1cvs allows to disable this header. If you search gmane.org or other squirrelmail list archives (this week articles), you will find bug numbers, comments and different patches. You should find explanation why it is dangerous to disable this header. You missed 3.5 RCVD_IN_NJABL_DIALUP SpamAssassin v.2.6.3 :) > 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer This is SpamAssassin bug fixed in 3.0.0cvs. check rules/20_head_tests.cf >From 1.4.0rc2 squirrelmail uses User-Agent: header. SpamAssassin does not check for User-Agent + Priority combination. Mozilla ThunderBird creates emails with User-Agent + Priority too. SquirrelMail 1.4.3cvs adds User-Agent and X-Mailer. By doing it SquirrelMail risks to get +40 points in some German SA installs. SquirrelMail 1.5 adds only User-Agent: header. SquirrelMail 1.4-STABLE will keep both headers until SA stable version with 20_head_tests.cf bugfix is released. -- Tomas ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
