I may have missed some of the nuances here, but it sounds to me like we're
requiring updates to the aliases file(s) in order to support .forward file
functionality. If so, this means the sysadmin will have to manage any
e-mail forwarding instead of the end user.

Regarding the changed you've recommended (set myorigin to the correct name
for the host and set masquerate_domains to the domain name) ... that solved
my problem. For some reason my masquerade_exceptions isn't working, but
that's a lesser issue that I'll investigate on my own. Thank you both for
all your help. You're help has been priceless.

                                                          -Brian

>
> Now I understand. So the .forward "surprise" is there, but the workaround
> is to not shoot yourself in the foot. Just store the ".forward" file
> entries in the aliases file instead.
>
> What if anything from this long thread is useful "don't" material for a
> README or FAQ? Or is the list archive a sufficient repository?
>
> --
> Viktor.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]