> You're right, I missed the "james-is-your-agent" model; instead, I was
> thinking of the JavaMail model where I get a status code upon each send.
You may have also missed the fact that messages inserted into the spool go
through the pipeline, and can still be processed by other mailets.
If your mailet needs to be a delivery agent, you can always replicate
everything done for you by RemoteDelivery. You'd spawn your own threads so
that you're not consuming those available for spool processing, do your own
retry queue, etc.
> I was hoping for some sort of direct notification mechanism
> (Observer pattern?) where my code can know the status of each
> outbound piece of email.
For each SMTP transaction? For each recipient?
Once we have mail attributes in place, in theory we could implement some
sort of callback with RemoteDelivery where one could attach a serializable
event listener object to a mail object. Alternatively, we could add an
event model to the Mailet API, and not be message specific. Come up with
reasonable use-cases.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
