Maybe a basic filter rule for 'failure' in the subject and MOVE to admin or a temp user for review?

Keeps them out of the users boxes.

You just have to ride it out, it will stop eventually. 

PS

"..and no relaying at all."

If you have outgoing mail you are relaying. Any mail accepted by your server addressed to a non-local domain must be relayed to the server that handles that domain. [:)]

I assume you mean that you do not relay mail from non-local sources. [:)]

I seem to have managed to make a mess of my normally well-behaved M/32 system this morning.

I have been having big problems with getting swamped by rejection notices from having my email spoofed by spammers. I asked for advice on dealing with this on the Internet list, but received none. So...    ....I thought I would try to deal with this using content control in Mercury.

 I added a new ruleset to try to catch the offending mail, but the net effect has been to now give a relay error when I try to send any mail to the internet.

 I removed the ruleset I had added and put content control back to the state it was in before I started.

All outgoing mail is still being rejected as a relay attempt (I don't allow any relaying).

What on earth have I done wrong?

Help!

Tim

Do you have IP ranges with exemption from relaying restrictions (mercS config) for your local users.

Do your users Authenticate to allow relaying? Is this occurring properly? (check mercS session logs)

Have you changed anything in the Core - Local Domains?

No  - I have no exemptions, no changes to the core and no relaying at all.

 I really don't know what was happening - but it seems to have straightened itself out. All mail is flowing normally again now, with no additional intervention from me!!!

Now I just have to solve my original problem of all those delivery failures....

Thanks for the help

 Tim