[Users] Minor niggles with Claws Mail

Jeremy veloce at nixnet.email
Tue Feb 16 19:08:32 UTC 2021


Hello everyone!

I am new here so I apologise if this is unwelcome in any way, and if I
missed something - I am in a bit of a rush.

I have recently switched from thunderbird to claws mail (I say
recently, well over 3 months ago now) in search of something that
did not leave me to grow old waiting for it to open, and would allow me
to use the default PGP keyring (I do not like the PGP behaviour in the
new thunderbird)

Unfortunately, I have been experiencing a few minor issues with the
program for which I cannot find any information online or in the bug
tracker. I am not submitting any bug reports yet as these errors are
trivial and there are likely fixes I am unaware of as yet

First of all, folder handling. I have multiple email addresses in
multiple maildirs, structured as follows:

~/Mail/Account1/inbox
      	       /drafts
	       /sent
               /queue
      /Account2/inbox
      	       /drafts
	       /sent
               /queue

The problem is as follows. When saving a message as a draft in account
two, the file is actually saved in the drafts folder in the mailbox for
account 1. The same can be said for the queue and the sent box, but
interestingly not the wastebin - that respects the mailbox the account
was from

I 'solved' the problem with some filtering rules, but I am a
perfectionist and naturally wondered whether there was a better way;
this is clearly not the way in which the client is meant to work

The other issue I have faced is that some keyboard shortcuts do not
work. The main ones do: Control-M, Control-R etc are all fine; but not
Control-return for editing address book entries. To my knowledge, there
is no shortcut in my window manager that is blocking it; nothing
happens when the combination is pressed. I would appreciate it if anyone
has any insight in to this

One thing to note is that I am using the install from the Debian Buster
repository, version 3.17.3 which is apparently from December 2018. It
is entirely possible that the bugs I am experiencing are now fixed and
that I need to compile a newer release myself

Again, any insight in to any of these issues is greatly appreciated.

Thanks in advance,
Jeremy


More information about the Users mailing list