Dear google,

About half a decade ago, I created a gmail account (maybe longer—not so sure anymore). After testing it out for a while, I decided that it wasn't for me; but as a gmail account comes with a google account for free, I didn't throw it out.

As time went on, I added a few other things to that account. I try to limit its use a bit, but I do own a few android devices (for lack of a better alternative), and I do use adsense on my website, and all of these are linked to my existing google account; so I don't want to throw it away.

I don't ever read mail sent to my gmail account, though; I prefer to read my mail in a local mail client (I used mutt for about a decade, having switched to thunderbird recently). Since it kept happening that people thought I would read my gmail account (which I do still use for XMPP, in spite of your recent crippling of that service), I configured an autoresponder on gmail to warn people off, and told them to use my main mail address instead of the gmail one. Additionally, I configured my main mail addresses (plural; they're really aliases) as "secondary" addresses on my gmail account, so that people who try to send mail to me could figure out where to actually send it before seeing the autoreply.

Unfortunately, for some reason you seem to have interpreted that as "screw his MX records and DNSSEC, we'll just intercept anything coming from our servers and going to Wouter Verhelst as going to his gmail account".

There's a word for that. I'm not going to use it.

Autoforward

You could just autoforward mail sent to gmail as explained here: https://support.google.com/mail/answer/10957?hl=en.

Alternatively you could check your gmail inbox with a local client using POP or IMAP.

Comment by beojan Fri Jan 3 18:26:01 2014
Re: Autoforward

Yes, there are shitloads of workarounds which I could implement. That's besides the point.

The fact of the matter is, I have an MX in my DNS, and this MX is verified by DNSSEC. That, and only that, should define where mail to my mail address needs to be routed.

Anything else is completely and utterly wrong.

Comment by wouter Fri Jan 3 18:50:34 2014
Re: Autoforward
Creatively wrong. Wrong on a level which takes significant effort. So unbelievable wrong that I almost admire it.
Comment by Kristof Provost Fri Jan 3 19:12:20 2014
Gmail handling secondary mail addresses oddly
This behavior should only be the case when you send a mail from Gmail to your secondary address (e.g. To or even Bcc). in this case it will create an unread mail in the inbox (or set unread on the sent item). The mail will still be delivered to the MX of your secondary address.
Comment by Philipp Kern (pkern@debian.org) Sat Jan 4 02:14:45 2014
Re: Gmail handling secondary mail addresses oddly

I don't know about what "should" be the case. I do know that there have been several cases of people sending me email through google servers where the mail was redirected to my gmail address, and I did not see the mail until I logged in to gmail.

Apparently there are cases where the mail will still arrive correctly, as you've shown by sending me a mail from gmail. Still, that doesn't mean there's no problem.

Comment by wouter Sat Jan 4 15:21:42 2014
Re: Gmail handling secondary mail addresses oddly
Well, I believe that this is a bug. If you are comfortable relaying headers to me (s/debian.org/google.com) I can probably point someone at it.
Comment by Philipp Kern (pkern@debian.org) Sat Jan 4 19:10:12 2014
Re: Gmail handling secondary mail addresses oddly
I've seen the letter/word/word notation a lot on the internet and don't know what it means.
Comment by jimbo1qaz (jimbo1qaz@gmail.com) Mon Jan 6 05:49:56 2014