1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/docs/uucp-setup	Sat Jun 19 18:53:45 2010 +0200
     1.3 @@ -0,0 +1,54 @@
     1.4 +This document includes UUCP related information
     1.5 +
     1.6 +Note: My knowledge of UUCP setups is very poor. I hope that the
     1.7 +      provided information is correct. Improvements to this document
     1.8 +      are very welcome.  --meillo
     1.9 +
    1.10 +UUCP setups call the MTA as `rmail'. Until version 0.2.23 masqmail
    1.11 +could be called with this name. It switched to read-message-from-stdin
    1.12 +mode then. AFAIK this is not enough to support UUCP, at least not at
    1.13 +the level that is presumed by UUCP software. It seems as if at least
    1.14 +the first input line should be handled special as it includes the
    1.15 +envelope recipient. (Correct me if I'm wrong.)
    1.16 +
    1.17 +A better, through still basic approach, was introduced with 0.2.24:
    1.18 +misc/rmail is a small shell script (taken from postfix), which calls
    1.19 +masqmail with appropriate options. Copy the script into your path and
    1.20 +ensure that the included sendmail variable points to the masqmail
    1.21 +executable.
    1.22 +
    1.23 +A more sophisticated rmail implementation seems to be available from
    1.24 +sendmail. I don't know details about it and whether it is needed. The
    1.25 +difference of sendmail's rmail implementation could be related to
    1.26 +address rewriting (user@example.org <-> org!example!user). But I
    1.27 +don't know details -- if you do, please let me know.
    1.28 +
    1.29 +
    1.30 +UUCP makes use of the -f (set return path address, i.e. from whom the
    1.31 +mail is) option of masqmail which is only permitted for user root,
    1.32 +the trusted user (usually `mail'), and the trusted group (often group
    1.33 +`mail'). UUCP, however, usually runs as user and group `uucp'.
    1.34 +
    1.35 +Masqmail currently supports only one trusted group and it is planned
    1.36 +to remain so for simplicity reasons. (If you have good arguments on
    1.37 +the case, try to convince me of the opposite.) Therefore the solution
    1.38 +for masqmail is to add the user `uucp' to the trusted group (often
    1.39 +group `mail'):
    1.40 +
    1.41 +    usermod -G mail -a uucp
    1.42 +
    1.43 +This is not the perfect solution but an acceptable trade-off.
    1.44 +
    1.45 +
    1.46 +If one really needs to enable user `uucp' to set -f but can not add
    1.47 +it to the trusted group, see the comment in is_privileged_user() in
    1.48 +permissions.c. It shows a hack which allows to trust another group,
    1.49 +for instance the group `uucp'.
    1.50 +
    1.51 +
    1.52 +See [1] for reasons why -f is important and needed.
    1.53 +
    1.54 +[1] http://bugs.hylafax.org/show_bug.cgi?id=842
    1.55 +
    1.56 +
    1.57 +meillo