News for hackers. Stuff that matters.

A comment on Google: Do what you want with Reader, but don't kill CalDAV. Parent comment

Re:Google: Do what you want with Reader, but don't kill CalDAV by onemorepassword on Friday March 15, 2013 @03:41AM (#5379574)
No they don't. This is the reason why this is such a hell. Yes, the account acknowledges the alternate name, but Google keeps publicly replacing it with the primary name as soon as you do anything.

This is not just ugly and confusing from a marketing and branding perspective, it leads to all kinds of complications with software that reacts to email-addresses, or services that are coupled to Google Apps.

[ Parent | on HN ]
Re:Google: Do what you want with Reader, but don't kill CalDAV by carl689 on Friday March 15, 2013 @08:46AM (#5380253)
Perhaps I am not following 100%, but I believe we have done this without this issue for years with google apps.

We have one primary domain and 15 alias domains. Email Example: [email protected] gets an email, when they reply it stays set to the alias, it doesn't change to the primary domain.

[ Parent | on HN ]
Re:Google: Do what you want with Reader, but don't kill CalDAV by csixty4 on Friday March 15, 2013 @01:06PM (#5381601)
Gmail sends a Sender: header with the account's primary email address, which some email programs treat as the "actual" sender. Some mail programs display this as "From [email protected] on behalf of [email protected]" and then those programs use the primary as the return address.

According to Google, they don't include this header if you upgrade to Google Apps for Business.

[ Parent | on HN ]