When using the help you may find that some pages are no longer in their previous location, multiple pages were consolidated into one topic or pages were removed as they were for an advanced setting and not required to get up and running with the product.
Add an Outgoing User
- Click on Outgoing > Manage users.
- In the Add a user panel, choose which type of user you want to add by selecting the relevant tab (Authenticating IP or range, Authenticating user or Authenticating domain (see Manage Outgoing Users for a description of each)).
- Enter the user details and click on Add & Configure.
- Configure the following user settings:
The Outgoing User Settings page is displayed:
- Password - Set the password for the username authenticated outgoing user (not applicable for IP outgoing users).
- Identification Method - Choose from: “envelope sender”, “authentication user” or “Header” as the identification method:
- Automatic lock - When enabled, and when the system detects that the user has sent approx 5 spam messages in 10 minutes, the user will be locked automatically. The user cannot send mail until they are unlocked (the administrator can do this from the alert sent or from the Manage Outgoing Users page.
- Lock Identities Automatically - This spam prevention, when enabled and the system detects that the identity has sent approx 5 spam messages in 10 minutes, the identity will be locked automatically. The identity cannot send mail until they have been unlocked. The identity can be unlocked from the Manage Identities page.
- User and Identity Lock timeout - The amount of time an outgoing user or identity will be unable to send messages. This only applies to if you are using the Automatic User Lock or the Automatic Identity Lock.
- Maximum unlocks by timeout - The maximum number of times the user will be automatically unlocked after the time-out value has passed. After this has been depleted, the user will have to be manually unlocked.
- Enable outgoing connection limits - Enable or disable limits on outgoing connections whether spam or not, to prevent bulk mailing.
- Limit per month - The amount of outgoing connections that can be opened per month.
- Limit per week - The amount of outgoing connections that can be opened per week.
- Limit per hour - The amount of outgoing connections that can be opened per hour.
- Limit per minute - The amount of outgoing connections that can be opened per minute.
- Valid Sender Address Required - (Available at Admin Level only) When enabled, the filtering servers do a 'null sender' callout to verify the sender. This means that the filtering server will connect to the sending address mailserver, using a sender of "<>" (as a bounce message does), and the specified sender as the RCPT To. After checking the sender, the connection will be properly closed (i.e. no message is actually sent). This is a good way to stop spammers and we recommend having this option enabled.
- DKIM Selector- Choose the selector you wish to use at domain level. Use the default or add one that has been generated using the DKIM Certificate Generation tool. Once you have created the certificate you need to add the TXT to your DNS.
- Maximum number of recipients per day - The maximum number of recipients the user can send emails to daily.
- Invalid Recipient limit - The limit for sending emails to invalid recipients (not applicable at Domain Level).
- Maximum days to retry - The maximum number of days the message will be retried for delivery (this applies to messages stuck in the delivery queue) (not applicable at Domain Level).
- Quarantine Response – When an outgoing message is detected as spam and it goes into the outgoing quarantine the response you send back to the sender can be Rejected or Accepted. If 'Rejected', legitimate senders will receive a bounce message when their mail gets blocked and quarantined even though the message is stored in the quarantine. If 'Accepted' the SMTP response would be ‘Accept’ and the message would still be blocked and shown in the quarantine but the sender will not receive a bounce message and will not know that the message is in the outgoing quarantine.
- Message archiving for senders - Enabled/Disabled – If enabled, all outgoing messages from the outgoing user will be archived. If this is disabled, no outgoing messages will be archived. See Ensure Archiving Option is Selected for Outgoing Mail.
|Envelope Sender||Use this if your system enforces the “envelope sender” (or MAIL FROM value). This is typically used by Spam Experts users.|
|Authentication User||The outgoing user’s authentication details. This is the best choice when you are providing unique usernames and passwords for each outgoing user, rather than using a smarthost system.|
If you choose this option, you are able to add any number of identification headers that we should search for in the message. For example, you might have a system that adds an “X-Client-ID” header, which uniquely identifies each of your end users. For each header, you may choose to either use the entire header value as the identity, or you can provide a regular expression that extracts out a part of the value to use. You may also choose to have our software remove the header after we have found the identity, if you don’t want this to be available to the recipient of the message.
We strongly recommend that an identity Header is set for all outgoing traffic. This makes monitoring and taking action against spammers much easier.
We recommend that you do not enable the Automatic lock if you are using IP authentication within a smarthost.
The administrator will be notified that there are messages in the outgoing quarantine in the Abuse Report by entering the Adminstrator's contact email address in the Outgoing > Settings page in the Domain Level Control Panel (see Configure the Abuse Report Address). Alternatively, use the Email Scout Reports to create a schedule report with details of outgoing quarantine content.
Tip - Administrators may use this option to prevent the sender receiving notifications when messages are quarantined. For example, they may want to review a rejected message before releasing it.