"Kees" <xxx@yyy> wrote in message
news:uk0882d2bjfhmluk4hp434a81ddgscmfb7@4ax.com...
> Is there an easy way to reject all extended SMTP?
TIdSMTPServer does not natively support that.
> Answering the EHLO with 502 should do it?
You don't have access to do that, unless you change Indy's source code.
I've been considering adding a PipelineEnabled property to TIdSMTPServer,
though. It technically wouldn't effect TIdSMTPServer's behvior at all in
regards to commands, it would just enable/disable the PIPELINING attribute
in the EHLO response.
> I'm trying to receive (not relay or send) mail from
> "altrade.nijmegen.internl.net". Does this mean there
> is still a spam check?
No. Just a problem with the two servers communicating with each other
properly. In theory, the pipelining should not be causing any problem, as
the DATA command would remain in Indy's InputBuffer after the RCPT command
was read, and thus still be available the next time TIdSMTPServer accesses
the socket after sending the RCPT response. In practice, though, I know
that TIdSMTP has problems with pipelining that always resolve themselves
when pipelining is disabled, so perhaps TIdSMTPServer has similar problems
with pipelining as well. That is the only descrepency that I can see in the
logs you have shown that could account for the problem you are seeing. In
your log that shows the working scenerio, each command is being received in
its own TCP packet. In the log that shows the failing scenerio, the RCPT
and DATA commands are arriving in the same TCP packet. Only pipelining can
do that. The only way to know for sure, though, is to trace through
TIdSMTPServer's code in the debugger to find the real cause of the hanging.
Gambit
