re:
https://techcommunity.microsoft.com/t5/exchange-team-blog/updated-requirements-for-smtp-relay-through-exchange-online/ba-p/3851357
Let's say I send an email. I use:
> mail from: <annoy...@spammer.com>
and in the data (body)
> From: Professional Legit Person
<igotalovelybunchofcoconuts@innocent.pizza>
Looking at headers from Microsoft, they track 2 fields: smtp.mailfrom
and header.from
From what I can work out, they'll start to say that if smtp.mailfrom !=
header.from (in my example, spammer.com != innocent.pizza), Microsoft
will bounce the email - even if authenticated etc. They seem very happy
to spend our time, huh? (unless I have something wrong)
I can & do use generic sender address masking successfully. In fact, in
the above example, in reality, "innocent.pizza" is actually the hostname
in most cases. generic is the wrong solution to my issue. Also
masquerading won't work, because I can't guarantee who the "mail from: "
that postfix includes will be.
I don't agree with Microsoft's action here, & think many use cases would
be broken if everyone did this, such as my forward from yahoo, & maybe
mailing lists.
My question is this: is there a way to hide the "mail from: " value
from Microsoft & instead use the generic mapped sender instead? In my
example, Microsoft would only ever see "innocent.pizza" and never
"spammer.com" as if I'd originally done this instead, when I did not:
> mail from: <igotalovelybunchofcoconuts@innocent.pizza>
Sorry for the wordy question & feel free to just point me to what I
should read if you know rather than explain.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
