Re: [Mailman-Users] Avoiding mangling in Mailman 3?
Allan Hansen writes: > But Apple Mail puts the mangled address To: into the ‘Previous > Recipients’ list to help with auto-completion later. I assume by "To" you mean "From". We don't munge "To" in this situation (there is a personalized list configuration where To is changed from the list to the subscriber, but that shouldn't cause client problems or DMARC issues). I don't see how we can do anything reliable about that. From is a *required* field in RFC 5322 message syntax, and it *must* contain a mailbox (perhaps along with a display name). Some possibilities follow. We could stick a .invalid address in there, which would immediately bounce back to the sender. But that screws those users because the client hides the address and we don't control the delivery service notice in that case, it's the user's outgoing mail gateway that will reject it. Or possibly silently drop it. So there's no guarantee they'll get a message that makes any sense to them. And if they figure out the list is related, you'll take some heat. We could put an "oopsie, did you mean to send to us" address at the Mailman host in there that replies with explanation from Mailman, but when you don't have the list in Reply-To, people who *intend* a reply to list will have to copy/paste by hand (as mentioned earlier a link in the footer will not have the features of a client-composed reply). That might be OK for you, since you seem to really discourage replies to list. Another try would be a Rule that checks for the "via list-at-this- server" formulation and automatically bounces the mail back (regardless of any "don't at me" settings), with an explanation of why the mail bounced and a suggestion to clean up Previous Recipients. You could simulate this with the existing spam hold feature, but I'm not sure that can be set to reject on a per recipe basis, and I don't think it would allow for the explanation to differ across rejections. Of course that will fail if the user changes the display name. What is your experience? Do these users just accept the display name with "via list" attached, or do they tend to fix it while failing to notice the unintended address? It sounds like this might be good enough, possibly combined with a second Rule which looks for the list's display name (and any variants popular with posters) and holds posts that don't contain it for moderation. (Note to me: Possibly the mail's entire content would need to be scrubbed when bouncing but available at the archive as a .bin thingie to avoid certain kinds of bounce spam. And if so, it would need to be removed in say 24 hours since it's almost certainly private. Also maybe a check for In-Reply-To/References could help identify likely private mail?) > I do tell people to clean up their ‘Previous Recipients’ list, they > eventually forget and this happens again. You're a hero! But this sucks for you. The point of an advanced list manager is that you shouldn't have to do this kind of mechanical work. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Resolved Mostly): New to Mailman 2.1.23 - group e-mails arriving as spam...
rabin...@sasktel.net writes: > I would still be interested in seeing and documentation on a known > good list configuration to ensure That doesn't exist. Spam fighters generally believe their users would rather lose mail than receive spam, and act aggressively on that belief. Some sites have worse problems, like leaking over 100 million user address books, and they act even more aggressively. Also, in general it's not the list configuration that triggers spam filters. It's general site reputation and message content. I don't know why your webmail likes Wrapped messages so much. What you can do to protect your site's reputation: 1. Check that your IP address is not in any DNS block lists. If it is, sometimes you can request a new allocation. 2. Spam filter mail incoming to Mailman aggressively. 3. If you have human mail users on the host, or lots of services running, you might want to filter on outgoing mail as well. 4. Use DKIM (and optionally SPF) to authenticate your outgoing messages. 5. (Optionally) participate in DMARC (not terribly useful for a Mailman site usually). 6. Use the ARC protocol to placate some sites (ARC usage is not universal yet, and AFAIK there are as yet no best practices for when to trust ARC-based claims of verified authentication). ARC, like most of these protocols, is best implemented in the MTA. However, Mailman 3 does have an option to implement ARC in Mailman. (This will probably not ever be backported to Mailman 2; for Mailman 2 ARC can only be implemented by your MTA.) I'm not sure what to say about content. My own site has obnoxiously high rates for both false positives and false negatives, and I have not been able to detect a pattern for these errors. :-( Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] New to Mailman 2.1.23 - group e-mails arriving as spam...
Apologies in advance for the noobness, but I've searched the archives and googled this issue, but I'm hoping some experience can maybe see what I'm missing. This is the first Mailman list I've set up, but since I've already gone live I'm struggling to find a solution so I figured I better reach out... Backstory: Migrating a list from yahoogroups to Mailman 2.1.23. List is up and running and tested great with 2-3 people, but found that I had to have it set to Wrap Message or it went into my spam folder. (I assume it's this setting that appends messages as attachments on some mail systems?) Toggling this back to "Munge to" setting sends it to spam. Selecting No sends it to spam folder. But when set to "Wrap message" it does not send it to spam, which leads me to think it's got to be something else in the settings I don't have correct. (Rather than it coming from a blacklisted source?) E-mails from this list are arriving fine as well so I'm hoping to figure out what would be a known good list of general settings, as well as digest and non-digest settings so that I can at least eliminate them. I've been searching for a known good Mailman settings to start off with, but to no avail. If anyone knows of some known good documentation so that I can at least eliminate how I've set the list up I'd be very grateful. My google-fu is usually pretty good, but I've not had any luck so far. Usergroup I'm migrating has just over 1500 members and only some of us were seeing messages as attachments when I had it set to wrap message, but I'm hoping to find that sweet spot so that it works properly for all. Thanks, Rabin http://list.canam-peugeot.com/listinfo.cgi/peugeot-l-canam-peugeot.com -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Resolved Mostly): New to Mailman 2.1.23 - group e-mails arriving as spam...
As per usual I find the issue AFTER I send in the e-mail for help. Turns out my ISP webmail client had a setting that ignored the safe sender list unless the bypass was checked off. So now I can at least get messages and advise others on what to look for to resolve if they run into similar issues. I would still be interested in seeing and documentation on a known good list configuration to ensure there isn't anything that makes e-mails more susceptible to spam filters. I'm still noodling around with set up, but at least my immediate issues appear to be resolved. Thanks, Rabin On Mon, 09 Dec 2019 12:33:53 -0500, rabin...@sasktel.net wrote: >> Apologies in advance for the noobness, but I've searched the archives and >> googled this issue, but I'm hoping some experience can maybe see what I'm >> missing. This is the first Mailman list I've set up, but since I've already >> gone live I'm struggling to find a solution so I figured I better reach >> out... >> >> Backstory: Migrating a list from yahoogroups to Mailman 2.1.23. List is up >> and running and tested great with 2-3 people, but found that I had to have >> it set to Wrap Message or it went into my spam folder. (I assume it's this >> setting that appends messages as attachments on some mail systems?) >> Toggling this back to "Munge to" setting sends it to spam. Selecting No >> sends it to spam folder. But when set to "Wrap message" it does not send it >> to spam, which leads me to think it's got to be something else in the >> settings I don't have correct. (Rather than it coming from a blacklisted >> source?) >> >> E-mails from this list are arriving fine as well so I'm hoping to figure out >> what would be a known good list of general settings, as well as digest and >> non-digest settings so that I can at least eliminate them. >> >> I've been searching for a known good Mailman settings to start off with, but >> to no avail. If anyone knows of some known good documentation so that I >> can at least eliminate how I've set the list up I'd be very grateful. My >> google-fu is usually pretty good, but I've not had any luck so far. >> >> Usergroup I'm migrating has just over 1500 members and only some of us were >> seeing messages as attachments when I had it set to wrap message, but I'm >> hoping to find that sweet spot so that it works properly for all. >> >> Thanks, >> >> Rabin >> http://list.canam-peugeot.com/listinfo.cgi/peugeot-l-canam-peugeot.com -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Apache ScriptAlias and POST
Mark, Thanks very much for your pointer, the addition of a DEFAULT_URL_PATTERN as per the article you linked to solved my problem immediately. Regards, Geoff On Mon, 9 Dec 2019 at 21:25, Geoff Campbell wrote: > > Mark, > > > It is due to redirection losing POST data, but the culprit is not > > ScriptAlias. It is whatever you have in your Apache config that > > redirects http to https. > > Ah, interesting. > > > I don't know why you couldn't find the answer in the archives. > > Well, I think the answer there is that there are many different > answers, all giving multiple paths to a solution, and I got routed off > down the incorrect little rat-hole. > > Thanks for the pointers, I'll work through them in the morning but I > suspect the configuration I want is easily available from them now > that I have your pointers, having had a quick glance through. > > Regards, > Geoff -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
