> How creative. I'm impressed.
>
> Thinking about the problem again, if he wants sender-based routing
> for ALL his mail, then it can be done with only a few lines of code
> in the Postfix queue manager.
>
> Below is an untested patch that turns on sender-based routing
> when you specify "sender_based_routing = yes".
>

When people say sender routing, they are often asking for something
else, sender (user granularity) dependent special processing, e.g.
diverting mail from a harrasser to corporate security to accumulate
evidence for a cease and desist order.

The queue manager + trivial-rewrite daemon route only on the destination
domain, so the granurality of virtual rewrites is not available.

Bennett's approach mapped

        MAIL FROM: <harassernasty.org>
        RCPT TO: <victimexample.org>
        DATA
        HEADER

        BODY
        .
to

        MAIL FROM: <harassernasty.org>
        RCPT TO: <harasser=40nasty=2Forgnasty-harasser.divert.invalid>
        DATA
        HEADER

        BODY
        .

The transport handling ".divert.invalid" encapsulates the message as a
message/rfc822 with a new header that logs the original envelope sender
and recipients and then forwards it to the appropriate mailbox:

        MAIL FROM: <>
        RCPT TO: <nasty-harrasserlocalhost.example.org>
        DATA
        From: <harassernasty.org>
        To: <victimexample.org>
        Subject: Diverted mail from ...
        Content-Type: message/rfc822

        HEADER

        BODY
        .

This is very different from routing on the sender domain... The important
elements are that the delivery agent selection is based on the entire
address and the delivered message is transformed in a customized fashion
to preserve in a new header the original envelope information.

-- 
	Viktor.
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]