[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2023-10-28 Thread Paul White
The upstream bug report has seen no activity for nine years now.

There has been no reply to comment #6 for over five years.

The Debian bug report was closed as 'fixed' in another package.

I'm closing this now as 'Invalid' but if it is  still an issue
then both this bug report and the upstream Thunderbird report
need to be updated with current 'version' information.

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Invalid
Status in kdepim package in Debian:
  Fix Released

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2022-10-12 Thread Bug Watch Updater
** Changed in: thunderbird
   Importance: Medium => Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Incomplete
Status in kdepim package in Debian:
  Fix Released

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2018-07-11 Thread gf
Hello Thorsten,
Thank you for submitting this bug and reporting a problem with Thunderbird.  
You made this bug report in 2014 and there have been several versions of Ubuntu 
and Thunderbird since then. 

Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you run the following (only once):
apport-collect 1357227
and upload the updated logs and and any other logs that are relevant for this 
particular issue. 

Thank you again for helping make Ubuntu and Thunderbird better. 
G

** Changed in: thunderbird (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Incomplete
Status in kdepim package in Debian:
  Fix Released

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2018-01-03 Thread Bug Watch Updater
** Changed in: kdepim (Debian)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  New
Status in kdepim package in Debian:
  Fix Released

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227]

2014-08-18 Thread Thorsten Glaser
Created attachment 8474439
eMail exhibiting the bug

OK. This eMail contains a PGP message encrypted to 0xD1D8EFD2 whose
public and secret (passphrase is 123123) key I also attached. I just
confirmed with a coworker that this does exhibit the bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227]

2014-08-18 Thread Thorsten Glaser
Created attachment 8474435
secret part of test GPG key

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227]

2014-08-18 Thread Thorsten Glaser
Created attachment 8474434
public part of test GPG key

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2014-08-16 Thread Bug Watch Updater
** Changed in: kdepim (Debian)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227]

2014-08-16 Thread Mkmelin+mozilla
Please attach a sample mail (save as .eml)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] [NEW] broken charset/encoding autodetection for encrypted messages

2014-08-15 Thread Thorsten Glaser
Public bug reported:

Version: 1:31.0+build1-0ubuntu0.12.04.1

Hi,

this is a bug Mozilla™ Thunderbird and KDEPIM share:

When I send an Inline PGP encrypted message, whose body is using UTF-8,
to another user, the message is ASCII armoured (and thus 7bit). The
other user, running Thunderbird or Kontact, (or my own Kontact instance
in the “sent-mail” folder), gets the message and interprets the post-
decryption body as ISO-8859-1 (or Windows-1252, probably) instead of
UTF-8.

Manually switching the encoding to Unicode in the menu corrects this…
for this one message. (See
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
well.)

The problem here is that the human message encoding (everything within
the PGP armour) must be separated from the transport message encoding
(the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
MESSAGE-” is transmitted) must be separated from each other, which
they aren’t.

Please fix this, it harms using those MUAs in an enterprise environment.

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: kdepim (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #754265
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265

** Also affects: kdepim (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Unknown

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2014-08-15 Thread Thorsten Glaser
** Bug watch added: Mozilla Bugzilla #1054187
   https://bugzilla.mozilla.org/show_bug.cgi?id=1054187

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1054187
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  Unknown
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Unknown

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2014-08-15 Thread Bug Watch Updater
** Changed in: kdepim (Debian)
   Status: Unknown = New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  Unknown
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  New

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

2014-08-15 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1054187.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-08-15T08:32:33+00:00 Thorsten Glaser wrote:

User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 
Firefox/31.0 (Beta/Release)
Build ID: 20140717132905

Steps to reproduce:

The Thunderbird user received an Inline PGP encrypted eMail from me. The
content of that was UTF-8 encoded; the transport message body contained
an ASCII-armoured PGP message.


Actual results:

The Thunderbird user got the message interpreted as ISO-8859-1 or
Windows-1252, instead of UTF-8. This was also reported as:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1357227

This means the automatic detection of UTF-8 is broken, and/or the
encoding of the RFC822 transport container is mixed up with the encoding
of the message.

Manually selecting Unicode from the message encoding menu, the message
is displayed correctly. Switching away from the message and back to it
causes the setting to reset; this was also reported as:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980


Expected results:

The user should have seen the Unicode characters in the message
correctly, instead of mojibake.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1357227/comments/1


** Changed in: thunderbird
   Status: Unknown = New

** Changed in: thunderbird
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1357227

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  New

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1357227/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp