On Feb 18, 2006, at 1:57 PM, Ed Lee wrote:
As usual, I come bearing questions. Today's topic is the
SMTPSocket class. In particular, I'm wondering a bit about it's
order of operations.
Set-up:
Let's say I've populated the message queue with... 5 messages. The
second message is intended for a user who's mailbox has gone over
quota, and cannot receive additional messages. The SMTP server
will give an immediate rejection error to the SMTPSocket.
So, here's what I'm wondering:
1. If I do not trap the ServerError event, does the app choke and die?
2. If I do trap the ServerError event, does the SMTPSocket continue
to process and send messages in the mail queue? I see from the
Language Reference that when the ServerError event occurs, the e-
mail is removed from the queue.
Now I just started using the SMTP sockets so there are plenty of gaps
in my knowledge...
I believe that the ServerError event is only for errors with the
user's SMTP Server. An over-quota error is an error on the receiving
SMTP server (rarely the server you are connecting to). I have only
seen reporting for errors such as these (unknown users, fatal error,
etc) after you get a bounce-back message from the receiving SMTP server.
I think that the ServerError event is mostly used for failures such
as your SMTP server requires authentication (user/pass) and the
values the app passed (or didn't) were invalid. That is the only
error I can think of.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
