Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No destination folders shown in settings. #116

Open
boscharun opened this issue Jun 19, 2019 · 14 comments
Open

No destination folders shown in settings. #116

boscharun opened this issue Jun 19, 2019 · 14 comments

Comments

@boscharun
Copy link

When trying to add a copy rule, clicking the destination folder doesn't show any folders. Using thunderbird 60.7.1. Please help.
image

@chrober
Copy link

chrober commented Jul 7, 2019

I am experiencing the very same problem. Not sure when it started, it seems to be related to a Thunderbird upgrade. I recently found out my mails have not been archived anymore. By checking the Awesome Auto Archive options I found out the destination folders are not displayed anymore!

However, checking the extensions.awsome_auto_archive.rules in TB's Config Editor I do see the proper dest attributes there. Nevertheless, as said before neither the Awesome Auto Archive config editor displays these nor does the archiving work!

I am currently using TB 60.7.2. Using Awesome Auto Archive 0.9beta from GitHub instead of the offcial 0.8 did not help.

@dmshimself
Copy link

I have the same issue - TB 60.7.2 as well

@elhennig
Copy link

elhennig commented Aug 1, 2019

Same here on Linux using TB 60.8.0

@SeagramFR
Copy link

Hi,

Same issue with Awesome Auto Archive (AAA) 0.8 with ThunderBird (TB) on Windows 10, currently 60.8.0 32bits (with auto update set).

My ISP was sending me "quota warning" alerts, so I was puzzled and checked TB contents and AAA settings and behaviour.

  • TB:
    Messages older than set delay are not archived any more.
    According to settings and dates of oldest messages not archived, AAA is broken since about October 12, 2018?
    (which can match update from TB 60.0 to 60.2.1 on October 2, 2018, with some fixes and new features related to calendar)
  • AAA:
    When checking "General settings" in options, "destination folder" fields are blank (not even an empty drop-down list, just white background).
    I delete every rule, and create a new one: "destination folder" appears as an empty drop-down list.
    I click [OK], then come back to settings: now "destination folder" is a drop-down list with each and every mail accounts or folders selectable -> I select one, then click on [Apply] below, then on [Run] above -> messages appear very quickly in the status bar, then eventually "Nothing done"!
    I click [OK], then come back to settings: "destination folder" fields are just white background

In the "Advanced settings" tabs of AAA options, I click on "Show verbose information in error console" checkbox, but I haven't seen any error in the TB console. Everything seems to go smoothly, it just does nothing. Just one weird thing: why is it necessary to check connections with mail servers before proceeding? What if the user does NOT want to fetch recent messages from server before archiving?
Some log lines are:

[...]
2019-08-02 18:51:45.363 this.rules: Array
/ 0 (object) [object Object]
| + enable (boolean) true
| + action (string)'archive'
| + src (string)'mailbox://[email protected]'
| + dest (string)'mailbox://nobody@Local%20Folders/___Archives/my.account%40pop.isp.tld'
| + from (undefined) undefined
| + recipient (undefined) undefined
| + subject (undefined) undefined
| + tags (undefined) undefined
| + age (number) 180
| *
2019-08-02 18:51:45.409 Running rule archive mailbox://[email protected] with filter { age => 180 }
2019-08-02 18:51:45.414 needCheck mail server: [email protected]
2019-08-02 18:51:45.414 downloading emails for server [email protected]
2019-08-02 18:51:45.415 Checking if server server11 on line using pop3://my%[email protected]:995/
2019-08-02 18:51:45.615 OnStopRunningUrl: server server11
2019-08-02 18:51:45.616 pop3://my%[email protected]:995 OK
2019-08-02 18:51:45.616 All servers checking done, has bad server? : false
2019-08-02 18:51:45.616 No need to updateFolder mailbox://[email protected]
2019-08-02 18:51:45.616 All FolderLoaded
2019-08-02 18:51:45.631 Searching
mailbox://[email protected]
with
2019-08-02 18:51:45.632 Total 0 messages hit
[...]
2019-08-02 18:51:45.636 skipReason: [object Object]
/ duplicate (number) 0
|+ exceed (number) 0
|+ cantDelete (number) 0
|+ deleted (number) 0
|+ srcLocked (number) 0
|+ destLocked (number) 0
|+ flaged (number) 0
|+ unread (number) 0
|+ tags (number) 0
|+ cantArchive (number) 0
|+ offline (number) 0
2019-08-02 18:51:45.636 autoArchiveService closeAllFoldersDB
2019-08-02 18:51:45.636 close msgDatabase for mailbox://[email protected]
2019-08-02 18:51:45.636 Proposed to change 0 messages, 0 bytes
2019-08-02 18:51:45.637 auto archive done for all rules, set next
2019-08-02 18:51:45.637 Archie: Nothing done
2019-08-02 18:51:45.639 Will wakeup @ 02/08/2019 19:51:45

If AAA is not fixed quickly on this, it is useless, and I will remove it. Too bad.

@chrober
Copy link

chrober commented Aug 2, 2019

If AAA is not fixed quickly on this, it is useless, and I will remove it. Too bad.

I hope it will get fixed (soon)!
I am not aware of any alternative which could replace AAA for my needs.

@SeagramFR
Copy link

Hi, @chrober

I am afraid I don't know of any alternative either.
Back to manual archiving? :-(

@chrober
Copy link

chrober commented Aug 3, 2019

Back to manual archiving? :-(

I am already back here, manual archiving is what I currently do. But it is no fun at all, it is a totally stupid task. It would be awesome if my computer would automatically maintain my e-Mail archive. Actually, that is what I have my computer for -- relieving me from stupid tasks.

@SeagramFR
Copy link

Hi, @chrober

I totally agree with you, that's what a computer is made for: perform stupid and tedious tasks ... once human has properly specified what is expected, which is often the longest part of it ;-)

First thing first, I may spend some time looking at the logs and the code and understand what goes wrong and what is to be fixed?

More on this later,

@quenton89
Copy link

The quick workaround (if its not already noted, did not see it) is to apply the change, close the window and re-open the archiver window. You can then select the folder - nuisance? perhaps, but the add-on is too useful to not use the workaround.

@dmshimself
Copy link

I cannot get that to work - the windows opens up a second time with the entry for the destination folder still disabled. Was there a particular sequence you used to get this to work?

@chrober
Copy link

chrober commented Sep 1, 2019

The quick workaround (if its not already noted, did not see it) is to apply the change, close the window and re-open the archiver window. You can then select the folder - nuisance? perhaps, but the add-on is too useful to not use the workaround.

This workaround does not work for me. What changes do you make before you press the "Apply" button? How do you close the window? With what TB version and under which OS is this supposed to work?

@quenton89
Copy link

Sorry - I had hoped it would work for everyone, I have been using it for months now.

Just to be sure, the steps I go through to add a new item are ...

  • open the Archiver window
  • add new item, set it to MOVE
  • select the from folder
  • set other options that I want, then hit OK which saves the new item and closes the window
  • open the Archiver window again, now I can select the target folder.

@dmshimself
Copy link

For me on TB 60.8.0 I can follow your method as long as long as Move is selected, but when I bring the windw back and change Move to Archive, the ability to select a destination folder is removed

@michaelminarcz
Copy link

michaelminarcz commented Sep 23, 2019

I have the same problem. TB 60.9.0 (64-bit) on MAC. Destination folder is empty, so I can't select the destination folder.... does anyone solve it?

https://ibb.co/b5L6L2R

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants