Traffic Control


Traffic Service provides server administrator a way to control incoming/outgoing email traffic and preserve CPU and other computer resources. By default, Traffic Service is stopped, and it can be started at Web Access->Service. After the service is started, the time interval for traffic service should be defined, as all email traffic count is based on this time interval. For example, if the time interval is set to 15 minutes and the email count limit from a single user is set to 100, users are not allowed send more than 100 emails in 15 minutes.

Incoming Traffic Control

Incoming traffic rules limit the email traffic from outside IP address to the SMTP service. It doesn't count the email traffic from authenticated user.

Incoming traffic rule syntax:
[IP address (*,? wildcard is supported)]:[Message Count]/[Message Size(MB)]
For message count and message size, 0 means unlimited. You can define multiple rules, every line presents a rule.

Usage Example:

The following rules limit: The email count is less than 100, and the total size of all emails is less than 20MB from 192.168.0.1 in the time interval. The email count is less than 300, and the total size of all emails is unlimited from 127.0.0.1 in the time interval.

192.168.0.1:100/20
127.0.0.1:300

The following rules limit: The email count is less than 100 and the total size of all emails is unlimited from every IP address but it doesn't limit the email from 192.168.0.1.

*:100
192.168.0.1:0

Note: The email count and email size is counted based on recipients count. For example: an email size is 1024KB, but it contains 20 recipients, then it yields 20 email count and 20 * 1024KB = 20MB email size.

Outgoing Traffic Control

The outgoing traffic rules limit the email traffic from authenticated user to outside domain. It doesn't count the email traffic to local domain.

The outgoing traffic rule syntax:
[user email address | domain (*,? wildcard is supported)]:[Message Count]/[Message Size(MB)]
For message count and message size, 0 means unlimited. You can define multiple rules, every line presents a rule.

Usage Example:

The following rules limit: The email count is less than 100 and the total size of all emails is less than 20MB from every user of emailarchitect.com in the time interval. The email count is less than 300, and the total size of all emails is unlimited from test@emailarchitect.com in the time interval.

*@emailarchitect.com:100/20
test@emailarchitect.com:300

The following rules limit: The email count is less than 100 and the total size of all emails is unlimited from every user but it doesn't limit the email from test@emailarchitect.com.

*@*:100
test@emailarchitect.com:0

The following rules limit: The email count is less than 1000 and total size of all emails is less than 100MB from the domain "emailarchitect.com".

emailarchitect.com:1000/100

Note: The email count and email size is counted based on recipients count. For example: an email size is 1024KB, and the email contains 20 recipients, in total it yields 20 email count and 20 * 1024KB = 20MB email size. This rule set doesn't apply to the email to local domain. For example, if user@emailarchitect.com sends an email to user2@emailarchitect.com, the traffic of this email is ignored.

Once the limit is reached, authenticated user can not send email to outside domains, "Too many outgoing traffic" error will be returned by SMTP service or Web Mail when user try to send the email to outside; however, the user can still send email to local domain.

See Also

Quick Tutorial  User Permissions  Domain Administration  User Administration  Services Administration  SMTP Service  POP3 Service  IMAP4 Service  Remote Object Call Service  Webmail Service  SSL Configuration  Realtime Black List  Anti-Spam  Anti-Virus  List Administration  Traffic Control  DBConnector  Mail Archive  DomainKeys and DKIM signature  Storage and User Mailbox   Incoming/outgoing Filters  Advanced Functions in Filter  Templates  

EmailArchitect Server Website
EmailArchitect Server Community