mailcow/data/conf
dofl d5eeb3e8af
Update main.cf
I was looking into creating a backup mx server for a high availability mailcow setup. It seems that this is not easily done. While researching to find out how long an average SMTP server keeps trying to send to a server that is down I found that RFC 5321 advises at least 4 to 5 days. Mailcow has a custom setup of 1 day, which is very short. The user will be unaware for 5 days that his mail has not been delivered, which can be negative. But I still would like to follow the advice of the RFC.

RFC 5321, in section 4.5.4.1, has this to say:
Retries continue until the message is transmitted or the sender  up;  the give-up time generally needs to be at least 4-5 days.  It MAY be appropriate to set a shorter maximum number of retries for non-delivery notifications and equivalent error messages than for standard messages. 

Postfix default is also 5 days: http://www.postfix.org/postconf.5.html

https://tools.ietf.org/html/rfc5321#section-4.5.4
2019-06-08 15:10:46 +02:00
..
clamav Update clamd.conf 2019-02-13 09:50:29 +02:00
dovecot [Dovecot] Rename sieve_after to global_sieve_after and create a global_sieve_before file 2019-06-01 13:53:24 +02:00
mysql [MySQL] Remove deprecated values for future use of MariaDB 10.3 2018-12-10 13:23:02 +01:00
nginx I'm an idiot 2019-04-01 22:52:45 +02:00
phpfpm add random masterpass for sogo admin login 2019-02-26 09:02:35 +01:00
postfix Update main.cf 2019-06-08 15:10:46 +02:00
rspamd [Rspamd] Remove authenticated user from auth results header 2019-05-29 18:02:14 +02:00
sogo add random masterpass for sogo admin login 2019-02-26 09:02:35 +01:00
unbound [Unbound] Reduce negative max ttl to 60s and min-ttl for all other keys to 5 2018-10-16 20:14:14 +02:00