Global email filters.
Hello good day.
My problem is that when I want to register a SPAM email in the section of global email filters I get the following message:
To prevent recursive email delivery issues, you can not use a recipient from a controlling domain in a global delivery filter.
Which was presented a few days ago, since we have been working with Cpanel for a long time and we never had an error of this kind.
I hope you can help us
-
add SPAM email address at spam filter > Additional Configurations > Blacklist (Emails Never Allowed) 0 -
Hello good day. My problem is that when I want to register a SPAM email in the section of global email filters I get the following message: To prevent recursive email delivery issues, you can not use a recipient from a controlling domain in a global delivery filter. Which was presented a few days ago, since we have been working with Cpanel for a long time and we never had an error of this kind. I hope you can help us
Can you explain what the filter is going to be doing? I'm not clear on why the Interface would note that error based on what has been explained this far. Thanks!0 -
I get a similar error. I have a set of global email filters to catch wildcard entries so basically richard-anything@mydomain will get forwarded to my richard mil box and so on for other email addresses. I do this by using a filter: Any recipient matches regex \b(?i)richard[A-Za-z0-9._%+-]+@mydomain.*\b and that redirects to richard@mydomain I posted in more detail in the wildcard thread here: 0 -
Same problem, and I'm not using wildcards: From: subscriber@='someone@company.com'>OtherCompany.com [and] To: listserv-bounces@MyDomain.com Redirect to: listserv@MyDomain.com Generates the error message: "To prevent recursive email delivery issues, you cannot use a recipient from a controlling domain in a global delivery filter" I have no idea what that message even means in this context. 0 -
@LanceHaverkamp - you'll actually experience the same error even without the "from" section. The reason for this is that it can cause an infinite loop. If you have a filter setup to route "address1@domain.com" to "address2"@domain.com, the filter will still need to process the headers to see the "To" section in this case, which would cause the email to infinitely be filtered. To break this loop, we just don't allow that. You can find additional details on this in an older thread here: 0 -
Ah, so because the Global Email Filter will be applied to all incoming email to the domain, they would be called each time an email is redirected to another email on that domain, and thus have them called again and again and again. The workaround is to go add a filter on just one (or more) accounts that redirect emails to the desired account. 0 -
Sorry to comment on this post, I know it's old, but I had this problem today and the solution is super simple...
If you saw this error, you are trying to deliver the email to a local account, so instead of using the "redirect to email" action, simply use the "Deliver to folder" action and select the account/folder that should receive the message ;D
0
Please sign in to leave a comment.
Comments
7 comments