>> The result is EIdSMTPReplyError.
>
> That means an error is being reported by the SMTP server. There should be
> a
> value in the E.Message property.
There isn't, I am using exactly your code. The GUI version does not report
an error, only the ISAPI.
>
>> The email was sent.
>
> If you are getting an EIdSMTPReplyError exception then the email can't be
> getting sent.
The email was DEFINITELY sent! I have tried it successfully over 50 times.
The email body is quite long. It reports a team standings ladder and the
games/results for a league for the entire season. The emails are perfect.
> Every command that TIdSMTP.Send() and TIdSMTP.Disconnect()
> send internally must succeed without any error. You are getting an error,
> though, so one of the commands failed. If even one command fails, then
> there is no way the server could have a complete email message to send.
>
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. If I don't provide a response
at the end of the code, it will mostly return an INTERNAL APPLICATION ERROR
without any additional message and sometimes produces Error decoding URL
style (%XX) encoded string at position xxxxx. I can't get it to return
e.message.
I am definitely using exactly the code you wrote which always returns the
internal application error but unless the Error decoding message is included
it will always send the email. Sometimes the email is delayed for several
minutes. It is coming from a thrid party email service.
This service appears not to require a user name and password to send and so
I don't assign them to the SMTP object. I don't use the service to read
email (POP). Emails are forwarded to other email accounts.
Mark Horrocks
