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
If people send LSs through the datatracker, the email generated comes from [email protected] and the person listed in the From flied doesn't get a copy. It would be good to also cc that person, especially for cases where the LS was sent to [email protected] and is uploaded by the secretariat manually. The original sender will get a note when the secretariat ticket is closed (and processed), however, it would be way nicer to have that person directly cc'ed in the send-out of the LS itself.
As a side note, if a LS is sent to a wg, the chairs show up in the To field and the mailing list only in the cc. That seems also unexpected. I would expect to have the wg list in To, either even just the list address or both the list address and the chairs directly. Sorry if this should be a separate issue, but it seemed easier for me to mention this here as well; also this part is not really a problem that needs fixing, it's more a note.
Description
If people send LSs through the datatracker, the email generated comes from [email protected] and the person listed in the From flied doesn't get a copy. It would be good to also cc that person, especially for cases where the LS was sent to [email protected] and is uploaded by the secretariat manually. The original sender will get a note when the secretariat ticket is closed (and processed), however, it would be way nicer to have that person directly cc'ed in the send-out of the LS itself.
As a side note, if a LS is sent to a wg, the chairs show up in the To field and the mailing list only in the cc. That seems also unexpected. I would expect to have the wg list in To, either even just the list address or both the list address and the chairs directly. Sorry if this should be a separate issue, but it seemed easier for me to mention this here as well; also this part is not really a problem that needs fixing, it's more a note.
Code of Conduct
The text was updated successfully, but these errors were encountered: