[bug #15074] Wrong $SUBJECTNA:U$ substitution for subject with mime encoding

2005-12-20 14:48:10

Update of bug #15074 (project mhonarc):

                  Status:                    None => Confirmed              


Follow-up Comment #1:

Not sure if it worth the effort to fix this bug.  If TEXTENCODE
is enabled, this problem does not exist since all non-ASCII
encoded text is decoded when messages are read.

When TEXTENCODE is disabled (the default), mhonarc stores
subject text in "raw" form, which may include non-ascii encoding.

The resource variable resolution does not check for non-ascii
encodings.  It could be added, but it complicates things and
increases processing overhead.  Details of why it complicates
things can be provided if interested.

The work-around solution is to enable TEXTENCODE, or whatever
is processing the subsequent URL is modified to deal
with non-ASCII encoded text.
(Note, DECODEHEADS can provide a partial solution for
selected charsets.)

Unless there is an overwhelming need, I will probably not
fix this bug and call it a limitation instead :)


Reply to this item at:


  Message sent via/by Savannah

To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the

<Prev in Thread] Current Thread [Next in Thread>
  • [bug #15074] Wrong $SUBJECTNA:U$ substitution for subject with mime encoding, Earl Hood <=