Re: T_DKIM_INVALID from yahoo.com

2017-01-01 Thread Tom Hendrikx
On 29-12-16 19:40, Marc Stürmer wrote: > Zitat von Tom Hendrikx : > >> Did you file a ticket with them? I'm curious as to what they are saying >> about it. > > Actually I got this info by their phone support, and the info was back > then it's not supported and unlikely will be supported very soon

Re: T_DKIM_INVALID from yahoo.com

2016-12-29 Thread RW
On Thu, 29 Dec 2016 11:35:13 +0100 Marc Stürmer wrote: > Zitat von RW : > > > Are there really resolvers that can't handle it? My understanding is > > that the relevant limit here is on the length of a string, 255 > > bytes. Yahoo have broken their DKIM TXT record into multiple short > > strings

Re: T_DKIM_INVALID from yahoo.com

2016-12-29 Thread Marc Stürmer
Zitat von Tom Hendrikx : Did you file a ticket with them? I'm curious as to what they are saying about it. Actually I got this info by their phone support, and the info was back then it's not supported and unlikely will be supported very soon. Just like DNSSEC, they also don't offer it and

Re: T_DKIM_INVALID from yahoo.com

2016-12-29 Thread Tom Hendrikx
On 29-12-16 11:35, Marc Stürmer wrote: > Zitat von RW : > >> Are there really resolvers that can't handle it? My understanding is >> that the relevant limit here is on the length of a string, 255 bytes. >> Yahoo have broken their DKIM TXT record into multiple short strings to >> keep within the

Re: T_DKIM_INVALID from yahoo.com

2016-12-29 Thread Marc Stürmer
Zitat von RW : Are there really resolvers that can't handle it? My understanding is that the relevant limit here is on the length of a string, 255 bytes. Yahoo have broken their DKIM TXT record into multiple short strings to keep within the limit. There are still enough resolvers around which

Re: T_DKIM_INVALID from yahoo.com

2016-12-26 Thread RW
On Mon, 26 Dec 2016 12:07:56 +0100 Marc Stürmer wrote: > Zitat von Groach : > > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.net; > > s=s2048; t=1482596721; > > DKIM entries do live in DNS space. Not every DNS server software > (and resolver) around is able to handle 2048

Re: T_DKIM_INVALID from yahoo.com

2016-12-26 Thread Marc Stürmer
Zitat von Groach : DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.net; s=s2048; t=1482596721; DKIM entries do live in DNS space. Not every DNS server software (and resolver) around is able to handle 2048 bit sized keys, which are 512 bytes. If you want to be on the safe s

Re: T_DKIM_INVALID from yahoo.com

2016-12-25 Thread Ian Zimmerman
On 2016-12-24 19:50, Michael Orlitzky wrote: > > All mail I get from yahoo customers [1] scores on T_DKIM_INVALID, > > and always has. Why? > > Is there any correlation between the DKIM result and the size of the > message? Hmm. I got a few more messages from those domains and they seem to be

Re: T_DKIM_INVALID from yahoo.com

2016-12-24 Thread Michael Orlitzky
On 12/24/2016 11:05 AM, Ian Zimmerman wrote: > All mail I get from yahoo customers [1] scores on T_DKIM_INVALID, and > always has. Why? > Is there any correlation between the DKIM result and the size of the message?

Re: T_DKIM_INVALID from yahoo.com

2016-12-24 Thread Ian Zimmerman
On 2016-12-24 16:32, Groach wrote: > I have just done a test and do not get the same results as you. My > yahoo incoming emails pass ok: And yours passed for me, too. So it's only a subset of yahoo senders, apparently :-( > This might explain it: > http://spamassassin.1065346.n5.nabble.com/

Re: T_DKIM_INVALID from yahoo.com

2016-12-24 Thread Groach
I have just done a test and do not get the same results as you. My yahoo incoming emails pass ok: Return-Path: stopspammin...@yahoo.net X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mailserver X-Spam-Level: * X-Spam-Status: No, score=1.1 required=3.0 tests=BAYES_50,DKIM_SIGNED,

T_DKIM_INVALID from yahoo.com

2016-12-24 Thread Ian Zimmerman
All mail I get from yahoo customers [1] scores on T_DKIM_INVALID, and always has. Why? Maybe I can prepare a spample, but it will take some work to find a privacy friendly specimen, since it obviously can't be altered. [1] same for hotmail, while other big domains get DKIM_VALID. -- Please *no