Hi all of you. Thanks for the input. 90 days are just an example. But I agree with you, My backup MX is more reliable than my primary MX. The is a test home setup running on an xDSL - line, and the last month, this xDSL has been running insanely unstable.
Even though it is a test mail, I do receive important mails on it from time to time, and I am able to view these mails on the backup mx by issuing: smtpctl show queue smtpctl show message <number> Yes, I agree... stupid. But it gets me where I wan. But.... the backup MX actually does send out notifications. It sends "could not delivers mails within 4 hours. trying for x days". I actually thought that a backup MX would just keep it and process it silently. How to change what is says - and change the interval it sends the notifications? Regards, Lars. On Sun, Nov 25, 2018 at 3:49 PM Gilles Chehade <gil...@poolp.org> wrote: > On Wed, Nov 14, 2018 at 10:41:44AM +0100, Lars Bonnesen wrote: > > I managed to figure it out. Seems quite simple. What does the trick is: > > > > action "disney" relay backup mx mxbackup.donald.duck > > > match from any for domain "donald.duck" action "disney" > > > > > > When the primare mx are down, I can see mails being queued up with: > > > > smtpctl show queue > > > > and mail shows up ending with: > > > > |pending|417|Network error on destination MXs > > > > > > For how long will they stay in the queue by default and how do I change > > this to say... 90 days? > > > > from man page smtpd.conf(5): > > queue ttl delay > Set the default expiration time for temporarily > undeliverable messages, given as a positive > decimal integer followed by a unit s, m, h, or d. > The default is four days (4d). > > > what you want is: > > queue ttl 90d > > > note that this is not really a very good idea ... > > it assumes your primary MX can be down for up to 90 days, whereas your > secondary MX is going to be up for that long, in which case you might > want to reconsider and swap both ;-) > > the value should be long enough so mail is not lost while your primary > MX is down, but it should still be the lowest possible because senders > will not know you didn't actually receive the mail since one of your > servers have accepted it. > > clearly if you have a secondary MX that keeps your mail for longer > than 4 days, which is already quite long, it means that you have more > trust in the reliability of your secondary MX than your primary MX and > this essentially means your setup is wrong. > > if you still want to do that, you should consider also looking at the > bounce warn-interval option so at the very least your senders know > that you didn't receive the mail for real yet. > > Cheers, > > -- > Gilles Chehade @poolpOrg > > https://www.poolp.org tip me: https://paypal.me/poolpOrg >
