[Users] [Bug 3251] New: A translated In-Reply-To header is sent translated
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Tue Aug 19 20:46:40 CEST 2014
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3251
Bug ID: 3251
Summary: A translated In-Reply-To header is sent translated
Classification: Unclassified
Product: Claws Mail
Version: GIT
Hardware: PC
URL: http://bugs.debian.org/758144
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: SMTP
Assignee: users at lists.claws-mail.org
Reporter: mones at users.sourceforge.net
Original reporter describes it in detail:
--------------
Configuration:
* LANG=es_ES.UTF-8
* claws-mail-i18n package installed
* "Translate header names" option enabled
* ~/.claws-mail/extraheaderrc file not present
* ~/.claws-mail/python-scripts/auto/compose_any file not present
* Python module installed but not enabled
Steps to trigger the bug:
* Web browse to the Debian user Spanish mailing list, i.e.
https://lists.debian.org/debian-user-spanish/2014/08/msg00000.html
* Click on the link to reply to the list (mailto protocol)
Claws-mail compose window appears. I've changed the recipient to my
own address to no disturb the list, and the subject to "Prueba". Here
are the headers of that mail. Please note the non-standard
En-Respuesta-A header instead of In-Reply-To.
--------------
You can see the whole headers on the URL above, just for completeness the wrong
header appears as:
En-Respuesta-A: <53DAF6C6.9030909 at sophie.unam.mx>
There's no need to really send the message, just queuing it and showing queue
source message shows the bug (and any --compose "mailto:..." with an
In-Reply-To header is enough to trigger it from command line, there's no need
to visit that page :)
I've been investigating a bit, but I don't see an obvious solution beyond stop
translating that header, of course. The In-Reply-To header is correctly parsed
and translated from the mailto: link into the compose window, but later is not
turned back to it's In-Reply-To value.
I suspect is just being treated as a custom added header because there's some
functions which do not include it as a "standard" header, like
compose_parse_header or compose_get_manual_headers_info in compose.c.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list