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
|
The most common problems with BeroList installation
===================================================
1) The list seems to be running - but new users can't subscribe.
================================================================
The source of this problem is, in all probability, that the program cannot
write to the list.members file - Probably, you have not set the permissions
correctly.
With most mailers, you should make the list files owned by bin.bin (user
bin, group bin).
To make sure the problem is not with permissions, make a test run with the
list program running setuid root (chown root.root list; chmod 4755 list).
I don't recommend leaving the program setuid root - I'm not aware of any
security problems caused by it, but I'm rather sure there are some.
Use "make user" if you want to make sure there's no problem with the
permissions.
If you need to find out which user ID the program is running as, create a
log file in a place the list program can't possibly write to (such as a
chmod 0000 file in a chmod 0000 directory, both owned by root). The error
message will contain the program's UID and GID.
2) Everything seems to work - but new users don't get the welcome message.
==========================================================================
Double-Check file permissions. The most common source is that the list
program may not read the file. Most mailers run mail filters like BeroList
as bin.bin.
See (1).
3) I have sender=original in the list.config - but still, all messages
come from a wierd address like bin@somewhere or list@somewhere
======================================================================
Your mailer is paranoid about fake messages. If you're using the old way
(#define USE_SENDMAIL), convert to the new way.
If you have still problems, try using a different SMTP host, or go back to
the 1.x.x way and use sendmail with #define TRUSTED and a Tbin line in the
sendmail.cf file.
4) The list returns MAILER-DAEMON messages all the time
=======================================================
As weird as this response may seem, read the MAILER-DAEMON message. BeroList
includes progress reports in error messages (in the "Transcript of session
follows" section), so you can at least find out where the program broke down.
If the last line in the progress report is something like "Can't write to
blah.log :(", check the permissions of your log files, or undefine LOG in
list.h and recompile.
5) I'm trying to compile on a non-linux system, and I'm getting error
messages when compiling.
=====================================================================
Some parts of the program might not be compatible with other Unixes - the
SMTP handling is most likely to be not portable.
Try recompiling with USE_SENDMAIL defined, and "socket" removed from the
Makefile.
6) The program won't compile...
===============================
The Makefile was written specifically for GNU make. It might not be
compatible with other makes.
7) Messages sent to the list don't get through
==============================================
Make absolutely sure the VERSION string (defined in list.h) does not contain
spaces.
8) The mailer program dies with signal 13...
============================================
There are a lot of possible sources for this problem (signal 13 just means
some program broke down). Make sure you're using a recent version of your
mailer (If you're running sendmail, get 8.8.4 or higher).
If it doesn't help, send a message to berolist@bero-online.ml.org or
root@bero-online.ml.org.
9) Messages to the list don't get through - I've subscribed someone@localhost
=============================================================================
Replace localhost with your hostname.
The member addresses are transferred to the SMTP server the way they are -
so someone@localhost is actually someone@SMTP_SERVER.
10) System administrators of other systems are receiving messages without
being subscribed to the list
=========================================================================
see 9).
11) I've just upgraded from < 2.5.3 to >= 2.5.3 - but the list still reports
it's running < 2.5.3...
============================================================================
As of version 2.5.3, the binaries are installed in /usr/sbin rather than the
list directory itself. Update your /etc/aliases entries, or use
--with-bindir when running configure.
(Now who said it wasn't necessary to check the README file for an upadte...)
12) I have any other problem, or the suggested solution doesn't work...
======================================================================
Send a message to the mailing list (berolist@bero-online.ml.org) or to me
directly (bero@bero-online.ml.org).
If the program doesn't work, compile it with "configure --enable-debugonly;
make". This will generate a version that sends a detailed error message in
reply to every mail sent to the list. Please include that message.
We'll try to find a solution.
|
