Your message dated Thu, 25 Dec 2008 22:50:40 +0100
with message-id <20081225225040.22bff...@busgosu>
and subject line closing sylpheed-gtk1 bugs (removed package)
has caused the Debian Bug report #302264,
regarding sylpheed: Fails to escape lines beginning with "From " in GPG signed
messages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
302264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302264
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sylpheed
Version: 1.0.4-0.backports.org.1
Severity: normal
When I send a GPG-signed (unencrypted) message that includes (in message body)
a line beginning with "From " following a blank line, no escaping happens.
If the escaping is performed at a later stage (e.g. by an MTA or mailing
list manager, as happens with Debian mailing lists!) the signature gets
broken.
Example:
This just a test
From my point of view, this will *not* be escaped...
--
Jack Sylpheeduser
will result in something like:
--Signature=_Wed__30_Mar_2005_23_45_23_+0200_lmdgK_kkQCIzcvI3
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
This is just a test
From my point of view, this will *not* be escaped...
--=20
Jack Sylpheeduser
--Signature=_Wed__30_Mar_2005_23_45_23_+0200_lmdgK_kkQCIzcvI3
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCSx34aPQnm9NkvIG4wCgkjEW
XKWPLXThAXZBQ=
=F3kR
-----END PGP SIGNATURE-----
--Signature=_Wed__30_Mar_2005_23_45_23_+0200_lmdgK_kkQCIzcvI3--
Note that Mutt behaves differently: it escapes the "From " line exploiting
quoted-printable characters:
--3V7upKqbjkZ4EhLz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
This is just a test
=46rom my point of view, this will be escaped...
--=20
Max Muttuser
--3V7upKqbjkZ4EhLz
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DCQFC4aPQnm9NkvIG4wCgkjEW
XKWPLXXZBQ=
=F3kR
-----END PGP SIGNATURE-----
--3V7upKqbjkZ4EhLz
I'm using a Sylpheed backport for Woody, but believe this issue does not
depend on packaging, but on upstream code...
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux neverland 2.4.29 #1 Wed Jan 19 21:55:41 CET 2005 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages sylpheed depends on:
ii libc6 2.2.5-11.8 GNU C Library: Shared libraries an
ii libcompfaceg1 1989.11.11-23 Compress/decompress images for mai
ii libgdk-pixbuf2 0.17.0-2woody2 The GdkPixBuf library.
ii libglib1.2 1.2.10-4 The GLib library of C routines
ii libgpg-error0 1.0-0.backports.org.1 library for common error values an
ii libgpgme11 1.0.2-0.backports.org.1 GPGME - GnuPG Made Easy
ii libgtk1.2 1.2.10-11 The GIMP Toolkit set of widgets fo
ii libldap2 2.0.23-6.3 OpenLDAP libraries.
ii libpisock4 0.9.5.0-8 Libraries for communicating with a
ii libssl0.9.6 0.9.6c-2.woody.7 SSL shared libraries
ii sylpheed-i18n 1.0.4-0.backports.org.1 Locale data for Sylpheed (i18n sup
ii xlibs 4.1.0-16woody5 X Window System client libraries
--- End Message ---
--- Begin Message ---
Hi there,
You're receiving this mail because time ago (probably years) filed a
bug against sylpheed-gtk1 package in Debian's Bug Tracking System (or
against sylpheed package before it was a GTK2 application which ended
assigned to sylpheed-gk1 package).
Anyway, the sylpheed-gtk1 package has been removed from Debian now, hence
I'm closing all the bugs related to it. Most of them are old, but, it may
be possible some of these are still within modern sylpheed.
If you're using sylpheed package right now, would be very helpful to check
if the bug being closed now still applies to sylpheed. If not using
sylpheed, well, you can still check it anyway if you want... :)
If bug doesn't apply to current sylpheed you're done.
If the current sylpheed package (2.6.0, in experimental) still has the bug,
please, file a _NEW_ bug report for sylpheed (unless you have already done
so in the past, of course). You may refer the old bug number if you want in
the description, but error details and reproduction method must be relevant
for sylpheed.
Sorry for the long mail and thanks for reporting.
Seasonal greetings where applicable,
--
Ricardo Mones
http://people.debian.org/~mones
«Don't relax! It's only your tension that's holding you together.»
signature.asc
Description: PGP signature
--- End Message ---
