I didn't try it, I just

mfoss — Mon, 10 Sep 2007 11:30:03 +0000

I didn't try it, I just looked at the source code.

Anonymous wrote:

I know there was a bug fixed in version 0.9 where vcard entries were left behind after removeing user's accounts but this seemed to only address deleting ejabberd managed accounts, not AD accounts.

When ejabberd is told to remove an account, it also removes the vcard, offline messages, and any other information related to that account...

Anonymous wrote:

as we delete the user in AD, there vcard entry still exists within ejabberd and we have no way of removing these obselete entries.

... However, when you use an authentication method external to ejabberd and you remove an account, ejabberd is not informed, right?. Does it have a chance to remove the information related to that account?

To solve this, a solution would be to check for account existence when serving a vcard request. Or periodically check that all the users associated to vcards really exist. A more general solution: implement a command that the admin can run when he deletes an account. That command checks vcard, offline... and any other table, and checks the users exist. Those solutions may consume a lot of resources if the tables are quite populated.

I guess this isn't a bug or a misconfiguration. It's a feature request, right?

Not using mod_vcard_ldap

Editure — Mon, 10 Sep 2007 04:31:55 +0000

Hi Zinid,

Thanks for your reply. We are only using the standard "mod_vcard" and not "mod_vcard_ldap".

Regards,

John

Are you using

zinid — Wed, 29 Aug 2007 22:30:42 +0000

Are you using mod_vcard_ldap?

ejabberd - Comments for "vCard entries left vjud after deleting AD accounts"

I didn't try it, I just

Not using mod_vcard_ldap

Are you using