Re: [mlmmj] Problem with mail sent by @orange.fr to @protonmail.com
Baptiste Daroussin <[email protected]> Mon, 27 Nov 2023 22:55:22 +0100
| Newsgroups | org.mlmmj.mlmmj |
|---|---|
| Message-ID | <[email protected]> |
Le 27 novembre 2023 16:09:47 GMT+01:00, Uffe Jakobsen <uffe@uffe=2Eorg> a = =C3=A9crit=C2=A0: >Pierre Cros writes: >>=20 >> It works well even for the pretty bad admin I am=2E But I don't know wh= ere to look to understand the following problem : >>=20 >> =E2=80=A2=C2=A0My list works well for all users most of the time >>=20 >> =E2=80=A2=C2=A0When a sender uses orange=2Efr SMTP to send a mail on th= is list, the subscribers with @protonmail=2Ecom adresses won't get the mail= at all (not even in the spams), the other subscribers will receive it=2E >>=20 >> =E2=80=A2=C2=A0if some @orange=2Efr sender, sends a mail directly (with= out the list) to some @protonmail=2Ecom receiver, it works >>=20 >> It looks like mlmmj adds something that will make mails sent by orange= =2Efr unacceptable for @protonmail=2Ecom mail serveur=2E >>=20 > >The most common problem is if a list member is sending from a domain that= exposes SPF/DMARC information=2E > >Relaying such message through mlmmj (and any other mailing list) will ret= ain the sender information - but with a new origin (the mlmmj server) > >If the receiving part (protonmail) inspects the SPF/DMARC (supplied by th= e originating domain) it will propably drop the email or put it in quaranti= ne=2E > >Mlmmj still nedds a proper sender rewriting feature that will rewrite the= sender information into something ala "Original sender name via mlmmj-list= e-name <mlmmj-list-name@mlmmj-domain-name=2Exxx>" > >PS: I'm just guessing about the reasons for your described problem=2E=2E= =2E > > >/UFfe > Well if you don t alter the email (no subject modifications for example) a= nd the email is signed with dkim the from munging is not required, all the = freebsd mailing lists are setup with mlmmj and have no problems with proton= mail and orange or any other mail provider with "strong" verification polic= y=2E I first went down the "munging from" path using rspamd in front of mlmmj (= hence the new feature of suporting X_ORIGINAL_FROM in mlmmj 1=2E4=2E0)=2E B= ut then realised that if I stop altering the emails (just play with custom = headers) then the dkim signatures remains valid and all mail providers do a= ccept the emails as only being relayed=2E Best regards, Bapt