Holger Weiß

> Maybe a better solution would be to force all c2s connections to the same priority, and strip /resource specifiers on c2s packets? The core XMPP RFCs specify how to...

> I think we can store info about subscribed tempsub nodes in c2s state This won't work for remote subscribers, though. I agree this shouldn't be merged as-is. I think...

> It seems the problem only occurs with our user using JWT as authentication (who doesn't exist in the users table...). I didn't look into this yet: Shouldn't the user...

I would've thought the problem description is misleading: The problem is _not_ that a message was received but not archived. The problem is that the message wasn't received (but bounced),...

> As we used JWT authentication, the recipient will never exist for ejabberd. This conclusion is the part I don't understand, but that's mostly due to me not being familiar...

Ok, quick look at [the code][1] explains the issue. I don't know whether there's a sane way to query a JWT service for user existence. If there isn't, the only...

There's [an extension][1] for this functionality, but it's not supported by ejabberd so far. I've [added][2] the necessary code to the [xmpp library][3] a while ago, and I have a...

I would still very much appreciate being able to somehow see the context of search results. But yes I guess the issue can be closed if nobody is motivated to...

Personally, when compiling ejabberd from source, I tell `./configure` to install everything below a dedicated directory (`/home/xmpp/server` or `/opt/ejabberd` or whatever). I keep the configuration, data, and log files _outside_...

> @weiss this probably should be fixed anyway, no? That would be nice of course :-) And yes, I can reproduce the problem.