samba - Aug 2015 - lists.samba.org's Mail Servers Are A Bit Wonky?

To Whom It May Concern,

I tried emailing the ostensible mailing list owner, at both addresses
noted, and got no response.  Maybe somebody here knows how to alert
whomever must know about this.

Observe...

From home (business class cable with static IP and valid rDNS)...

    $ host -t mx samba.org
    samba.org mail is handled by 10 smtp.samba.org.
    samba.org mail is handled by 5 ns1.samba.org.
    $ host smtp.samba.org
    smtp.samba.org has address 144.76.82.148
    smtp.samba.org has IPv6 address 2a01:4f8:192:486::147:1
    $ host ns1.samba.org
    ns1.samba.org has address 162.209.107.11
    ns1.samba.org has IPv6 address 2001:4802:7800:2:be76:4eff:fe20:b2b2
    $ telnet 144.76.82.148 25
    Trying 144.76.82.148...
    ^C
    $ telnet 162.209.107.11 25
    Trying 162.209.107.11...
    ^C
    $ ping 144.76.82.148
    PING 144.76.82.148 (144.76.82.148) 56(84) bytes of data.
    64 bytes from 144.76.82.148: icmp_seq=1 ttl=47 time=117 ms
    64 bytes from 144.76.82.148: icmp_seq=2 ttl=47 time=114 ms
    64 bytes from 144.76.82.148: icmp_seq=3 ttl=47 time=113 ms
    ^C
    --- 144.76.82.148 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 113.948/115.229/117.293/1.473 ms
    $ ping 162.209.107.11
    PING 162.209.107.11 (162.209.107.11) 56(84) bytes of data.
    64 bytes from 162.209.107.11: icmp_seq=1 ttl=53 time=27.7 ms
    64 bytes from 162.209.107.11: icmp_seq=2 ttl=53 time=23.4 ms
    64 bytes from 162.209.107.11: icmp_seq=3 ttl=53 time=22.5 ms
    ^C
    --- 162.209.107.11 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 22.535/24.570/27.716/2.263 ms
    $

So: Neither MX connects, but both hosts are "there".

From work (business fiber connection with SWIP'd netblock and rDNS
for all):

    $ host -t mx samba.org
    samba.org mail is handled by 5 ns1.samba.org.
    samba.org mail is handled by 10 smtp.samba.org.
    $ host smtp.samba.org
    smtp.samba.org has address 144.76.82.148
    smtp.samba.org has IPv6 address 2a01:4f8:192:486::147:1
    $ host ns1.samba.org
    ns1.samba.org has address 162.209.107.11
    ns1.samba.org has IPv6 address 2001:4802:7800:2:be76:4eff:fe20:b2b2
    $ telnet 144.76.82.148 25
    Trying 144.76.82.148...
    Connected to hr2.samba.org.
    Escape character is '^]'.
    220 hr2.samba.org ESMTP Exim 4.84 Fri, 28 Aug 2015 18:54:15 +0000
    quit
    221 hr2.samba.org closing connection
    Connection closed by foreign host.
    $ telnet 162.209.107.11 25
    Trying 162.209.107.11...
    telnet: connect to address 162.209.107.11: Connection refused
    telnet: Unable to connect to remote host
    $

Both hosts are there, but one is not accepting connections on port 25.

From my Digital Ocean server (static IP and rDNS):

    $ host -t mx samba.org
    samba.org mail is handled by 10 smtp.samba.org.
    samba.org mail is handled by 5 ns1.samba.org.
    $ host smtp.samba.org
    smtp.samba.org has address 144.76.82.148
    smtp.samba.org has IPv6 address 2a01:4f8:192:486::147:1
    $ host ns1.samba.org
    ns1.samba.org has address 162.209.107.11
    ns1.samba.org has IPv6 address 2001:4802:7800:2:be76:4eff:fe20:b2b2
    $ telnet 144.76.82.148 25
    Trying 144.76.82.148...
    Connected to 144.76.82.148.
    Escape character is '^]'.
    220 hr2.samba.org ESMTP Exim 4.84 Fri, 28 Aug 2015 18:58:05 +0000
    quit
    221 hr2.samba.org closing connection
    Connection closed by foreign host.
    $ telnet 162.209.107.11 25
    Trying 162.209.107.11...
    telnet: Unable to connect to remote host: Connection refused

Again: Both hosts are there, but one is not accepting connections on
port 25.

What I finally did to get email through to the list was kill my
original subscription, from my network at home, re-sign up with the
email at had running on a droplet at Digital Ocean, then put in an
explicit transport map entry to force the mail server there to use only
smtp.samba.org.

Regards,
Jim

On Fri, Aug 28, 2015 at 3:09 PM, Jim Seymour <jseymour at jseymour.com>
wrote:
>   $ host -t mx samba.org
>     samba.org mail is handled by 10 smtp.samba.org.
>     samba.org mail is handled by 5 ns1.samba.org.
Might be an error, might be some sort of anti-spam set up as well.
Could be one just answers privately. Do note that the mailing list
address is @lists.samba.org whose MX records vary slightly from those
of @samba.org:
========================================$ dig +nocl +nocmd +nocomments +nottlid
lists.samba.org MX
;lists.samba.org.       IN MX
lists.samba.org.        MX      10 lists.samba.org.
lists.samba.org.        MX      10 ns1.samba.org.
========================================$ dig +nocl +nocmd +nocomments +nottlid
samba.org MX
;samba.org.             IN MX
samba.org.              MX      10 smtp.samba.org.
samba.org.              MX      5 ns1.samba.org.
========================================
Both include ns1.samba.org (the one not answering publicly).

Note that lists.samba.org and smtp.samba.org have different IP addresses.
========================================$ dig +nocl +nocmd +nocomments +nottlid
smtp.samba.org A
;smtp.samba.org.                IN A
smtp.samba.org.         A       144.76.82.148
========================================$ dig +nocl +nocmd +nocomments +nottlid
lists.samba.org A
;lists.samba.org.       IN A
lists.samba.org.        A       144.76.82.147
========================================
I've never experienced a problem sending to the list. Also any
properly working mail server should have worked as well. If one MX
server doesn't answer it should try the next one... as long as one is
up the mail should go through.

Chris

On Fri, 28 Aug 2015 17:27:03 -0400
Sonic <sonicsmith at gmail.com> wrote:

[snip]
> 
> I've never experienced a problem sending to the list. Also any
> properly working mail server should have worked as well. If one MX
> server doesn't answer it should try the next one... as long as one is
> up the mail should go through.
Yeah, I know how it's supposed to work, I was just having a massive
synapse lapse.  Part of the problem was a router misconfiguration on my
end, and troubleshooting email delivery problems was not at the top of
my mind--finding the answers to Samba questions was.

Anyway: I've solved it.

(Tho one remaining question is why Postfix is trying to use IPv6
responses when no IPv6 routes exist, but that's a question for another
mailing list...)

Thanks,
Jim
-- 
Note: My mail server employs *very* aggressive anti-spam
filtering.  If you reply to this email and your email is
rejected, please accept my apologies and let me know via my
web form at <http://jimsun.LinxNet.com/contact/scform.php>.