From original mail by betelgeuse: > can we implement a filter to gentoo-dev-announce that does not allow > mails to get in without Reply-To being set? If it needs procmail etc > work I can help with that.
I have added the following rule to the mlmmj access control: deny !^Reply-To:
I am afraid this is not enough. My original e-mail had a Reply-To header set properly. The problem is that I cross-posted to multiple mailing lists. So what we need here is to prevent more than one entries in the CC: field when you send something to gentoo-dev-announce.
Sorry I've just read your e-mail. Well, I feel the problem is partially solved so can we keep this bug open?
Can infra add a proper auto-reply if the mail got rejected? Right now the sender doesn't receive anything, right?
I submit that we shouldn't be munging the reply-to headers at all; this violates RFC2822. The below reference offers solutions for this issue. [1]. Thanks for your consideration, William [1] https://woozle.org/~neale/papers/reply-to-still-harmful.html
Nothing to do for comrel here.
We don't munge Reply-To for gentoo-dev-announce, but we do REQUIRE they are set by the author.