On Wed, Nov 25, 2009 at 11:56:41AM -0500, Dennis Putnam wrote:
> Thanks, that clears up a few things. It appears that this applies to
> individual users via the $name parameter.
There is no "$name" parameter. That is a generic place-holder for any of
the parameters above it, to explain that you can use ${extension?foo}
or ${extension:bar} (for example) to handle the case when there is
(or is not) an address extension.
> It is not clear how to handle
> many users (surely I can't list everyone) which may be on different
> servers. Is there a wild card format and/or a default?
What do you mean "on different servers"? The forward_path specifies
a local file on the Postfix server's filesystem which contains
the ".forward" content for each user. Various ${parameters}, as part
of this setting, make the path user-dependent.
> Can the path be set to a mounted filesystem that contains the user
> home directories? If no mount, how does the user create/maintain the
> .forward file in that alternate location?
If you want users to edit their own .forward files with "vi", "emacs",
"ed", ... Give them home directories on the mail server, use NFS if
that's sufficiently reliable, and the security risk is acceptable.
[ Please don't top-post, and reply to each paragraph in-line with the
original text "quoted" with "> ", as above ].
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[email protected]?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
