On 2/15/2017 11:13 AM, Marek Kozlowski wrote: > On 02/15/2017 02:18 PM, Marek Kozlowski wrote: >> On 02/15/2017 02:04 PM, Marek Kozlowski wrote: >>> sender_canonical_maps = sth1, sth2, sth3 >> >> One more question: >> >> Is it possible to apply different `sender_canonical_classes' for sth1, >> sth2 and sth3 respectively? > > OK, I'll explain it more thorough. The problem is:
Postfix built-in address rewriting is based on fairly simple key|result tables, and isn't designed for conditional processing. Postfix provides several plugin interfaces for external processing such as milter, proxy, or content filters. Perhaps one of these interfaces can provide the extra functions you need. -- Noel Jones > > I have two mail servers: let's say: A and B. For some reasons a few A > mail accounts have been moved to the B server (moreover: with different > user names) but I'd like to keep that change transparent. For this > reason there are virtuals on A redirecting incoming mail for those users > to the B server and canonicals on B rewriting sender addresses for > outgoing mail from those users to their official A-type addresses. Of > course: most client programs show `from:' rather than envelopes so at > this point canonical needs to rewrite both. > > But those users are allowed to forward their mail to their external (for > example: Gmail) accounts. Gmail uses SPF checks so I have to use > postsrsd for adding SRS entries to envelope addresses. I don > t want postsrsd to modify `from:' fields because it has nothing to do > with SPF and those fields are visible in client programs and should be > "clean". > > The problem is that postsrsd from the postfix perspective acts as a yet > another canonical lookup table so the same `sender_canonical_classes' > apply to it and the normal canonical described above... > > Best regards, > Marek > >
