Exclude certain receipt email for srs about postsrsd HOT 9 CLOSED

Currently, the exclusion mechanism works with domain names only. I haven't tested this, but you could try and add a file-based lookup table to the canonical_maps like

sender_canonical_maps = dbm:/etc/postfix/no-srs, tcp:127.0.0.1:10001

and put a no-op rewrite for all excluded addresses in there:

[email protected]    [email protected]

Let me know if that works.

from postsrsd.

I was thinking about that a while ago as well. When external mails (with arbitrary sender address) are delivered to a local mailbox, the envelope-sender will still be rewritten by postsrsd in the proposed setup. Somehow postsrsd would have to know when to rewrite the envelope sender based on the envelope recipient (i.e. something like recipient_dependent_sender_canonical_maps, which obviously does not exist in postfix).

from postsrsd.

I have tried your suggestion above of canonical_maps. Unfortunately it does not seem to work. Emails delivered to local address still got rewritten.

from postsrsd.

Did you resolve it?

from postsrsd.

Unfortunately no.

from postsrsd.

So there is no way to disable SRS for a local virtual mailbox?

from postsrsd.

There is, but you have to have two set up two postfix instances (which isn't too hard). A receiving instance, that only decodes SRS, listens on the public ip and devlivers to mailboxes i.e. via delivery agents or lmtp and a sending one, that is set up as usual, but only listens on loopback. For the receiving one, you have to set the default smtp transport to the sending one.

from postsrsd.

I was also thinking about something like this, but how do you encode SRS in your setup?

Example 1: Mail from gmail to my server on a virtual alias map to forward the mail to yahoo
In this case SRS needs to ne applied to the mail so yahoo has a SRS return path.

Example 2: Mail from gamil to my server on a virtual mailbox. Here I do not need any SRS on the return path.

However, both cases also need to handle incoming mail already having SRS encoded addresses and in both cases bounces need to be handled correctly.

from postsrsd.

Example 1: gmail --> postfix-in --> postfix-out (+SRS encode) --> yahoo
Example 2: gmail --> postfix-in --> dovecot
Bounce should work as expected, since both instances are able to decode SRS. postfix-in will decode multi-hop bounces and postfix-out will decode single-hop bounces. Just tested a single-hop bounce, works as expected.

from postsrsd.