Rated 3 out of 5 stars

by Vanili on Sept. 24, 2021 · permalink

I really like this extension, but I think it could get much better, here some proposals:

- Interaction with filters:
AutoBucket seems to tag my mails _after_ my filters are applied. As a result, in the IMAP inbox the tags are applied, but only after my filters have copied the mails to the local folders. In my case, it would be useful that AutoBucket would apply before the filters, or that you could choose if after or before. It would be useful, for example, to be able to use the tags of AutoBucket to filter the mails.

Another issue seems to be that AutoBucket only applies to mails which did not get any tag from the filters. I like that, but maybe this could also be user defined. It would be useful for the learning that AutoBucket would learn from the tags applied by the filters.

- No points boundary: It would be very useful to be able to set a bounday below which no tag would be applied. Right now, _all_ mails get a tag from AutoBucket (except those already tagged by the filters), but often the mails should not get a tag. AutoBucket should tag only when the tag is clearly to be applied. For example, some mails get a tag with 0,009 points, that is nonsense. A boundary should be able to be set. I would like for example a 0.2 or 0.3.

- I don't know if this is only my issue, but the learning and judging through context menu is extremely slow.

- I also don't understand if re- or untagging false positives corrects the learning. And also don't understand if learning is done only manually or if each tagged mail is learned (and unlearned if the tag is corrected). Maybe a bit more information would make it easier to understand the function. And, as I said above, learning from filters would be great (maybe integrating an action in the filters, something like "learn as X in AutoBucket").