FS#48239 - Notification emails for new requests and requests acception/rejection do not get threaded correctly
Attached to Project:
AUR web interface
Opened by Baptiste (zorun) - Thursday, 18 February 2016, 17:26 GMT
Last edited by Lukas Fleischer (lfleischer) - Sunday, 14 August 2016, 19:50 GMT
Opened by Baptiste (zorun) - Thursday, 18 February 2016, 17:26 GMT
Last edited by Lukas Fleischer (lfleischer) - Sunday, 14 August 2016, 19:50 GMT
|
Details
When a acception/rejection notification email is sent to
aur-requests, the email is not threaded to the original
request email in the mailing list archives.
For instance, see this orphan request and subsequent acception in February: https://lists.archlinux.org/pipermail/aur-requests/2016-February/thread.html [aur-requests] [PRQ#4837] Orphan Request for ring-daemon [aur-requests] [PRQ#4837] Request Accepted They are not threaded in mailman's web interface, which makes it hard to visually see what the acception or rejection actually refers to. Now, when a human replies to an email, the reply gets threaded correctly in mailman's web interface. Strangely enough, the code already seems to set the In-Reply-To and References headers (see "thread_id" in request_open() and request_close(), in file scripts/notify.py). Thus, this may be a bug in aurweb OR in mailman's archive web page. |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Sunday, 14 August 2016, 19:50 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 4.2.1.
Sunday, 14 August 2016, 19:50 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 4.2.1.
FS#46645which was closed, found this bug, and I think it's fixed since PRQ#4858. First notification mail now lacks References/In-Reply-To and has a custom Message-ID, and thus the responses get threaded properly.