You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g.: I send a message with From: =?UTF-8?Q?M=C3=A4rtin_Sluka?= <martin@sluka.de> to a list named localpart@domain, and back comes a message with From: "Märtin Sluka via it-intern" <localpart@domain>, that is, with unescaped non-ASCII-characters in the From: header line.
BTW, I must say I find it a bit disadvantageous that rewritefrom is enforced for domains with DMARC policy reject, because if it wasn't, I could just continue using my own wrapper script for these things. (But with rewritefrom I get very strange From: header lines and double Reply-To: header lines as soon as I set the DMARC policy for our own domain to reject, which BTW hit me by surprise yesterday as kind of an April Fool's joke by ezmlm. ☺)
Regards
fany
P.S.: Thanks a lot for maintaining ezmlm! We are using it for twenty or so years now for some hundred mailing-lists @mensa.de.
The text was updated successfully, but these errors were encountered:
E.g.: I send a message with
From: =?UTF-8?Q?M=C3=A4rtin_Sluka?= <martin@sluka.de>
to a list named localpart@domain, and back comes a message withFrom: "Märtin Sluka via it-intern" <localpart@domain>
, that is, with unescaped non-ASCII-characters in theFrom:
header line.BTW, I must say I find it a bit disadvantageous that
rewritefrom
is enforced for domains with DMARC policy reject, because if it wasn't, I could just continue using my own wrapper script for these things. (But withrewritefrom
I get very strangeFrom:
header lines and doubleReply-To:
header lines as soon as I set the DMARC policy for our own domain to reject, which BTW hit me by surprise yesterday as kind of an April Fool's joke by ezmlm. ☺)Regards
fany
P.S.: Thanks a lot for maintaining ezmlm! We are using it for twenty or so years now for some hundred mailing-lists @mensa.de.
The text was updated successfully, but these errors were encountered: