Remy Lebeau,
Thanks for wrestling through the log-files and trying to figure out
what was going on.
>"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.
The scenario that works:
I run the SMTP server on a computer (10.0.0.204) in my LAN. In the
mail client (10.0.0.203) I set the SMTP server to 10.0.0.204 and I
send mail. Thiis is the log file:
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 220 Welcome to SMTP
Server<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: EHLO kees3.inter.nl.net<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 250-Hello
kees3.inter.nl.net<EOL>250-AUTH
LOGIN<EOL>250-ENHANCEDSTATUSCODES<EOL>250 PIPELINING<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: AUTH LOGIN<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 334 VXNlcm5hbWU6<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18:
cG9wNS5pbnRlci5ubC5uZXQvMTEwL2tibGVpamVu<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 334 UGFzc3dvcmQ6<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: VihAKmQzI0U=<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 535 5.7.0 Authentication
Failed<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: RSET<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 250 Ok<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: MAIL
FROM:<k.bleijenberg@inter.nl.net><EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 250 2.1.0
k.bleijenberg@inter.nl.net Address Okay<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: RCPT
TO:<info@bleijenberg.homeip.net><EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 250 2.1.5
info@bleijenberg.homeip.net Address Okay<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: DATA<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 354 Start mail input; end with
<CRLF>.<CRLF><EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: Message-Id:
<6.2.3.4.0.20060602102633.01ee7c40@127.0.0.1><EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: X-Mailer: QUALCOMM Windows
Eudora Version 6.2.3.4<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: Date: Fri, 02 Jun 2006
10:26:36 +0200<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: To:
info@bleijenberg.homeip.net<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: From: Kees Bleijenberg
<k.bleijenberg@inter.nl.net><EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: Subject: test3<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: Mime-Version: 1.0<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: Content-Type: text/plain;
charset="us-ascii"; format=flowed<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: <EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: test3<EOL><EOL>.<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 250 Ok<EOL>
10.0.0.203:1700 Recv 2-6-2006 10:28:18: QUIT<EOL>
10.0.0.203:1700 Sent 2-6-2006 10:28:18: 221 Signing Off<EOL>
The scenario that doesn't work.
I run the smtp-server again on 10.0.0.204. I've set NAT (port 25) to
this PC. Now I send mail from 10.0.0.203 to smtp5.inter.nl.net (the
SMTP-server of my ISP ). A minute later "altrade.nijmegen.internl.net"
connects to my SMTP server at 10.0.0.204. But after sending the line:
217.149.192.18:55772 Sent 2-6-2006 10:53:30: 354 Start mail input; end
with <CRLF>.<CRLF><EOL>
nothing happens.
>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.
I will investigate this PIPELINING.
Is there an easy way to reject all extended SMTP? Answering the EHLO
with 502 should do it?
I'm trying to receive (not relay or send) mail from
"altrade.nijmegen.internl.net". Does this mean there is still a spam
check?
Greetings and thanks
Kees
