Re: [mailop] DKIM + mailinglists (rehash)

2016-06-16 Thread John Levine
>If Mailman (and other MLMs) would provide some header data that listed >msg modifications (i.e. pre-pended subject with 6 chars, post-pended >body with 6 lines, etc), would this be beneficial for anyone to use in >order to reconstruct an original msg and validate the original DKIM >sig

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-16 Thread Rich Kulawiec
On Wed, Jun 15, 2016 at 10:47:07AM +0300, Gil Bahat via mailop wrote: > Your users will pay a price and netease will pay a price. There's always a price. The costs associated with both FP and FN are non-zero -- although they might be negligibly small -- for either sender or recipient or both.

[mailop] GMail 421 is sometimes a permanent failure?

2016-06-16 Thread Jeffry Dwight
Today I noticed the following response from GMail after submission of email: 421-4.7.0 [x.x.x.x 15] Our system has detected that this message is 421-4.7.0 suspicious due to the nature of the content and/or the links within. 421-4.7.0 To best protect our users from spam, the message has been

Re: [mailop] DKIM + mailinglists (rehash)

2016-06-16 Thread Brandon Long via mailop
In the simplest cases, potentially yes. I think there was one suggestion on one of the dmarc lists of having an encoded diff result in a header, allowing you to reverse it. It doesn't help as much for removals, especially lists that remove entire attachments or parts. I mean, you could still

[mailop] DKIM + mailinglists (rehash)

2016-06-16 Thread Jim Popovitch
Hello! If Mailman (and other MLMs) would provide some header data that listed msg modifications (i.e. pre-pended subject with 6 chars, post-pended body with 6 lines, etc), would this be beneficial for anyone to use in order to reconstruct an original msg and validate the original DKIM sig

Re: [mailop] change at gmail???

2016-06-16 Thread Shawn K. Hall
> I guess what I'm trying to understand is why anyone would > base their acceptance or rejection on the 822 From: header. > It seems that this causes mailing list managers to have to > jump through hoops to rewrite the From: header in strange ways. Mostly because there are other reasons to

[mailop] MailChimp Contact on list? Might be interested in this.

2016-06-16 Thread Michael Peddemors
Looks like someone is using a similar name to spam? Return-Path: Received: from mailchimps.eu (HELO mailchimps.eu) (62.76.179.14) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=key1; d=mailchimps.eu;

Re: [mailop] MailChimp Contact on list? Might be interested in this.

2016-06-16 Thread Neil Schwartzman
Looks like a counterfeit/malicious/phish attempt to me. registered 2016-05-25 Registrant: NOT DISCLOSED! Visit www.eurid.eu for webbased whois. Technical: Name: Domain Manager Organisation: PublicDomainRegistry.com Language: en Phone: