Thanks Rolf.

Its a very rare issue. Removing the faulty forwarding fixed the problem. Wanted to make sure that I had all Mercury/32 settings correctly set.

Thanks again.

Compton

Hi

I'm using 4.74. I encountered an issue for which I need assistance/advice on the best method of handling.

A local user forwarded his email to another local user, unfortunately it was an incorrect email address. The server forwards the email resulting in an error message (user not existing), to the originating mail account which then encounters the forwarding and thus attempts to also forward the error email....and it then begins loops on and on.....the queue fills up with undeliverable messages and the server got hung up.

Some particulars - In the core - I return the first 30 lines - I had the number of retries before failure set to 4...now set to 2 -  the progressive retry algorithm set to ON -  Minimum period between queue retries set to15mins.

What is the best way to handle this issue?

Any thoughts/assistance/advice would be very much appreciated.

Thanks

 Compton

Mercury will try to catch and break loops, but this was apparently one that couldn't be caught. Apart from the obvious solution (to remove the faulty forwarding!) you could probably stop Mercury from sending non-delivery notifications altogether by clearing the Delivery failure template field in Core configuration / Files. I wouldn't recommend it, though, as it most likely would have some undesired effects in other non-delivery cases.

/Rolf