Thanks for the reply Peter. I realize it's a weird case, and I was by mistake reading RFC 3921, which says:
Upon receiving the presence stanza of type "subscribe" addressed to the contact, the contact's server MUST determine if there is at least one available resource from which the contact has requested the roster. If so, it MUST deliver the subscription request to the contact (if not, the contact's server MUST store the subscription request offline for delivery when this condition is next met; I now see that RFC 6121 addresses the point more explicitly: If the presence subscription request cannot be locally delivered or remotely routed (e.g., because the request is malformed, the local contact does not exist, the remote server does not exist, an attempt to contact the remote server times out, or any other error is determined or experienced by the user's server), then the user's server MUST return an appropriate error stanza to the user. Unfortunately, I don't think I'm getting that error response with the version of ejabberd that I'm using. I'll double check it and inquire in the ejabberd list if this turns out to be the case. thanks, Dan _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
