They should just fix searching in Outlook web instead.
Microsoft adding support for custom '+' email addresses in Office 365
11–20 of 129 posts
Re: Microsoft adding support for custom '+' email addresses in Office 365
#12Now 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.
Re: Microsoft adding support for custom '+' email addresses in Office 365
#13I understand the appeal of this feature for sorting, but it seems ineffective for things like "figure out who sold my email to the spammers" because everyone knows about it and it's elementary to just trim off everything after the plus sign. Unless you do some kind of verification and filter email sent to addresses without a valid suffix?
Hyphens and equals are other options that are supported by various services:
* https://en.wikipedia.org/wiki/Email_address#Subaddressing
Equals specifically is used by mailing list software (esp. Mailman) for bounce processing (VERP):
* https://en.wikipedia.org/wiki/Variable_envelope_return_path
Re: Microsoft adding support for custom '+' email addresses in Office 365
#14FastMail had some of the cleverest ideas for plus addressing. username+tag@fastmail.fm could be given away as tag@username.fastmail.fm
I used this for a few sites, but then stopped as I realized this would be a pain to change if I ever wanted to change to a different email provider.
Wish every provider would support this as I’m sure spammers have caught on to the plus addressing scheme.
Re: Microsoft adding support for custom '+' email addresses in Office 365
#15Earlier quoted context omitted.
I would agree with this technique, but it’s not possible due to the high number of services that don’t permit “+” in the email address or break because they don’t URI encode it. I have several services I will never be able to unsubscribe from because of the latter—and yes, I tried manually URI encoding it and changing the form fields with dev tools.
Such services are likely breaking the law. Edit: Downvote me all you want, they're still breaking the law… In the US there's the CAN-SPAM act ( https://www.ftc.gov/tips-advice/business-center/guidance/can... ) and nearly every other country has similar laws. Most of them require one-click unsubscribes to work. It's still failure to comply even if it's due to negligence/ignorance/incompetence.
What does one-click unsubscribe have to do with accepting an email with a + in it?
Re: Microsoft adding support for custom '+' email addresses in Office 365
#16Earlier quoted context omitted.
Such services are likely breaking the law. Edit: Downvote me all you want, they're still breaking the law… In the US there's the CAN-SPAM act ( https://www.ftc.gov/tips-advice/business-center/guidance/can... ) and nearly every other country has similar laws. Most of them require one-click unsubscribes to work. It's still failure to comply even if it's due to negligence/ignorance/incompetence.
What does one-click unsubscribe have to do with accepting an email with a + in it?
The parent post to the one you're responding explicitly calls out that they cannot unsubscribe from lists when they've subscribed with a +-address:
> I have several services I will never be able to unsubscribe from because of the latter—and yes, I tried manually URI encoding it
Re: Microsoft adding support for custom '+' email addresses in Office 365
#17Now 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.
That's not going to help, since everybody knows you can just strip everything after the '+' and get to the main mailbox.
Re: Microsoft adding support for custom '+' email addresses in Office 365
#18Now 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.
That's not going to help, since everybody knows you can just strip everything after the '+' and get to the main mailbox.
Jokes on them, if my spam+ doesn't have a tag it's straight in the bin.
Re: Microsoft adding support for custom '+' email addresses in Office 365
#19Earlier quoted context omitted.
If bad actors cut off the +, fight back by not using your bare email at all: Provide everyone with a + address, ignore all emails that come without.
I would agree with this technique, but it’s not possible due to the high number of services that don’t permit “+” in the email address or break because they don’t URI encode it. I have several services I will never be able to unsubscribe from because of the latter—and yes, I tried manually URI encoding it and changing the form fields with dev tools.
I've long held the thought of having a mailbox that receives [everything]@[domain], except certain blacklisted addresses.
As certain addresses get spam and/or I lose interest in the business I gave the address to, I add them to the blacklist. So far, I'm using AWS SES, which seems to be focused on the sending of marketing emails, and are not fussed on receiving, but includes rudimentary blacklisting. So far, it's zero cost.
Re: Microsoft adding support for custom '+' email addresses in Office 365
#20I understand the appeal of this feature for sorting, but it seems ineffective for things like "figure out who sold my email to the spammers" because everyone knows about it and it's elementary to just trim off everything after the plus sign. Unless you do some kind of verification and filter email sent to addresses without a valid suffix?
Since I have my own domain, I receive all emails addressed at whatever@domain.com. Of course, different values of "whatever" end up in different directories, and should one of those display an insufficient SNR, it would go straight to /dev/null. This way the "proper" address, i.e., the one that goes to the actual inbox, is not easy to extract.
The hard part is social acceptance. This morning the Whirpool technician was very puzzled by me giving him whirpool@domain.tld as my email, although he accepted my explanations in the end. (I might use more opaque identifiers, but then I would forget about what is what, so for the moment I am trying to stick with this scheme, until it becomes too difficult)