Recipient verification
Overview
MetaDefender Cloud Email Security can be configured to apply a rule only if the recipient of the email is accepted by any of the SMTP servers of the SMTP server profile configured for the rule.
The problem
This option can help avoiding situations when MetaDefender Cloud Email Security accepts emails even if it is known to be unable to forward it, cause no SMTP server will accept the recipient.
In such cases the email ends up in Failed status and pollutes the Email History with email junk that can not be delivered with a message in Processing history like SMTP send failed to (Response: Unknown user (550, MailboxUnavailable)) smtp://localhost:25.
The solution
When this option is enabled, then before accepting the email, MetaDefender Cloud Email Security checks whether it will be able to forward it based on the current settings. If it will be able to forward, then accepts it. But if it knows that it will not be able to forward the email, then the email gets rejected on the SMTP level.
In this case the message No policy for recipient is returned to the sender’s email client.
How it works
When SMTP relay recipient verification is enabled for the rule, then MetaDefender Cloud Email Security will attempt to initiate sending an email to the recipient via the SMTP servers of the SMTP server profile configured for the rule (GENERAL / SMTP relay server profile).
If the recipient (RCPT TO) is accepted by the remote SMTP server, then MetaDefender Cloud Email Security aborts the connection, and accepts the emails as it will be possible to be delivered.
Auto rule selection
Enabling SMTP relay recipient verification for all the rules, MetaDefender Cloud Email Security will apply the first rule for an email that will be able to deliver it to an SMTP destination.
SMTP server(s) unreachable
If there are some SMTP servers in the server profile, that are not reachable, MetaDefender Cloud Email Security will accept the email, cause it can not ensure, whether the email can later be delivered or not.
Caching
On successful initiation recipient addresses are cached for 10 minutes. It means that within this timeframe MetaDefender Cloud Email Security won’t check whether the recipient will be accepted by the servers of the configured server profile, it assumes success.