|
⇤ ← Revision 1 as of 2008-03-07 16:53:02
Size: 792
Comment:
|
Size: 1280
Comment: Replaced note about sitelist.cfg which isn't relevant.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename SEC/versions/3276854 | #pragma page-filename SEC/versions/3276857 |
| Line 14: | Line 14: |
| To change the way messages from non-subscribers are handled, edit /etc/mailman/sitelist.cfg and change the value of the setting '''generic_nonmember_action''' to 1 (Hold) or 3 (Discard). | The normal default setting for new lists is to hold messages from non-members. If appropriate, you can change this default to discard by putting DEFAULT_GENERIC_NONMEMBER_ACTION = 3 in mm_cfg.py, and of course, you can change generic_nonmember_action for any specific list after it is created. Also, if generic_nonmember_action for a list is hold, you can consider setting the list's respond_to_post_requests to No. There is no configuration setting to make this No by default for new lists. Note however that the number of such autoresponses to a single address is limited to MAX_AUTORESPONSES_PER_DAY which defaults to 10, but can be set as low as 1 in mm_cfg.py. |
Backscatter
PROBLEM: Mailman comes out of the box ready to backscatter spam people.
RESOLUTION:
- Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup.
- Discard or hold messages from non-subscribers by default.
DETAILS:
Removing aliases depends on the installation method.
If using mm-handler, an experimental version is available that can optionally remove support for the problem aliases at http://home.uchicago.edu/~dgc/sw/mailman/mm-handler/mm-handler-2.10.
The normal default setting for new lists is to hold messages from non-members. If appropriate, you can change this default to discard by putting
DEFAULT_GENERIC_NONMEMBER_ACTION = 3
in mm_cfg.py, and of course, you can change generic_nonmember_action for any specific list after it is created.
Also, if generic_nonmember_action for a list is hold, you can consider setting the list's respond_to_post_requests to No. There is no configuration setting to make this No by default for new lists. Note however that the number of such autoresponses to a single address is limited to MAX_AUTORESPONSES_PER_DAY which defaults to 10, but can be set as low as 1 in mm_cfg.py.