-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Am 2013-01-21 18:10, schrieb Daniel Kahn Gillmor:
> I'd be fine making it an experimental change, and documenting it
> in README.Debian. I confess i'm wary of plunging into another
> 100-message thread on the upstream list, but i'm willing to p
On 01/19/2013 01:07 PM, Willi Mann wrote:
> What is unclear to me is if inline PGP messages are broken by design.
> Bug#698080 more looks like a regression that should be fixable, not an
> inherent problem of inline PGP. For attachments, enigmail per default
> asks how to send them.
i agree that #
On 19/01/13 19:07, Willi Mann wrote:
>> However, inline PGP messages get into trouble with broken
>> character encodings, broken charsets, non-ASCII characters (e.g.
>> http://bugs.debian.org/698080), attachments and other common
>> features of the modern e-mail landscape.
>
> What is unclear to m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
> PGP/MIME signed messages occasionally get into trouble with some
> non-MIME-aware mailing lists, some broken mailing lists, and some
> archaic mail user agents.
>
> However, inline PGP messages get into trouble with broken
> character encod
Package: enigmail
Version: 2:1.5.0+id17-1
Severity: wishlist
PGP/MIME signed messages occasionally get into trouble with some
non-MIME-aware mailing lists, some broken mailing lists, and some
archaic mail user agents.
However, inline PGP messages get into trouble with broken character
encodings,
5 matches
Mail list logo