-
Notifications
You must be signed in to change notification settings - Fork 98
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
MailMover configuration accepts a regex folder, but fails silently #314
Comments
Hello @naegling , The code for the MailMover is far form ideal and patches are welcome (with tests as much as possible). Regarding you issue, please link the documentation that would be wrong, what version, configurations etc. |
Thanks @GuillaumeSeren . Where is the best place to discuss what I have in mind? here or irc? I know what I want, but would prefer an implementation others could use as well. I can post an RFC analogue. |
Hey @naegling , Please explain a more precise case on the issue, |
Original post covered 2 topics. I will continue here with the bug report and open a new topic for the proposed enhancement. MailMover accepts a folder list containing a regex. The regex even almost works. matching messages are queried in MailMover.py:64, but then all matching messages are silently discarded by MailMover.py:69. Three fix suggestions:
Although I initiated this report, I am no longer impacted by it. Instead, I am implementing a FolderTagSync feature to maintain a simple 1-1 correspondence between tags and MailDir folders (for those of us saddled with o365). I will open a enhancement post for discussion leading to a PR if desired by the community, |
While considering changes to MailMover to address, I realized the mailmover configuration seemed overly complex for its task. Why not just a list of pairs (query, target_folder)? All mail that satisfy the query that are not already in
target_folder
are moved. Also yields a natural way to handle cloning vs moving. (i.e. multiple copies vs 1st move only).Anyone have any thoughts? Of course, if implemented, I'll send a PR.
The text was updated successfully, but these errors were encountered: