The above description mentions "queueing if needed", so it is not clear to me that you can know the mail has actually left the jurisdiction of James or not. In the event that it is asychronous (outgoing mail queues up, not really "leaving yet" because unreachable hosts, etc.), then your original bulk mailet cannot afford to stick around waiting for the "accounting" to be done by your modified/extended LocalDelivery and RemoteDelivery mailets. It could literally take days for some remote deliveries to finally go out if the destination host is unreachable.
You have to go read the source. It's not that complicated, and this is a non-standard feature. You can hack it if you wish and make a SeibRemoteDelivery and SeibLocalDelivery, or you could refactor the main ones and send patches to us with that refactoring and have your extend it, or whatever you want.
-- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
