On Tue, Jan 10, 2023 at 03:02:36PM -0800, Dan Mahoney wrote:
> We are already using the alias-function as you suggest:
>
> support-contacts: support-st...@isc.org,
> :include: /usr/local/etc/rt42/contact-alias.lst
I don't see an "owner-support-contacts" alias paired with this. That's
needed so that the envelope-sender is replaced with the list owner
address.
> And I see the bit about -owner being special, however, this is not
> about the envelope sender, but the envelope RECIPIENT:
You're confused. The envelope recipients are whatever you put in that
alias.lst file
> When we attempted to deliver to someone hosted on office 365, we get a
> bounce like the below, where it seems to not have rejected on the
> envelope header, but on the envelope recipient..
s/header/sender/ I think...
> I spun up a test list, with and owner- alias, and the “owner” magic
> seems to also omit the envelope RECIPIENTS,
You remain confused. Of course the recipients can't be hidden from
the receiving system, the message has to be delivered to them after all.
> but none of the docs for reset_owner_alias, owner_request_special, or
> aliases seem to mention this header,
Envelope != Header.
> Here’s that bounce message:
> Delivery has failed to these recipients or groups:
>
> support-conta...@support.isc.org Your message couldn't be delivered to
> the recipient because you don't have permission to send to it.
What's in your Postfix logs for the outbound delivery of this message?
What recipients was it sent to? The domain in question is NOT hosted
by Office365, how did the message get there?
support.isc.org. IN MX 5 mx.pao1.isc.org.
support.isc.org. IN MX 10 mx.ams1.isc.org.
If Outlook is applying delivery restrictions based on *header*
recipients, they're broken, and there's not much that Postfix can
reasonably do about that (though generic(5) rewriting can perform some
limited 1-to-1 header recipient rewriting on output).
--
Viktor.
