Configuration Settings Specific
to DList:
This page details only those
dmail.conf settings which apply specifically to DList.
For more settings see: DMail Config File, DSMTP settings and DPOP settings
NB: You must make DSMTP reload after changing
DList lists so that it can create the aliases that it needs for the lists (check for
them in the file aliases.dml in the work directory).
Sections on this page . . .
General settings for DList are contained in dmail.conf, list.
Specific settings are stored in lists.dat in the dlist_path
directory. You can directly edit dmail.conf and lists.dat in a
text editor or use the management utility DMAdmin.
As with dmail.conf, all settings are one per line, and you can exclude
a line by starting it with the # character. You do not need to reload the
DList server after making changes to dmail.conf (as you do with DSMTP and
DPOP), as DList automatically checks the dmail.conf and the lists.dat files
before each check for list messages.
To review the list of commands able to be sent
directly to lists by users, moderators and of course the DList
server manager, look at the
DList mail commands
page. This is the page that is sent to users when they join a list.
An example lists.dat file with entries for two lists,
talk and juggling:
Setting |
Default |
Description |
dlist_path |
(none) |
The directory for lists.dat and all DList work files,
log file, and list archiving |
dlist_domain |
host_domain |
The default @xxx address for messages from DList |
dlist_loglvl |
info |
Logging level (debug,info,warn,error) |
dlist_rotate |
50000 |
Size of log file in bytes before it is rotated (default and
minimum value is 60 kbytes) |
dlist_smtp_host |
127.0.0.1:3025 |
DList will ALWAYS send out messages to the ip address,
127.0.0.1, but you
can use this setting to set the port that it talks on by
following the ipaddress with a colon followed by the port number that
your smtp server is running on. |
dlist_names |
??? |
??? |
dlist_web_abs |
??? |
??? |
dlist_web_rel |
??? |
??? |
Note: Access settings can generally take one of the following settings,
- member - refers to list members and in general the list moderator as
well
- anyone - no restriction
- moderator - only the list moderator can do it
- *domain - the person trying to do it must have the email address
ending in 'domain'
Setting |
Default |
Example |
Description |
access_join |
anyone |
*netwinsite.com |
Controls who can join the mailing list |
access_leave |
anyone |
in version 2.5d (2.4k) and above:
members: (can unsubscribe themselves, moderator can unsubscribe anyone)
moderator: (only moderator can unsubscribe - members cannot
unsubscribe themselves) |
Controls who can unsubscribe from the mailing list,
by default anyone can unsubscribe anyone else. |
access_post |
members |
moderator |
Controls who can post messages to the mailing list |
access_who |
members |
anyone |
Controls who can retrieve the list of current members |
archive |
false |
true |
If set, DList will record all incoming messages in an
'archive' sub directory, off the list's directory. |
footer (version 2.4h and above) |
(none) |
footer
c:\dmail\dlist\listname\footer.txt |
The full path to a file that you want added onto the
end of all messages as a footer. |
from_list |
???? |
from_list ???? |
????? |
join_cookie |
false |
true |
If set, when users join the list they will be asked to respond with a specific cookie
(number) to prove that they are real humans. This setting prevents people from subscribing
other people, or worse, other lists to an existing list. |
list |
(none) |
dnews-discussion |
The name of the list. This cannot contain spaces, and
must be the first setting for each new list in lists.dat |
max_size |
40K |
100K |
Limits the maximum size of an item that can go
through the mailing list. You should follow the
number value with a units multiplier, e.g. k, Mb etc. |
max_per_user (2.4g and above) |
200 (changed from 50 in vers. 2.5d) |
1000 |
Sets the max number of messages allowed to be
posted to all lists on the server per user per hour.
Note: 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 (the default is 200). |
moderator |
(none) |
fred@netwinsite.com |
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 or tabs (or commas in version 2.5d and above) |
reply_to_user |
false |
true |
If set, 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. |
status_interval |
7 |
1 |
Period in days between automatic status reports being
sent to the moderator. |
skip_mailer_check |
false |
TRUE |
If TRUE, DList will not ignore messages
from users called, MAILER-DAEMON (all in capitals). These are
normally bounced messages and so would not normally be wanted
as posts to the list. |
skip_postmaster_check |
FALSE |
TRUE |
If TRUE, DList will not ignore messages
from users called, POSTMASTER (all in capitals). These are
normally bounced messages and so would not normally be wanted
as posts to the list. |
subject_prefix |
(none) |
Juggle: |
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 |
(none) |
N.Z. Juggling |
A title for the list, shown in headers and lists
output. |
Settings still to document:
path, access_put,
access_get, access_overwrite,
bounce_remove,
domain,
invisible,
password, from,
list_global |
???? |
???? |
???? |
Creating a Mailing List
To create a mailing list on the list server DList, you need to
add a new list setting in the lists.dat file, e.g.
list listname
where listname is the name of the list. You can edit the lists.dat
file with a text editor (e.g. notepad or vi). Alternatively, the windows administration
tool DMAdmin will edit the file for you if you
use the "Mailing Lists" button.
If you are doing it manually, add any
other settings that you require for your list below the list setting , e.g.
title title of my list
Then RESTART the DSMTP server with DMAdmin. You must restart DSMTP
after changing DList lists so that it can create the aliases that it
needs for the lists.
In order to try out the list, you should add a user to the list and then post a
message to the list. For information on this, see
Adding Users to a List
DList Email Commands
Welcome Messages
DList comes with an example welcome message. It is stored in a file
called join.tpl in a template format.
You can edit this template to the look that you require, and you can
copy it to each list's directory (off the main DList directory) so
that individual lists can have their own welcome message.
The template can use the following template variables, which will be
replaced by DList with the appropriate information. A template variable
is parenthesized with double percent signs, e.g. %%variable%% so that
DList can recognize it as a variable.
%%list-name%% | BigList | The name of the list. |
%%list%% | biglist@domain.com | The address that list
members send messages to post on the list. |
%%list-request%% | biglist-request@domain.com | The
address that people send list request messages to, e.g. in order
to subscribe. |
%%h_user%% | bob | The username of the 'person' who
has joined the list. |
Adding users to a list
Usually, users would add themselves to a list by sending a
message to the list request address, e.g. listname-request@domain
with the word subscribe in the message body.
DList will then add them to the users.lst file for that list.
Users.lst for each list is stored in that list's directory (named
after the list), off the DList directory (probably \dmail\dlist\listname\users.lst
or /usr/local/dmail/dlist/listname/users.lst )
To add a number of users you have two options:
- Add yourself as a moderator for the list and send the listname-request
address a message with multiple subscribe lines in the body.
So, as a moderator, you send the following email:
To: listname-request@domain
From: your_moderator_address
subscribe bob@domain1.com
subscribe judy@domain1.com
subscribe george@domain99.com
to join up the email addresses,
bob@domain1.com
judy@domain1.com
george@domain99.com
- Directly edit the users.lst text file for the list and add the email
addresses, one per line.
So, to add the same three users, you might edit the users.lst file to
look like this:
u:tam@1.2.3.4 f:Tam Willacy p:0 t:0
bob@domain1.com
judy@domain1.com
george@domain99.com
where the first line is an existing user on the list.
Don't worry about the format of lines for existing users. The next
time that DList has to write anything to the users.lst file
it will add the email addresses that you have pasted/typed in correctly.
Moderated lists
This is still being written :-)
There are two ways of posting into a moderated list, depending on
whether the access_post setting is set to Password or Moderator:
- Password: DList accepts the message from the user and sends it
to the
moderator, who, if they want to approve it, then submits it to the list
with the first line of message body being
approve Password
e.g.
approve xxxx
For this to work, the access_post setting for the list
in lists.dat
must be set to 'Password' and the list password setting must
match the password given in the approve line, e.g.
access_post Password
password xxxx
- Moderator: The return address of the incoming message matches
that of
the moderator setting and the access_post setting is set to
Moderator in the lists.dat file, e.g.
access_post Moderator
moderator moderator@domain
where moderator@domain is the address that must match.
Notes:
- There must always be a moderator for a list set to password post access
because password is a more secure moderated list.
Archives and Files
This is still being written :-)
DList lists can be set to save an archive of all messages by setting the
list specific setting in lists.dat,
archive true
If this is set, DList will create the archive messages in a subdirectory
called, 'archive' below the list's directory, e.g.
c:\dmail\dlist\listname\archive\1.msg
c:\dmail\dlist\listname\archive\2.msg
etc.
Then if the user sends an email to the listname-request address with the
command 'dir' in the message body, then DList will send
back a message telling the user how many archived messages there are.
If the user wants one of the messages, they can send the
'get' command to fetch the archived message.
If you want to provide other files to the list members, you
create your own directory off the list's directory called 'files' and
put the files that you want to provide there, e.g.
c:\dmail\dlist\listname\files\picture.jpg
Then when the user does a 'dir' command, they will also be shown a list
of other files available.
For details on the list commands see,
DList Email Commands
|