Viktor, I apologize for the off-list email — I would like to add some context here, but also not mention my day job by name specifically on a public mailing list.
We are already using the alias-function as you suggest: support-contacts: [email protected], :include: /usr/local/etc/rt42/contact-alias.lst And I see the bit about -owner being special, however, this is not about the envelope sender, but the envelope RECIPIENT: 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.. I spun up a test list, with and owner- alias, and the “owner” magic seems to also omit the envelope RECIPIENTS, but none of the docs for reset_owner_alias, owner_request_special, or aliases seem to mention this header, only the envelope-sender address . Do the docs need to be updated to cover this as well? -Dan === Here’s that bounce message: Delivery has failed to these recipients or groups: [email protected] <mailto:[email protected]> Your message couldn't be delivered to the recipient because you don't have permission to send to it. Ask the recipient's email admin to add you to the accept list for the recipient. For more information, see DSN 5.7.129 Errors in Exchange Online and Office 365 <https://go.microsoft.com/fwlink/?LinkId=389365>. > On Jan 10, 2023, at 2:07 PM, Viktor Dukhovni <[email protected]> > wrote: > > On Tue, Jan 10, 2023 at 01:07:40PM -0800, Dan Mahoney wrote: > >> Does anyone know of a simple remailer tool that can be used inside an >> aliases (via a pipe) file that will: > > If you configure: > > # Add explicit domain if $myorigin is not right here > owner-somelist: somelist-request > somelist: :include:/some/path/myexploder-aliases > > Then no trace of the original envelope remains. THe ":include:" file > should have one recipient per line. See aliases(5) for details. > > -- > Viktor.
