-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, folks.
We have a new and exciting issue although I think I've seen it or
something similar, a long time ago.
What happens is, a user registers with the transport, they get pushed
their list of contacts, but for some reason all the contacts are left
in a mode where the subscription hasn't gone both ways (that is, the
MSN user hasn't authorised the Jabber user.) The workaround people
have been doing is to manually re-request authorisation from every
contact, which then works immediately. So it makes me think there is
some kind of issue with PyMSNt not doing something it's supposed to
when a user registers.
Interestingly not all users have reported this problem, although
enough users have reported it to make me take notice of it.
TX
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFE3mhnuMe8iwN+6nMRAsapAKCCGDxefKkCaXiNfFbmaYcAcprY5QCeK7XQ
6796kKADUg2ziEofF3ypbqk=
=KMJ6
-----END PGP SIGNATURE-----
From [EMAIL PROTECTED] Sun Aug 13 01:15:01 2006
From: [EMAIL PROTECTED] (James Bunton)
Date: Sun Aug 13 01:15:16 2006
Subject: [py-transports] PyMSNt showing "waiting for authorisation" for
all MSN contacts for some users
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
With ejabberd right? Hopefully fixed in trunk. I checked and noticed
that sendRosterImport (used when users register) wasn't trimming
resources of the to attribute of presence stanzas. ejabberd requires
that this is done.
---
James
On 13/08/2006, at 9:46 AM, Trejkaz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, folks.
>
> We have a new and exciting issue although I think I've seen it or
> something similar, a long time ago.
>
> What happens is, a user registers with the transport, they get
> pushed their list of contacts, but for some reason all the contacts
> are left in a mode where the subscription hasn't gone both ways
> (that is, the MSN user hasn't authorised the Jabber user.) The
> workaround people have been doing is to manually re-request
> authorisation from every contact, which then works immediately. So
> it makes me think there is some kind of issue with PyMSNt not doing
> something it's supposed to when a user registers.
>
> Interestingly not all users have reported this problem, although
> enough users have reported it to make me take notice of it.
>
> TX
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (Darwin)
>
> iD8DBQFE3mhnuMe8iwN+6nMRAsapAKCCGDxefKkCaXiNfFbmaYcAcprY5QCeK7XQ
> 6796kKADUg2ziEofF3ypbqk=
> =KMJ6
> -----END PGP SIGNATURE-----
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
