b05bfbf523
[Compose] New Dovecot and ACME images
2019-06-25 18:48:38 +02:00
71c6c59f1c
[Dovecot] Fix cleanup of old quarantine items, fixes #2721
2019-06-22 23:12:23 +02:00
f2d1a56104
[Rspamd] Increase OLEFY_MACRO score
2019-06-20 10:18:43 +02:00
f35bc07a30
[Web] Generate readable passwords
2019-06-20 10:18:09 +02:00
39f95b8284
[Compose] Add olefy container, new Postfix iamge and new ClamAV image
2019-06-16 17:37:25 +02:00
aea957e949
[Olefy] New container and image
2019-06-16 17:36:32 +02:00
04940429ba
[Rspamd] Add oletools via olefy, big thanks to @c-rosenberg
2019-06-16 17:35:58 +02:00
6f99f06c6d
[Rspamd] Add OLEFY_MACRO symbol
2019-06-16 17:35:24 +02:00
9c347e36fc
[Rspamd] Less aggressive bayes
2019-06-16 17:34:58 +02:00
c7a85fc520
[Web] Fix BCC error message
2019-06-16 16:00:41 +02:00
59798357f7
[Web] Fix SPF link
2019-06-16 16:00:14 +02:00
247d3928f0
Merge pull request #2711 from MaxXor/master
...
Add missing WATCHDOG_NOTIFY_BAN update option
2019-06-15 22:51:45 +02:00
831a96551d
Add missing WATCHDOG_NOTIFY_BAN update option
2019-06-15 21:55:23 +02:00
090e14ee8d
[Netfilter] Keep musl-dev, update pip
2019-06-13 21:10:49 +02:00
8984240e44
[Watchdog, Config] Added WATCHDOG_NOTIFY_BAN to disable IP ban notifications
...
[Netfilter] Remove unused files after installation
[Compose] Some new images and a new option for watchdog: WATCHDOG_NOTIFY_BAN - defaults to y
2019-06-13 19:38:53 +02:00
e43951331c
[Rspamd] Sign ARC inbonud, thanks to @Kraeutergarten
2019-06-11 11:41:59 +02:00
59e4212702
[Update] Check if file is tracked before running git rm
2019-06-10 22:44:10 +02:00
7145c380b0
[Watchdog] Minor text changes and send whois report of banned IP
2019-06-10 22:40:21 +02:00
7bc2b6b35b
[Compose] Update watchdog
2019-06-10 22:39:58 +02:00
7f6acdb791
[Watchdog] Fix for fix for wrong mails
2019-06-10 21:53:44 +02:00
84307e85f2
[Update] Hide error when running git rm on old worker passwd file
2019-06-10 21:44:22 +02:00
eb69162095
[Compose] Update watchdog
2019-06-10 20:20:49 +02:00
0d7681d0a5
[Watchdog] Fix broken mail with more than one rcpt in some cases
2019-06-10 20:20:41 +02:00
9c5eda13aa
[Update] Remove controller passwd file from index
2019-06-10 18:37:19 +02:00
f48c56d48d
[Compose] Update PHP-FPM
2019-06-10 13:40:02 +02:00
c257724cd0
[PHP-FPM] Add exif module
2019-06-10 13:39:53 +02:00
4ae5e0e43b
[Compose] Update watchdog
2019-06-10 10:57:52 +02:00
dcd0bfc13e
[Watchdog] Send mail when IP was banned
2019-06-10 10:57:38 +02:00
ffb008f72a
Merge branch 'master' of https://github.com/mailcow/mailcow-dockerized
2019-06-09 16:50:04 +02:00
5795988cfd
[Compose] New images: Postfix, PHP, Rspamd
2019-06-09 16:50:00 +02:00
e25e9c7b40
[Postfix] Create resource maps
2019-06-09 16:49:38 +02:00
5ce6688c78
[Web] Show resource alias
2019-06-09 16:49:17 +02:00
de3a89ac7a
[Postfix] Remove duplicate proxy read maps, add resource maps
2019-06-09 16:49:02 +02:00
4999842f41
Merge pull request #2694 from DevTek314/master
...
Increase db version for merge #2594
2019-06-09 12:15:16 +02:00
1634a486fc
[web] increased db version
2019-06-09 12:08:23 +02:00
9325bb6f4e
Merge pull request #2594 from FELDSAM-INC/domain-default-mailbox-quota
...
Default quota for mailbox
2019-06-09 10:49:43 +02:00
73b9b8cf45
Merge pull request #2693 from dofl/patch-1
...
[Postfix] Retry for 5 days instead of 1
2019-06-09 10:47:33 +02:00
fa4c4b138e
Update main.cf
...
Added the delay_warning_time (http://www.postfix.org/postconf.5.html#delay_warning_time ) with 4 hours as setting. Postfix will inform the user that the e-mail has not been delivered, but that it will try for the next 5 days.
There is also a setting called confirm_delay_cleared (http://www.postfix.org/postconf.5.html#confirm_delay_cleared ), but according to the Postfix this can lead to a sudden burst of notifications at the end of a prolonged network outage.
2019-06-09 07:39:36 +02:00
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
53bda04848
[PHP-FPM] Update PHP and some modules
2019-06-05 06:56:58 +02:00
797e97d619
Merge pull request #2670 from MAGICCC/master
...
[update.sh] Rename enable_ipv6 option
2019-06-02 21:21:14 +02:00
f586b0e5a9
[update.sh] Rename enable_ipv6 option
2019-06-02 20:56:08 +02:00
af46a93e76
[Postfix] Remove authed user from header
2019-06-01 22:14:48 +02:00
de03e4178a
[Dovecot] Run cronjob at 4:15 AM to remove max aged quarantine items (default: 365 days)
2019-06-01 21:23:43 +02:00
d9361a6263
[PHP-FPM] Add Q_MAX_AGE key and set to 365 days if missing
2019-06-01 21:22:58 +02:00
9328ea54f4
[Compose Update PHP and Dovecot images
2019-06-01 21:22:29 +02:00
176f2a3f34
[Web] Allow to set max_age for quarantine items
2019-06-01 21:22:14 +02:00
5f8dd69a2d
[Web] Fix lang strings for sieve pathes and sieve flow
2019-06-01 14:10:01 +02:00
dcacf85a5d
[Dovecot] Rename sieve_after to global_sieve_after and create a global_sieve_before file
2019-06-01 13:53:24 +02:00
aaf0d521a2
[Postfix] Add UA header check, not enabled by default
2019-06-01 08:29:53 +02:00
andryyy
MaxXor
Aiko Appeldorn
Timo N
dofl
dofl
MAGIC