masqmail-0.2
view docs/uucp-setup @ 179:ec3fe72a3e99
Fixed an important bug with folded headers!
g_strconcat() returns a *copy* of the string, but hdr->value still
pointed to the old header (which probably was a memory leak, too).
If the folded part had been quite small it was likely that the new
string was at the same position as the old one, thus making everything
go well. But if pretty long headers were folded several times it was
likely that the new string was allocated somewhere else in memory,
thus breaking things. In result mails to lots of recipients (folded
header) were frequently only sent to the ones in the first line. Sorry
for the inconvenience.
| author | meillo@marmaro.de |
|---|---|
| date | Fri, 03 Jun 2011 09:52:17 +0200 |
| parents | 39014fc31dbe |
| children |
line source
1 This document includes UUCP related information
3 Note: My knowledge of UUCP setups is very poor. I hope that the
4 provided information is correct. Improvements to this document
5 are very welcome. --meillo
7 UUCP setups call the MTA as `rmail'. Until version 0.2.23 masqmail
8 could be called with this name. It switched to read-message-from-stdin
9 mode then. AFAIK this is not enough to support UUCP, at least not at
10 the level that is presumed by UUCP software. It seems as if at least
11 the first input line should be handled special as it includes the
12 envelope recipient. (Correct me if I'm wrong.) I discovered that exim
13 has rmail support like this. That's probably the reason why it was
14 the same in masqmail.
16 A better, through still basic approach, was introduced with 0.2.24:
17 misc/rmail is a small shell script (taken from postfix), which calls
18 masqmail with appropriate options. Copy the script into your path and
19 ensure that the included sendmail variable points to the masqmail
20 executable.
22 A more sophisticated rmail implementation seems to be available from
23 sendmail. I don't know details about it and whether it is needed. The
24 difference of sendmail's rmail implementation could be related to
25 address rewriting (user@example.org <-> org!example!user). But I
26 don't know details -- if you do, please let me know.
29 UUCP makes use of the -f (set return path address, i.e. from whom the
30 mail is) option of masqmail which is only permitted for user root,
31 the trusted user (usually `mail'), and the trusted group (often group
32 `mail'). UUCP, however, usually runs as user and group `uucp'.
34 Masqmail currently supports only one trusted group and it is planned
35 to remain so for simplicity reasons. (If you have good arguments on
36 the case, try to convince me of the opposite.) Therefore the solution
37 for masqmail is to add the user `uucp' to the trusted group (often
38 group `mail'):
40 usermod -G mail -a uucp
42 This is not the perfect solution but an acceptable trade-off.
45 If one really needs to enable user `uucp' to set -f but can not add
46 it to the trusted group, see the comment in is_privileged_user() in
47 permissions.c. It shows a hack which allows to trust another group,
48 for instance the group `uucp'.
51 See [1] for reasons why -f is important and needed.
53 [1] http://bugs.hylafax.org/show_bug.cgi?id=842
56 meillo