Wietse Venema:
> Matus UHLAR - fantomas:
> > bumping if anyone has a better idea.
> >
> > On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
> > >I'm trying to implement SRS using postsrsd. Since it always rewrites
> > >non-local sender (even for incoming mail) I'm trying to restrict it
> > >only for outgoing mail.
>
> SRS sender rewriting is in scope for email that is forwarded from
> elesewhere to elsewhere through virtual aliasing etc., or for email
> that is delivered locallly AND FORWARDED through ~/.forward files,
> or delivery to "|command".
This delivers remotely with a remote envelope sender.
> SRS sender rewriting is not in scope for email that originates
> locally, email that a less-preferred MX forwards to a more-preferred
> MX, or email that is delivered locallly AND NOT FORWARDED through
> ~/.forward file or delivery to "|command".
This delivers remotely with a local envelope sender, or
remotely with a remote envelope sender.
> Also, one email message can have multiple recipients, some in scope
> for SRS and some recipients of that same message not in scope. This
> determination may not be possible in the general case with a single
> MTA instance. You may have to delete functionality (eliminate
> ~/.forward and "|command"), or you may have to split email streams
> and handle different streams with different MTA configurations.
Start with two MTA instances: one MTA for MX service and remote
deliveries, and one internal MTA for local submission and delivery.
Apply SRS to email on the way from the internal MTA to the MX MTA
if the envelope sender is not local (sender_dependent_default_mumble).
I haven't considered the SRS reverse transformation. It probably
needs to happen on the way from the MX MTA, to the internal MTA.
Maybe a dedicated SMTP port on the internal MTA.
Wietse
