Greetings again,
So my plan was to refactor RemoteDelivery, and create a "Retry" mailet, from which ToRecipients and ToSender would derive. Of course this doesn't work. Because ToRecipientFolder would retry all the recipients, so some users would get the mail multiple times. My alternate action would be to modify the repository. But I don't know how to bounce. Because I don't have a mailet context. Or I wonder if I can get the mailet context from the config. If anyone has any thoughts, feel free to chime in. Is it possible to bounce a mail without a mailet context? Is it possible to store a mailet context in a DB? -tim On Sun Oct 07 10:50:50 EDT 2012, tim <[email protected]> wrote: > > Hey there, > > I thought I would check if anyone has any input before I go ahead and > implement this: > > I need to write to a respository which is sometimes disconnected. If it is > disconnected at mail-receive time, I need to queue for writing and retry > later. > > > > I plan on implementing this by copying RemoteDelivery, cutting out all of the > socket stuff, and inserting the custom write to repository. > > > > Is there some other way I should attempt which would reuse more and code less? > > > > Thanks, > > > > -tim > >
