Qmail documentation fix (was: RT and dotqmaildashext)

[Cc’ing -users because I posted there originally.]On Tue, Jan 29, 2002 at 12:17:03PM -0500, Rich Lafferty (rich+rt@lafferty.ca) wrote:

Does anyone recall why ~alias/.qmail-QUEUENAME with
"|/path/to/rt-mailgate" in shouldn’t work?

As it turns out, the “problem” mentioned in the documentation is
historical; ~alias/.qmail-foo aliasing works fine (but requires
preline to turn qmail-command envariables into the appropriate
headers).

IMPORTANT: Current rt and qmail users MUST use preline to pipe
mail to rt-mailgate to add a valid Return-Path to the message.

Jesse, here’s a replacement blurb for the qmail section of the
installation instructions:

-----8<----- cut here -----8<-----
qmail

Users of qmail will need to set up qmail aliases in ~alias/. For
example, to direct mail sent to support@example.com to the "support"
queue as correspondence, put the following in ~alias/.qmail-support:

| /var/qmail/bin/preline /path/to/rt2/bin/rt-mailgate --queue support --action correspond

To direct mail sent to support-comment@example.com to the "support"
queue as comments, put the following in ~alias/.qmail-support-comment:

| /var/qmail/bin/preline /path/to/rt2/bin/rt-mailgate --queue support --action comment

Keep in mind that rt-mailgate will be running with UID “alias”; if you
have configured RT to log to a directory other than /tmp, you must
ensure that that directory is writeable by the “alias” user.
-----8<----- cut here -----8<-----

Also, the section “make install” reads:

If this is a new installation, create a group called ‘rt’. Note that
if you plan to use Qmail as your mailserver, you will also need to add
a user called ‘rt’.

The last sentence is incorrect and can be struck.

ObDJB: The path to preline is rigidly defined in the qmail
specification and doesn’t need to be “/path/to”'d like the path to
rt-mailgate does. Also, for the section heading, “qmail” has a
lowercase “q”.

That blurb doesn’t address virtualdomains, but users using
virtualdomains and users/assign will have a sufficiently complex local
configuration that they’ve already had to figure out how to configure
virtualdomains and users/assign – so for the sake of simplicity I’ve
omitted it entirely. The sendmail and exim instructions omit
domain-specific configurations as well.

Cheers,

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html
rich@lafferty.ca -----------±----------------------------------------------