I'm sure there must be one, but I have never heard a really good reason for EVERY implementing a catchall... unless someone is just masochistic and likes spam...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For a working domain, implementing catchalls totally breaks smtp in that someone who sends an email to a mistyped address will never be informed that their message was never delivered... BAD, BAD, BAD... don't do it...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I'm aware of the traditional reasons not to do this. The entire domain serves as a spamtrap, but there are a couple addresses I'd like to reject at the border for testing purposes.
I think doing an access map in Postfix is the most likely solution. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there a method in place to reject mail for specific addresses while still allowing all other addresses to be aliased to the domain catchall?
You could presumably do it through Postfix (some sort of smtp_recipient_restriction I guess?)
I'm sure there must be one, but I have never heard a really good reason for EVERY implementing a catchall... unless someone is just masochistic and likes spam...
For a working domain, implementing catchalls totally breaks smtp in that someone who sends an email to a mistyped address will never be informed that their message was never delivered... BAD, BAD, BAD... don't do it...
Yes, I'm aware of the traditional reasons not to do this. The entire domain serves as a spamtrap, but there are a couple addresses I'd like to reject at the border for testing purposes.
I think doing an access map in Postfix is the most likely solution. Thanks!