Yeah that is a shortcoming of sieve mostly as webclients build filters which are often incompatible with each other, since sieve is more like a programming language rather than a config setting. Maybe in the future we can build a better language runtime for parsing and editing. This is also the reason nearly all webclients create their own rules file with the client's name.
To be honest this mess is part of why we wanted to build our own here so we have more control over those topics.
That's the feature I meant. In order to streamline things, I would probably show the folder list immediately and make the search field more visible... Thank you!
About the blocklists/allowlists: the ones on Cloudron side are server global and managed by admins. The ones here are mailbox local and controlled by user. They are merged essentially but the mailbox one "wins" and has more priority in case of conflicts.
IMO, the admin one is only there in case the admin finds there is some major phishing or something going on and wants to block things for sure. Usually these lists are best controlled by end users themselves.
I can fix the wording in the Cloudron dashboard since the Mail app is targeting the end user who doesn't care about the admin role settings.
Thanks for the offer @imc67 ! Definitely, we will make it translatable. I think we will have to make it a bit more stable UI wise first, otherwise translators are going to get frustrated with all the rework
I really like the overall experience. One feature I’d love to see added is a clear notification or unread-count badge for important updates. A quick filter or search option would also make it easier to find specific information quickly. The inquiry option could be made more intuitive with clearer wording. Multilingual support would also be a great future addition. Overall, these improvements could make the experience more user-friendly and efficient.
@necrevistonnezr said:
Allow i.e. something like "has:attachment" or "from:sender" in the search field (and expose such parameters in the UI)
+
They need to be able to work together too eg
"from:sender has:attachment"
So the issue was the old mailbox names were cached and needed a fix in our error handling code. Thanks for reporting @user123456 .
For the security concern: only the mailbox names were listed. The app itself has no permission to read other people's mail. So, the mailboxes were all failing to load and as a result the loading was very slow.
