Re: [Mailman-Users] Munge From was: non-subscribers getting through--email address in "Real Name"

On 07/25/2018 05:24 PM, Richard Damon wrote: >> >> Perhaps the wrapper message would look like today's munged ML messages - >> From: Real Person / Reply-To: Real Person >> - but a list-aware MUA would largely hide that. >> >> Of course there are a million details and getting adoption would be

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

In article <885f93f0-36ec-d74f-7c5f-52b42f2d6...@jordan.maileater.net> you write: >Hmm.  It would take MUA changes to be fully effective, but a possibility >that comes to mind is to have mailing lists leave the original message >absolutely unmodified, but wrap it in a message that comes "from"

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 7/25/18 1:48 PM, Jordan Brown wrote: > Hmm.  It would take MUA changes to be fully effective, but a possibility > that comes to mind is to have mailing lists leave the original message > absolutely unmodified, but wrap it in a message that comes "from" the > mailing list.  That way everything

Re: [Mailman-Users] Mailman Migrate 3.0 (beta) to 3.2

On 07/25/2018 06:55 AM, Ryan McClung wrote: > The mailman 3.0 install is on the same box as 3.2. Is there a quick and > dirty way to flip over? Other than updating your MTA and web server to point at the 3.2 install, you need to ensure that 3.2 accesses the old 3.0 database(s) and after doing

Re: [Mailman-Users] ARC, was non-subscribers getting through--email address in "Real Name"

> As I said a few messages ago, if lists did more stringent tests on > incoming mail, a lot of this complexity could be avoided, I don't understand this. If lists got a pass, every spam would grow RFC 2369 header fields. No? Large mail systems already know where all the mailing lists are.

Re: [Mailman-Users] Argh. Postfix/Mailman compatibility on Gentoo

On 07/25/2018 11:43 AM, Phil Stracchino wrote: > > The easy solution: > > 1. In /etc/postfix/main.cf: > mail_owner= postfix > default_privs = mailman > > 2. Restart Postfix Or sudo chown mailman /path/to/mailman/data/aliases.db which doesn't even require restart/reload

[Mailman-Users] Mailman Migrate 3.0 (beta) to 3.2

The mailman 3.0 install is on the same box as 3.2. Is there a quick and dirty way to flip over? -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 W.

[Mailman-Users] Argh. Postfix/Mailman compatibility on Gentoo

: Command died with status 2: "/usr/lib64/mailman/mail/mailman post caerllewys". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try

Re: [Mailman-Users] Mailman 2.x to 3.1.x Migration

On 07/25/2018 02:54 AM, Andrew Hodgson wrote: > > Thanks for this; I am on the Docker version which is not updated yet. once > it gets updated and I migrate to it, will I be able to re-import those > missing messages by running a complete import again or will this cause more > trouble now?

Re: [Mailman-Users] ARC

On 7/25/2018 2:53 AM, Stephen J. Turnbull wrote: > Note that if I were intuit.com's CISO, I would fight tooth and nail > against the system you suggest, because it implies that I have DKIM > private keys for all those subdomains owned by clients. Every spammer > in the world would be trying to

Re: [Mailman-Users] ARC

On 07/25/2018 03:53 AM, Stephen J. Turnbull wrote: That's not how "on behalf of" worked in practice. What happened in April 2014, was that a home business owner (HBO) would send a pile of completed order notices to intuit.com, and intuit.com would send an invoice to each customer on behalf of

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

Hmm.  It would take MUA changes to be fully effective, but a possibility that comes to mind is to have mailing lists leave the original message absolutely unmodified, but wrap it in a message that comes "from" the mailing list.  That way everything about the message is verifiably true. A

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On Tue, Jul 24, 2018 at 8:20 PM Grant Taylor via Mailman-Users < mailman-users@python.org> wrote: > > > Right, thereby causing a great deal of entirely legitimate mail that > > DMARC cannot describe to go missing, along with a certain amount of spam. > > "legitimate mail that DMARC cannot

Re: [Mailman-Users] ARC, was non-subscribers getting through--email address in "Real Name"

John Levine writes: > As I said a few messages ago, if lists did more stringent tests on > incoming mail, a lot of this complexity could be avoided, I don't understand this. If lists got a pass, every spam would grow RFC 2369 header fields. No? So ISTM the received chain needs to be

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

Grant Taylor via Mailman-Users writes: > On 07/24/2018 03:16 PM, John Levine wrote: > > Turning it on for aol.com, yahoo.com, and other domains with user > > mailboxes, > > So, are you stating that DMARC should NOT be used on domains that > (predominantly) contain end user mailboxes?

Re: [Mailman-Users] Mailman 2.x to 3.1.x Migration

Mark Sapiro wrote: >On 07/24/2018 06:32 AM, Andrew Hodgson wrote: [...] >> - There were older messages in the mbox without message-ids in the archive >> that failed to import. I took the easy way out on this one and didn't >> import them. In an archive with around 120,000 messages it

Re: [Mailman-Users] ARC

Grant Taylor via Mailman-Users writes: > I would think / hope / expect that such services would be from a > different (sub)domain of the client that they are sending email on > behalf of. That's not how "on behalf of" worked in practice. What happened in April 2014, was that a home