On 26/02/16 08:57 AM, Viktor Dukhovni wrote:
On Fri, Feb 26, 2016 at 08:16:43AM -0800, Jack Bates wrote:Hmmm ... That is what's happening, but why's there no user context? I expected the first case ("the rights of the receiving user on whose behalf the delivery is made") vs. the second ("the absence of a user context").Entries in /etc/aliases that happen to have the same name as a user in /etc/passwd are not presumed to have the privileges of that user account. For the latter, you need a ".forward" file belonging to the user. Local aliases(5) are processed before user accounts are looked up, and in many deployments after alias expansion local mail is delivered via a "mailbox_transport", and no user accounts are involved at all.
Gotcha. Switching from /etc/aliases to a .forward file is working for me. In my case it makes no difference that the .forward file is owned by the user because the user doesn't have shell access to the server. If it were an issue, I'm sure there's a more complicated way to keep the user from editing the configuration.
Thanks!
