[gentoo-user] Re: gmail smtp overwrites the sender

[Grant Edwards <grant.b.edwards@gmail.com>]

On 2012-03-11, Nikos Chantziaras <realnc@gmail.com> wrote:
> On 11/03/12 18:14, Grant Edwards wrote:
>> On 2012-03-11, Nikos Chantziaras<realnc@gmail.com>  wrote:
>>
>>> There is no "display from".  I use Thunderbird and it reports the
>>> "from" correctly (that is, it says the mail did not come from GMail.)
>>> All mail clients do that.
>>
>> Outlook never used to.  It always used to display the "on behalf of"
>> stuff.
>>
>>> They use the "From:" address.  It's a standard specified in an RFC.
>>
>> Oh, well Microsoft has never violated an RFC, so I'm sure you're right.
>
> GMail does not generate an "on behalf of" header either.
>
> I just tested it.  I've sent an email through GMail's SMTP.  Here are
> the relevant headers of the email that arrived.  "my_other_address"
> is what I used as "From:"
>
>    Return-path: <realnc@gmail.com>
>    Envelope-to: my_other_address
>    Sender: Nikos Chantziaras <realnc@gmail.com>
>    From: my_other_address

Ah!  Apparently gmail has fixed the "sender" problem.  According to
wikipedia, they now allow you to use somebody else's SMTP server:

  http://en.wikipedia.org/wiki/Gmail#On_behalf_of

That's not what you're doing?

If they have indeed fixed it so you can send mail using Google's SMTP
server and have something other than your gmail address show up in the
"sender" field, then it's time to celebrate.

> The OP mentioned that the problem is that he wants to subscribe to a 
> mailing list, but that list sends the verification mail to the "Sender:" 
> address rather than the "From:" address.  Which sounds very weird to me. 
>   If you want to subscribe the "From:" address to a list, why would they 
> want to verify the "Sender:" address instead?  Makes no sense.

Dunno.  I didn't relly understand what the OP was saying.  I was
confirming (erroneously), the gmail would always put the gmail address
in the "sender" header, which then triggered Outlook to display the
"on behalf of" stuff.  That issue has apparently been fixed.

-- 
Grant