Noel J. Bergman wrote:

Maxime,

James will place the e-mail ONCE and ONLY once into the spool from SMTP
handler.  At any given point after that, it will be somewhere in the spool
until it goes into a delivery mailet.  So there is a tiny window between
James spooling the message, and telling the sender that all is well.

There is no means to guarantee that a mid-processor mailet will receive the
message only once.  If james is stopped during processing, when it starts
again, messages will start at the top of the same processor they were last
recorded as having been in.  However, none of that means that they are
duplicated.

From what I understand, the spool is like a producer/consumer queue, from which the JamesSmtp server
enqueues mails, and mailet threads asynchronously dequeue mails for processing. The enqueue and dequeue operations
both have a small window where duplication can occur.

Is this accurate ?

Because if mymailet does a 'put in database', the end result will be a duplicate...



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

Reply via email to