Hi folks:
Didn't get any replies to this a week ago, so I thought I'd bring it up
again.
Any thoughts? Thanks!
See below.
_________________________________________
| |
| ED LEE ed_lee @ ncsu.edu |
|_________________________________________|
| |
| Windows Systems Support |
| College of Design |
| NC State University |
|_________________________________________|
Ed Lee wrote:
As a way to try to get us off of the RB-complaints threads from this
weekend, I'd like to re-ask a question here that I asked on the Getting
Started list yesterday. I didn't get much of a response, but maybe some
others on here can help out.
I'm looking for some input on the order of operations here with the
SMTPSocket class.
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.
Thanks!
_______________________________________________
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>
