Re: [mailop] Anyone from Yahoo - icmpv6 filtering breaks login.yahoo.com MTU detection

2016-11-18 Thread Valdis . Kletnieks
On Fri, 18 Nov 2016 13:01:50 -0800, Carl Byington said: > response to that will be a bunch of full size packets from Yahoo with > the certificate, etc. The *far* end of my tunnel will be sending the > icmpv6 "packet too big" back to Yahoo. And you identified that the problem was at Yahoo, and

Re: [mailop] Anyone from Yahoo - icmpv6 filtering breaks login.yahoo.com MTU detection

2016-11-18 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2016-11-18 at 15:41 -0500, valdis.kletni...@vt.edu wrote: > Did you do anything to specifically identify Yahoo's routers as the > offenders? > Hint: If there's a tunnel in the path, it will be *your* end of the > tunnel > that sends back

Re: [mailop] Anyone from Yahoo - icmpv6 filtering breaks login.yahoo.com MTU detection

2016-11-18 Thread Mike Joseph
Hi Carl, Could you please send me IPv6 traceroutes to the Yahoo server(s) in question? I'll have someone take a look. -MJ On Fri, Nov 18, 2016 at 11:58 AM, Carl Byington wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > https://login.yahoo.com > > If you

Re: [mailop] Anyone from Yahoo - icmpv6 filtering breaks login.yahoo.com MTU detection

2016-11-18 Thread Valdis . Kletnieks
On Fri, 18 Nov 2016 11:58:58 -0800, Carl Byington said: > If you have IPv6 connectivity thru a tunnel, with a smaller MTU, that > will fail. With a 1500 byte MTU, it works. The TCP handshake works - it > then hangs during the TLS handshake which sends full size packets. Did you do anything to

[mailop] Anyone from Yahoo - icmpv6 filtering breaks login.yahoo.com MTU detection

2016-11-18 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://login.yahoo.com If you have IPv6 connectivity thru a tunnel, with a smaller MTU, that will fail. With a 1500 byte MTU, it works. The TCP handshake works - it then hangs during the TLS handshake which sends full size packets. echo -e 'GET /

Re: [mailop] Amazing when Banks don't use SPF records..

2016-11-18 Thread Matt Vernhout
Try - phish...@td.com That is their published reporting address... And yes I've pointed this out to them several times and it's all deaf ears each time. As one of the top 5 banks in Canada they are the only one not participating in any form of email authentication - the others are ding at least

[mailop] Amazing when Banks don't use SPF records..

2016-11-18 Thread Michael Peddemors
There is a large round of TD Bank phishing going around.. Would have liked to report this to their abuse team.. but.. *Delivery has failed to these recipients or groups:* ab...@td.com The e-mail address you entered couldn't be found. Please check the recipient's e-mail

Re: [mailop] Any Cloudmark Employees?

2016-11-18 Thread ryan prihoda
We got it all squared away with the reset page. Thanks though. I've never had to deal with cloudmark before but I am you all are so responsive. Thanks James On Fri, Nov 18, 2016, 3:24 AM James Hoddinott wrote: > Hi Ryan, > > My team looks after CSI and the remediation

Re: [mailop] Any Cloudmark Employees?

2016-11-18 Thread James Hoddinott
Hi Ryan, My team looks after CSI and the remediation thereof. If you want to send me IP details to jhoddin...@cloudmark.com I'll take a look. On 17 November 2016 at 16:29, ryan prihoda wrote: > > One of our client's email servers has been blacklisted by cloudmark sender