Can't add a wildcard email redirection

babolivier commented 8 years ago

Hi,

As asked by an user, I'm currently fixing a Node.JS app using the Node OVH API so it can allow an user to use a wildcard email redirection (*@domain.tld). However, when it comes to sending the request via the API, the answer is:

{ message: 'Invalid email address: *@domain.tld }

Is it even possible to add this kind of redirection? If not, why? I have a lot of friends using other email hosting who use a wildcard alias all the time...

P.S.: I'm not sure here's the right place to ask this question. If not, could you please redirect it to the right person? I may have a few cookies left as a thank-you gift.

yadutaf commented 8 years ago

Hi babolivier,

I double checked with the mail team, "catch-all" email addresses are not supported on OVH emails as they attract too much unsolicited mails in the catch-all mailbox.

Could you tell me more about your use case ?

As this question is not directly related to node-ovh itself, I'll mark the issue as closed. Nonetheless, feel free to continue the conversation.

babolivier commented 8 years ago

Hi @yadutaf,

As some friends of mine (including the user I'm referring to), I usually have a "catch-all" email address redirecting to my main address. This allows me to use one email address per service without having to log in to my control panel each time I want to sign up somewhere (for instance github@mydomain.com for GH, twitter@mydomain.com for Twitter, etc, all redirect to my main email address). I'm doing this so:

I can filter the e-mail traffic per service, put, for instance, all emails from Beatport, iTunes, etc in a "Music receipts" IMAP folder (which isn't always easy by only checking the sender's email address as this can change without you knowing it). This means that if I want a whole service not to be able to contact me anymore, I can do this easily by blacklisting the destination email, as they only have the redirection I gave them.
I can know which service sells my information. If I receive a spam or an advertisement on xxx@mydomain.com, this will means without a doubt that the service "xxx" sold my personal infos to someone else.
As I am only using redirections when giving my email address online, the final mailbox's address can be kept secret. I feel a lot safer knowing that, if someone wants to flood my mailbox and for some reason I can't just blacklist a few sender email addresses, I just have to add a new rule blacklisting a specific redirection, and I'm not forced to move a whole mailbox from one address to another.

I can do this because I'm currently hosted on a friend's mail server (Postfix+Dovecot), running with the Horde software so I can add the rules I've talked about. The user I've talked with was asking if it was possible to change an app I'm helping to maintain, which (among other things) administrates his domain, so he can have this kind of usage of his mails on his domain.

yadutaf commented 8 years ago

Thanks for your feedback. I've forwarded it to the team. For the record, here is why it had been disabled in the first place: https://forum.ovh.com/showthread.php/50634-Le-catch-all

mdrzn commented 1 year ago

It's been 13 years since the reason it was disabled, and 7 years since someone officially asked to get it back. I'm not bringing it up again. Can we have a wildcard? It's a given in 2022. (Also the creation of a wildcard via web interface too).

bnema commented 1 year ago

Yes a wildcard we want

Neustradamus commented 1 year ago

It is possible to reopen this issue?

rbeuque74 commented 1 year ago

Hello,

As it was already indicated in 2015:

As this question is not directly related to node-ovh itself, I'll mark the issue as closed.

The correct way to report this would be to either:

open a support ticket
start a thread on OVHcloud Community https://community.ovh.com/
post on the customers community mailing-lists

Thanks Romain

ovh / node-ovh

Can't add a wildcard email redirection #6