Maybe I missed that but it seemed to me that once it hit the /var/mail/errors directory it was just dead... I didn't see any re-delivery attempts for those messages. Do I have something configured incorrectly?
Is there some way to force-redeliver the messages in that folder? On Mon, May 4, 2015 at 10:42 AM, Vincent Pang <[email protected]> wrote: > James has built-in re-delivery feature already. It is easy to make another > manual re-delivery feature at mailet layer too. Currently built-in > re-delivery is automatically and configurable. > > Vincent > > On Mon, May 4, 2015 at 10:35 AM, Drew Morris <[email protected]> wrote: > > > Hi all...I had a small incident where my shared file server was > unavailable > > for a short time and messages stacked up in the /var/mail/error directory > > during that time. Can anyone provide any guidance on how to re-queue > these > > messages? > > > > I would ideally like to find a way to do this manually for a sys admin as > > well as an interface to do it programmatically in the future so I can > write > > a process to re-try messages after a specific amount of time. Does anyone > > have any recommendations? > > > > I personally would love to see an option in JAMES to handle these errors > > differently using an exponential back-off in re-delivery so it can retry > > the delivery a bunch of times over a day or 2 before being relegated to > the > > /var/mail/error folder. > > > -- Drew Morris hi
