Matt Healey
My feedback
3 results found
-
84 votesMatt Healey supported this idea ·
-
4 votesMatt Healey supported this idea ·
-
27 votesAdminGabriel (PM, Axigen) responded
I understand the request, but before we schedule this, I would like to better understand the actual use case.
@All: Could you please detail your catch all usage, with a practical example, and as well as give some examples as to what kind of rules you would create (e.g. 1. conditions, 2. actions)?
Thank you,
GabrielAn error occurred while saving the comment Matt Healey supported this idea ·
Specific use case is being able to block specific incoming email addresses, while using a catch all. Once an email address starts to receive a lot of spam, we used to create a rule in Kerio that would simply mark anything to that address as spam and delete it. Creating a catchall, in Axigen seems to not run any rules, or give us the ability to deny-list a TO or CC address (only From), and makes having a catch-all very cumbersome.
So I agree with the other statements. Have a catch-all go to a specific account, and then let rules at the Server/Domain/Account level handle things from there.