Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

2023-06-14 Thread Hideki Yamane
Hi,

 Please describe reproduce way step by step, and describe your environment
 at detail. I cannot see such issue until now.


On Sat, 20 May 2023 12:00:16 +0200 =?ISO-8859-1?Q?Jos=E9?= Luis 
=?ISO-8859-1?Q?Gonz=E1lez?=  wrote:
> If a new mail arrives to an account other than the current one it is
> changed without permission nor warning to the one receiving the email,
> which means all activity from then on is done unadvertingly on the
> switched-to account.
> 
> Considering the consequences of sending email from an account different
> from the one intended, like sending from a private one to a public
> forum (like a mailing list available on the web, or the DBTS), or using
> an account that is not permitted for what was unwantedly done, this
> makes the package mostly unusable since the consequences of can't be
> usually undone and can be very grave, which renders the program
> unusable for any serious user.
> 
> 



-- 
Hideki Yamane 



Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

2023-05-20 Thread José Luis González
Hi again,

I have observed this happens with new coming from any account,
including the current one. So if I have an email account that is
private@gmail and I get new mail on my current one, it also switches
unwantingly and unadvertedly to private@gmail.

The problem is really serious and obnoxious.



Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

2023-05-20 Thread José Luis González
Package: sylpheed
Version: 3.7.0-8
Severity: grave

If a new mail arrives to an account other than the current one it is
changed without permission nor warning to the one receiving the email,
which means all activity from then on is done unadvertingly on the
switched-to account.

Considering the consequences of sending email from an account different
from the one intended, like sending from a private one to a public
forum (like a mailing list available on the web, or the DBTS), or using
an account that is not permitted for what was unwantedly done, this
makes the package mostly unusable since the consequences of can't be
usually undone and can be very grave, which renders the program
unusable for any serious user.