On Thu, Jan 13, 2022 at 08:20:55PM -0800, Kevin J. McCarthy wrote: > On Fri, Jan 14, 2022 at 03:26:36AM +0100, Vincent Lefevre wrote: > > I strongly disagree with the addition of $reply_prefix (commit > > 9c1ce59874ce1c8e97d0c5bd71847596dafb1d50), as this is contrary to > > RFC 5322, and non-standard prefixes are annoying in practice and not > > necessarily recognized by other users. > > Why strongly against? $reply_regexp has had "aw" listed for years > (although I just took that out of the default value too...).
I agree with what you're saying overall (in your whole message, not just the quoted part), Kevin. That said, following the robustness principle (be conservative in what you do, be liberal in what you accept from others) I do see a difference between $reply_prefix and $reply_regex, because $reply_regex is trying to _clean up_ the "undesirable consequences" mentioned in rfc5322, while $reply_prefix runs the risk of _creating_ or worsening them. w
