Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread Jan-Pieter Cornet
On 2014-4-15 4:50 , Joseph Brennan wrote: > DMARC is actually checking the header From, not just the envelope > $Sender, and Yahoo is telling recipient systems to reject if the > header From has a yahoo.com address and the message was not sent > (directly) by yahoo.com. This breaks mailing lists an

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread Kevin A. McGrail
On 4/15/2014 9:52 AM, David F. Skoll wrote: On Tue, 15 Apr 2014 09:35:19 -0400 "Kevin A. McGrail" wrote: - All the various recipients that acknowledge p=reject reject the mail as forged That's the part I don't understand. Mail from my list will not have a yahoo.com envelope sender. And if I

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread Joseph Brennan
"David F. Skoll" wrote: what basis could third parties possibly have for considering the email to be forged? But this is not about logic! Joseph Brennan Columbia University Information Technology ___ NOTE: If there is a disclaimer or other lega

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread David F. Skoll
On Tue, 15 Apr 2014 09:35:19 -0400 "Kevin A. McGrail" wrote: > - All the various recipients that acknowledge p=reject reject the > mail as forged That's the part I don't understand. Mail from my list will not have a yahoo.com envelope sender. And if I remove the DKIM header, what basis could t

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread Kevin A. McGrail
On 4/14/2014 10:50 PM, Joseph Brennan wrote: DMARC is actually checking the header From, not just the envelope $Sender, Thanks. That's what I was overlooking. The problem I've got at our gateway is that milter gives us the @Recipient as in the RCPT TO, but I need to know what the recipient is

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-15 Thread Kevin A. McGrail
On 4/14/2014 10:06 PM, David F. Skoll wrote: Specifically, here's a test from my Yahoo! account to an autism mailing list. Even though smfi_chgfrom appears to have worked, when the email is parsed by mailman, it does not appear to reflect the changed sender. Any thoughts appreciated... smfi_chgf

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-14 Thread Joseph Brennan
if ($Sender =~ /kevin_mcgrail\@yahoo\.com>?$/i and ($recip =~ m/\@mailman\./i or DMARC is actually checking the header From, not just the envelope $Sender, and Yahoo is telling recipient systems to reject if the header From has a yahoo.com address and the message was not se

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-14 Thread David F. Skoll
On Mon, 14 Apr 2014 16:27:58 -0400 "Kevin A. McGrail" wrote: > However, we are seeing an issue with the change_sender(); function. > Specifically, here's a test from my Yahoo! account to an autism > mailing list. Even though smfi_chgfrom appears to have worked, when > the email is parsed by mail

Re: [Mimedefang] Yahoo! DMARC and smfi_chngfrom was Yahoo DMARC

2014-04-14 Thread Kevin A. McGrail
On 4/14/2014 12:50 PM, Joe Quinn wrote: We are having issues with Yahoo's DMARC policy unsubscribing a very large number of members for Mailman lists we host. Does anyone have a quick piece of code that we can use which bounces their message and inserts a nice description of why? We are alrea

[Mimedefang] Yahoo DMARC

2014-04-14 Thread Joe Quinn
We are having issues with Yahoo's DMARC policy unsubscribing a very large number of members for Mailman lists we host. Does anyone have a quick piece of code that we can use which bounces their message and inserts a nice description of why? We are already matching on Yahoo senders to /mailman.