JWM wrote:
If my proposal above for my own code sounds reasonable, then so be it.  I
have no problem writing it.  I just want to know if that is my only/best
solution for guaranteeing 100% that never more than 1 copy of the email is
sent.  (I'll accept 0 or 1 copy being sent.  The sender can resend if
necessary).

This is not how SMTP works: SMTP grant the messages will be sent at least once.

There's no way to be sure you send a message a single time in SMTP: the most common "hole" is in the time between the receiving server say it has accepted the message and the client acknowledge this fact. If anything happens in that moment the message is resent (by specification).

Apart RFC consideratons you should write your own code to protect from this behaviour. Your solution seems acceptable given your specifications.

BTW I didn't understand your exact scenario: I've had sql problems in past but I never had James looping with thousands of duplicated messages sent.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to