Welcome to the mailbox.org user forum!

New Topic

mailbox.org Support Topic Problem Encryption

Category Encryption

Tags filters, email

Inbox Auto PGP encryption seems to break when mail was filed into any non-inbox folder

k234525 shared this problem ago

Published

The inbox Auto PGP encryption seems to break when mail was filed into any non-inbox folder. I got a couple of rules that simply match a sender (or partial sender) and then use "File Into" for a folder, and whenever one of those matches the mail ends up saved completely unencrypted:

5a64d9e1e6d68bd1502557452d66ffb6

I would understand this happening if the "fall through" at the right hand side was disabled, but it isn't disabled, so that the inbox encryption rule doesn't apply afterward seems like a potential bug. or is there something I missed that makes this intended behavior?

Files:

The same problem 0

Replies (2)

Anonymous ●

Have you tried first encrypting and then moving the mail. I can't remember but I think I read that somewhere.

Reply URL

k234525 ●

But that would potentially break filtering if it depends on contents, right? It doesn't make logical sense to me to do it in that order.

I think mailbox should repair the filter, unless there's a reason this is somehow intended. It sure looks like a bug.

URL

k234525 ●

It seems like as of today, 2025-07-01, this problem seems to be still ongoing.

Reply URL

zapata ●

Have you created a support ticket? If so, what was their reply?

URL

k234525 ●

I haven't since I have an account with no technical support included (sadly I'm a bit short on money). Feel free to create a support ticket if you want to.

URL

zapata ●

I don't know how the inbox encryption exactly works and if it can be "fixed" easily. But it would be great if we could at least add a header via the Inbox Rules. Then I guess we could bypass the current limitations of the inbox encryption. Have you tried to send an e-mail to helpdesk @ mailbox.org?

URL

zapata ●

The mailbox.org IMAP server obviously supports the editheader extension. So maybe this can already be achieved with an external sieve editor. But I am not sure if it will break the inbox encryption.

URL

zapata ●

Adding a header doesn't seem to work and in the mailbox.org suite I am now getting an error:

106a550ea5f498535aca177cda6ce5b6

URL

k234525 ●

If you have a plan that includes technical support and you happen to hear back from them about this, let me know.

URL

zapata ●

I have created a ticket.

URL

Maximus ●

Filter rules are supposed to be processed from top to bottom, in that order of priority. Does dragging the Inbox encryption rule to the top (and ensuring it stays there) not fix this? If it doesn't, you have identified a huge privacy and security breach. Please keep us posted.

URL

k234525 ●

If you want to filter the messages to go into different folders based on contents, I assume the rule can't be at the top. (Otherwise, how would the filter still work based on the message contents, given my PGP key isn't available to the mailbox backend?) Therefore, in such cases the rule needs to be applied after filtering, hence it's placed at the bottom for me. There is no indication in the UI that this isn't meant to be a supported use case.

URL

k234525 ●

Update: it seems like the rule can simply be left at the top, and all the filter rules work as before. don't ask me how, I guess it might briefly cache the unencrypted contents.

In that case however, I don't understand why it can even be moved downward if 1. it doesn't apply anymore farther down even if no "do not process subsequent rule(s)" rule matches and 2. there is no real reason to move it downward anyway.

It seems to be at the very least a UI inconsistency that's somewhat dangerous.

URL

zapata ●

Removed.

URL

k234525 ●

Actually you are correct, disregard my last comment. The reason it works in that order is probably because I don't filter on body for now, but ideally I would still want to put the filter rule at the bottom.

URL