I know that, but believe it or not, this is exactly what a customer is asking me.
I would like to tell him "No, it's impossibile" but it would not be so cool if he then discover a way to do that.
Well, I'm trying to make him change his mind with diplomacy... but I want to be prepared :)
I think that playing with the SEND_ACCESS table in mappings I could achieve this..
One thing I've learned over the many years I've done support is that when a customer asks for something you know is a Bad Idea, it's typically best not to just give it to him.
Surpressing all error messages to mail senders can result in "lost" mail, which will cause your customer many, many headaches. Here's a likely scenario:
1. A user types a mail address incorrectly, and sends a message.
2. Since the address is incorrect, it never gets to the person he's trying to send it to.
3. Since no error message comes back, he assumes that the message got there.
Now, you have "lost mail".If the message was important, you have very unpset users.
Better, get your customer to tell you what problem he's expecting to solve by surpressing messages to the users, and in what condition. Perhaps we can help you educate your user.
Hi,
Getting notifications sent to the postmaster-only implies that you want to change the envelope from address - so that bounce emails are therefore sent to this address instead of the original sender. This will of course break mail posting restrictions that rely on email addresses - which a lot do and as Jay has already noted, messages potentially 'disappearing' from the end-user perspective.
If you really insist on going down this path the following may help:
FROM_ACCESS
*|SMTP*|*|tcp_*|from_address@domain.com|* $Jpostmaster@domain.com
This will rewrite the envelope from address for emails with an envelope from of from_address@domain.com to postmaster@domain.com.
Please note this rule will apply to ALL emails including emails sent from outside your organisation. The rule can be further restricted to apply to say just authenticated email (tcp_auth/tcp_submit) or email within your organisation (tcp_intranet) or just your own domain (*@domain.com) etc.
Regards,
Shane.