Bowie Bailey wrote:
Catch-all setups always have this problem. You could use SA to figure
out which addresses are likely to be valid, but this means that you have
to accept the message and then call SA for EVERY one of these emails.
I'm aware of that... but the benefits outweigh the problems.
The best way is to use your MTA. Set up a method for your users to
create these email addresses as real email aliases in your MTA. Then
you can set your MTA to only accept valid email addresses and the
problem goes away.
That would be a problem - since there is no definitive list of 'valid'
email addresses - however I do know the form of all valid email
addresses. If I could replace list-based lookup with a function to
parse and validate email addresses with my MTA, I'd be laughing.
It's no big problem to process every spam - but it would be desirable to
at least mark all these made-up email address destinations with a higher
spam score. Is there an existing rule I can customise, or would I have
to start from scratch?
