Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-28 Thread Stephen J. Turnbull
Mark Sapiro writes: > On 11/24/18 9:17 PM, Jayson Smith wrote: > > I had a Mailman/DNS problem after upgrading a lot of packages. A > > message came in, Mailman couldn't properly look up the DMARC > > policy of the sending ISP, didn't munge the From: and sent the > > message on its way... >

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Grant Taylor via Mailman-Users
On 11/25/18 1:03 PM, Lindsay Haisley (linode) wrote: mail redirected through a .forward will always fail SPF validation. That is not always accurate. It is relatively easy to configure an MTA to support Sender Rewriting Scheme, either for everything that is sent out or just things that

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Lindsay Haisley (linode)
On Nov 25, 2018, at 1:06 PM, Mark Sapiro wrote: > > A .forward normally does not cause issues with DMARC because .forward > redirection normally does not transform the message in ways that break > DKIM signatures. Which assumes that the sending system includes a DKIM signature in the original

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Mark Sapiro
On 11/25/18 11:12 AM, Lindsay Haisley wrote: > > Similarly, if you're using from_is_list in Mailman, > or dmarc_moderation_action, the domain name associated with the list > must have a proper SPF record. These days, publishing SPF and DKIM signing outgoing mail is good practice in general, but

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Lindsay Haisley
On Sun, 2018-11-25 at 11:06 -0800, Mark Sapiro wrote: > A .forward normally does not cause issues with DMARC because .forward > redirection normally does not transform the message in ways that break > DKIM signatures. Thus if the original message was DKIM signed by a > domain "aligned" with the

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Mark Sapiro
On 11/24/18 9:17 PM, Jayson Smith wrote: > > I had > a Mailman/DNS problem after upgrading a lot of packages. A message came > in, Mailman couldn't properly look up the DMARC policy of the sending > ISP, didn't munge the From: and sent the message on its way... What was the lookup issue? I.e.,

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Mark Sapiro
On 11/25/18 10:43 AM, Lindsay Haisley wrote: > > How does a .forward problem relate to Mailman? Please excuse my > ignorance if this is obvious. I use Courier-MTA and the equivalent > facility is the .courier file, which redirects email. In the case of > Mailman mailing lists, I use the

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-25 Thread Lindsay Haisley
On Sun, 2018-11-25 at 00:17 -0500, Jayson Smith wrote: > I've been using .forward to forward Email from some user mailboxes to  > other addresses. Normally this works just fine, but a few weeks ago a  > situation happened which demonstrates how it can be an epic fail. I had  > a Mailman/DNS

Re: [Mailman-Users] OT - Smart .forward replacement?

2018-11-24 Thread Grant Taylor via Mailman-Users
On 11/24/18 10:17 PM, Jayson Smith wrote: Hi, Hi, I've been using .forward to forward Email from some user mailboxes to other addresses. Normally this works just fine, but a few weeks ago a situation happened which demonstrates how it can be an epic fail. I had a Mailman/DNS problem after

[Mailman-Users] OT - Smart .forward replacement?

2018-11-24 Thread Jayson Smith
Hi, I've been using .forward to forward Email from some user mailboxes to other addresses. Normally this works just fine, but a few weeks ago a situation happened which demonstrates how it can be an epic fail. I had a Mailman/DNS problem after upgrading a lot of packages. A message came in,