From: Victor Duchovni (no email)
Date: Sun Aug 01 2004 - 17:03:26 EDT
On Sun, Aug 01, 2004 at 10:47:16PM +0200, Arvinn Lokkebakken wrote:
> You can use an access map to FILTER to through an optional transport.
> Check out access(5) and transport(5).
>
Bounces are internally generated and not subjected to filters or
access lookups. The bounce recipient is subject to "relayhost",
default_transport, local_transport, ... settings and transport table
lookups, but these are not specific to bounces.
It is possible to create a Postfix input instance that sends all real
mail to Postfix output instance A and all bounces and notices to
Postfix output instance B.
content_filter = smtp:[127.0.0.1]:portA
relayhost = [127.0.0.1]:portB
neither portA or portB should have a listener in the same instance,
they need to live in a separate main.cf/master.cf file. Either or both
ports could be filtered by an SMTP proxy of some sort.
This could "solve" configurable bounce text, but it is the wrong solution.
The right solution is to invent a suitable template format.
What happens when a single message is sent to recipients in multiple
customer domains? Which bounce template should be used when multiple
recipients fail? There is no good answer.
Therefore each domain needs a separate SMTP listener, i.e. this requires
virtual (secondary) IP addresses. Then one Postfix instance per domain,
can use a suitable template for that instance.
All that is missing is a suitable mechanism for specifying the bounce
text. This could probably be a project that also adds configurable headers
(what to add if missing, which headers to canonicalize, ...)
-- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:?body=unsubscribe%20postfix-users>
|
|
|