I’ve been using a catch-all on all my custom domains for as long as I’ve had a custom domain and it’s worked great.
However, about 2 weeks back my business custom domain started creating loads of aliases that were used to send me spam (all related to finance/accounts, the message would say I owe a vendor money.) I disabled the catch-all so that they spam would stop, but I’d still like to use it if possible (via the auto create rules).
Does anyone have a regex for Simplelogin that I can use to help combat this issue? Or is this there not much that I can do?
I can provide a list of the aliases that were created if it helps?
Looks like they’re just spamming at the domain owner. If they’re coming from the same sender, block the sender, otherwise you could try and use auto-create and designate an abnormal string like .*zdz.* — so that every alias that includes the string “zdz” somewhere will work.
Be sure to test it out at the bottom of the rule page.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !protonprivacy@lemmy.world
Empowering you to choose a better internet where privacy is the default. Protect yourself online with
Proton Mail, Proton VPN, Proton Calendar, Proton Drive. Proton Pass and SimpleLogin.
Proton Mail is the world’s largest secure email provider. Swiss, end-to-end encrypted, private, and free.
Proton VPN is the world’s only open-source, publicly audited, unlimited and free VPN. Swiss-based, no-ads, and no-logs.
Proton Calendar is the world’s first end-to-end encrypted calendar that allows you to keep your life private.
Proton Drive is a free end-to-end encrypted cloud storage that allows you to securely backup and share your files. It’s open source, publicly audited, and Swiss-based.
Proton Pass Proton Pass is a free and open-source password manager which brings a higher level of security with rigorous end-to-end encryption of all data (including usernames, URLs, notes, and more) and email alias support.
SimpleLogin lets you send and receive emails anonymously via easily-generated unique email aliases.
I’ve added a screenshot with the aliases but I don’t think regex will help unless I setup a structure to follow.
Looks like they’re just spamming at the domain owner. If they’re coming from the same sender, block the sender, otherwise you could try and use auto-create and designate an abnormal string like .*zdz.* — so that every alias that includes the string “zdz” somewhere will work.
Be sure to test it out at the bottom of the rule page.
There was 3 or 4 different accounts. After the first round of emails the rest went straight to spam.
I’ll think of something that I can add to make it more unique like you mentioned. Thanks for the help!