| Subject Prefix |
This string will be added to the front of
every subject line of messages from this list, this makes it easy for
people to sort list messages out from other messages. |
| Title |
A title for the list, shown in headers and
lists output. |
| Moderator |
A list of one or more moderator email
addresses, a moderator often has extra access rights, like the ability
to subscribe other people etc. Separate multiple entries with spaces,
tabs or commas, emails are only sent to the first moderator in the list,
but any moderator can send moderated messages. |
| Password |
The password used for moderating. |
| Maximum Users |
Maximum users allowed on this list.(default
unlimited) |
| Reply to User |
If set to true, the reply-to header in each
message will be pointed to the original poster, rather than the mailing
list, this is recommended for large mailing lists. In place of true you
can specify an address as the reply address for ALL messages posted to
the list. If given, posted messages will have any Reply-To: header
turned into X-Reply-To:, and the address given is added to a new
Reply-To: header. |
| To User |
If true then the To: address in each
message sent will be the users email address instead of the list name. |
| Access Join |
Controls who can join the mailing list,
valid settings are anyone, member, moderator, or a wild card string that
must match the username. |
| Access List |
Controls who can see this list when a list
command is sent to the server, valid settings are anyone, member,
moderator, or a wild card string that must match the username. |
| Access Leave |
Controls who can unsubscribe from the
mailing list. anyone=anyone can unsubscribe anyone else. member=members
can unsubscribe themselves, moderator can unsubscribe anyone.
moderator=only moderator can unsubscribe members. |
| Access Post |
Controls who can post messages to the
mailing list, valid settings are anyone, member, moderator, or a wild
card string that must match the username. |
| Access Who |
Controls who can retrieve the list of
current members, valid settings are anyone, member, moderator, or a wild
card string that must match the username. |
| Auth Moderator |
STRONGLY recommended for all lists where
the moderator is a local user. Requires that the moderator uses smtp
authentication to prove they are genuine. |
| Auth Who |
STRONGLY recommended for ALL lists. Only
allow who requests from local authenticated users. |
| Moderate via Web |
Allows the moderator to moderate the posts
to the list via this web interface. |
| Max Size |
Limits the maximum size of an item that can
go through the mailing list in kbytes. NB: this setting applies to
messages to the -request address as well as the posting address. |
| Max Per User |
Sets the max number of messages allowed to
be posted to all lists on the server per user per hour. Note that the
count is per user for posts to ALL lists, whereas the setting is per
list. So the count is global but whether it applies to a list is list
specific. |
| Status Interval |
Period in days between automatic status
reports being sent to the moderator. |
| Archive |
If set, all incoming messages will be
recorded in an 'archive' sub directory, off the dlist directory. |
| Web Archive |
If set, allows people to view the list
archive via the
web interface |
| Web Hide Email |
If set, hides the email addresses of
posters to prevent address harvesting by spammers. |
| Join Cookie |
If set, when users join the list they will
be asked to respond with a specific cookie (number) to prove they are
real humans, this setting prevents people from subscribing other people
or worse other lists to an existing list. Note: a cookie will not be
sent if the subscriber is a moderator or if access_join for the list is
set to moderator or password. |
| Join Cookie Template |
Use a specified template for the 'Join
Cookie' message. |
| Allow IP |
A wildcard list of ip's that are allowed to
post to list any others will be rejected. |
| Bounce Remove |
If set, then DList will log all bounces
that it receives, and if it can work out that the bounce was because of
a permanent error, then it will remove that address from the mailing
list. DList will also send a summary email to the moderator each day
recording any addresses it has removed from the list and the bounce
error that was the reason for the removal. This is a new 'beta' setting
so let us know how it goes if you try it. You might like to try, the
log_bounce setting as a first step to turning on this setting. |
| Log Bounce |
This is a debugging setting, that may be
more generally useful. It causes dlist to log all addresses that bounce
and the reason for the bounce to the file, bounces.log, in the list home
directory. The log is appended to for every bounce received when sending
any messages to the list. See also 'bounce_remove'. |
| No Processed Message |
This setting is very powerful. If set to
'true' for a particular list, no command processed messages are sent by
DList for that list. This means that users will only see list posts;
they will get no response to any DList commands they send (i.e. who,
lists etc.). This would only really be useful if you wanted to subscribe
users to a list without them receiving notices. |
| No Welcome Message |
By default, DList sends a welcome message
to each user directly after that user successfully subscribes to a list.
If set to 'true' for a particular list, then users subscribing to that
list will not be sent a welcome message. |
| Strip Headers |
List of headers to strip from messages. |
| Post Members Only |
Only allow posts to the moderator from
members of the list. |
| Moderator Instructions Hide |
Remove moderator instructions in posts sent
to moderators. |
| Hide Sender |
Try and remove any identification (from,
sender, etc from the message. |
