We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When opening a new mail account from infomaniak, all inbox mails are marked as "Important", with red text and markbox.
It is noticeable that Infomaniak mail server doesn't manage tags / labels. (see this feature request)
So I think this bug affects "no-label-servers".
To Reproduce Steps to reproduce the behavior:
Expected behavior No automated tags (except $HasAttachment maybe
$HasAttachment
Please complete the following information:
No relevant log to show.
Edit : it is really annoying as I don't see a way to batch delete the inappropriate tags...
The text was updated successfully, but these errors were encountered:
I understand it is annoying. But just like Nextcloud Mail, it is the fault of infomaniak that we can't prevent.
Maybe i can make it partially batch by adding menu item in messaglist "clear flags"
Sorry, something went wrong.
It would be great to select the flag to clear, I would love to keep "$HasAttachement"
Anyway, thank you for this great work!
No branches or pull requests
Describe the bug
When opening a new mail account from infomaniak, all inbox mails are marked as "Important", with red text and markbox.
It is noticeable that Infomaniak mail server doesn't manage tags / labels. (see this feature request)
So I think this bug affects "no-label-servers".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No automated tags (except
$HasAttachment
maybePlease complete the following information:
No relevant log to show.
Edit : it is really annoying as I don't see a way to batch delete the inappropriate tags...
The text was updated successfully, but these errors were encountered: