MX-VERIFY-CGI run for ``dibona.com''


Doing resolver lookup for T=MX domain=``dibona.com''

DNS yields following MX entries

  dibona.com  (120s) IN MX   0 aspmx.l.google.com
  dibona.com  (120s) IN MX   1 alt1.aspmx.l.google.com


Testing MX server: aspmx.l.google.com

Address lookup did yield following ones:

  IPv4 74.125.129.27

Testing server at address: IPv4 74.125.129.27

[ CONNECTED! ]

 220 mx.google.com ESMTP e7si5740116pdf.73 - gsmtp
 EHLO vger.kernel.org
 250-mx.google.com at your service, [209.132.180.67]
 250-SIZE 35882577
 250-8BITMIME
 250-STARTTLS
 250-ENHANCEDSTATUSCODES
 250-PIPELINING
 250 CHUNKING

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 2.1.0 OK e7si5740116pdf.73 - gsmtp

Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1

 RSET
 250 2.1.5 Flushed e7si5740116pdf.73 - gsmtp
 MAIL FROM:<postmaster@vger.kernel.org>
 250 2.1.0 OK e7si5740116pdf.73 - gsmtp
 RCPT TO:<postmaster@dibona.com>
 250 2.1.5 OK e7si5740116pdf.73 - gsmtp

Apparently OK!


Testing MX server: alt1.aspmx.l.google.com

Address lookup did yield following ones:

  IPv4 74.125.193.27

Testing server at address: IPv4 74.125.193.27

[ CONNECTED! ]

 220 mx.google.com ESMTP yb19si26031641icb.30 - gsmtp
 EHLO vger.kernel.org
 250-mx.google.com at your service, [209.132.180.67]
 250-SIZE 35882577
 250-8BITMIME
 250-STARTTLS
 250-ENHANCEDSTATUSCODES
 250-PIPELINING
 250 CHUNKING

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 2.1.0 OK yb19si26031641icb.30 - gsmtp

Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1

 RSET
 250 2.1.5 Flushed yb19si26031641icb.30 - gsmtp
 MAIL FROM:<postmaster@vger.kernel.org>
 250 2.1.0 OK yb19si26031641icb.30 - gsmtp
 RCPT TO:<postmaster@dibona.com>
 250 2.1.5 OK yb19si26031641icb.30 - gsmtp

Apparently OK!