Mechiel Lukkien

Interesting. The string `&DiAOMg4pDjU-66_xF8FF_&DhsOAQ4qDgQ-` is decomposed into: 1. `&DiAOMg4pDjU-` (utf-7) 2. `66_xF8FF_` (regular text) 3. `&DhsOAQ4qDgQ-` (utf-7) I don't think `_xF8FF_` has any special meaning in email protocols. It looks...

I can imagine the F8FF is meant as a literal slash to indicate "this/or/that", and not meant as a hierarchy separator (directories). Perhaps the mailboxes can be renamed both at...

Closing, I don't think we can do anything in mox about this. We don't want to recognize special private uses like _xF8FF_, and it doesn't seem wise to interpret it...

What kind of delivery failures are these? Is proofpoint immediately responding with a permanent failure, so the user immediately gets a message back that delivery has failed? Or are they...

i know of specific commands (like search and append) that can mention charsets. could you describe a scenario where mox is currently doing the wrong thing? that makes it easier...

> If the user receives a reply to their own email, both the sent email and the reply should appear as threads in the inbox. I justed tested this, and...

> Instead, you should see the thread with your original message first, and then the reply you received. That's what it looks like in for me. I also tested with...


Assuming this is solved after last message. If there is still a problem, please reopen this issue!

Good to hear you're giving it a try! It's not immediately obvious from the report what the problem is. The first error is about selector 2023a. That selector uses ed25519....