meillo@88: This document includes UUCP related information
meillo@88: 
meillo@88: Note: My knowledge of UUCP setups is very poor. I hope that the
meillo@88:       provided information is correct. Improvements to this document
meillo@88:       are very welcome.  --meillo
meillo@88: 
meillo@88: UUCP setups call the MTA as `rmail'. Until version 0.2.23 masqmail
meillo@88: could be called with this name. It switched to read-message-from-stdin
meillo@88: mode then. AFAIK this is not enough to support UUCP, at least not at
meillo@88: the level that is presumed by UUCP software. It seems as if at least
meillo@88: the first input line should be handled special as it includes the
meillo@90: envelope recipient. (Correct me if I'm wrong.) I discovered that exim
meillo@90: has rmail support like this. That's probably the reason why it was
meillo@90: the same in masqmail.
meillo@88: 
meillo@88: A better, through still basic approach, was introduced with 0.2.24:
meillo@88: misc/rmail is a small shell script (taken from postfix), which calls
meillo@88: masqmail with appropriate options. Copy the script into your path and
meillo@88: ensure that the included sendmail variable points to the masqmail
meillo@88: executable.
meillo@88: 
meillo@88: A more sophisticated rmail implementation seems to be available from
meillo@88: sendmail. I don't know details about it and whether it is needed. The
meillo@88: difference of sendmail's rmail implementation could be related to
meillo@88: address rewriting (user@example.org <-> org!example!user). But I
meillo@88: don't know details -- if you do, please let me know.
meillo@88: 
meillo@88: 
meillo@88: UUCP makes use of the -f (set return path address, i.e. from whom the
meillo@88: mail is) option of masqmail which is only permitted for user root,
meillo@88: the trusted user (usually `mail'), and the trusted group (often group
meillo@88: `mail'). UUCP, however, usually runs as user and group `uucp'.
meillo@88: 
meillo@88: Masqmail currently supports only one trusted group and it is planned
meillo@88: to remain so for simplicity reasons. (If you have good arguments on
meillo@88: the case, try to convince me of the opposite.) Therefore the solution
meillo@88: for masqmail is to add the user `uucp' to the trusted group (often
meillo@88: group `mail'):
meillo@88: 
meillo@88:     usermod -G mail -a uucp
meillo@88: 
meillo@88: This is not the perfect solution but an acceptable trade-off.
meillo@88: 
meillo@88: 
meillo@88: If one really needs to enable user `uucp' to set -f but can not add
meillo@88: it to the trusted group, see the comment in is_privileged_user() in
meillo@88: permissions.c. It shows a hack which allows to trust another group,
meillo@88: for instance the group `uucp'.
meillo@88: 
meillo@88: 
meillo@88: See [1] for reasons why -f is important and needed.
meillo@88: 
meillo@88: [1] http://bugs.hylafax.org/show_bug.cgi?id=842
meillo@88: 
meillo@88: 
meillo@88: meillo