NobMail
Based on mailcow: dockerized
Repository composition by tracked source files.
Clone
https://nobgit.com/orgs/nobgit/nobmail.git
ssh://[email protected]:2222/orgs/nobgit/nobmail.git
Commit
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
d5eeb3e8
data/conf/postfix/main.cf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)Diff
diff --git a/data/conf/postfix/main.cf b/data/conf/postfix/main.cf
index b0fda8bb..95301c43 100644
--- a/data/conf/postfix/main.cf
+++ b/data/conf/postfix/main.cf
@@ -19,7 +19,7 @@ bounce_queue_lifetime = 1d
broken_sasl_auth_clients = yes
disable_vrfy_command = yes
maximal_backoff_time = 1800s
-maximal_queue_lifetime = 1d
+maximal_queue_lifetime = 5d
message_size_limit = 104857600
milter_default_action = accept
milter_protocol = 6