Did this used to work, do you have an older example of when it did work? Folks here are correct that we're parsing the Received headers looking for an IP to use to do SPF authentication here. We really want to know the auth status in order to do better spam detection.
Another "solution" would be to DKIM sign the message, but I imagine the local delivery probably avoids that as well. In any case, if there was an actual change in behavior on our part, having the old/new to look at would help for filing a bug. Brandon On Tue, Feb 22, 2022 at 9:11 AM Christos Chatzaras via mailop < mailop@mailop.org> wrote: > To make it more clear: > > 1) Customer logins to Gmail and sends e-mail from to supp...@elmetal.gr > to sa...@elmetal.gr using our SMTP (server13.cretaforce.gr) > > 2) Customer logins to other Gmail account and receives the above e-mail. > > Both supp...@elmetal.gr and sa...@elmetal.gr are on the same server ( > server13.cretaforce.gr) so we have local delivery. > > I will try to remove the authenticated sender line. > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
