----- Original Message ----- From: "Dan Hollis" <[EMAIL PROTECTED]> To: "Shane Williams" <[EMAIL PROTECTED]> Cc: "Daniel Quinlan" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Mark" <[EMAIL PROTECTED]> Sent: Saturday, February 22, 2003 2:43 AM Subject: [SAtalk] Re: Spamassassin 2.50 rewrites Received: headers, how to stop it?
> Not to mention violating the "rule of least astonishment", eg > spamassassin should behave in a way that astonishes the user the least. I doubt it. :) Either a user is completely clueless to headers, in which case 127.0.0.1 will mean nothing to him; or he is computer-savvy enough to know what 127.0.0.1 stands for, in which case he will no longer be surprised. > Receiving spam mails from 127.0.0.1 is certainly suprising to say > the least. But they are NOT receiving spam from localhost, are they? They receive a notification from localhost, containing a spam as attachment. Big difference. In fact, giving the pseudo Received: header an IP address other than originating from localhost (or hostname), would be more "spammish", really. - Mark ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
