Utilities: Administration: Server: Server Settings: Security: Bans
Mail Receive Rules
Defines the rules by which ListManager determines whether or not mail should be processed.
By default, ListManager looks at the username of email it receives to determine whether it should process the message. The host name portion of the mail address is not consulted. It does this to support any number of virtual hosts without needing to be configured. By default, ListManager will automatically assume the hostname identity of any email it receives which is addressed to a valid ListManager user name.
This Mail Receive Rules option allows you to change this default behavior, so that ListManager first looks at the rules you have defined, and if the local recipient address does not match a rule, the message is not processed.
The Mail Receive Rules are simple text search rules. For example, to accept any mail addressed to the "yourcompany.com" domain, the rule would be:
yourcompany.com
This would allow any of these different addresses to be received:
lyris@yourcompany.com
lyris@lists.yourcompany.com
lyris@discussions.yourcompany.com
But any address which did not have "yourcompany.com" in it would be rejected.
If your rule was "@yourcompany.com", only the first example above "lyris@yourcompany.com" would be accepted.
The most common use for this feature is if you are using ListManager in front of another mail server, and you want to make sure that ListManager only accepts mail addressed to itself, and forwards on any mail addressed otherwise. If you have told it to "Forward non-ListManager Mail" to another location, any mail which does not match a "Mail Receive Rule" will automatically be forwarded on to the other server. See Utilizes: Administration: Server: Server Settings: Network Settings: Receive Email.
If you do not have "Forward non-ListManager Mail" defined, then mail which does not match a Mail Receive Rule will simply be rejected.
You can define multiple Mail Receive Rules, each on a separate line.
Ban All Mail From
This option allows you to reject any incoming mail from specific addresses. For example, if a user is a troublemaker, you can have ListManager automatically reject any postings from this person.
Note: This mail from: value applies to the SMTP transaction MAIL FROM: <> value. In email messages, this is usually, but not necessarily the same as the From: in the mail you receive. ListManager displays the MAIL FROM: <> value in any message it receives in the Return-Path: header line. Most other mail servers follow this convention as well.
You can use this feature if a user has threatened to mail bomb you and you want to protect your server from them. Mail bombing is the tactic of sending hundreds of messages to someone, in the hopes of overwhelming them, or their server, and wasting their time. If you ban someone's email with this technique, ListManager will not even accept their messages over SMTP, and the amount of processing it does for each message is extremely small, thus defusing the power of their mail bomb.
You can specify as many email addresses as you like, by putting each address on a separate line.
For example:
bob_mischief@example.com
jane_trouble@elsewhere.com
Banned Members
This setting tells ListManager to deny subscription requests and postings from these people for any list on the site. If a banned person tries to join any list on this site, they will be rejected.
This feature works by matching the text patterns that you specify matched against the entire From: line that includes both the person's email address and their name.
If any text pattern matches, the person is banned. For example, if you wanted to ban all members from "trouble.com", you would type:
trouble.com
If you wanted to ban the email addresses "jane@trouble.com" and "bob@trouble.com" you would enter these email addresses on two separate lines:
bob@trouble.com
jane@trouble.com
If you wanted to ban a person named "Jane Trouble" and "Bob Mischief" you would type:
Jane Trouble
Bob Mischief
Note: This would ban any person whose name is matched, regardless of their email address.
There is a "not contains" feature which is activated by placing a tilde, a "~" at the beginning of the line. In the above example, to ban everyone except email addresses from "mycorp.com", you would type:
~@mycorp.com
However, you are encouraged to use the Accepted setting rather than the tilde notation. The tilde notation is confusing when multiple values are put in, whereas the "Accepted" feature is much more straightforward to comprehend.
Accepted Members
This setting tells ListManager to allow subscribe requests and postings ONLY from these people to lists on your site. If an accepted person tries to submit a posting or subscribe to your list, they will always be allowed. Everyone else will be rejected.
This feature works by matching the text patterns that you specify matched against the entire From: line that includes both the person's email address and their name.
If any text pattern matches, the person is accepted. For example, if you wanted to accept all members from "doright.com", you would type:
doright.com
If you wanted to accept the email addresses "jane@doright.com" and "bob@doright.com" you would enter these email addresses on two separate lines:
bob@doright.com
jane@doright.com
If you wanted to accept a person named "Jane Doright" and "Bob Benevolent" you would type:
Jane Doright
Bob Benevolent
Note: This would accept any person whose name is matched, regardless of their email address.
Please also note that Accepted Members takes precedence over Banned Members. Thus, if you want to allow some people from "doright.com" but not everyone you would put the following entries in Accepted:
Bob@doright.com
Jane@doright.com
Then, you would put the following entry in Banned:
Doright.com
More
1. Utilities: Administration: Server: Server Settings
1. Utilities: Administration: Server: Server Settings: Security: User Limits
2. Utilities: Administration: Server: Server Settings: Security: Bans
3. Utilities: Administration: Server: Server Settings: Security: GUI Hosts
|
|