Rated 5 out of 5 stars

by Dieter on June 13, 2020 ·

I really like this add-on to organize my outgoing mail. Some days ago I installed TB with "maildir" instead of "mbox" mail storage and installed Copy Sent to Current as well. But it seems that it doesn't work with maildir - although "ask for folder when sending" is enabled, no popup is shown to select the folder and the outgoing mail goes directly to the sent folder.
Can you please check the maildir support? I now need maildir as I have many problems with mbox - especially the *.msf files (duplicate mails are shown) - with the folders located on my NAS now. And I don't want to miss Copy Sent to Current.

Thanks! I solved it by changing "other folder" to "select / chose folder when sending" (I have the German UI, so I don't know the right English text) under (account settings | copies and folders - and now it works as expected!
Rating changed to 5 stars.

This review is for a previous version of the add-on (2.0.3). 

by Günter Gersdorf (Developer) on June 14, 2020 ·

Probably the add-on didn't found the sent-folder (i know, there should be an error message...)

Be sure, all folders from the server are shown in TB:

Go to 'Tools' > 'Account Settings' > 'Server Settings' for the mail account. Click on 'Advanced' button, Uncheck: 'Show only subscribed folders'. Close popups. Double click on the account two times to get all folders from the server.

If this doesn't help, please contact me by email.
Günter

Rated 4 out of 5 stars

by Dieter on Sept. 24, 2019 ·

I use this add-on for many years now and I love it - but:
Copy Sent to Current 2.0 does not work with TB 68.1.0 under (Arch) Linux with option "choose folder when message is sent". The folders are displayed, I can select one, but then the selection window remains open - and if I close it, the message is put in the default folder. Selection at sent time works for sent folder and inbox, but not for self defined folders.

This review is for a previous version of the add-on (1.2.4). 

by Günter Gersdorf (Developer) on Sept. 29, 2019 ·

This is fixed in version 2.0.2