Good Morning,
Is there a way to hide the syserr as well as the path returned by a
pipe transport? For instance, I have virtual accounts and they are
handled by a custom transport. When a message is sent to a
non-existent user, the mailer-daemon response to the sender is:
b...@example.com:
Adam:
Good Morning,
Is there a way to hide the syserr as well as the path returned by a
pipe transport? For instance, I have virtual accounts and they are
handled by a custom transport. When a message is sent to a
non-existent user, the mailer-daemon response to the sender is:
Wietse:
Thank you for the reply. Rest assured this was specifically for SASL
authenticated users. Non-authenticated users would have had an
unknown recipient rejected by the policy service.
I solved the issue by setting up virtual_mailbox_maps. My primary
reason for wanting to avoid that was
On Fri, Jun 18, 2010 at 05:01:14AM -0500, Adam wrote:
Good Morning,
Is there a way to hide the syserr as well as the path returned by a
pipe transport? For instance, I have virtual accounts and they are
handled by a custom transport. When a message is sent to a
non-existent user, the
