Miranda Version : v0.10.21.0 x64 (Built Jan 15 2014 17:37:36) Unicode Build : Yes

What steps will reproduce the problem? 1. download and unzip miranda-im-v0.10.21-x64.7z 2. download and install plugin scriver.dll from miranda-im-v0.10.21-x64-contrib.7z 3. run Miranda, create profile, add jabber account, connect to network 4. in "Options -> Network -> <jabber account> -> Advanced" change (tick) option "Send messages slower, but with full acknowledgement" (under "Miscellaneous -> Messaging") 5. send message to some jabber contact using desktop Trillian

What is the expected result? - Message is sent to the contact, added to history and displayed in chat log

What happens instead? - message is delivered to the contact, but not added into local history and chat log - error appears: The message send timed out. (see screenshot)

VersionInfo and network log is attached.

Same error with several different sending accounts from Miranda and with several different receiving accounts on Trillian. Captured test is performed against account gury@jabber.cz, resource GURY-PC, software Trillian, version 5.4.0.15.

It seems to be working as expected on 32 bit build (with 32 bit scriver) and also with any other accounts using non-Trillian software. Also with Trillian on iPhone (version 2.1.0.9d) it is working well.

The only information related to this issue I have found on internet is bug report on Miranda-ng: http://trac.miranda-ng.org/ticket/457 I've also asked on forum: http://forums.miranda-im.org/showthread.php?29193-Delivery-reports-problem-with-Trillian-on-Jabber but with no replay.

Is this issue a bug? Is it a bug of Miranda? Or of Trillian? Did anybody came across this issue in the past?

Thanks for replay and possible for patching it. Fosfor

The tocket on Miranda NG bug tracker makes it quite clear:

it's a well known problem with the Trillian's stupidity. Trillian declares that it's able to deal with chat states, but fails to support the message delivery. it's definitely not a problem of Miranda.

The bug is definately NOT on Miranda side, but on Trillian side

You can try a workaround: Set in database editor the setting /MsgAck to 0. This disables message delivery notification for the specific contact.

Hi and sorry for a late answer - I had tested to disable message delivery notifications and because it was working I've completely forget about this issue;) So:

As I didn’t find DB editor for my 64bit version, I tried to disable delivery notification for whole jabber ("Send messages slower, but with full acknowledgement" off) and then this issue disappeared. Drawback is that you are not aware of real undelivered messages.

Was this issue somehow discussed with Trillian? With what result?

In case it was not discussed - please help me clarify the problem (I'll try on my own with Trillian developers):

According to the log - Trillian client declares to handle jabber:x:event feature (which is obsoleted for more than 3 years, but client does not declares to handle a "new" urn:xmpp:receipts), but when my client sends a message with it gets no answer - which is a problem, because it should (if the message itself is delivered/stored for offline delivery). And this is a problem of the Trillian client, which should replay to this request. Am I right?

BTW: it has no connection with “chat states” (XEP-0085) as this doesn't handle per-message event itself - OK?

No one will answer you here. All Miranda IM devs are gone. If you can, switch to Miranda NG :-)

And I think you should discuss it with Trillian yourself, surely no one else from here did.