Re: Roster options question
Matthias Wimmer <[email protected]> Mon, 7 Mar 2005 18:00:30 +0100
| Newsgroups | gmane.network.jabber.exodus.user |
|---|---|
| Message-ID | <20050307170029.GB13359@false> |
Hi Paul!
Paul C. schrieb am 2005-03-07 11:04:16:
> It doesn't seem to work for us. Here is the debug info. This is build
> 39 with the option checked to detect the no longer available users.:
Not sure, but I think exodus looks for error presences, not for error
messages. But someone should be here with more insigt to Exodus.
> 20050307T15:57:36: [warn] (jabber2.OurDomain.com): xdb_file failed to
> open file [path to spool]/spool/jabber2.OurDomain.com/testuser.xml: No
> such file or directory
>
> I have been told that 1.4.3 supports deleting a user's xml file better
> than 1.4.2 does, and will deal with the server side later.
Not sure what is meant by that. Presently I am not aware of a difference
in jabberd 1.4.2 / 1.4.3(.1) regarding handling of deleted users. In
both they just disappear if you delete the xml file (and have setup xdb
to cache xml files only for a limited time).
What has been changed in handling of deleted users is, that 1.4.4-beta1
does and 1.4.4 will send unsubscription requests to the contacts of a
user, if a user deletes his account. But this only works, if the account
of the users is unregistered "the normal way". If you just delete a
users xml file, the server has no way to unsubscribe to the user'c
contact, as it does not longer have knowledge who subscribed to this
user's presence.
If you delete users on a regulary basis, you should really consider
deleting the users sending an unregister request after authenticating as
this user and not just deleting the users file.
Tot kijk
Matthias
--
Fon: +49-(0)70 0770 07770 http://web.amessage.info
Fax: +49-(0)89 312 88 654 xmpp:mawis-QDLRX95UGO4k+I/[email protected]
_______________________________________________
Exodus mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/exodus
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCLIitPSc92k5Zx+YRAsp6AKCIvWr4K2BxJslkarpLeX8t5a/9sQCeKwjp /gYeUSEnTqsKEoTrp12Supk= =NJeE -----END PGP SIGNATURE-----