Rajnish Bhaskar schrieb:
> Hi all,
> I've been notified of changes in our organisational firewall
> coming up over the next few months that will block all incoming
> requests except on ports explicitly unblocked. My question is
> what ports will I need open to allow Jabber/PyMSNt to continue to
> run.
Where is the jabber server running? Is it external? Then you don't need
any additional port than the ports you already mentioned.
Bye!
Michael
From [EMAIL PROTECTED] Fri Jun 9 08:59:56 2006
From: [EMAIL PROTECTED] (Alexey Nezhdanov)
Date: Fri Jun 9 09:00:13 2006
Subject: [py-transports] Another bug in pyMSN-t
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
? ????????? ?? ??????? 08 ???? 2006 18:26 James Bunton ???????(a):
> On 08/06/2006, at 10:43 PM, Alexey Nezhdanov wrote:
> > Here I describe actually two bugs. One bug is obvious - pyMSN-t
> > replies with
> > type='subscribed' too fast and second may be not so easy to catch -
> > account
> > going offline for some reason.
> >
> > Here is example of this: two contacts, one registered in pyMSN-t
> > and other one
> > logged in in GAIM trying to chat with each other.
> > pyMSN-t accont is operating by script, GAIM operated by human.
> > All packets going there and here very fast, I didn't measured, that
> > may be
> > pretty about 0.1-0.2 second.
> >
> > 1) script sends subscription request to gaim and waits for
> > subscription
> > approval by gaim
> > <presence from='[EMAIL PROTECTED]' to='snakeru11%
> > [EMAIL PROTECTED]'
> > type='subscribe' id='117'/>
> >
> > 2) (First bug) pyMSN-t immidiatedly sends back subscription approval
> > <presence to='[EMAIL PROTECTED]' from='snakeru11%
> > [EMAIL PROTECTED]'
> > type='subscribed'/>
> >
> > 3) pyMSN-t notifies that other party is offline
> > <presence to='[EMAIL PROTECTED]'
> > from='[EMAIL PROTECTED]/msn' type='unavailable' />
> >
> > 4) script ignores "user is offline" presence and sends a message
> > <message from='[EMAIL PROTECTED]/reply'
> > to='[EMAIL PROTECTED]' id='119'><body>test</
> > body></message>
> >
> > 5) scrpt deletes newly-added contact from roster
> > <presence from='[EMAIL PROTECTED]' to='snakeru11%
> > [EMAIL PROTECTED]'
> > type='unsubscribe'/>
> >
> > 6) (second bug) account suddenly going offline
> > <presence to='[EMAIL PROTECTED]' from='msn.localhost'
> > type='unavailable'/>
> >
> > Obviously second bug is triggered by way too fast stanzas coming in:
> > subscribe+message+unsubscribe. Though transport still better should
> > stand it
> > IMHO.
> >
> > --
> > Respectfully
> > Alexey Nezhdanov
>
> The first 'bug', is designed. Unfortunately, there's no way around it.
> The MSN protocol provides no way to know when somebody authorises, or
> deauthorises you. So PyMSNt just assumes it happens immediately. Its
> the best guess we can do :)
>
> The second is indeed a bug. Deleting a contact should not cause the
> transport to log you off. What version of the transport are you
> using?
r170
> I have fixed a few contact list bugs, so it may be fixed in
> the latest SVN version.
ok, I'll check it thank you.
>
> You can switch to that by doing
> svn switch svn://delx.cjb.net/pymsnt/trunk/
> from within your PyMSNt directory, and then restarting the transport.
>
> ---
>
> James
--
Respectfully
Alexey Nezhdanov
