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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
README file for Listar
-----------------------------------------------------------------------
For now, this file assumes you have a modicum of unix experience, it will
get better over time. If you have questions about getting this code set
up and installed on your machine, please feel free to subscribe to the
listar-support@listar.org (send an email to
listar-support-request@listar.org with the word 'subscribe' (no quotes) in
the subject).
Edit the top level makefile to set up configuration settings for your
machine. I'm assuming some type of advanced makefile (ala GNU)
After editing, perform a make in the top level. This will create the
modules and the listar executable.
You probably want to create a listar user/group so that the program runs
as an unpriveledged user. Chmod the listar executable to this user and
make sure this user is a trusted user of your sendmail program. Also make
sure all the list directories have the correct permissions and can be
read/written by the listar user/group.
You'll want to rename the listar.cfg.dist to listar.cfg, if this is a
first time install. The reason for the .dist extension is to prevent a
user from accidentally unpacking over an existing installation and
destroying their previous configurations.
If you want to use the bounce-management on a nightly basis, just add
'listar -procbounce' to your crontab. Similarly, if you want to ensure
the digest processing is handled at a certain time, add the command
'listar -procdigest' to your crontab. Both CAN be omitted; Listar will
then handle it automatically when something is posted to the list after
too long has passed. If you have virtual hosts set up, and choose to use
the -procbounce feature, you will need to set a crontab line for each
virtual host, with the appropriate -c parameter.
To make new mailing lists, you will want to run Listar with the -newlist
parameter. Be sure to run Listar with the full path *as used by your mail
aliases*, for example:
/home/listar/listar -newlist mylist
/etc/smrsh/listar -newlist mylist
You can follow the instructions Listar will give you, and the list will be
generated for you. Listar will spit back the aliases on stdout, for
sendmail-style aliases. Thus, you can do:
/home/listar/listar -newlist mylist >> listar.aliases
And the aliases will be in that textfile. Once you have the aliases in a
valid alias file for your mailserver, run newaliases (or your equivalent)
and it should be ready.
If you have qmail, and use dot-qmail aliases files as opposed to
FastFoward, you can do:
/home/listar/listar -qmail -newlist mylist
Then, Listar will make a 'qmail-aliases' directory under the new list
directory, containing the dot-qmail files (for example .qmail-mylist,
.qmail-mylist-request, and so on). You can copy those to the qmail
aliases directory.
If you have virtual hosts set up, you can pass in the host config file
when doing newlist:
/home/listar/listar -c virthost.cfg -newlist mylist
*IMPORTANT*
If your mail server runs smrsh (sendmail restricted shell), then you will get
errors like the following when you try to send mail to a listar list.
"|/home/listar/listar -s alist"
(expanded from: alist@some.machine.dom)
----- Transcript of session follows -----
sh: listar not available for sendmail programs
554 "|/home/listar/listar -s alist"... Service unavailable
If this is the case, then you need to do some additional setup.
First, find out where your mail server's smrsh directory is. For RH 6.0,
this is /etc/smrsh. For other OS's and MTA's this may be different. Ask
your sysadmin (or if you are the sysadmin, ask the support people for your
OS or MTA where it is).
In that directory, create a shell script containing the following
---->8---- cut here ---->8----
#!/bin/sh
/home/listar/listar $@
----8<---- cut here ----8<----
Of course you should use /your/path/to/listar instead of /home/listar.
Then, all your Listar aliases should be set up as /etc/smrsh/listar (or
whatever the path to the wrapper is) instead of the actual Listar path.
This should be sufficient to make listar work with your MTA.
You *should* now have an operational listar mailing list server.
Please report any bugs to bugs@listar.org so that they can be fixed as
soon as possible. Posts to this address will automatically go into the
Listar bug tracking system (http://bugs.listar.org/listar/).
Please also feel free to submit changes, enhancements, and ideas for
listar as well. Feature requests can be mailed to bugs@listar.org for
addition to the 'Wishlist' section of the Listar database. Please note
that it is a feature request in the message, though. (Ideally, put
SUGGESTION: or REQUEST: at the beginning of the subject line.)
In addition to listar-support@listar.org (open subscription via
listar-support-request@listar.org), there is also be an open mailing list
for developers called listar-dev@listar.org (subscribe via
listar-dev-request@listar.org) which can be used to discuss changes and
implementations of various modules, extensions to existing modules, bug
fixes and the like.
Thank you.
Rachel Blackman (Sparks)
Joseph Traub (JT)
-----------------------------------------------------------------------
As the authors, we'd really like to know about any improvements, fixes,
changes and such that are made to this software so that we can incorporate
them into future versions as well as improve the software over time.
|
