Unfortunately, this is a crock.  All they are doing is verifying a RCPT to the email 
address.  AOL will accept anything and send
back a failure notification of the email does not exist.  You can try it yourseld with 
telnet or the iMS SMTP test console.  Connect
to the AOL server and send mail to somthing like "[EMAIL PROTECTED]" and you 
will see that it will accept it.  AOL is not
the only ISP that works this way.

There are also other email servers that accept the mail and, if the address is 
invalid, it will forward the mail to the postmaster.
So, in most cases, the mail goes through and you don't get any type of failure back.

Regards,

Howie

----- Original Message -----
From: <[EMAIL PROTECTED] (paul smith)>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Friday, May 31, 2002 2:33 PM
Subject: Re: [iMS] checking valid email


> I had a service "clean" a list the other day.  Here is some of the log they
> sent me.
>
> best,  paul
>
> ================================================================================
>
> ORIGINAL EMAIL: [EMAIL PROTECTED]
>     CLEAR EMAIL: [EMAIL PROTECTED]
>          RESULT: Exist
>         COMMENT: mailin-01.mx.aol.com "250 OK"
>    CHECKING LOG:
>
> Request DNS for SMTP servers for this e-mail...
> Try DNS-server 64.39.2.170
> Sending DNS request...
> Wait for DNS reply...
> Found 4 relay(s) (mailin-01.mx.aol.com [15], mailin-02.mx.aol.com [15],
> mailin-03.mx.aol.com [15], mailin-04.mx.aol.com [15])
> Check via mailin-01.mx.aol.com SMTP-server
> Connecting to SMTP server...
> Connected with SMTP-server
> 220-rly-xg02.mx.aol.com ESMTP mail_relay_in-xg2.10; Wed, 22 May 2002
> 10:21:41 -0400
> 220-America Online (AOL) and its affiliated companies do not
> 220-     authorize the use of its proprietary computers and computer
> 220-     networks to accept, transmit, or distribute unsolicited bulk
> 220      e-mail sent from the internet.
> HELO go.listdeliver.com
> 250 rly-xg02.mx.aol.com OK
> MAIL FROM: <[EMAIL PROTECTED]>
> 250 OK
> RCPT TO: <[EMAIL PROTECTED]>
> 250 OK
> RSET
> 250 OK
> QUIT
> mailin-01.mx.aol.com "250 OK"
>
> ================================================================================
>
> ORIGINAL EMAIL: [EMAIL PROTECTED]
>     CLEAR EMAIL: [EMAIL PROTECTED]
>          RESULT: Exist
>         COMMENT: mx05.mindspring.com "250 <[EMAIL PROTECTED]>...
> Recipient ok"
>    CHECKING LOG:
>
> Request DNS for SMTP servers for this e-mail...
> Try DNS-server 64.39.2.170
> Sending DNS request...
> Wait for DNS reply...
> Found 12 relay(s) (mx05.mindspring.com [5], mx06.mindspring.com [5],
> mx07.mindspring.com [5], mx08.mindspring.com [5], mx09.mindspring.com [5],
> mx10.mindspring.com [5], mx11.mindspring.com [5], mx00.mindspring.com [5],
> mx01.mindspring.com [5], mx02.mindspring.com [5], mx03.mindspring.com [5],
> mx04.mindspring.com [5])
> Check via mx05.mindspring.com SMTP-server
> Connecting to SMTP server...
> Connected with SMTP-server
> 220 niles.mail.mindspring.net EL_3_5_6 /EL_3_5_6  ESMTP Earthlink Mail
> Service Wed, 22 May 2002 10:22:03 -0400 (EDT)
> HELO go.listdeliver.com
> 250 niles.mail.mindspring.net Hello go.listdeliver.com [64.39.30.114],
> please to meet you
> MAIL FROM: <[EMAIL PROTECTED]>
> 250 <[EMAIL PROTECTED]>... Sender ok
> RCPT TO: <[EMAIL PROTECTED]>
> 250 <[EMAIL PROTECTED]>... Recipient ok
> RSET
> 250 reset state
> QUIT
> mx05.mindspring.com "250 <[EMAIL PROTECTED]>... Recipient ok"
>
> ================================================================================
>
> ORIGINAL EMAIL: [EMAIL PROTECTED]
>     CLEAR EMAIL: [EMAIL PROTECTED]
>          RESULT: Exist
>         COMMENT: etrn.napanet.net "250 2.1.5 <[EMAIL PROTECTED]>...
> Recipient ok"
>    CHECKING LOG:
>
> Request DNS for SMTP servers for this e-mail...
> Try DNS-server 64.39.2.170
> Sending DNS request...
> Wait for DNS reply...
> Found 4 relay(s) (etrn.napanet.net [50],
> napanet.net.napanet.mail1.psmtp.com [100], postini-mail.napanet.net [300],
> napanet.net.napanet.mail2.psmtp.com [65480])
> Check via etrn.napanet.net SMTP-server
> Connecting to SMTP server...
> Connected with SMTP-server
> 220 etrn.napanet.net ESMTP Sendmail 8.11.6/8.11.2; Wed, 22 May 2002
> 07:22:09 -0700 (PDT)
> HELO go.listdeliver.com
> 250 etrn.napanet.net Hello go.listdeliver.com [64.39.30.114], pleased to
> meet you
> MAIL FROM: <[EMAIL PROTECTED]>
> 250 2.1.0 <[EMAIL PROTECTED]>... Sender ok
> RCPT TO: <[EMAIL PROTECTED]>
> 250 2.1.5 <[EMAIL PROTECTED]>... Recipient ok
> RSET
> 250 2.0.0 Reset state
> QUIT
> etrn.napanet.net "250 2.1.5 <[EMAIL PROTECTED]>... Recipient ok"
>
> ================================================================================
>
> ORIGINAL EMAIL: [EMAIL PROTECTED]
>     CLEAR EMAIL: [EMAIL PROTECTED]
>          RESULT: Unknown
>         COMMENT: mail.smn.com "554 rewrite: excessive recursion (max 50),
> ruleset 3"
>    CHECKING LOG:
>
> Request DNS for SMTP servers for this e-mail...
> Try DNS-server 64.39.2.170
> Sending DNS request...
> Wait for DNS reply...
> Found 1 relay(s) (mail.smn.com [10])
> Check via mail.smn.com SMTP-server
> Connecting to SMTP server...
> Connected with SMTP-server
> 220 jean-grey.pixi.com ESMTP Sendmail 8.9.3/8.9.3; Wed, 22 May 2002
> 03:48:30 -1000
> HELO go.listdeliver.com
> 250 jean-grey.pixi.com Hello go.listdeliver.com [64.39.30.114], pleased to
> meet you
> MAIL FROM: <[EMAIL PROTECTED]>
> 250 <[EMAIL PROTECTED]>... Sender ok
> RCPT TO: <[EMAIL PROTECTED]>
> 554 rewrite: excessive recursion (max 50), ruleset 3
> RSET
> 250 Reset state
> QUIT
> mail.smn.com "554 rewrite: excessive recursion (max 50), ruleset 3"
>


==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to