Loading ...
Sorry, an error occurred while loading the content.

AOL declines mails with "421dnsnr" on one of our nodes

Expand Messages
  • Christian Parpart
    Hi all, I am about to mvoe our postfix MTAs from physical nodes into virtual nodes, as they re just transmitting and we re not receiving mails on these
    Message 1 of 5 , Jun 2, 2012
    • 0 Attachment
      Hi all,

      I am about to mvoe our postfix MTAs from physical nodes into virtual nodes,
      as they're just transmitting and we're not receiving mails on these postfix'es anyways,
      I thought it might be not that an overhead, however, everyone seems to accept
      the mails from our new VM postfix node except AOL, responding with
      an error code [1].

      No matter how often I am to read this text, I still don't get what they actually want from me.
      We've properly set up DNS (name-to-IP and reverse IP-to-name).

      In the logs, I see a message like this:

      (delivery temporarily suspended: host mailin-02.mx.aol.com[64.12.139.193] refused to talk to me: 421 4.7.1 :

      Does anyone know what I might have been missing in my config? Well, the config file looks
      almost the very same as on the physical nodes, it's just, that the VM doesn't have a direct public IP now.
      But the outgoing IP is set up with DNS properly, however.

      Many thanks in advance,
      Christian Parpart.
    • Wietse Venema
      ... You have told everything but the IP address, so how can we help? Wietse
      Message 2 of 5 , Jun 2, 2012
      • 0 Attachment
        Christian Parpart:
        > But the outgoing IP is set up with DNS properly, however.

        You have told everything but the IP address, so how can we help?

        Wietse
      • Christian Parpart
        ... 46.231.176.107 sorry, I thought that weren t really required :-) So long, Christian.
        Message 3 of 5 , Jun 2, 2012
        • 0 Attachment
          On Sat, Jun 2, 2012 at 5:24 PM, Wietse Venema <wietse@...> wrote:
          Christian Parpart:
          > But the outgoing IP is set up with DNS properly, however.

          You have told everything but the IP address, so how can we help?

          46.231.176.107 

          sorry, I thought that weren't really required :-)
          So long,
          Christian.
        • Stan Hoeppner
          ... ~$ host 46.231.176.107 107.176.231.46.in-addr.arpa domain name pointer cesar1.dawanda.com. ~$ host cesar1.dawanda.com cesar1.dawanda.com has address
          Message 4 of 5 , Jun 2, 2012
          • 0 Attachment
            On 6/2/2012 12:21 PM, Christian Parpart wrote:

            > 46.231.176.107

            ~$ host 46.231.176.107
            107.176.231.46.in-addr.arpa domain name pointer cesar1.dawanda.com.

            ~$ host cesar1.dawanda.com
            cesar1.dawanda.com has address 46.231.176.107

            Looks good querying from my local resolver in net 65.40.0.0/15.

            --
            Stan
          • Wietse Venema
            Stan Hoeppner: [ Charset ISO-8859-1 unsupported, converting... ] ... Even better, both 176.231.46.in-addr.arpa DNS servers agree. Wietse
            Message 5 of 5 , Jun 3, 2012
            • 0 Attachment
              Stan Hoeppner:
              [ Charset ISO-8859-1 unsupported, converting... ]
              > On 6/2/2012 12:21 PM, Christian Parpart wrote:
              >
              > > 46.231.176.107
              >
              > ~$ host 46.231.176.107
              > 107.176.231.46.in-addr.arpa domain name pointer cesar1.dawanda.com.
              >
              > ~$ host cesar1.dawanda.com
              > cesar1.dawanda.com has address 46.231.176.107
              >
              > Looks good querying from my local resolver in net 65.40.0.0/15.

              Even better, both 176.231.46.in-addr.arpa DNS servers agree.

              Wietse
            Your message has been successfully submitted and would be delivered to recipients shortly.