This bug is now tagged since quite some time as pending,
and you can count me and several people around me as
another one of the group counting it as
serious
The default setup *has* to respect privacy. If not, I will file
a chnage against policy that the failure to respect privacy
has to be considered a grave bug, like a security bug.
I consider the ignorance with which the maintainers of mutt are treating
this bug quite inappropriate. A simple upload with unsetting the
write_bcc is definitely a must, and *now* and not at some
unspecified time. This discussion is now running since years!!
That this bug is present in stable -- the bug is not the wrong
documentation, but that mutt does not delete the bcc headers --
and still the same is going on in unstable.
I urge the maintainers to take action, or I will raise the priority
to make it clear that releasing software and letting it into
the next stable that still breaks the basic rules of privacy
is not acceptable. Furthermore, if no proper action is taken, I will
prepare an NMU for that.
BTW, I didn't complain till now, because in my .muttrc this is set since
ages. If I would have realized that *per*default* in Debian BCC headers
are *not* stripped from emails, I would have gone havoc already
3 years earlier.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining prein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
HODNET (n.)
The wooden safety platform supported by scaffolding round a building
under construction from which the builders (at almost no personal
risk) can drop pieces of cement on passers-by.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
