EmailDiscussions.com - View Single Post

horatio8 · 18 Oct 2020, 07:45 AM

Here's a quote from Bill from 2014:

If you have a wildcard target set up, you can also set up other targets. The wildcard will only be used if no specific aliases are found.
If a virtual alias targets itself, that address won't exist. So if you enter nemo@mydomain targeting nemo@mydomain, messages sent to that address will generate a bounce (as if the address does not exist). This will happen even if the wildcard alias is active, and is one way to block certain addresses at your domain?

Is this still the preferred way to block a particular alias when you have a wildcard at your own domain? For example, I get spam at paypal@mydomain.com. Should I create an alias where paypal@mydomain.com targets paypal@mydomain.com to bounce it? Should this alias come before the *@mydomain.com targeting my Fastmail address, or after?

Or is there a better way? Thanks.

18 Oct 2020, 07:45 AM	#1
horatio8 Senior Member Join Date: Jan 2006 Posts: 112	Bouncing emails preferred method Here's a quote from Bill from 2014: If you have a wildcard target set up, you can also set up other targets. The wildcard will only be used if no specific aliases are found. If a virtual alias targets itself, that address won't exist. So if you enter nemo@mydomain targeting nemo@mydomain, messages sent to that address will generate a bounce (as if the address does not exist). This will happen even if the wildcard alias is active, and is one way to block certain addresses at your domain? Is this still the preferred way to block a particular alias when you have a wildcard at your own domain? For example, I get spam at paypal@mydomain.com. Should I create an alias where paypal@mydomain.com targets paypal@mydomain.com to bounce it? Should this alias come before the *@mydomain.com targeting my Fastmail address, or after? Or is there a better way? Thanks.