forked from jasontibbitts/majordomo
-
Notifications
You must be signed in to change notification settings - Fork 1
/
README.QMAIL
59 lines (44 loc) · 2.65 KB
/
README.QMAIL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
This is a skeleton document containing what the author knows about qmail
(which isn't much). Please feel free to submit embellishments and
corrections.
qmail supports two (perhaps more?) methods of routing mail to Majordomo for
a particular domain. A call to Majordomo can go in the .qmail-default file
(the simplest, preferred method) or you can make several .qmail files for
each list and place them in the proper directory. Majordomo supports the
former method automatically.
Majordomo receives messages via a single mj_enqueue command. When given the
-Q option, mj_enqueue examines the contents of the LOCAL environment variable
and figures out what it should be doing. If it sees that the address is
bound for some Majordomo-run address is does the appropriate processing and
does one of two things:
if the -S option was given, it will 'exit 99' to stop processing of further
lines in the .qmail-default file
if the -S option was not given, it will 'exit 0' and qmail will continue
to process other lines in the .qmail-default file
The -S option may make it possible for Majordomo to coexist with other
programs that make use of the -default mechanism.
So, for the virtual domain example.com with Majordomo responding to
[email protected], placing the following in the .qmail-default
directory:
| /usr/local/majordomo/bin/mj_enqueue -d example.com -S -Q majordomo
is sufficient to enable the list manager.
About automatic configuration:
During the configuration process, if Majordomo is told that it is running
under qmail it will ask if it should set up the necessary .qmail-default
files itself. If so, it will prompt for the location of the qmail
directory for each domain and will create .qmail-default files there unless
those files already exist and contain lines that Majordomo doesn't
recognise (in which case it will do nothing).
If you elect not to have Majordomo maintain the .qmail-default files, you
can do so yourself. If you elect not to use the -default mechanism at all
you must instead make .qmail files for each list, -request and -owner
address at your site.
Special note about the 'whoami' configuration variable:
A very small amount of functionality is lost because of this extremely
simple setup mechanism. This is necessary because the decision about
whether or not an address is bound for Majordomo must be done as quickly as
possible; there is no time to start up the full Majordomo system to extract
configuration information. Thus the value of the 'whoami' variable must be
passed on the command line (via '-Q') and if it is changed later (through
the normal Majordomo configuration mechanism) the .qmail-default file must
be edited to match.