Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft adding support for custom '+' email addresses in Office 365

zdnet.com

Post reply on HN
Print view View original

91–100 of 129 posts

Re: Microsoft adding support for custom '+' email addresses in Office 365

#91

Post by donmcronald »

inanutshellus wrote: post #59

The process for sending email /from/ a + address is tricky. First -- in GMail at least -- you have to explicitly set up a + account as being in your list of "from" accounts and then you have to remember to use it every time you reply! Not to mention forgetting the email I gave them when resetting passwords sucks, too. "Was that foo+hn or foo+ycombinator or foo+ycombinator.com or foo+hackernews or... hm... uhhh..." (Y…

You can't even send from a normal alias in Office 365, so I'd be shocked if you'll be able to send from these '+' aliases.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#92

Post by gumby »

Hnrobert42 wrote: post #12

Now if only websites will stop rejecting plus-addressed email addresses as invalid. The most frequent offenders are mom & pop websites that you just _know_ are going to get breached.

I simply changed my mail configuration to use a different character, in my case _ though X would have worked as well.

I wish seive were better supported in mail clients. It works fine on the back end, but I edit my .seive file by logging into the server and sparking up Emacs rather than being able to handle it directly from my mail client.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#93

Post by aclindsa »

6c696e7578 wrote: post #78
Hnrobert42 wrote: post #12

Now if only websites will stop rejecting plus-addressed email addresses as invalid. The most frequent offenders are mom & pop websites that you just _know_ are going to get breached.

I use qmail, where - has been the extension for, well, since it was created. If you're a postfix person, you can use + or -, with recipient_delimiter. You're less likely to bump into issues with -. Some shops don't like their trade name in the email, so rot13 (g? in vim) solves that if your goal is to trace back the leaks. I have not found a reliable way of auto dropping mail from bad sources, sometimes companies cha…

> If you're a postfix person, you can use + or -, with recipient_delimiter.

Even better: postfix and dovecot (as of v2.3) now both allow specifying multiple recipient delimiters. So if you run your own mail server you can specify as many recipient delimiters and switch between them if websites are being picky.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#94

Post by grok22 »

jnwatson wrote: post #70
isoprophlex wrote: post #61

Earlier quoted context omitted.

I use shopname@firstname.lastname.email, with my own lastname.email domain. Fastmail makes configuring your dns records for this super simple. It's always fun interacting with customer service reps when they for example confirm my email address... "errrrrr yeah so we email you at ourname@...?"

I've done that for nearly twenty years now. Importantly, it allows one to trace how your email gets distributed and stolen.

Did you find anything interesting? I started doing this recently and did not find anyone misusing my email so far and am now wondering if it's worth the extra effort.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#96

Post by DenseComet »

jasonv wrote: post #88

I moved all my public emails from first@last.something to first.last@wellknownmailprovider and then spent a lot of time changing my email address in accounts that I've had a really long time. Shocked at how badly that went, actually. For certain service providers, I couldn't change my email address and was encouraged to open a new account, which would've meant losing certain records in the old accounts. I couldn't co…

What was your reasoning behind moving your emails to a public email provider instead of an email with a domain you seemed to control?

I've been trying to move in the other direction and its been exactly as much of a pain as you've mentioned.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#97

Post by girzel »

gumby wrote: post #92
Hnrobert42 wrote: post #12

Now if only websites will stop rejecting plus-addressed email addresses as invalid. The most frequent offenders are mom & pop websites that you just _know_ are going to get breached.

I simply changed my mail configuration to use a different character, in my case _ though X would have worked as well. I wish seive were better supported in mail clients. It works fine on the back end, but I edit my .seive file by logging into the server and sparking up Emacs rather than being able to handle it directly from my mail client.

Emacs can be used to edit sieve files directly on the server, with M-x sieve-manage, so long as you have the managesieve daemon running.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#98

Post by oneplane »

grok22 wrote: post #94
jnwatson wrote: post #70

Earlier quoted context omitted.

I've done that for nearly twenty years now. Importantly, it allows one to trace how your email gets distributed and stolen.

Did you find anything interesting? I started doing this recently and did not find anyone misusing my email so far and am now wondering if it's worth the extra effort.

For alias addresses they are filtering that because the data thiefs and middlemen know a small portion of people do this. They cut off the plus or dot part when your domain has a well known MX/MTA connected to it.

That still leaves custom mailservers and non-alias (as in aliases via plus or dot, not actual mailserver aliases) which does give an indication as to who is sharing your data.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#99

Post by loosescrews »

cm2187 wrote: post #43
lawn wrote: post #37

Earlier quoted context omitted.

Nowadays I just use tag@mydomain when I interact with websites.

Couldn’t agree more. If the website is breached, the login isn’t a login for any other website, and advertisers have a harder time correlating your identity, and if you get spam you know who is the culprit, and you can stop the spam by deleting the alias. With this, no need for any other antispam logic. Back to the mid 90s (which is a good thing as far as email traffic is concerned!).

I always do this as well. I knew for months before they announced it that Dropbox had been breached. Yes, they waited so long to announce that the thieves had started using the emails for spam.

Re: Microsoft adding support for custom '+' email addresses in Office 365

#100

Post by parliament32 »

gumby wrote: post #92
Hnrobert42 wrote: post #12

Now if only websites will stop rejecting plus-addressed email addresses as invalid. The most frequent offenders are mom & pop websites that you just _know_ are going to get breached.

I simply changed my mail configuration to use a different character, in my case _ though X would have worked as well. I wish seive were better supported in mail clients. It works fine on the back end, but I edit my .seive file by logging into the server and sparking up Emacs rather than being able to handle it directly from my mail client.

I use the managesieve plugin in claws-mail, works great with no issues.
Post reply on HN