Matt, I just took a look at the email you sent earlier in the week. All of the spamassassin tests that your example failed were tests on the Recieved line (hence the RCVD_IN test names). A brief (and not hugely thorough look) at the Spamassassin source doesn't turn up any tests against a IP address in the Message-ID. Unfortunately, you didn't include the headers from the original message that Spamassassin rejected, so I wasn't able to see what all it rejected on. Since Message-ID is defined as an identifier that the host is guarantees is correct, the use of an IP address is more of a convention than a standard. There is nothing stopping a client or SMTP server from sticking whatever it wants there. If a SMTP server wanted to put the client address that connected to it, it could. If Spamassassin does or decides to test against that, I'd say that it is broken and not Squirrelmail.
Seth. Matt Gostick said: > No,It seems SquirrelMail adds the dialup IP as part of the msgid. > SpamAssassin is parsing that IP from the msgid and flagging it as spam > because of dialup. I posted a message about this a couple of days ago, > but no-one gave a decent response. > > I have grep'd/awk'd through my maillog and it seems that SquirrelMail is > basically the only one I can eyeball out that is doing this... > > Matt. > -- Seth Randall IT Support Specialist Missoula Federal Credit Union [EMAIL PROTECTED] ------------------------------------------------------- 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
