search

ValentijnNK / miranda

Automatically exported from code.google.com/p/miranda
0 stars 0 forks source link

No alerts delivery error messages from jabber transports #279

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Miranda Version                  : 0.9.0 alpha build 
Unicode Build                    : Yes
Test Build # (if applicable)     : #2
Plugin Version # (if applicable) : Jabber v.0.9.0.1 [21 Sep 2009] |Unicode
aware|

No alerts delivery error messages from transports
If such a situation occurred that transport disconnect and say I have not
noticed deciding to write this transport contact offline, the message is
written into the history and visually it would look as if the message 
send as off-line, but in fact it went nowhere without any warning.
Only in XML console i see:
    <message type="chat" to="jabber%vke.ru@xmpp.jrudevels.org" id="mir_105">
        <body>проверка</body>
    </message>

    <message from="jabber%vke.ru@xmpp.jrudevels.org"
to="nightfox@miranda.im/666" type="error">
        <error code="503" type="cancel">
        <service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
        </error>
    </message>

You can do that I would announce the unsuccessful sending via TabSRMM as is
done in a normal situation?

Original issue reported on code.google.com by x696Nigh...@gmail.com on 29 Sep 2009 at 9:06

GoogleCodeExporter commented 9 years ago

Original comment by sami%mir...@gtempaccount.com on 29 Sep 2009 at 9:09

GoogleCodeExporter commented 9 years ago 
Can add a notice about too quick posting to Jabber conferences, and they just 
don't
send, that's what I see in the console:
<message from="...@conference.jabber.ru" to="NightFox@miranda.im/666" 
type="error"
xml:lang="ru">
<body>9</body>
<error code="500" type="wait">
<resource-constraint xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Превышен лимит 
скорости посылки
информации</text>
</error>
</message>

Original comment by x696Nigh...@gmail.com on 3 Oct 2009 at 10:39

GoogleCodeExporter commented 9 years ago 
This stuff is supported in current Jabber, thus closing.

Original comment by borkra on 14 Apr 2011 at 2:18