Godwin Stewart wrote: > It's almost certainly because your machine is identifying itself > incorrectly, pretty much the same way a machine taken over by a spammer > would. > > Upon connecting to a remote server, your machine is sending back this > string: > > EHLO ?192.168.1.3? > > This is invalid. The EHLO string must be a fully-qualified domain name > resolveable in DNS or an address literal (enclosed in square brackets, > not question marks), and that address should be your public IP address, > not a private address. > > Fix that and filters like SpamAssassin etc. will be less prone to flag > your mail as spam. > Ok... I checked one of my emails, and this is what I read for that line... Received: from unknown (HELO ?192.168.1.3?) (wittig.robert@xxxxxxxxxxxxx@70.142.248.62 with plain) by smtp107.sbc.mail.re2.yahoo.com with SMTP; 3 Feb 2007 11:37:16 -0000 Now... parsing this... 192.168.1.3 is the private IP address for my Red Hat Enterprise Desktop machine... the one I am sitting at, typing this, and from which I will send this email, when I post it. 70.142.248.62 is the IP address on the public side of my gateway router, that NAT uses for all the Desktop machines on my LAN. wittig.robert@xxxxxxxxxxxxx is the SMTP that I send my outgoing Desktop email to. ...and my emails are plain-text... and the rest of the line... by smtp107.sbc.mail.re2.yahoo.com with SMTP; 3 Feb 2007 11:37:16 -0000 ...would, therefore, be contain the FQDN of the SMTP server. That is the SBC-Yahoo server that I use for most all of my email, because that is how my ATT-SBC-Yahoo DSL ISP prefers that I send email. I think this is a correct parsing of the line, and that the line should be valid, but if I am wrong, I would of course be interested in knowing what I should do to correct it. My robertwittig.com and robertwittig.com sendmail servers are functional, and do send me outgoing email... my logs, insecurity reports, etc... on a daily basis... but I do not bother using either for relaying my personal email, because ATT-SBC DSL has port-blocking on the standard SMTP port 25, and I did not feel like changing the port number just to defeat the ISP's countermeasure... particularly because I was an extreme newbie (and still am, but less-so, by about a year)... and felt like playing it safe, where the possibility of having my mailservers used as spam relays was concerned. I just ran all my static IP's (I lease 5 from ATT) through SpamCop (I do this every so often) ...and, as always... they all came up clean. -- You are receiving this message as part of your subscription to the "ringzero" mailing list at freelists.org. To unsubscribe, send an e-mail to ringzero-request@xxxxxxxxxxxxx?subject=unsubscribe