Seib, Broc wrote:
Serge Knystautas writes:
Christophe Laumond wrote:Yes, this would be the way to do it. There is currently no hook capability to run code upon successful delivery completion.
Are there any way to verify that the emails has been
sent succesfully so I can create a receipt email like
this? I thougt a bit about modifying the LocalDelivery
and RemoteDelivery mailets and store the state
information there but I am not really sure whether
this is the way to go.
Rather than hack the existing code, would you not extend the
LocalDelivery and RemoteDelivery classes, override the service() method,
call super(), then do your accounting? From the API:
Thanks for the replies.
We did consider subclassing the existing LocalDelivery and RemoteDelivery mailets but could not quite see how to verify if mails have been passed on successfully or not so we ended up modifying the existing mailets. We have a ReceiptManager class which handles the state of all of this and sending of the actual receipt email. It is initialized in the bulk mailet and updated from the LocalDelivery and RemoteDelivery mailet.
This also means we do not have a problem with the actual bulk mailet waiting for all bulk mails to finish due to the asynchronous delivery since the ReceiptManager and not the bulk mailet handles sending of the receipt. It hasn't been tested thoroughly yet but it seem to work ok.
Christophe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
