I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it?
I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it? Sounds tedious if it’s the former
How do you prevent someone from spamming you with random usernames? For example: random1@lastname.com random2@lastname.com random3@lastname.com Do you have a whitelist as well?
I do the same as KMnO4 and I think I have never received an email to a random address that I haven't shared before. Currently the biggest volume of spam is coming to adobe@ and github@ (along with some dating sites). Actually, I did receive one, from my friend who typed the entire message in the name before the @ and left the body and subject empty :D
> Actually, I did receive one, from my friend who typed the entire message in the name before the @ and left the body and subject empty :D
So something like this?
From: bobby@tables.com
To: myplanejustlandedcanyoucomepickmeup.thx@lastname.com
Subject:
Body:
in my experience that sort of "send some spam to addresses we have no reason to believe exist" behavior takes the form of sending stuff to $commonfirstname@domain not $service@domain nobody is sending email to alsdkjfadf@domain
You are right. But I think using a catch all with a separate username for each service/business is becoming an increasingly common practice so I would imagine it’s only a matter of time before spammers catch on and begin exploiting this.
I use service name + 4 random alphanumeric characters. Seems to strike a reasonable balance between just using the service name vs. completely random characters.
I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it? Sounds tedious if it’s the former
I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it? Sounds tedious if it’s the former
I do this but it requires 0 setup, it's a feature in Fastmail.
I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it? Sounds tedious if it’s the former
A catch-all that forwards to one account works very well.
How do you prevent someone from spamming you with random usernames? For example: random1@lastname.com random2@lastname.com random3@lastname.com Do you have a whitelist as well?
Using random emails like that is a super easy way of getting caught up in a spam trap, which would get you blocked easily. One of our users used a throwaway a@apple.com, which earned us a complaint inside of an hour, just by sending a welcome/confirm message.
That's not really an issue for end users getting emails at @, which is what the thread is about.
in my experience that sort of "send some spam to addresses we have no reason to believe exist" behavior takes the form of sending stuff to $commonfirstname@domain not $service@domain nobody is sending email to alsdkjfadf@domain
> nobody is sending email to alsdkjfadf@domain That’s actually the kind of spam I used to receive on a very short domain with a catch-all. I guess they loop through short domain names and then try to brute-force the local part.
Interestingly, I have .one but I think because it's an uncommon TLD and a seemingly random 3 letters, I haven't had that issue.
I use an email catch all for everything. github@lastname.com, reddit@lastname.com, randomstore@lastname.com all direct to firstname@lastname.com. I rarely get spam these days, but when I do, I simply block the address and move on.
Do you have to set up a new email address for each website you sign up for or do you have software that automatically handles it? Sounds tedious if it’s the former
I use a catch all alias that maps all local parts to one account (unless a specific account or alias already exists)