On Wed, May 21, 2025 at 05:46:34PM -0400, Wietse Venema via Postfix-users wrote:
> Matthew Kitchin via Postfix-users:
> > Hey all, former longtime user, but been away from Postfix for about 13
> > years.
> > I'm migrating a datacenter to Azure. We have a variety of things
> > (websites, copiers, monitoring apps, etc.) that send emails that don't
> > need to be replied to. In an Azure environment, we have to route these
> > through Azure SMTP services and they have to come from a designated
> > address. These emails routed to Azure SMTP have to be from
> > f...@example.com. Postfix came to mind as the ideal solution. This
> > setting does the trick.
> > sender_canonical_maps = static:f...@example.com
> > The problem is it seems to strip out the display name too. I've tried
> > various options with
> > sender_canonical_classes
> > and it doesn't seem to help.
>
> Sorry, those tweaks will not affect the display name, because Postfix
> canonical mapping affects only the emil address portion of a message
> header, not the display name.
>
> If something strips out the display name, then that happens with
> Postfix header_checks, with some non-Postfix content_filter, miklter,
> or smtpd_proxy_filter, or it happens outside of Postfix.
The above is correct, but Setting it aside the for a moment, have you
considered relaying the outbound mail from Azure via an on-prem
submission service you control? That way, you're not subject to
Azure's policies, and can send the messages with whatever content
you choose, appropriately DKIM-signed if (typically) desired, ...
The Postfix system on Azure can use a TLS client cert (self-signed cert
with a fixed keypair) or a SASL password to authenticate submission
(port 587 or 465) via your preferred MSA.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
