On 5/6/2010 9:16 AM, charles wrote:
/dev/rob0 wrote:
 > On Thu, May 06, 2010 at 07:37:00AM -0500, CT wrote:
 >> I do believe this is a relatively simple issue to solve. but
 >> haven't found it yet..
 >>
 >> *my-relay* = internal relay
 >> *master-relay* = internal and external relay
 >>
 >> Setup
 >> Sending host => *my-relay* => *master-relay*
 >>
 >> relayhost = master-relay
 >>
 >> Looping issue..
 >> When the *master-relay* sends *my-relay* a bounced message *my-relay*
 >> sees the destination and then sends it back to the *master-relay*.
 >>
 >> I want my-relay to "receive" *all* email from the *master-relay*
 >> and dump it into the Postmaster (alias) mailbox instead of sending it
 >> *back* to the *master relay*..
 >>
 >> What would be the best way to do this.?
 >
 > I think it is simple too. Solve it outside of Postfix, in the MUA
 > and/or mail-sending software. Set the sender domain to be in your
 > $mydestination, and the localpart to be a valid local(8) user or
 > something in aliases(5). Then when a bounce comes from the
 > master-relay, your Postfix will know what to do with it.
 >
 >> here is the postfinger output..
 >
 > Munged beyond all possible usefulness. Mail routing issues tend to
 > require real domain names to diagnose properly. Please also include
 > logs if you think you need to post again.
 >
 >> -- postfinger output --
 > [snip]

I should have stated, I have no control over the sending hosts in the
trusted networks, subsequently *most* are *send-only*and in most cases
do not have an internal or external DNS or MX record.

The master-relay is a "required" setting as it does all the filtering,
my-relay is a legacy service that needs to stay in place due to several
necessary static mappings in the transport file that can not be entered
on the *master-relay*.

There is only 1 SMTP admin for the *master-relay* (actually there are 3
masters) and I want to do my part to fix any *send-only* hosts that use
*my-relay*.

I do finally get the bounced messages but only after "too many hops".


You can use a check_sener_access map with something like
<>  REDIRECT postmas...@localhost

or whatever the local postmaster address is.

Beware: This will catch all null-sender messages and has the potential to break other things.

 -- Noel Jones

Reply via email to