[Tickets #7641] Re: Changes of subject field of whups notification emails

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7641
------------------------------------------------------------------------------
  Ticket             | 7641
  Updated By         | a-dinc at hotmail.de
  Summary            | Changes of subject field of whups notification emails
  Queue              | IMP
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


a-dinc at hotmail.de (2008-11-05 12:26) wrote:

> You didn't say this in your original e-mail.  Your original e-mail
> said IMP does not display anything between brackets.  That is not
> true.

i'm sorry if there was a missunderstanding.
here is an example:
Subject: [Tickets #20] Re: Re: iptables
^^^^^^^^^^^^^^^^^^^^^^^^^^ original mail-subject when mail is viewed

changes to:

Subject: Re: iptables
^^^^^^^^^^^the subject-field when replied to the mail

> It is true that we do strip information in brackets from the subject
> header when replying/forwarding, when appropriate.
> http://cvs.horde.org/diff.php/imp/lib/Compose.php?r1=1.392&r2=1.393
>
> This subject cleaning uses the "base subject" algorithm defined in
> RFC 5256 [2.1]:
> http://tools.ietf.org/html/rfc5256

> I believe it is appropriate to strip this information out.
> obviously, any algorithm that attempts to "clean" a subject line has
> the chance of potentially removing desired information.  But this
> particular algorithm has been discussed for many years and the logic
> behind it is sound.  Most important, stripping this information does
> not affect in any way subsequent threading/subject sorting done on
> this message.
>
> If whups is sending out e-mails with ticket information in brackets,
> we should probably change that.  So this is probably a whups issue
> rather than an IMP issue.

maybe an other indication of that particular ticket would help sorting  
tickets. particularly when whups is used with emails updates.