Allowing you to authenticate against another SMTP server always seemed like such an easy win for them and I couldn't understand why they didn't just do it. But I guess I'm not the one supporting millions of people on my platform. :)
This makes GMail an even stronger candidate now to replace a desktop mail client in my book. Thanks, Google.
We heard your request for another option that wouldn't show the "on behalf of" text loud and clear,
right. loud and clear. The imperative word there is probably "heard" - the thread about this on their support forum was started around at the time when gmail began adding support for 3rd party addresses and all the customers got was a mixture between silence and "working as intended".
Don't get me wrong: I'm incredibly happy that this is fixed now, but talking about how well they were listening to their users and how quickly they reacted is borderline cynical.
This is the feature that I have been waiting for! I can finally manage all of my mail in one place and respond to professors in a professional manner through the school email server and keep my gmail totally behind the scenes. Awesome
I'm also elated for this. Countless times at work, I send an email from gmail using my work/school .edu email and when that mail gets replied and forwarded around back to me with my gmail user name exposed. Not a lot of people know me by my username (which is my gmail) and sometimes I want to keep it that way.
So you don't want your username exposed. On the other hand, some people do not like to reply to Gmail addresses because they don't want their mail to be scanned by an advertising company.
You don't want server side PGP support - you'd have to give your private key to Google. As much as I trust Google, I still don't trust them that much.
Much more secure to handle the crypto client side. Ideally, Google should work with the firegpg guy so that he has notice before they change the interface (FireGPG tends to break for a day or two whenever there is any change to the GMail UI).
This change does not seem to affect secondary gmail accounts: does anyone know of a way to get them to work too? Or is there a technical reason why Google cannot do it?
In case someone does not understand the problem: I have a few gmail addresses that I use in contexts where I don't want to disclose my real name. For convenience, all mail sent to these addresses gets forwarded to my primary account, which does use my real name. But because of the sender field, I can't use my primary account to reply to these mails, which makes the situation quite messy.
Great! Now gmail needs to make the "conversations" view optional and give me the ability to view my mail just like any other e-mail client (that is, without automatically combining unrelated e-mails into the same "conversation" just because they share a subject line).
Anybody know if this will work w/ 3rd party email clients?
For example, if I use smtp.gmail.com, but I construct the from address appropriately, will it relay to smtp.mydomain.com and put a copy of the message in my sent items folder on my Gmail account?
Note for IMAP/POP users: If you access Gmail through a POP or IMAP email client (e.g. Outlook) and would like to send messages with a custom "from" address, you have two options. We recommend that you configure your email client with two outgoing SMTP servers, one for Gmail and one for your other address. Your second option is to use Gmail's outbound servers with a different "from" address. If you've already configured the custom from address in the web interface, your message will be sent from:[email protected], sender:[email protected], regardless of which custom from configuration you chose. Your messages will be sent from your regular Gmail address if you never configured your custom from settings in the web interface.
It works! The trick here is that you need to specify your own smtp server but specify "smtp.gmail.com" anyway and for the user name, use the full address: [email protected] - also, make sure to use SSL. Just tested, works like a charm.
[+] [-] thinkzig|16 years ago|reply
Allowing you to authenticate against another SMTP server always seemed like such an easy win for them and I couldn't understand why they didn't just do it. But I guess I'm not the one supporting millions of people on my platform. :)
This makes GMail an even stronger candidate now to replace a desktop mail client in my book. Thanks, Google.
[+] [-] scs|16 years ago|reply
[+] [-] pilif|16 years ago|reply
right. loud and clear. The imperative word there is probably "heard" - the thread about this on their support forum was started around at the time when gmail began adding support for 3rd party addresses and all the customers got was a mixture between silence and "working as intended".
Don't get me wrong: I'm incredibly happy that this is fixed now, but talking about how well they were listening to their users and how quickly they reacted is borderline cynical.
Sorry. I just had to vent.
[+] [-] conorgil145|16 years ago|reply
[+] [-] mojaam|16 years ago|reply
[+] [-] sfk|16 years ago|reply
[+] [-] grinich|16 years ago|reply
[+] [-] smanek|16 years ago|reply
You don't want server side PGP support - you'd have to give your private key to Google. As much as I trust Google, I still don't trust them that much.
Much more secure to handle the crypto client side. Ideally, Google should work with the firegpg guy so that he has notice before they change the interface (FireGPG tends to break for a day or two whenever there is any change to the GMail UI).
[+] [-] delayclose|16 years ago|reply
In case someone does not understand the problem: I have a few gmail addresses that I use in contexts where I don't want to disclose my real name. For convenience, all mail sent to these addresses gets forwarded to my primary account, which does use my real name. But because of the sender field, I can't use my primary account to reply to these mails, which makes the situation quite messy.
[+] [-] anthropocentric|16 years ago|reply
[+] [-] zacharypinter|16 years ago|reply
For example, if I use smtp.gmail.com, but I construct the from address appropriately, will it relay to smtp.mydomain.com and put a copy of the message in my sent items folder on my Gmail account?
[+] [-] pmh|16 years ago|reply
Note for IMAP/POP users: If you access Gmail through a POP or IMAP email client (e.g. Outlook) and would like to send messages with a custom "from" address, you have two options. We recommend that you configure your email client with two outgoing SMTP servers, one for Gmail and one for your other address. Your second option is to use Gmail's outbound servers with a different "from" address. If you've already configured the custom from address in the web interface, your message will be sent from:[email protected], sender:[email protected], regardless of which custom from configuration you chose. Your messages will be sent from your regular Gmail address if you never configured your custom from settings in the web interface.
[+] [-] neilc|16 years ago|reply
[+] [-] jseifer|16 years ago|reply
[+] [-] spydez|16 years ago|reply
[+] [-] snprbob86|16 years ago|reply
[+] [-] unknown|16 years ago|reply
[deleted]