tickets #80694
closedMailing list archives break text like "<gp@suse.com>"
100%
Description
Looking at
my signature which usually reads
Dr. Gerald Pfeifer gp@suse.com, CTO @SUSE + chair @openSUSE
shows up as
Dr. Gerald Pfeifer <gp(a)suse.com>om>, CTO @SUSE + chair @openSUSE
I understand replacing @ by (a), but verbatim showing < and > looks wrong,
and doing that and adding "om>" definitely does.
Files
Updated by pjessen over 3 years ago
- Tracker changed from communication to tickets
- Private changed from Yes to No
GeraldPfeifer wrote:
Looking at
my signature which usually reads
Dr. Gerald Pfeifer gp@suse.com, CTO @SUSE + chair @openSUSE
shows up as
Dr. Gerald Pfeifer <gp(a)suse.com>om>, CTO @SUSE + chair @openSUSE
I understand replacing @ by (a), but verbatim showing < and > looks wrong,
and doing that and adding "om>" definitely does.
Agree, that is not right.
I have also opened a couple of tickets on the archiving, I am slowly beginning to wonder if Mailman/Hyperkitty might not be quite finished.
Updated by pjessen over 3 years ago
pjessen wrote:
I have also opened a couple of tickets on the archiving, I am slowly beginning to wonder if Mailman/Hyperkitty might not be quite finished.
ticket #80624 - header duplicated in "view headers" ?
ticket #77701 - (post mortem) - archives - how can I view the source of a message? Is download the only option?
ticket #77701 - (post mortem) - archives - in the downloaded message, virtually all headers have been deleted?
Updated by pjessen almost 2 years ago
- Category changed from Mailing lists to Upstream
Assigning to Upstream.
Updated by pjessen 11 months ago
- File Screenshot_20230530_080625.jpeg Screenshot_20230530_080625.jpeg added
- Status changed from New to Resolved
- % Done changed from 0 to 100
crameleon wrote:
@pjessen: What's the upstream reference (link to bug report, email conversation, ...)?
There is nothing - pursuing bugs with mailman is very tiresome, I don't get paid enough for that.
I merely assigned to "Upstream" to indicate that we are dependent on upstream, that there is nothing we can or are going to do.
Judging by the current looks of that archive page, the problem appears to have been resolved.
Updated by GeraldPfeifer 11 months ago
Nice to see this has been resolved via upstream.
And it means $SOMEONE seems to have made it a point keeping our mailing list/mailman infrastructure up to date. Thank you for that!