Seth Randall said: > 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.
Some background of the ip address of the client in the message-id: Not long ago (october 2003) we used the ip address of the server where squirrelmail was located as message-id. SA complained that the client didn't generate a message-id and that the message-id was inserted by the smtp-server (which was not the case). To avoid the false assumption I changed to the client ip address instead of the server's ip address. Marc. ------------------------------------------------------- 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_id70&alloc_id638&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
