[Nov 23, 2009 14:09] Web access to Microsoft Live@edu accounts now works.
Privacy settings allow you to configure subscription and membership exposure policy for your list. You can also control whether a list is public or not. See also the Archiving Options section for separate archive-related privacy settings.
Privacy Options
- Subscription rules:
- Privacy options detailed in Initial Options, plus the following options:
- Advertise list when people ask what lists are on this machine:
- Default is No, and it is strongly recommended that this setting stay No. Choosing Yes means the name and address of the list are publicly available to anyone on the internet browsing for list addresses at U.Va.
- Banned addresses:
- As administrator, you may list specific addresses who are banned from ever subscribing to the list. These may be ex-members who routinely abused list privileges, or persons for whom membership in your list is inappropriate. If you are in doubt about the appropriateness of posts or activity of list members, list members should send the offending message(s) along with a note explaining the concern to the list administrator (example address: sample-owner@Virginia.edu); list administrators should send the offending message(s) along with a note explaining the concern to abuse@virginia.edu for advice.
- Obscure membership addresses:
- Default is Yes, which means email addresses of list members are displayed on the web in a format that does not make them easily obtainable by automatic Web crawling agents designed to collect addresses for purposes of spamming them. It is strongly recommended you leave this setting as Yes.
- Sender filters
- Privacy options detailed in Initial Options, plus the following options:
- Action to take when a moderated member posts to the list:
- Default is Hold which means that all messages sent by a moderated member to the list address are held for review before distribution to the members of the list; other options are Reject, which deletes the message without distributing it to the members of the list and sends a rejection notice to the sender of the message and Discard, which deletes the message without distributing it to the members of the list without notifying the sender
- Text to include in any rejection notice to be sent to moderated members who post to this list:
- Default is none; enter whatever text you want to appear in a rejection notice for the list.
- List of non-member addresses whose postings should be automatically accepted:
- Messages sent from any of the addresses specified will be distributed to list members without review/approval by the list administrator, providing all of list criteria are met. Regular expressions can be used to indicate a generic form of an address. For example, the regular expression ^.*@.*virginia.edu will allow anyone whose email address ends with virginia.edu to have their message distributed directly to list members. Warning: regular expressions can cause unintended chaos; use them with great caution.
- List of non-member addresses whose postings will be immediately held for moderation:
- A message to the list from an email address specified in this box will be held for review by the list administrator (hold for moderation). Regular expressions can be used to indicate a generic form of an address. For example, the regular expression ^.*@.*spam.site Warning: regular expressions can cause unintended chaos; use them with caution.
- List of non-member addresses whose postings will be automatically rejected:
- A message to the list from an email address specified in this box will be deleted with notification to its sender of the deletion (rejected). Regular expressions can be used to indicate a generic form of an address. For example, the regular expression ^.*@.*spam.site Warning: regular expressions can cause unintended chaos; use them with caution.
- List of non-member addresses whose postings will be automatically discarded:
- A message to the list from an email address specified in this box will be deleted without notification to its sender (discarded). Regular expressions can be used to indicate a generic form of an address. For example, the regular expression ^.*@.*spam.site Warning: regular expressions can cause unintended chaos; use them with caution.
- Should messages from non-members, which are automatically discarded, be forwarded to the list moderator?
- This option allows the moderator to see the messages that are otherwise deleted without notification.
- Text to include in any rejection notice to be sent to non-members who post to this list.
- This option allows the list administrator to customize the email notice sent to non-members when their email message to the list is rejected
- Recipient filters
- Privacy options detailed in Initial Options plus the following options:
- Alias names (regexps) which qualify as explicit to or cc destination names for this list.
- Entering a regular expression of an email address or alias in this section will allow messages containing a matching address to be accepted for distribution or moderation depending on how the list is configured.
- Ceiling on acceptable number of recipients for a posting.
- If an email message sent to the list has this number, or more, of recipients in the TO:, CC:, and BCC: fields (not the number of list members/subscribers), it is held for approval. Use 0 for no ceiling.
- Spam filters
-
- Filter rules to match against the headers of a message.
- Each header filter rule has two parts, a list of regular expressions, one per line, and an action to take. Mailman matches the message's headers against every regular expression in the rule and if any match, the message is rejected, held, or discarded based on the action you specify. Use Defer to temporarily disable a rule. You can have more than one filter rule for your list. In that case, each rule is matched in turn, with processing stopped after the first match. Note that headers are collected from all the attachments (except for the mailman administrivia message) and matched against the regular expressions. With this feature, you can effectively sort out messages with dangerous file types or file name extensions.
- Hold posts with header value matching a specified regexp.
- Regular expressions entered in this section will be matched against values present in the specified header of incoming messages. The message will be held if a match is found, disregarding letter case.