"Kees" <xxx@yyy> wrote in message
news:0hv2821au9q74m96kinp3ss0rlbtnu8u4t@4ax.com...
> But when I send my mail to my normal (remote) smtp-server.
> The mail is not delivered. Email returned:
Where exactly are you sending the message from? From your client
application, or from your TIdSMTPServer app? Where exactly are you sending
the message to? Most IPSs won't allow users to run their own SMTP servers
locally, let alone allow those local servers to relay messages through the
ISP's own SMTP servers. Too many spammers do that, so the ISP's strictly
control who can connect to whom.
217.149.192.18:41610 Recv 3-6-2006 12:31:49: RCPT
To:<info@bleijenberg.homeip.net><EOL>DATA<EOL>
217.149.192.18:41610 Sent 3-6-2006 12:31:49: 250 2.1.5
info@bleijenberg.homeip.net Address Okay<EOL>
217.149.192.18:41610 Sent 3-6-2006 12:31:49: 354 Start mail input; end
with <CRLF>.<CRLF><EOL>
Your are receiving both the RCPT and DATA commands in the same TCP packet.
You are receiving the DATA command before the response to the RCPT command
has been sent. Offhand, I would guess that the client at
"altrade.nijmegen.internl.net" is trying to pipeline the connection, which
is probably throwing off the TIdSMTPServer's handling of the connection.
Siunce you did not show the log for the scenerio that is working for you, I
would guess that the client in that scenerio is not trying to pipeline the
connection. Unfortunately, there is no way to stop the response to the EHLO
command from sending the PIPELINING capability, unless you change
TIdSMTPServer's source code and then recompile Indy.
> -> here is the difference. In the remote SMTP scenario everything
> stops here.
Please elaborate. What EXACTLY is happening. What is the EXACT scenerio,
step-by-step?
Gambit
