Re: Claws-Mail vs. Sylpheed

On Tue, 27 Aug 2024 09:42:53 +0100
"Kerr-Mudd, John" <admin@127.0.0.1> wrote:

On Tue, 27 Aug 2024 02:11:11 -0000 (UTC)
Ini Nagap <invalid@nagap.ini> wrote:
 

Claws Mail client has gotten increasingly buggy over time on Linux.
 
Now it crashes often. It especially crashes when accessing pop and
nntp over a Tor proxy. The way it interfaces with the gnu nntp
library causes it to crash a lot. This newsreader has become
aggravating to use. It is almost like someone put the bug there on
purpose to discourage Tor usage.

 
But you're a newbie; you've not posted to usenet before. Why do you
need to hide behind Tor?
 

I am looking at Sylpheed as a replacement. Does anyone have
experience with Sylpheed? What has that experience been like? Do
unexpected bugs hide in its woodwork? Has the developer gone AWOL?
What is the status of the project? 

 
Works OK, some grumbles: I haven't got a KF working, have to manually
snip sigs, and xposted messages don't seem to get Marked As Read.
 
No idea after that. I *think* I moved to it for utf support - but I
haven't checked if it does.
 

 
I can't use Thunderbird. It takes 30 to 45 seconds just to open the
program and it freezes up periodically.
 
 

 
Standard.

Libsylph seems to have none of the problems of libetpan20. Since Claws
is based upon Sylpheed the Claws devs could just re-link to Libsylph
for the proxy and nntp logic. If anyone knows how to compile claws-mail
that way I would be willing to try and test it.

I cannot understand why claws devs thought it a good idea to move to
libetpan. They created one more external dependency for no benefit.
Sylpheed was (almost) bug free.

One gripe about sylpheed is that after marking newsgroups read, the
next time it syncs the very messages marked read are marked unread
again. Unless and until a bevy of new messages are posted to the group,
every time the application is synced all the read messages from the
former session will be re-marked as unread. This is very annoying.

Another Sylpheed gripe is the inability to mark all folders read
recursively. If I am reading 25 newsgroups I have to mark them read
individually.