Thanks. This seems to be the case.
Charles Yeomans
On Jul 29, 2008, at 6:34 PM, Navdeep Bains wrote:
Hello,
A single bad RCPT TO command shouldn't cancel the entire transaction
unless the server is disconnecting you on the spot. I'm pretty sure
this is just a case of the SMTPSocket not providing the necessary
hooks for catching the error message to RCPT TO and allowing you to
correct the error. Here's a telnet session:
iMac:~ navdeepbains$ telnet smtp.comcast.net 25
Trying 76.96.30.117...
Connected to smtp.g.comcast.net.
Escape character is '^]'.
220 OMTA06.emeryville.ca.mail.comcast.net comcast ESMTP server ready
EHLO me
250-OMTA06.emeryville.ca.mail.comcast.net hello [98.208.80.56],
pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN CRAM-MD5
250-SIZE 15728640
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
MAIL FROM: <info@bainsware.com>
250 2.1.0 <info@bainsware.com> sender ok
RCPT TO: <@>
550 5.5.0 <@> domain missing or malformed
RCPT TO: <support@bainsware.com>
250 2.1.5 <support@bainsware.com> recipient ok
DATA
354 enter mail, end with "." on a line by itself
...
Thanks,
Navdeep Bains
Bains Software
On Jul 29, 2008, at 3:00 PM, Charles Yeomans wrote:
I'm surprised that it is not optional in the SMTPSocket though.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|