On Thu Oct 9 12:11:25 2008, Jonathan Schleifer wrote:
Am 09.10.2008 um 06:51 schrieb Peter Saint-Andre:
This doesn't apply, because a publish happens via IQ. And why
would the
pubsub service poke the publisher if not all the messages can be
delivered? I think it would be the service's responsibility to
retry the
notifications.
ejabberd sends the message that would have been delivered to the
recipient with an error attached. This is very funny for PEP, as
some clients don't see that there's an error attached and you see
your own mood / activity / tune at ohters then when there was an
error :) *looking at Adium, looks at old Gajim versions*.
Yes, PEP does this because the normal message bounce gets addressed
to the bare jid, and therefore delivered according to normal message
rules to the most available resource.
I suppose the solution is most likely to intercept all messages of
type error to the bare jid, and see if they might be PEP, and handle
them accordingly.
Dave.
--
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade