"mark horrocks" <markhorrocks@yahoo.com> wrote in message
news:47a97d39@newsgroups.borland.com...
> There isn't, I am using exactly your code. The GUI version does not report
> an error, only the ISAPI.
Is there any chance you can run a packet sniffer on either the ISAPI or SMTP
server machine so you can see the actual TCP traffic? The alternative is to
attach a TIdLog... component, such as TIdLogFile or TIdLogEvent, to the
TIdSMTP so you can generate your own log of the traffic.
> The email was DEFINITELY sent! I have tried it successfully over
> 50 times.
The only possible way for an EIdSMTPReplyError to be raised after the server
has fully accepted the email data for delivery is if the server is returing
an error when responding to the QUIT command that Disconnect() issues.
Disconnect() will still shutdown the socket if an exception is raised while
sending a command to the server, but it will not block the exception from
reaching your code afterwards.
> Then I can only assume that somehow the idSMTPResponse thingy
> isn't managing to return to the ISAPI. I have exactly the same code
> in a Win32 GUI and in an ISAPI. The ISAPI never produces
> e.message.
The only way for the EIdSMTPReplyError.Message property to be empty is if
the server sent an empty error message.
Gambit
