Test |
Meaning |
---|---|
Shows whether SEPPmail Cloud can connect to customer's target server. Failure to connect indicates wrong server or server outage. In such cases, SEPPmail Cloud will not be able to deliver mail. |
|
SMTP Banner of the target server. Any code other than 2xx indicates an error on the target server. |
|
If the target server is a Cisco PIX, we highly recommend to switch off "SMTP Fixup". |
|
Response to EHLO request. It should display features supported by target server. Any code other than 2xx indicates an error on the target server. |
|
Response to STARTTLS request. Any code other than 2xx indicates an error on the target server. |
|
SHA1 checksum of the target server's SSL certificate. |
|
Canonical name for which SSL certificate of target server was issued. |
|
Name of issuer of SSL certificate. |
|
Alternative names for which SSL certificate is valid. |
|
Date and time of SSL certificate expiration. |
|
Is SSL certificate currently valid or already expired? |
|
SSL version used for this connection. |
|
SSL cipher used for this connection. |
|
SSL magic bits used for this connection. |
|
Response to our EHLO request. It should display features supported by target server. Any code other than 2xx indicates an error on the target server. |
|
Envelope sender address used for this test. |
|
Envelope recipient address used for this test. Postmaster and Abuse should be accepted. A random generated address should be rejected (recipient filtering). |
|
Message delivery can be delayed if target server uses greylisting. |
|
Mail will be lost if target server performs SPF checks. If SPF check is detected, we highly recommend to disable it on the target server. If no SPF check was detected, it is best to leave it switched off. |
|
Response to DATA request. Any code other than 2xx indicates that mail was not accepted and should be considered an error of the target server. |
|
Response to QUIT request. Any code other than 2xx indicates an error on the target server. |
|
Test could not be completed. The server's message should point to the reason. |
|
Error while connecting or performing the test. The error message should point to the reason. |
|
Please report error message, target server and recipient to support@seppmail.ch. |
|
Detailed log of SMTP test transaction. |
|
Recipient filtering should always be enabled on target server. This allows for proper count of active users, prevents backscatter or spam to inactive users. |
|
Mail will be lost if target server performs SPF checks. If SPF check is detected, we highly recommend to disable it on the target server. If no SPF check was detected, it is best to leave it switched off. |
|
An open relay accepts mail from any sender to any recipient. Once detected by spammers this server will be abused and risks getting listed by blocklists. An open relay is the most critical misconfiguration and must be fixed immediately. |
|
Domain's MX record should point to Cloud (customerid.gate.seppmail.cloud). |
|
SEPPmail Cloud filtered domains should have exactly one MX record. |
|
Verify domain's MX record is DNS resolvable. |
|
A record (IPv4 address) of target server. |
|
PTR record (reverse DNS) of target server's IPv4 address. |
|
AAAA record (IPv6 address) of target server. |
|
PTR record (reverse DNS) of target server's IPv4 address. |