I think it causes more trouble then benefit if it delays a mail for not less then 5 days _without_ notifying the sender after 24 hours, saying that "I am James, your email is delayed, but I am still trying to deliver".
----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003 5:34 PM Subject: RE: [PATCH] RemoteDelivery multiple delay times > If no one else gets to this sooner, I should have some time to review it on > the weekend. One minor thing that I'm not spotting, which I can add when I > integrate it, is a change to james-config.xml to use this in new > deployments. > > My proposed default configuration is: > > <delayTime> 5 minutes </delayTime> > <delayTime> 10 minutes </delayTime> > <delayTime> 45 minutes </delayTime> > <delayTime> 2 hours </delayTime> > <delayTime> 3 hours </delayTime> > <delayTime> 6 hours </delayTime> > > <maxRetries> 25 </maxRetries> > > As I mentioned once before, that provides a 5 day retry period, with 4 > attempts in the first hour, two more within the first 6 hours, and then > every 6 hours for the rest of the period. > > Any comments, alternatives, etc.? > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
