[email address] on behalf of Steven Mills [[email address]]
(where [email address]' is the main email address associated with
the gmail account, and [email address]' is the other external
account)
In other words, even though I'm sending from a non-Gmail account,
because it's going through Gmail the recipient is made aware of this.
Is there any way round this? I'm almost positive there's nothing in
the settings- what about some script or add-on/plug-in for Firefox
(which is my browser)?
Any help gratefully required.
Regards
Steven Mills
Some e-mail clients, wrongly, use this field for the "on behalf of"
type setting, which is not the purpose. The purpose, and why GMail is
setting it, is to aid receiving systems in spam detection. Normally
you want your from address "yourdomain.com" to match a legal address
of the sending system "gmail.com". Since they don't, "Sender" is
included to show that you are a legal sender from the "gmail.com"
domain. This should prevent systems from marking your message as
spam.
There are a couple ways you can "get around this" but it's not well advised.
1) Use POP/SMTP. Then you can send with your domain, and "Sender"
will not be added (as far as I know).
2) Use Google Apps for your domain. This is a separate account, so it
doesn't set the "Sender" field.
On Sep 4, 6:15 pm, "Zack (Doc)" <z...@tnan.net> wrote:
> When you send e-mail GMail sets a header attribute "Sender"https://mail.google.com/support/bin/answer.py?answer=20616
>
> Some e-mail clients, wrongly, use this field for the "on behalf of"
> type setting, which is not the purpose. The purpose, and why GMail is
> setting it, is to aid receiving systems in spam detection. Normally
> you want your from address "yourdomain.com" to match a legal address
> of the sending system "gmail.com". Since they don't, "Sender" is
> included to show that you are a legal sender from the "gmail.com"
> domain. This should prevent systems from marking your message as
> spam.
>
> There are a couple ways you can "get around this" but it's not well advised.
>
> 1) Use POP/SMTP. Then you can send with your domain, and "Sender"
> will not be added (as far as I know).
>
> 2) Use Google Apps for your domain. This is a separate account, so it
> doesn't set the "Sender" field.
>
Basically, if you own the domain, you can register with Google to
provide you services for your domain, which includes e-mail (GMail
accounts) and many other Google services. Read ahead at the link for
the best explanations.
On Sep 6, 6:44 pm, "Zack (Doc)" <z...@tnan.net> wrote:
> Not any better than Google can:http://www.google.com/a/
>
> Basically, if you own the domain, you can register with Google to
> provide you services for your domain, which includes e-mail (GMail
> accounts) and many other Google services. Read ahead at the link for
> the best explanations.
>
http://www.google.com/support/a/bin/answer.py?answer=53295&hl=en
On Sep 17, 3:39 am, "reneluc...@gmail.com" <reneluc...@gmail.com>
wrote:
> > > > > > Steven Mills- Hide quoted text -
>
> - Show quoted text -
Cheers,
Eric
Now that I think of it, I should reword it a bit. Does MICROSOFT DO
THIS to all versions of Google Apps... I suppose may be more
appropriate.
Cheers!
Eric
On Oct 5, 8:27 am, geek <denverge...@gmail.com> wrote:
That said... You shouldn't have this problem with Google Apps, Free or
otherwise, as long as you're following some simple rules.
The reason MS is doing this, is cause Google is properly using the
"Sender" header entry (which MS thinks they own and have co-opted for
their own uses). Google only sets the "Sender" header entry when you
use a Web Interface (so your POP idea works, IMAP might as well, but I
don't know), to generate a message where the "From" address does not
match the account you logged into. So if you have 2 accounts in the
same domain, when you send from the account you're logged into, there
should be no "Sender" header, but if you use a "Custom From" to
duplicate the "From" from the other account, you should get "Sender"
again, and MS will put "On Behalf Of".
So... you prevent people with MS from ever seeing "On Behalf Of" you
must log into each account when you are going to send "From" that
address. If you're using a program to POP your mail to your local PC
and composing from there, that program would create the headers, and
therefore, probably never add the "Sender" tag.
On 11/2/07, skyline5k <gen...@terascape.net> wrote:
>
Otherwise, you've got it, login to whichever account you want to send
from. Like Ryan said, perhaps use your business one primarily, and
"friends" won't mind if your e-mail to them says "From: business@mail
On Behalf Of personal@mail".
On 11/2/07, Eric Jones <gen...@terascape.net> wrote:
If you google this problem it really shows that IT IS A PROBLEM,
hotmail and yahoo does NOT do this.
And even though it might be microsoft that's the idiots, it really
doesn't change the fact that GMail is realisticly the program that
needs to fix this.
The WORLD COMMUNITY decided YEARS AGO what "Sender" was for, and
that's it's purpose. X-Sender is *NOT* for that purpose, so if GMail
would "use the X-sender header instead" we'd compound one misuse with
another.
I've just confirmed (again??? I've done this dozens of times) that
when I send an e-mail from an account I've created on GAfYD that there
is *NO* Sender header field, so what you're saying is wrong. The only
way I can get a Sender header is by using an address that I'm not
currently logged into.
GMail should not fix the problems of Microsoft, especially when the
practical upshot is that MS's inappropriate use of the header results
in no functional loss of use, but only a cosmetic appearance.
Remember, that even MS users who get "From: real...@gmail.com On
Behalf Of secon...@thisdomain.com" will send the replies back
"To:secon...@thisdomain.com" when they click "Reply". All that's
happened is that they've *SEEN* your GMail address. If it's soooo
important that you **HIDE** your real address, you need to get your
own private SMTP server (like spammers do) and send EVERYTHING from
behind that (like spammers do), so your header can read exactly the
way you want it to (like spammers do). Just remember that this will
cause your messages to sometimes get caught by spam filters (like
spammers do).
There are two things that Google needs to fix:
1. When you are logged into a Gmail account, and send an email from
another Gmail account, there is no reason to add these headers. The
sending server is the same in either case.
No disagreements there.
> BUT, they don't make it clear to you as a user that they are doing
They don't point it out in giant flashing letters, but they are not
hiding it. It is clearly stated in at least two different help pages
related to custom from addresses that they do this; per the standards,
and why they are doing it.
> this. Just because Microsoft shows it in their replies doesn't mean
> the problem is exclusive to Microsoft. The email address you are
A, they don't show it in the replies, they show it in their short
headers. When a Microsoft user clicks reply, it will only fill in the
proper address, and have no reference to the GMail address in that
header.
B, true that it's not EXCLUSIVE to Microsoft, but MS (client software
not their Hotmail BTW) is the only client highlighting this point for
people.
> logged into is ALWAYS in your headers, and is being sent to everyone
Uh... yeah, you logged into it, it's a verified connection, why
shouldn't it be sent?!?
> you send email to. If you keep your email addresses and usernames
> seperate (job searching account, personal real name account, school
> account, embarassing mailing list account), Gmail is exposing them
> without your knowledge or permission, which can be either a "minor
> cosmetic issue" or a major privacy problem, depending on how you use
A, "without your knowledge", would only be because you failed to read
the information provided; and,
B, "without your permission" is completely false, cause you chose to
use a service and it's performing exactly as advertised. If you want
to "give your permission" for something like that, use a different
service that performs differently.
Since *YOU* chose to use a service that works like this, and YOU chose
to send this message (which NEVER claims to HIDE your address), then
it can't be a "major privacy issue". If you have a privacy issue, use
a system that promises to HIDE the information you want hidden.
> There are two things that Google needs to fix:
>
> 1. When you are logged into a Gmail account, and send an email from
> another Gmail account, there is no reason to add these headers. The
> sending server is the same in either case.
I could agree with this point, and think that's an excellent
suggestion for you to send to Google on your next suggestion
submission.
> 2. Like Outlook or any other email program, Gmail should allow you to
> enter server information for your other accounts, instead of just
> sending it from their own servers. So you would enter your school's
> SMTP server and password, and when you send an email from your school
> address, it would be sent from their servers. Then they wouldn't need
> to add the headers for this either.
There's the rub... GMail isn't an email "program" like Outlook.
That's a SIGNIFICANT difference to note. But first to your
"suggestion" to change the way GMail sends these messages.
When a client program (like Outlook) sends a message through a
different SMTP server, it is a unique connection, with message
origination there. Often these servers require authentication of at
least a basic IP level, as in they come from a known IP address range,
like a campus network.
When another SMTP server (like GMail's) sends a message through a
different SMTP server, it is called SMTP-RELAY, which most servers do
not allow, and even when they do, it's considered bad practice, and
frowned upon in the Internet community. This is why GMail cannot do
as you suggest.
NOW... if you happen to read your GMail in an e-mail client... That
client can send your alternate e-mail through alternate servers as you
suggest, to get the effect you're looking for. ALSO... even still
using the GMail SMTP servers, your client forms the header, and
therefore you won't have the "Sender" field unless your client adds
it. THEREFORE, this is only a problem when you use "Custom From"
addresses and you wish to HIDE your true account information, and you
choose to use the webmail interface. I'd say the solution is that if
the first two are the case for you, then you should not choose to use
the webmail interface for those messages.
I won't argue with most of your stuff, as it's a preference thing, but
Gmail *can't* send the exact same way a desktop client would because
of the pseudo-login restrictions virtually all SMTP servers have. As
Zach noted, most servers, particularly ISP and corporate ones, require
that the connections to them are coming from a known IP range. This is
fine for a desktop client, as it will likely be connecting from a
relatively static location.
In the case of a web-based email though, if the SMTP connection is
established by the client-side half of Gmail then the fact that the
email is likely to be accessed from virtually anywhere causes problems
as the person could only send email through some alternate addresses
when they are connected to a certain network. If the connection to the
foreign SMTP server is established from Google's servers as though it
where a normal desktop client, then the problem would be even worse,
as it would be impossible for some messages to _ever_ be sent (Google
doesn't have servers on your company's network).
In either case, Google doesn't want to explain to people why sending
only works occasionally, under very specific situations. They have
instead chosen to take the, IMHO, more correct route where they make
it "just work." Only an arguably non-standards compliant email client
breaks this in any fashion, and the "break" really isn't overly
painful as long as you realize it exists.
Ryan
This field contains the authenticated identity of the AGENT
(person, system or process) that sends the message. It is
intended for use when the sender is not the author of the mes-
sage, or to indicate who among a group of authors actually
sent the message. If the contents of the "Sender" field would
be completely redundant with the "From" field, then the
"Sender" field need not be present and its use is discouraged
(though still legal). In particular, the "Sender" field MUST
be present if it is NOT the same as the "From" Field.
The two key points here are that the Sender *MUST* be present if it's
not the same as From, and it must contain the *AUTHENTICATED IDENTITY*
of the "AGENT that sends the message".
The Sender field cannot be the custom address, because you did not
authenticate your identity at that address. When you performed the
initial add, you authenticated the AUTHORITY to use it, but that is
not the same as authenticating identity. When you log into your GMail
account you're authenticating your identity.
I still don't understand how a business can be ruined because of this.
Embarrassed perhaps, but considering there are better ways of doing
what people are trying to do by "hiding" their information, this
should be minor. And I'm sorry, but as soon as I hit Send up above, I
can consider NOTHING associated with this message as private anymore;
from my real name, or custom address, to the IP of the machine that's
sending it (being a GMail server, they don't need *MY* IP, I'm
authenticated to the server). The best I can hope for is to limit
it's dissemination to only appropriate parties.
That said... re-read what I wrote. You've authenticated authority to
send messages from there, but you're not authenticating identity;
evidenced by my statement above that I can access my wife's account,
but I don't own it, and aren't proving it EACH TIME I log into GMail.
The only thing I'm proving each time I log into GMail is that I have
access to the GMail account, and that I am probably the person who
owns it.
Further to the point. There are a couple addresses that my wife, son,
and I share as custom from addresses. Mail sent TO these addresses
actually get delivered to each of us, but only one of us is a sender
at a time. This is essentially what the purpose of the Sender field
is.
GMail can't change the SPF record of any domain not under their
control, so no they couldn't change the SPF record of hotmail.com to
allow them to send with that custom from address without adding
sender. In fact, because of SPF records, many mail services would
reject mail that originated from GMail servers with a from of hotmail,
WITHOUT the sender header. So your comment about SPF records just
goes to show WHY they MUST include a Sender field, and what it must
read.
Additionally... you mention Google Apps. Google Apps does have you
set an SPF record, and does NOT send a "Sender" field when you send
from the account you're logged into. I've done this myself. I don't
understand how this is affecting you.
I also still don't understand the customer who stops giving you
business because they receive an e-mail from:
"trusted...@business.com On Behalf Of user...@gmail.com". If
they're freaked out by the gmail.com part, their a) naive, and b) need
to do business in person instead of e-mail because their concerns
SHOULD be bigger than the domain in use.
Ryan
On Jan 15, 2008 10:53 AM, Kadhumia Flo <kadhum...@gmail.com> wrote:
>
> Does Zach work for Google?
>
> If not, then how else can we contact Google.
>
>
> >
>
--
Make long URLs memorable: http://urlet.com
No, I don't work at Google. I'm just a user like yourselves. I do
work in networking, and therefore have a lot of knowledge of the RFCs
and why some things work and others don't. I can tell you, that in a
very short time, NOT adding the Sender header will cause mail delivery
to fail, and all providers will have to start doing it when they're
not the owner of the domain you're sending from.