Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-19 Thread John Levine via mailop
In article you write: >> AFAIK he.net filter ingoing and outgoing port 25 *by >> default*: Odd, my main mail server is on an IPv6 HE tunnel and works fine. Maybe I'm silently grandfathered or something. >I verified this by trying to connect to the address John used for the

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-19 Thread Noel Butler via mailop
On 19/05/2019 03:47, Steve Dodd wrote: > On Sat, 18 May 2019 at 01:00, Noel Butler via mailop > wrote: > >> I am using HE tunnels and can access them > >> the demos I provided yesterday were all from HE tunnels >> >> nothing to see here, time to move along. > > AFAIK he.net [1] filter

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-18 Thread Jost Krieger via mailop
Am 18.05.2019 um 19:47 schrieb Steve Dodd via mailop: On Sat, 18 May 2019 at 01:00, Noel Butler via mailop mailto:mailop@mailop.org>> wrote: AFAIK he.net filter ingoing and outgoing port 25 *by default*: https://ipv6.he.net/certification/faq.php That's it. And they do it by

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-18 Thread Steve Dodd via mailop
On Sat, 18 May 2019 at 01:00, Noel Butler via mailop wrote: > I am using HE tunnels and can access them > the demos I provided yesterday were all from HE tunnels > > nothing to see here, time to move along. > AFAIK he.net filter ingoing and outgoing port 25 *by default*:

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread John Levine via mailop
In article <4ef5b4df-ee83-4f85-bed1-7375869a7...@rub.de> you write: >>No, you're refusing the connections. When I connect via an IPv6 tunnel >> >>from HE you refuse the connection, when I connect from a VPS somewhere >>else, you accept it. Traceroutes show it's going to you, not anywhere

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread Noel Butler via mailop
I'd dont see levines posts, probably same as why the remote site is denying him :) so replying to it here BS I am using HE tunnels and can access them the demos I provided yesterday were all from HE tunnels nothing to see here, time to move along. On 18/05/2019 02:23, Jost Krieger via

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread Luis E. Muñoz via mailop
And here, though the first connect took ~6 seconds or so. ``` swaks -6 -f 'none' -t testing@relay -s rrmx.imp.ch --quit-after helo === Trying rrmx.imp.ch:25... === Connected to rrmx.imp.ch. <- 220 idefix.imp.ch ESMTP Postfix -> EHLO s4.libertad.link <- 250-idefix.imp.ch <- 250-PIPELINING <-

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread Jost Krieger via mailop
Am 17. Mai 2019 16:42:17 MESZ schrieb John R Levine via mailop : >No, you're refusing the connections. When I connect via an IPv6 tunnel > >from HE you refuse the connection, when I connect from a VPS somewhere >else, you accept it. Traceroutes show it's going to you, not anywhere >else.

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread John R Levine via mailop
Hi, this is very odd, could you send a traceroute to those IPv6 destinations? I can confirm the servers do NOT refuse IPv6 connections. I suppose there is a transit problem from certain ISP. No, you're refusing the connections. When I connect via an IPv6 tunnel from HE you refuse the

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-17 Thread Benoit Panizzon via mailop
> >nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable > >nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable > >nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable > > > >So maybe AWS SES is trying to connect to the IPv6 address and

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-16 Thread Sébastien Riccio via mailop
Hi, Same from here, hosts responds to v6 : Trying 2001:4060:1:1001::12:5... Connected to 2001:4060:1:1001::12:5. Escape character is '^]'. 220-obelix.imp.ch ESMTP Postfix Trying 2001:4060:1:1001::12:4... Connected to 2001:4060:1:1001::12:4. Escape character is '^]'. 220-asterix.imp.ch ESMTP

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-16 Thread Noel Butler via mailop
Connected to 2001:4060:1:1001::12:5. Escape character is '^]'. 220-obelix.imp.ch ESMTP Postfix Connected to 2001:4060:1:1001::12:4. Escape character is '^]'. 220-asterix.imp.ch ESMTP Postfix Connected to 2001:4060:1:1001::12:6. Escape character is '^]'. 220-idefix.imp.ch ESMTP Postfix On

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-16 Thread John Levine via mailop
In article you write: >$ host -t mx leunet.ch >leunet.ch mail is handled by 10 rrmx.imp.ch. >$ nc -4 -vz rrmx.imp.ch. 25 >Connection to rrmx.imp.ch. 25 port [tcp/smtp] succeeded! >$ nc -6 -vz rrmx.imp.ch. 25 >nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable >nc: connect

Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-16 Thread Yiorgos [George] Adamopoulos via mailop
This is what I see: $ host -t mx leunet.ch leunet.ch mail is handled by 10 rrmx.imp.ch. $ nc -4 -vz rrmx.imp.ch. 25 Connection to rrmx.imp.ch. 25 port [tcp/smtp] succeeded! $ nc -6 -vz rrmx.imp.ch. 25 nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable nc: connect to

[mailop] Anyone on this List with Access to Amazon SES Maillogs?

2019-05-16 Thread Benoit Panizzon via mailop
Please contact me off-list Short story: A customer of Amazon SES is attempting to send emails to one of our customers. Our customer is not getting them, we don't see ANY trace of those emails in our logs, they just seem to disappear in transit. Re-Tested yesterday, exact times known. Long