201–210 of 212 posts
Earlier quoted context omitted.
I'd think spammers would have caught on to that and would either start sending e-mail to nico@domain.com or nico+someotherdomainname@domain.com
You think spammers are people going through emails? It is all automated.
Earlier quoted context omitted.
Been there done that. If you catch all e-mail you will also get a lot of spam to random addresses like say sven@marak.com, lollerskates95@marak.com and so on and so forth. So then you need spam filtering anyway, or you need to configure which addresses are valid. I still host my own e-mail but I no longer do catch-all. There are only a few sites and services I care about. For those I have trusted them with my e-mail…
If you host your own domain you'll likely need spam filtering for abuse@ or at least postmaster@ (or ignore RFCs, like most unfortunately do..).
I've had a catch-all for *@mydomain.com forward to my primary email address for 10+ years. In that time I signed up for services and websites with [domain]@mydomain.com thinking I'd catch all those dirty scoundrels selling my email address and have an easy way to filter unwanted mail. But you know what really happened? I wound up with hard to remember email logins and caught less than a handful of services sharing my…
I've had a catch-all for *@mydomain.com forward to my primary email address for 10+ years. In that time I signed up for services and websites with [domain]@mydomain.com thinking I'd catch all those dirty scoundrels selling my email address and have an easy way to filter unwanted mail. But you know what really happened? I wound up with hard to remember email logins and caught less than a handful of services sharing my…
So what's it like when NBox goes under and you can't recover your password on any of your sites?
Hi midnitewarrior, here is a post where I try to answer that (valid) concern: https://www.producthunt.com/posts/nbox/comments/483328
The other problem with this is that there is now a middle man in my security chain. If you get hacked, potentially all of my accounts can be hacked. If you have a rogue employee, same thing. If you have a flaw in your security, I too am at risk from a centralized source.
I've had a catch-all for *@mydomain.com forward to my primary email address for 10+ years. In that time I signed up for services and websites with [domain]@mydomain.com thinking I'd catch all those dirty scoundrels selling my email address and have an easy way to filter unwanted mail. But you know what really happened? I wound up with hard to remember email logins and caught less than a handful of services sharing my…
Only downside, is when company merges or renames: if it merged I end up with to accounts which have half of the history; if it renames -- hard to remember original email (recent example wayfair's old name was something else).
Now, I'm switching to single email -- it's just simpler
Earlier quoted context omitted.
Can you say something from the service perspective? Why shouldn't a service flag you as malicious and refuse users with email from your domain? What do you do to prevent mass account creation on the service? Thanks!
Hi ecesena, > Why shouldn't a service flag you as malicious and refuse users with email from your domain? Some services might block our addresses some day, but that would be a mistake because nBox is not a disposable email service. > What do you do to prevent mass account creation on the service? If your question is in regard to services which might block us, I don't think they care about mass account creation, a few…
As for my 2nd question it was related. Often time spammers rely on tools like nbox to create a massive amount of accounts on services like Winterest, so Winterest has to flag your domain as potentially malicious.
I was wondering if you have any countermeasures to this problem, such as a rate limit on the number of accounts one can create per service. I'm sure Winterest would appreciate :)
A link to the chrome extension on the landing page would be quite useful (Otherwise visitors need to go to the chrome web store and search for it...and some of them are too lazy to do it). But otherwise I really like the idea. I'll give it a try ;) P.S. here's the link for the extension: https://chrome.google.com/webstore/detail/nbox-your-registra...
thanks ported it to Edge and Firefox https://github.com/Scrxtchy/nbox-everywhereElse
The Firefox extension was following the validation process, it's now published: https://addons.mozilla.org/en-US/firefox/addon/nbox/
Earlier quoted context omitted.
Hi ecesena, > Why shouldn't a service flag you as malicious and refuse users with email from your domain? Some services might block our addresses some day, but that would be a mistake because nBox is not a disposable email service. > What do you do to prevent mass account creation on the service? If your question is in regard to services which might block us, I don't think they care about mass account creation, a few…
Thanks! The non-disposable is a good point. As for my 2nd question it was related. Often time spammers rely on tools like nbox to create a massive amount of accounts on services like Winterest, so Winterest has to flag your domain as potentially malicious. I was wondering if you have any countermeasures to this problem, such as a rate limit on the number of accounts one can create per service. I'm sure Winterest woul…
For a given service we authorize only one address, but we haven't implemented a rate-limit yet.