I'm using Conversations on my phone and lurch on my desktop.
The peer is using Conversations on their phone.
I can receive encrypted messages from the peer but all messages sent are red (non-encrypted) at the receiver.
/lurch status tells me:
Your contact does not support OMEMO. No devicelist could be found.
When sending a message I get (in red):
Even though an encrypted session exists, the recipient's devicelist is empty.The user probably uninstalled OMEMO, so you can add this conversation to the blacklist.
Note that I can successfully decrypt messages from the peer.
This isn't currently high prio -- which means I can spend time testing/debugging this without having to switch to something else :-)
Ah and would it be possible that my phone sees msgs from lurch and vice-versa? This doesn't seem to be the case currently (which is probably an xmpp question, not lurch).
Ah and I'm using ejabberd on debian stable: 24.12-3+deb13u2, most modules are 0.2025.01.11~dfsg0-2+deb13u2
I'm using Conversations on my phone and lurch on my desktop.
The peer is using Conversations on their phone.
I can receive encrypted messages from the peer but all messages sent are red (non-encrypted) at the receiver.
/lurch status tells me:
Your contact does not support OMEMO. No devicelist could be found.
When sending a message I get (in red):
Even though an encrypted session exists, the recipient's devicelist is empty.The user probably uninstalled OMEMO, so you can add this conversation to the blacklist.
Note that I can successfully decrypt messages from the peer.
This isn't currently high prio -- which means I can spend time testing/debugging this without having to switch to something else :-)
Ah and would it be possible that my phone sees msgs from lurch and vice-versa? This doesn't seem to be the case currently (which is probably an xmpp question, not lurch).
Ah and I'm using ejabberd on debian stable: 24.12-3+deb13u2, most modules are 0.2025.01.11~dfsg0-2+deb13u2