Comments on: Gmail Sender header http://vafer.org/blog/20060502022752 ramblings of a creative mind Sun, 07 Mar 2010 01:54:16 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Bruce Wagner http://vafer.org/blog/20060502022752/comment-page-1#comment-59192 Bruce Wagner Sat, 20 Jun 2009 01:48:58 +0000 http://vafer.org/blog/20060502022752#comment-59192 What is the best solution!?!? We have Google Voice accounts... and we, stupidly, connected them to Gmail accounts with names we would rather NOT use... (rather NOT be known as....). However, we LOVE the idea of integrating all our Contacts with Gmail AND Google Voice... (If we had it to do over again... I would have created a brand new gmail address for the Google Voice account... a generic one. For example, for a Google Voice number, 313-453-3011... I would have created a new Gmail account called 3134533011@gmail.com ....If only I had know this would be a problem.) And NOW.... Once the Google Voice (& associated phone number) is connected to a Gmail account... it's "PERMANENT"... OY MAMA!!!! IF only I had known!!! I want to remain logged in to use Google Voice, Gmail, Google Calendar, and Google Docs.... all day long... I don't want to have to log out, and log back in... EVERY SINGLE TIME I CHECK FOR NEW VOICEMAIL and SMS MESSAGES.... Geez. What is the best solution!?!?

We have Google Voice accounts… and we, stupidly, connected them to Gmail accounts with names we would rather NOT use… (rather NOT be known as….).

However, we LOVE the idea of integrating all our Contacts with Gmail AND Google Voice…

(If we had it to do over again… I would have created a brand new gmail address for the Google Voice account… a generic one. For example, for a Google Voice number, 313-453-3011… I would have created a new Gmail account called 3134533011@gmail.com ….If only I had know this would be a problem.)

And NOW…. Once the Google Voice (& associated phone number) is connected to a Gmail account… it’s “PERMANENT”… OY MAMA!!!! IF only I had known!!!

I want to remain logged in to use Google Voice, Gmail, Google Calendar, and Google Docs…. all day long… I don’t want to have to log out, and log back in… EVERY SINGLE TIME I CHECK FOR NEW VOICEMAIL and SMS MESSAGES…. Geez.

]]> By: Grrr http://vafer.org/blog/20060502022752/comment-page-1#comment-59142 Grrr Tue, 21 Apr 2009 16:32:26 +0000 http://vafer.org/blog/20060502022752#comment-59142 "then Google has no choice but to add the Sender header" Choice 1: Save password information and log into the other email address's account to send it from the correct server, like a normal desktop email client. Choice 2: Use a dummy Sender address like "forwarded-mail@gmail.com" to protect the user's privacy. “then Google has no choice but to add the Sender header”

Choice 1: Save password information and log into the other email address’s account to send it from the correct server, like a normal desktop email client.
Choice 2: Use a dummy Sender address like “forwarded-mail@gmail.com” to protect the user’s privacy.

]]> By: Grrr http://vafer.org/blog/20060502022752/comment-page-1#comment-59141 Grrr Tue, 21 Apr 2009 16:28:30 +0000 http://vafer.org/blog/20060502022752#comment-59141 This really irritates me, and they don't seem to see any reason why this should be changed, even though it's a violation of privacy for a lot of users who are completely unaware of the consequences. When you're logged into Gmail address A, and sending from Gmail address B, why aren't the headers identical to being signed into Gmail address B? I log out and log back in to send from different addresses to avoid this. This really irritates me, and they don’t seem to see any reason why this should be changed, even though it’s a violation of privacy for a lot of users who are completely unaware of the consequences.

When you’re logged into Gmail address A, and sending from Gmail address B, why aren’t the headers identical to being signed into Gmail address B? I log out and log back in to send from different addresses to avoid this.

]]> By: tcurdt http://vafer.org/blog/20060502022752/comment-page-1#comment-59032 tcurdt Tue, 16 Dec 2008 00:12:24 +0000 http://vafer.org/blog/20060502022752#comment-59032 Well, I yet have to find a proper alternative. And grown-up as you call it is not a feature but a requirement. Well, I yet have to find a proper alternative. And grown-up as you call it is not a feature but a requirement.

]]> By: Rick van der Zwet http://vafer.org/blog/20060502022752/comment-page-1#comment-59031 Rick van der Zwet Mon, 15 Dec 2008 23:10:09 +0000 http://vafer.org/blog/20060502022752#comment-59031 Welcome to the email system which it's aim it is to make you 70% happy. They do not give much about opinions (they say thank you every time tough). Feel free to switch if you don't like it as there are plenty alternative around. All-tough not many are yet grown-up. Welcome to the email system which it’s aim it is to make you 70% happy. They do not give much about opinions (they say thank you every time tough).

Feel free to switch if you don’t like it as there are plenty alternative around. All-tough not many are yet grown-up.

]]> By: tcurdt http://vafer.org/blog/20060502022752/comment-page-1#comment-59030 tcurdt Mon, 15 Dec 2008 20:15:09 +0000 http://vafer.org/blog/20060502022752#comment-59030 @Andy: if I can receive email at that address (and this was verified) it should be totally OK to relay the mail. At least in theory. @Andy: if I can receive email at that address (and this was verified) it should be totally OK to relay the mail. At least in theory.

]]> By: steve http://vafer.org/blog/20060502022752/comment-page-1#comment-59020 steve Wed, 10 Dec 2008 22:00:15 +0000 http://vafer.org/blog/20060502022752#comment-59020 I get around the gmail "sender" header issue with eudora that lets me send using any domain I want and does not use a "sender" header. I also do this on a domain I run with SPF. all kosher. long live eudora POP3 on gmail I get around the gmail “sender” header issue with eudora that lets me send using any domain I want and does not use a “sender” header. I also do this on a domain I run with SPF. all kosher. long live eudora POP3 on gmail

]]> By: Andy Beverley http://vafer.org/blog/20060502022752/comment-page-1#comment-58886 Andy Beverley Wed, 06 Aug 2008 13:04:02 +0000 http://vafer.org/blog/20060502022752#comment-58886 I don't think setting it will make any difference. It's just that Google have to assume that you do have one, and therefore set the Sender header. Regardless of the SPF record though, Google still need to set a Sender header to sign email with DKIM, which gives your email some authenticity. The whole issue really boils down to the need to get away from the luxury of being able to forge email addresses, which is essentially what Google has to do to set your from address. I think if email was designed today with spammers in mind, then it would be a lot more difficult to "send email on behalf of". I don’t think setting it will make any difference. It’s just that Google have to assume that you do have one, and therefore set the Sender header. Regardless of the SPF record though, Google still need to set a Sender header to sign email with DKIM, which gives your email some authenticity.

The whole issue really boils down to the need to get away from the luxury of being able to forge email addresses, which is essentially what Google has to do to set your from address. I think if email was designed today with spammers in mind, then it would be a lot more difficult to “send email on behalf of”.

]]> By: tcurdt http://vafer.org/blog/20060502022752/comment-page-1#comment-58884 tcurdt Wed, 06 Aug 2008 11:28:15 +0000 http://vafer.org/blog/20060502022752#comment-58884 Well, my vafer.org domain has no SPF record still there is the problem. Question is whether setting it would solve the problem. Well, my vafer.org domain has no SPF record still there is the problem. Question is whether setting it would solve the problem.

]]> By: Andy http://vafer.org/blog/20060502022752/comment-page-1#comment-58883 Andy Wed, 06 Aug 2008 11:07:27 +0000 http://vafer.org/blog/20060502022752#comment-58883 Royce is absolutely correct. If the domain of the email address that you want your email to appear to come from has an SPF record (very likely these days), then Google has no choice but to add the Sender header, otherwise your email is likely to be discarded as spam. This is because any receiving email server will say "well this email claims it is from joebloggs.com, but I know that the server I received it from should not be sending emails from joebloggs.com, so I'll ditch it". Ultimately this is one of the many problems that spammers have left us with I'm afraid. Google is doing the right thing to ensure your mail is delivered properly. The header also allows Google to sign your messages with DKIM, reducing further the chance of them being classed as spam. Royce is absolutely correct. If the domain of the email address that you want your email to appear to come from has an SPF record (very likely these days), then Google has no choice but to add the Sender header, otherwise your email is likely to be discarded as spam. This is because any receiving email server will say “well this email claims it is from joebloggs.com, but I know that the server I received it from should not be sending emails from joebloggs.com, so I’ll ditch it”.

Ultimately this is one of the many problems that spammers have left us with I’m afraid. Google is doing the right thing to ensure your mail is delivered properly. The header also allows Google to sign your messages with DKIM, reducing further the chance of them being classed as spam.

]]>