Failed delivery forward the bounce to another email address?
Problem reported by Jay Altemoos - Today at 8:59 AM
Being Fixed
Good day everyone,

I had an odd request from one of my clients, one of their office people will type in a wrong email address from time to time and they want to get notified of that instance so they can make sure to resnd with the proper email address. I tested a scenario on their account and setup a rule with content filter to foward the message when this happens, but the tests I have done so far don't forward the message. Our current build is 9322.

I have the content filter setup like this:
Any condition must be met

Subject or body
Delivery has failed to these recipients

Action: forward the email

Now with that said, I tested it through webmail and since it never left our server, the email comes back as noreply@ (their domain name). Now I guess I could try that noreply@ address but I can't be certain this will always be the case. The guess I have here is since the email never left our server, the content filter never trips the rule. Any other ideas here?

Any input is greatly appreciated.

Thank you
Matt Petty Replied
Employee Post
Content filtering is only for inbound domains or users. However, We're actively putting together a solution that will operate at the spool level that will be able to apply more "routing" based behaviors to the email and it will function for ANY email that hits the spool. This should cover some huge requests we've gotten from customers to allow them to better control the routing of messages on their server. It will function very similar to content filtering. Hoping to have out there soon stay tuned!

(These new changes would accomidate this particular scenario especially if you knew the common misspellings of the email and compiled them into a list)
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com

Reply to Thread

Enter the verification text