Comment 59 for bug 1974214

(In reply to Gedalya from comment #45)
> (In reply to Sergio Durigan Junior from comment #44)
> >
> > Thanks for also confirming that your server is still deferring emails. My
> > container did have IPv6 enabled, so I completely disabled it just in case.
>
> You don't need to disable TPv6 as much as you need to enable IPv4.

IPv4 was never disabled; it works normally.

> > # exim4 -d+all -q 1nxCYB-0000At-E1 2>&1 | tee /tmp/exim.debug
> >
> > I get the following output:
> >
> > https://dpaste.com//AVEDX2WT4
> >
> > It seems strange that the second connectio (to mx2) didn't work either.
>
> It's not working for the same reason mail.gedalya.net isn't working. It
> works for you via IPv6 but you can't reach my servers on IPv4.
>
> > I don't see a segmentation fault anywhere, although the email isn't being sent
> > and keeps showing in "exim4 -bp".
>
> You need to successfully connect to the first server and receive a deferral
> (4xx SMTP code).
>
> Figure out why you can't reach my servers out of this container. Ordinary
> network troubleshooting.
>
> Note that some "cloud" providers block outbound TCP connections to
> destination port 25, some block only for IPv6 but not for IPv4, maybe you
> have a reverse case? But whatever, just do network troubleshooting, or set
> up a local reproducer.

I tried something simpler here:

$ telnet mail.gedalya.net 25

It doesn't connect. I can connect to my personal email server via port 25, though, so I'm thinking that maybe my IP has been blocked on your side? Anyway, I was able to get ahold of another server (with another IP) and finally reproduced the bug.

Are you OK with me writing a test case for https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214 using your server? Only a member of the Ubuntu SRU team will eventually check it, and the test case can be deleted afterwards if you'd like.

Thanks.