Acknowledgement sent
to José Luis González <[email protected]>:
New Bug report received and forwarded. Copy sent to Ricardo Mones <[email protected]>.
(Fri, 26 May 2023 15:54:03 GMT) (full text, mbox, link).
Package: sylpheed
Version: 3.8.0~beta1-1
Severity: grave
After upgrading to Debian 12 and booting again the computer I am unable to
use sylpheed to neither send email with both accounts I have set up, nor
read new messages, just with the IMAP one in this case.
Both accounts are from Gmail.
The error message I get trying to send with the POP3 is
Error
Hubo un error enviando el mensaje:
501 5.5.2 Cannot Decode response
r11-20020a5d494b000000b00300aee6c9cesm5425569wrs.20 - gsmtp
while with the IMAP one is
Hubo un error enviando el mensaje:
501 5.5.2 Cannot Decode response
j13-20020a5d604d000000b00306344eaebfsm5456150wrt.28 - gsmtp
Whereas, trying to open the inbox of the IMAP one, or any other folder,
gets this:
Error
No se pudo establecer una conexión con el servidor.
making it impossible to read or query new mail.
Acknowledgement sent
to Ricardo Mones <[email protected]>:
Extra info received and forwarded to list.
(Sat, 03 Jun 2023 11:39:02 GMT) (full text, mbox, link).
Subject: Re: Bug#1036799: sylpheed: unable to send or read email after
upgrading to Debian 12
Date: Sat, 3 Jun 2023 13:35:56 +0200
control: severity -1 important
control: tags -1 confirmed
control: forwarded -1 https://www.sraoss.jp/pipermail/sylpheed/2023-May/007127.html
Hi José Luis,
On Fri, 26 May 2023 17:46:44 +0200
José Luis González <[email protected]> wrote:
> Package: sylpheed
> Version: 3.8.0~beta1-1
> Severity: grave
>
> After upgrading to Debian 12 and booting again the computer I am
> unable to use sylpheed to neither send email with both accounts I
> have set up, nor read new messages, just with the IMAP one in this
> case.
>
> Both accounts are from Gmail.
>
> The error message I get trying to send with the POP3 is
>
> Error
>
> Hubo un error enviando el mensaje:
> 501 5.5.2 Cannot Decode response
> r11-20020a5d494b000000b00300aee6c9cesm5425569wrs.20 - gsmtp
>
> while with the IMAP one is
>
> Hubo un error enviando el mensaje:
> 501 5.5.2 Cannot Decode response
> j13-20020a5d604d000000b00306344eaebfsm5456150wrt.28 - gsmtp
>
> Whereas, trying to open the inbox of the IMAP one, or any other
> folder, gets this:
>
> Error
>
> No se pudo establecer una conexión con el servidor.
>
> making it impossible to read or query new mail.
Right, but that doesn't deserve a 'grave' severity as only gsmtp users
are affected and no data is lost or security hole is introduced. I've
adjusted this accordingly.
That has been reported on the list that downgrading to 3.7.0 fixes the
problem: https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html
Can you check if downgrading fixes it?
best regards,
--
Ricardo Mones
http://people.debian.org/~mones
«Tempt not a desperate man. -- William Shakespeare, "Romeo and Juliet"»
Acknowledgement sent
to José Luis González <[email protected]>:
Extra info received and forwarded to list. Copy sent to Ricardo Mones <[email protected]>.
(Sun, 23 Jul 2023 12:27:03 GMT) (full text, mbox, link).
Subject: Re: Bug#1036799: sylpheed: unable to send or read email after
upgrading to Debian 12
Date: Sun, 23 Jul 2023 14:22:34 +0200
control: severity -1 grave
Hi Ricardo,
> Right, but that doesn't deserve a 'grave' severity as only gsmtp users
> are affected and no data is lost or security hole is introduced. I've
> adjusted this accordingly.
The definition of grave severity is:
grave
makes the package in question unusable or mostly so, or causes
data loss, or introduces a security hole allowing access to the
accounts of users who use the package.
This bug renders sylpheed unusuable or mostly so for me, so it is
indeed a grave bug. I am restoring severity accordingly.
> That has been reported on the list that downgrading to 3.7.0 fixes the
> problem: https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html
> Can you check if downgrading fixes it?
I wish I could check it but so far the only way I have to do so is
installing from source. What I can confirm is the bug appeared when
upgrading from version 3.7.0 to version 3.8.0~beta1-1.
I hope you understand this bug is preventing me from using sylpheed
and so from reading and writing email, unless from gmail's web
interface. I find of great concern that the bug is in Debian's new
stable distribution: bookworm. If you know the bug is in version
3.8.0~beta1-1 I would suggest downgrading stable to 3.7.0 if you can
manage to do so.
Best regards,
José Luis
Acknowledgement sent
to Ricardo Mones <[email protected]>:
Extra info received and forwarded to list.
(Sat, 29 Jul 2023 18:45:02 GMT) (full text, mbox, link).
Subject: Re: Bug#1036799: sylpheed: unable to send or read email after
upgrading to Debian 12
Date: Sat, 29 Jul 2023 20:41:35 +0200
control: severity -1 important
Hi José Luis,
On Sun, 23 Jul 2023 14:22:34 +0200
José Luis González <[email protected]> wrote:
> control: severity -1 grave
>
> Hi Ricardo,
>
> > Right, but that doesn't deserve a 'grave' severity as only gsmtp
> > users are affected and no data is lost or security hole is
> > introduced. I've adjusted this accordingly.
>
> The definition of grave severity is:
>
> grave
> makes the package in question unusable or mostly so, or
> causes data loss, or introduces a security hole allowing access to the
> accounts of users who use the package.
>
> This bug renders sylpheed unusuable or mostly so for me, so it is
> indeed a grave bug. I am restoring severity accordingly.
No, it's not. That "for me" you added is the part that is not mentioned
in the definition and that's a quite important difference: that the
package is unusable for _you_ doesn't make it unusable for _everybody_,
and that's what the definition mean when it says the package is
unusable.
Anybody not using Gmail can use Sylpheed without problems, for example,
so even if it makes unusable it for you, please keep severity as it
should be.
> > That has been reported on the list that downgrading to 3.7.0 fixes
> > the problem:
> > https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html
>
> > Can you check if downgrading fixes it?
>
> I wish I could check it but so far the only way I have to do so is
> installing from source. What I can confirm is the bug appeared when
> upgrading from version 3.7.0 to version 3.8.0~beta1-1.
Building Sylpheed 3.7.0 from source in Debian 12 is pretty simple, go to
some empty dir and run:
$ sudo apt install build-essential devscripts
$ sudo apt build-dep sylpheed
$ dget http://deb.debian.org/debian/pool/main/s/sylpheed/sylpheed_3.7.0-8.dsc
$ cd sylpheed-3.7.0/
$ dpkg-buildpackage -us -uc
$ cd ..
$ sudo dpkg -i sylpheed_3.7.0-8_amd64.deb
> I hope you understand this bug is preventing me from using sylpheed
> and so from reading and writing email, unless from gmail's web
> interface. I find of great concern that the bug is in Debian's new
> stable distribution: bookworm. If you know the bug is in version
> 3.8.0~beta1-1 I would suggest downgrading stable to 3.7.0 if you can
> manage to do so.
Yeah, I understand the situation is not funny for you. Fact is upstream
has still not dealt with this bug despite the time passed (months), so
there's no patch I can apply to current version.
This fact joined with the increased slowness of upstream development
during the past years makes me wonder if it's still worth to maintain
Sylpheed within Debian.
regards,
--
Ricardo Mones
http://people.debian.org/~mones
«Bank error in your favor. Collect $200.»
Acknowledgement sent
to Nicholas Bamber <[email protected]>:
Extra info received and forwarded to list. Copy sent to Ricardo Mones <[email protected]>.
(Sun, 07 Apr 2024 16:24:03 GMT) (full text, mbox, link).
Subject: sylpheed: unable to send or read email after upgrading to Debian 12
Date: Sun, 7 Apr 2024 17:20:58 +0100
I am a long term gmail user and I have tried sylpheed in the past, long
before Debian 12. I could not get it to work.
From my investigations gmail works with relatively few email clients on
Linux. It does however work with Thunderbird. From what I understand it
takes a considerable amount of effort (and money) to get an email client
to work with gmail. As such it is probably unreasonable to demand any
specific email client to do that work.
I suggest that the bug be renamed to change "email" to "gmail" and
remove "after upgrading to Debian 12".
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.