search

wangvisual / autoarchive

A Thunderbird extension that can move or archive your mails based on rules.
GNU General Public License v3.0
41 stars 13 forks source link

New Archiving option: Archive using Thunderbird archiving system and rules #5

Closed rerecrose closed 10 years ago

rerecrose commented 10 years ago

Thunderbird already has an archiving system. You can define where the archives go and it even splits by years or year-month, etc

But there is NO good way to invoke the archiving event to run automatically (other extensions do NOT work well... or they tend to leave an unresponsive TB client)

Perhaps Awesome Autoarchive could have an additional action for "Archive following TB rules"

Thanks!

awesome_autoarchive__archive_using_tb_archive_subsystem_and_rules

wangvisual commented 10 years ago

Currently auto archive will using TB's archive, which will create structure of year or year/month, based on user's settings. This is what you mean for 'Using TB archive system'

So 'Following filter rules' is? You can using move for that, right?

wangvisual commented 10 years ago

Can you talk in more details about "But there is NO good way to invoke the archiving event to run automatically (other extensions do NOT work well... or they tend to leave an unresponsive TB client)"?

I didn't see any issues so far.

rerecrose commented 10 years ago

About using the move and copy rules: OK. I was thinking about using some filter rule with a name prefix for "Awesome autoarchiver" to follow (But it's ok as it is)

About the memory problems not appearing :+1: It seems the problem does NOT appear in current version >= 0.3 if proper limits are set

Suggestion: Perhaps the new default message limit should be something as low as a few hundred msgs to avoid creating delays and memory issues. I limited to 300 msgs per round and now all seems to work. I'am testing with several dozen thousand msgs

The default of Message limits=0 [ No limits (0) ] could be 400 o similar [whatever you consider appropiate]

Thanks

I'm testing... if ok... then I'm donating

Good work

I'd suggest the new version should be committed/sent to the Mozilla repositories so all users can just do a simple update

wangvisual commented 10 years ago

About change default limit, yes, I'm thinking the same thing.

For new versions, typically I do some code enhancement, then 2~3 days to use and test, to see if anything broken. and then upload to Mozilla, as Mozilla need manually review the addon, I don't want to overload them :-)