infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Updated] (INFRA-17093) dev@ commons is misconfigured to force-set reply to
Date Thu, 04 Oct 2018 03:50:00 GMT


Chris Lambertus updated INFRA-17093:
    Status: Waiting for user  (was: Waiting for Infra)

Thanks Greg. 

If the project wants to change this behavior, please link a vote thread in favor and we'll
make the change.

> dev@ commons is misconfigured to force-set reply to
> ---------------------------------------------------
>                 Key: INFRA-17093
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mailing Lists
>            Reporter: Eitan Adler
>            Assignee: Chris Lambertus
>            Priority: Major
> The mailing list appears to always and forcibly set the header
{{Reply-To: Commons Developers List <>}}.
> This is broken for multiple reasons.
> It violates RFC 2822 which requires that reply-to MUST only be used for when " ... the
author of the message suggests that replies be sent."
> While this should be enough, it is useful to explain some of the reasoning the standard
is the way it is:
> It breaks MUAs that have "reply to all" and "reply" (and maybe even "reply to list").
In doing so, having this setting greatly increases the chance of privacy violations by people
that expect the mailing lists to act normally
> It adds nothing: by means of copy and paste a private reply is still
> possible, just annoying, and a workaround for a broken mailing list
> Some mail readers provide 'personal mail' indicators.  This only
> triggered when you are on the CC or TO lines. The 'feature'
> breaks this.
> Some people prefer mail CCed to them as well as the mailing list,
> especially if reading a mailing list is lower priority than personal
> mail.

This message was sent by Atlassian JIRA

View raw message