or this .......
20011004 080810 127.0.0.1 SMTP (952) Trying trimble.com (0) 20011004 080810 127.0.0.1 SMTP (952) Connect trimble.com [206.40.88.20:25] (1) 20011004 080823 127.0.0.1 SMTP (952) 220 authorized ESMTP access only 20011004 080823 127.0.0.1 SMTP (952) >EHLO mail.oilfielddirectory.com 20011004 080823 127.0.0.1 SMTP (952) 250-mothra.trimble.com Hello [216.126.27.237], pleased to meet you -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andy Schmidt Sent: Thursday, October 04, 2001 7:57 AM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] MISSING_REVERSE_DNS:spam filter problems with ezsignup It is possible, that the @216.126.27.237 is actually coming an invalid SETUP. May be there is a configuration screen or a setup option for whichever mailer he is using (I wish we could see the entire header with the X-Mailer statement) - and someone entered 216.126.27.237 as the "host name" instaed of using "[216.126.127.237]" or instead of specifying the true FQDN of the host. i think your right...it is the ip adress of the imailserver, the FQD is mail.oilfielddirectory.com Neither CDO/NTS or BLAT have any problems that I'm aware off. But they are NOT immune against the very basic data procressing rule of "garbage in - garbage out". -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Thursday, October 04, 2001 08:30 AM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] MISSING_REVERSE_DNS:spam filter problems with ezsignup >I appreciate the reply, but how do i fix it now, ( put a message id header >as you mentioned below) this is a simple "autoresponder" message the person >gets when they fill out a submission form on our site. How would i fix it. You need to update the software that sends the E-mail (blat? CDONTS?). If the latest version doesn't include a Message-ID: header, you may need to put pressure on the developers (even if you whitelist the E-mail at your server, it still may get tagged as spam on the recipient's computer). >Message-Id: <[EMAIL PROTECTED]> <<<<<<<< isn't this a >message id header you talked about ???????? Yes, it is. However, it is not valid -- "216.127.27.237" isn't a valid host name; it should be in the format "...@[216.126.27.237]". Most likely, the machine said "HELO 216.127.27.237" (which is likely illegal, but I don't know for sure), and then did not supply a Message-ID:. IMail then (knowing how important the Message-ID: header is) added one, assuming that the HELO name was a valid host name. IMail certainly gets an "A for effort", but it still wasn't able to fix the mess from the remote machine. -Scott --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
