Yes, I should been more exact in my statement...they are bouncing as undeliverable, but I was referring to queue files. I want them to just hang around until the primary comes back online.
In the meanwhile I adjusted the number of retries to give the primary more time, but I don't really want to wait that long for all the rest of my undeliverables, so I was hoping there was a way to have the secondary MX functionality have a separate setting from the rest of the outgoing mail. On Tue, 7 Sep 2004 16:47:44 -0400, Eric Shanbrom [Ipswitch] <[EMAIL PROTECTED]> wrote: > IN reality is should bounce them back to the sender with an > undeliverable...Are you sure this isn't happening instead? > > Eric S > > > ----- Original Message ----- > From: "Patrick Burm" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, September 07, 2004 3:46 PM > Subject: [IMail Forum] Secondary MX Queue Timing > > > Having unsuccessfully searched the archives for this.... > > > > I have a few domains I am performing simple store and foreward > > secondary MX services for. I incorrectly assumed (actually I thought I > > read it somewhere) that Imail would simply hang on to messages in that > > setup until the primary MX came online, and either an ETRN command, or > > the next queue run would then deliver the messages. > > > > I found out the hard way that it was deleting the messages after the > > number of tries set in the SMTP settings. > > > > Is there any way to change this behavior, or am I perhaps doing > > something wrong? Or do I need to just set my queue timer a number of > > retries that will satisfy my client's needs? > > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
