| Main Archive Page > Month Archives > postfix-users archives |
Re: Forwarding emails, quick question
From: Brian Pribis <brian_at_nospam>Date: Thu Sep 23 2010 - 14:11:51 GMT
To: postfix-users@postfix.org
O.k., I figured it out. I think. Problem wasn't with the MUA, or
postfix (which I knew), or the configuration. It was with me (who
would have thought?). Apparently what I am seeing is normal for
MTA's and aliases. At least, it works the same for sendmail and
postfix. I hadn't realized that. I assumed I had configured something
wrong.
Thanks for all your help!
brian
On Wed, Sep 22, 2010 at 6:00 PM, mouss <mouss@ml.netoyen.net> wrote:
> Le 22/09/2010 14:40, Brian Pribis a écrit :
>>
>> Victor,
>>
>> On Tue, Sep 21, 2010 at 10:39 AM, Victor Duchovni
>> <Victor.Duchovni@morganstanley.com> wrote:
>>>
>>> On Tue, Sep 21, 2010 at 08:36:49AM -0400, Brian Pribis wrote:
>>>
>>> complain to the provider of your MUA.
>>>
>>> In any case, this thread is closed, the issue has
>>> NOTHING to do with Postfix. You can explore the semantics of your MUA
>>> in another forum.
>>>
>>
>> Seriously? You are suggesting I contact gmail, mozilla and the
>> creators of the mail program on my freebsd machine?
>
> Brian, with all due respect, you're being too aggressive. let's try to start
> again:
>
> - aliases and virtual aliases only change the _envelope_ recipient. This has
> no influence on headers. if you believe it doesn't work that way for you,
> please show evidence.
>
> - the reply button should use the Reply-To: header if present, and the From:
> header if not. if you think it doesn't work that way for you, then please
> show evidence.
>
> - your original post says "When the email arrives in my mail client it
> arrives with test@virtual_domain.com in the CC field. ..." if it's so, then
> this has nothing to do with virtual aliases. once again, virtual aliases do
> not change headers.
>
> - just in case you don't, you must understand the difference between the
> envelope (which is used for routing) and headers (which are part of the
> message).
>
>> [snip]
>
>