-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in selective service #256
Comments
I went on a yak-shaving expedition attempting to expand the testing suite to catch issues like this. Let me look back into it. |
These next few weeks I am going to have very little or no availability. Anyone is welcome to take a look at this and submit a PR. |
Great that this issue has been reported! I struggled to figure out what went wrong after setting It seems reasonable to switch to an alternative service config as suggested in #297 while fixing this bug – it will require some config refactoring anyway. IMHO not having a spam filter and an anti-virus has more pros than cons since it suggests a lightweight start with an option for extra nice features on demand. Otherwise, lots of users end up with a large chunk of their RAM swallowed by the container while they only use it as a simple ‘reverse-proxy’ for their corporate or private mail. |
I have not looked into this issue much as I have still been trying to figure out an acceptable way to remedy #324. I may switch gears in the next week and at least push out a simple fix that will work for the time being. |
I was able to turn off virus and spam checking in amavis while keeping DKIP and it had a dramatic impact on RAM usage: (a peak before the break is an example how much memory each incoming message consumed!) The solution was to create
Now I am not sure that we need to have an option to remove |
That is a pretty big reduction in resources @kachkaev. You bring up a good point regaring keeping I am going to attempt to turn off the virus and spam checking on my personal server as I am moving to a smaller host. Once I get a clean implementation I'll open up a PR. Also, what dashboard / munitioning system are you using @kachkaev? I like the looks of it. |
Grafana probably. |
One important thing to note before anyone else has started to encounter this. I don't know if this is related to turning off spam and virus filtering, but I've recently started to spot these pretty sad warnings in the logs from time to time:
Key message (from gmail):
It turns out that some attempts to forward notifications from github, ebay and other services to gmail via my custom email server fail. I was doing this kind of forwarding for years without using fancy things like DKIM, Letsencrypt, DNS records, etc. and never heard of this issue before. A shallow search reveals that this a side-effect of google's recently updated spam policy. What is interesting is that real spam is either successfully discarded by zen.spamhaus.org on my server or is successfully swallowed by google and placed into the gmail's spam folder. My personal emails (hopefully) go well in both directions. Mail-testing services like http://mail-tester.com/ & http://mxtoolbox.com/ say that my settings a perfect. Neither IP address nor host name appear in any ban lists. Not sure that this is something to be discussed in the thread or even in this repo, but I've still decided to share such a finding as this might save others some time. I'll be happy to join a discussion in another issue thread if this problem does not look to irrelevant to |
Hi @KyleOndy, have you been able to fix the selective service startup? |
I'm gonna work on this one. |
And I think everything should be |
* Removed DISABLE_AMAVIS * Renamed DISABLE_* to ENABLE_* with 0 as default value. (this must be explicit) * Added missing tests for ENABLE_* * Improved readme and docker-compose example Should fix docker-mailserver#256 and docker-mailserver#386
Bug found by @ep0ch2 in #250
@KyleOndy: I'm opening this issue for reminder.
Will you be able to work on it? May I help?
Thank you.
The text was updated successfully, but these errors were encountered: