We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

How do I configure my Plesk email server to reject invalid recipients with the Email Security Gateway?

  • Type: Knowledgebase
  • Date changed: 10 months ago
Solution #00003306

Applies to all Email Security Gateway deployments that have a Plesk email server as a destination, firmware versions 3.5.11 and above.

When somebody sends an email message to an email address that does not exist under your domain, the Plesk mail server will by default accepts the email, processes it, and when it finds out that there is no such a recipient under that domain it will return the email back to sender with a this address no longer accepts mail notice.

You can choose to:
  • Change the default notice if you do not like it
  • Forward all such mail to a desired, catch-all email address
  • Reject such mail without accepting it and without notifying the senders
The third option can decrease mail server load caused by a large amount of spam, which is often sent to randomly-generated usernames.

To configure the site-wide settings for handling mail to nonexistent users on a Plesk mail server, follow these steps:

  1. Click the Domains shortcut in the navigation pane.
  2. Click the required domain name in the list. 
  3. Click Mail. 
  4. Click Preferences. 
  5. Choose a desired option and specify the information as required. 
  6. Click OK.
If the "Reject" option is selected, it will dramatically decrease the load on the Email Security Gateway since the Barracuda's recipient verification can now drop emails addressed to an invalid recipient.

Additional Notes:
For more information on how the Email Security Gateway interacts with destination mail servers when performing recipient verification over SMTP, see Solution #00003521.

Link to This Page: