SmarterMail Help

SMTP Blocks

SMTP Blocks are an effective method for temporarily canceling a domain or indiviual user's ability to send email on the server. For example, if a particular account is sending an abnormal amount of email, you can add their address to the SMTP Blocks list, and they will be unable to send email until you remove them. Users and/or domains can be left on the list for whatever time you deem appropriate, and can be an effective stop-gap versus actually deleting the user and/or domain from the server.

To access the SMTP Blocks, log into SmarterMail as a System Administrator and click on the Settings icon. Then click on Security in the navigation pane and select the SMTP Blocks tab.

To create a new block, click on New. When adding or editing an entry, the following configuration settings will be available, based on the Block Type chosen:

Email Address

  • Blocked Address - The complete email address of the user.
  • Direction - The types of messages that should be blocked from sending: Incoming, Outgoing or Both.
  • Description - A friendly name or brief description of the block.

EHLO Domain

  • Blocked Address - This is the return value given when SmarterMail sends the EHLO or HELO command. A standard EHLO domain is the fully qualified domain name set up for the mail server you're wanting to block. (E.g., However, it IS possible that it will be something differnt based on whether the command is sent by the SmarterMail Web interface or an email client. For example, it may be the local IP address of the sending machine. Therefore, there is no well-established rule for what should be entered until some testing is done by the system administrator.
  • Description - A friendly name or brief description of the block.

Note: SMTP blocking does NOT occur immediately when the EHLO command is given. Instead, a "soft" block is used and SmarterMail will fail any authentication attempts or RCPT TO commands. This is because if the failure occurs right after the EHLO commaned, any person attempting to spam from a mail server could figure out what the problem is and change the domain given with the command on each send. A "soft" failure should, instead, make the spammer believe he is using an incorrect password.