> 1) On the sender side (the SMTP source) :
What you describe is what most SMTP servers do already. They send until
they believe that it was received successfully. You receive the 250
response code from James or you continue to send the message.
> 2) On the receiver side (James) :
> if(!alreadyExistsInPersistentStore(mail))
> persist(mail);
There is no GUID for e-mail, so how would you implement that generically?
:-) But in a controlled environment, this is basically what I mentioned
last week.
> The only prerequisite for this is that SMTP provides for some kind of
> acknowledgement of receipt, and that the SMTP source implementation
> uses this ack. to delete the mail from its "to send" list...
There is already an acknowledgement of receipt. The real prerequisite is
that the SMTP sender provide a GUID that can be used by the receiver to deal
with duplicates. Look again at your logic.
If you are doing this in a controlled environment, your custom sender and
your custom mailet can use this approach.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
