A secondary MX should queue the messages to be delivered to the primary MX for at least 24 hours but not more than 48 hours, in general terms.
This also is true for any message your server handles. You should configure the SMTP and Queue Manager so that the "retry" time follows those guidelines. I believe there is a RFC that talks about this. John Tolmachoff Engineer/Consultant/Owner eServices For You > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:IMail_Forum- > [EMAIL PROTECTED] On Behalf Of Patrick Burm > Sent: Tuesday, September 07, 2004 12:46 PM > To: [EMAIL PROTECTED] > 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/ 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/
