Sudden increase in "***UNCHECKED***" in email subjects
Hi all, I have just noticed a big jump in the number of emails going out with "***UNCHECKED***" added to the subject line. Some of these are from users who had their moderation set to "Accept Immediately," but even after I change that to "Default processing" I am still getting those messages. The default action for members is "Default processing" Any ideas what settings I am missing? Thanks, Dave C -- https://bcc2020.github.io/ https://galaxyproject.org/
On 7/18/20 9:30 AM, Dave Clements wrote:
Hi all,
I have just noticed a big jump in the number of emails going out with "***UNCHECKED***" added to the subject line.
This does not come from Mailman. Some milter or other process in your MTA or elsewhere in the delivery chain is adding this to the Subject: -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 7/18/20 7:46 PM, Mark Sapiro wrote:
On 7/18/20 9:30 AM, Dave Clements wrote:
Hi all,
I have just noticed a big jump in the number of emails going out with "***UNCHECKED***" added to the subject line.
This does not come from Mailman. Some milter or other process in your MTA or elsewhere in the delivery chain is adding this to the Subject:
Hi Dave, I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf: # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; # Hope it helps :) Best regards, Peter
Hi Peter and Mark, Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart. Thus our mail really was unchecked. Restarting processes and cleaning up some things has fixed this. Cheers, Dave C On Sun, Jul 19, 2020 at 4:07 PM Peter Adebahr via Mailman-users < mailman-users@mailman3.org> wrote:
On 7/18/20 7:46 PM, Mark Sapiro wrote:
On 7/18/20 9:30 AM, Dave Clements wrote:
Hi all,
I have just noticed a big jump in the number of emails going out with "***UNCHECKED***" added to the subject line.
This does not come from Mailman. Some milter or other process in your MTA or elsewhere in the delivery chain is adding this to the Subject:
Hi Dave,
I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf:
# $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; #
Hope it helps :)
Best regards, Peter
_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On Jul 19, 2020, at 5:11 PM, Dave Clements <clements@galaxyproject.org> wrote:
Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart.
My fresh new mailman3 install (3.3.1, Django 2.x, nginx, Postgres, memcashd, etc) is very clearly leaking memory and has eaten all the swap I set up as a safety net. Maybe yours is, too?
I am in the process of gathering data and will start a separate thread when I have enough to present.
- Mark
mark@pdc-racing.net | 408-348-2878
On Mon, Jul 20, 2020 at 12:43 PM Mark Dadgar <mark@pdc-racing.net> wrote:
On Jul 19, 2020, at 5:11 PM, Dave Clements <clements@galaxyproject.org> wrote:
Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart.
My fresh new mailman3 install (3.3.1, Django 2.x, nginx, Postgres, memcashd, etc) is very clearly leaking memory and has eaten all the swap I set up as a safety net. Maybe yours is, too?
It seems that after running for a few months without restart, Django (which we run two instances of, for two domains on the same Mailman server) was consuming quite a bit more memory than it does on startup.
We were also out of space on the filesystem where ClamAV stores its database, causing corruption, so both issues had to be fixed before ClamAV could start.
Thanks, --nate
I am in the process of gathering data and will start a separate thread when I have enough to present.
- Mark
mark@pdc-racing.net | 408-348-2878
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 7/20/20 12:43 PM, Mark Dadgar wrote:
My fresh new mailman3 install (3.3.1, Django 2.x, nginx, Postgres, memcashd, etc) is very clearly leaking memory and has eaten all the swap I set up as a safety net. Maybe yours is, too?
I am in the process of gathering data and will start a separate thread when I have enough to present.
The only time I saw memory issues with Mailman 3 was with indexing bots hammering the server. Have you checked the web server log for any bot activity?
-- Please let me know if you need further assistance.
Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com
-- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase
EMWD's Community Forums http://discourse.emwd.com/
On Jul 20, 2020, at 10:37 AM, Brian Carpenter <brian_carpenter@emwd.com> wrote:
On 7/20/20 12:43 PM, Mark Dadgar wrote:
My fresh new mailman3 install (3.3.1, Django 2.x, nginx, Postgres, memcashd, etc) is very clearly leaking memory and has eaten all the swap I set up as a safety net. Maybe yours is, too?
I am in the process of gathering data and will start a separate thread when I have enough to present.
The only time I saw memory issues with Mailman 3 was with indexing bots hammering the server. Have you checked the web server log for any bot activity?
Great point - I will check. All my archives are private, though, so there shouldn’t be much for them to index.
- Mark
mark@pdc-racing.net | 408-348-2878
participants (6)
-
Brian Carpenter -
Dave Clements -
Mark Dadgar -
Mark Sapiro -
Nate Coraor -
Peter Adebahr