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 209.85.216.47

Testing server at address: IPv4 209.85.216.47

[ CONNECTED! ]

 220 mx.google.com ESMTP 5si1049757pxi.89
 EHLO vger.kernel.org
 250-mx.google.com at your service, [209.132.180.67]
 250-SIZE 35651584
 250-8BITMIME
 250-ENHANCEDSTATUSCODES
 250 PIPELINING

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 2.1.0 OK 5si1049757pxi.89

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

 RSET
 250 2.1.5 Flushed 5si1049757pxi.89
 MAIL FROM:<postmaster@vger.kernel.org>
 250 2.1.0 OK 5si1049757pxi.89
 RCPT TO:<postmaster@dibona.com>
 250 2.1.5 OK 5si1049757pxi.89

Apparently OK!

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

Address lookup did yield following ones:

  IPv4 209.85.217.6

Testing server at address: IPv4 209.85.217.6

[ CONNECTED! ]

 220 mx.google.com ESMTP 6si1878490gxk.26
 EHLO vger.kernel.org
 250-mx.google.com at your service, [209.132.180.67]
 250-SIZE 35651584
 250-8BITMIME
 250-ENHANCEDSTATUSCODES
 250 PIPELINING

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 2.1.0 OK 6si1878490gxk.26

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

 RSET
 250 2.1.5 Flushed 6si1878490gxk.26
 MAIL FROM:<postmaster@vger.kernel.org>
 250 2.1.0 OK 6si1878490gxk.26
 RCPT TO:<postmaster@dibona.com>
 250 2.1.5 OK 6si1878490gxk.26

Apparently OK!