> we are not running a guaranteed message deliver service within James ...
> there is a window - however small - of either loss or duplicates;
> depending on how the transfer validation was implemented.
I disagree that loss and duplication are two heads of the same coin,
semantically speaking.
> i may be anal about this but SMTP is not a guaranteed delivery mechanism
and
> neither is the internal spool/queue that we are using.
Read the code. Line 321 of JamesSpoolManager.java is the only place in all
of James where a message that has been successfully inserted into the spool
is ever removed from it. That happens only if a mailet sets the status to
GHOST, which happens after the message is successfully transfered to another
store, or a determination is made by a mailet to discard it.
As I have said, once the message goes into the spool it remains in the spool
until it has been successfully stored elsewhere or requested to be
destroyed.
> the window of loss/duplication is very small - but there IS a window.
> we can not pretend that it doesn't exist
A window for duplication, yes. Show me the window for loss. You will have
to posit a defect in the code, not a window, because removal from the spool
does not occur until afterwards.
> In point of fact, if the database is unavailable when the handler
> receives e-mail from the sender, it will return an error to the sender.
> no, this is incorrect as i have pointed out in the dev list.
As has been demonstrated to you, if the database is down, and the JDBC
driver reports the error, a 451 error is returned to the sender. That's
working in James already. What you were told is that there are planned
improvements so that James will reacquire connections within requiring a
restart after a db server crash. That does not amount to a window for data
loss.
I see nothing in your messages to james-dev that adds any additional
information. Are you saying that the JDBC driver you are using reports
success even if there is a failure?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
