MX-VERIFY-CGI run for ``trevor@tecnopolis.ca''

Doing resolver lookup for T=MX domain=``tecnopolis.ca''

DNS yields following MX entries

  tecnopolis.ca  (86400s) IN MX   0 tecnopolis.ca

Only one MX record...
Well, no backups, but as all systems are looking for MX record in every case, not bad..

Testing MX server: tecnopolis.ca

Address lookup did yield following ones:

  IPv4 24.78.148.126

Testing server at address: IPv4 24.78.148.126

[ CONNECTED! ]

 220 tecnopolis.ca ESMTP Sendmail 8.17.2/8.17.1; Sun, 1 Sep 2024 01:39:16 -0500
 EHLO vger.kernel.org
 250-tecnopolis.ca Hello vger.kernel.org [23.128.96.18], pleased to meet you
 250-ENHANCEDSTATUSCODES
 250-PIPELINING
 250-8BITMIME
 250-SIZE
 250-DSN
 250-ETRN
 250-DELIVERBY
 250 HELP

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 2.1.0 <>... Sender ok

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

 RSET
 250 2.0.0 Reset state
 MAIL FROM:<postmaster@vger.kernel.org>
 250 2.1.0 <postmaster@vger.kernel.org>... Sender ok
 RCPT TO:<trevor@tecnopolis.ca>
 250 2.1.5 <trevor@tecnopolis.ca>... Recipient ok
 RCPT TO:<postmaster@tecnopolis.ca>
 451 4.7.1 Greylisting in action, please come back later

Eh ? What ? No ``postmaster'' supported there ? That violates RFC 2821 section 4.5.1.

Apparently OK!