Hi Thomas,
i don't use .forward(5) and am not sure whether what you say
is true or false, but the form is definitely not ok.
Thomas de Grivel wrote on Tue, May 31, 2011 at 08:15:28PM +0200:
> --- forward.5.~1.9.~ Wed May 4 17:24:22 2011
> +++ forward.5 Tue May 31 19:53:17 2011
> @@ -35,8 +35,8 @@
> Multiple entries may be specified on one line, comma separated.
> Additionally, a copy of all mail may be retained
> on the local machine using a
> -.Dq \euser
> -entry.
> +.Dq \eUSER
> +entry where USER names a valid user on the local machine.
1. I guess you want to say that the string "user" has to be
replaced by some other string. Expressing that by all caps
is not ok.
2. Probably, "user" should be marked up as .Ar (argument),
which is the macro used for such purposes, like in
In place of an e-mail address,
.Dq \e Ns Ar user
may be used to deliver a copy of the message to the specified
.Ar user
account on the local machine.
> .Pp
> .Pa .forward
> files must not be group or world writable.
> @@ -55,7 +55,7 @@
> # empty lines are ignored
> # #@# with whitespace on both sides may be used to start a comment
>
> -f...@bar.baz.com, \euser #@# is a comment anywhere
> +f...@bar.baz.com, \efoo #@# is a comment anywhere
> "| /usr/local/libexec/slocal -user foo"
> .Ed
> .Sh SEE ALSO
Not sure about that one.
If i understand correctly what you are trying to say,
that explicitly does *not* need to be "foo", but might
by some other user, right?
Besides, i'm not sure this manual is maintained here at all.
Isn't it part of the sendmail distribution, that is,
shouldn't it be maintained upstream?
Even if we do maintain it in tree, there are more serious
problems with this manual:
- It should say that all this only works if the MTA is configured
to look at .forward files, which may not be the case.
- What is "the name of a private incoming mailer"?
That is utterly incomprehensible.
- What happens if a .forward file is world writeable?
I assume it will be ignored?
- EXAMPLES should not contain new material, but...
well, examples.
Comments should be explained in the DESCRIPTION.
Pipes should be explained in the DESCRIPTION.
To sum up, this manual is in dire need of a rewrite.
Yours,
Ingo
