Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail
Hi,
we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post:
The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen.
I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look?
Best regards Torge
I don't *think* we have a checkbox for this, but I've definitely seen this behaviour in Mailman 2 and had trouble with Mailman getting blocked as a result, so I think this would be a very nice feature request.
Terri
On January 16, 2020 10:49:38 a.m. PST, Torge Riedel torgeriedel@gmx.de wrote:
Hi,
we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post:
The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen.
I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look?
Best regards Torge
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/
Am 16.01.20 um 20:22 schrieb Terri Oda:
but I've definitely seen this behaviour in Mailman 2 and had trouble with Mailman getting blocked as a result, so I think this would be a very nice feature request.
Hi Terri,
I agree. So how to proceed on that? Get developers involved, post somewhere a feature request? To be honest I don't know how this is handled in development community of mailman3.
Best regards Torge
On 1/18/20 7:11 AM, Torge Riedel wrote:
I agree. So how to proceed on that? Get developers involved, post somewhere a feature request? To be honest I don't know how this is handled in development community of mailman3.
You can post to mailman-developers@python.org, but such things tend to get put aside and forgotten.
The best way to report a bug, feature request, issue, etc is to use the trackers at gitlab.com. In the case of Mailman core, this is https://gitlab.com/mailman/mailman/issues
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Am 18.01.20 um 19:45 schrieb Mark Sapiro:
The best way to report a bug, feature request, issue, etc is to use the trackers at gitlab.com. In the case of Mailman core, this is https://gitlab.com/mailman/mailman/issues
Hi Mark,
just opened a new issue: https://gitlab.com/mailman/mailman/issues/670
Best regards Torge
participants (3)
-
Mark Sapiro -
Terri Oda -
Torge Riedel