NAVIGATION
CATEGORIES
REFERRENCE
LINKS
All together now...
18 answers - 18 bytes -
Thank you, Google!No.1 | | 185 bytes |
| 
PGP SIGNED MESSAGE
Hash: SHA1
Hal Rottenberg wrote:
Thank you, Google!
It seems that I need to get subscription from gmail user to be able to
send them messages.No.2 | | 496 bytes |
| Hi,
Jan 17, 2006, at 5:21 PM, Maciek Niedzielski wrote:
Hal Rottenberg wrote:
>Thank you, Google!
>>
>
>
It seems that I need to get subscription from gmail user to be able to
send them messages.
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
They don't have a socks5 proxy yet, though.
Best regards,No.3 | | 746 bytes |
| PGP SIGNED MESSAGE
Hash: SHA1
Pedro Melo wrote:
>>
>It seems that I need to get subscription from gmail user to be able to
>send them messages.
>
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
Both ways?
I could send from gmail to "somewhere else", but sending to gmail failed:
<error type="cancel" code="503" >
<service-unavailable xmlns=""/>
</error>
- --
Maciek
xmpp:machekku (AT) chrome (DOT) pl
PGP SIGNATURE
Version: GnuPG v1.2.1-nr1 (Windows XP)
pYR799hSneY9LRG1IWs=
=LUZ
PGP SIGNATURENo.4 | | 239 bytes |
| 1/17/06, Maciek Niedzielski <machekku (AT) miroku (DOT) uaznia.netwrote:
Both ways?
I could send from gmail to "somewhere else", but sending to gmail failed:
Don't worry, it's a Beta.
Google joke there. :)No.5 | | 528 bytes |
| PGP SIGNED MESSAGE
Hash: SHA1
Hal Rottenberg wrote:
1/17/06, Maciek Niedzielski <machekku (AT) miroku (DOT) uaznia.netwrote:
>Both ways?
>I could send from gmail to "somewhere else", but sending to gmail failed:
Don't worry, it's a Beta.
new anti-spim policy ;)
- --
Maciek
xmpp:machekku (AT) chrome (DOT) pl
PGP SIGNATURE
Version: GnuPG v1.2.1-nr1 (Windows XP)
6+zN4LEtF/QIjvgVF9vRVDY=
=afii
PGP SIGNATURENo.6 | | 268 bytes |
| Does anyone know if the s2s is TLS/SASL or good old Dialback?
It seems to me to just be Dialback, but I'd expect Google to follow the RFCs
as best they can
1/17/06, Hal Rottenberg <halr9000 (AT) gmail (DOT) comwrote:
Thank you, Google!No.7 | | 692 bytes |
| I've managed to get gmail->darkskies working, but darkskies->gmail
gets dropped as soon as the connection is made.
1/17/06, Pedro Melo <melo (AT) co (DOT) sapo.ptwrote:
Hi,
Jan 17, 2006, at 5:21 PM, Maciek Niedzielski wrote:
Hal Rottenberg wrote:
>Thank you, Google!
>>
>
>
It seems that I need to get subscription from gmail user to be able to
send them messages.
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
They don't have a socks5 proxy yet, though.
Best regards,No.8 | | 1126 bytes |
| The only problem I've had is gtalk seems to randomly remove subscriptions.
I'll be talking to someone on gtalk from my server, and all is well, until I
get a presence type='unsubscribed' that he didn't send.
Since they haven't made an announcement I'm guess they're still working out
the bugs.
1/17/06, Norman Rasmussen <norman (AT) rasmussen (DOT) co.zawrote:
I've managed to get gmail->darkskies working, but darkskies->gmail
gets dropped as soon as the connection is made.
1/17/06, Pedro Melo <melo (AT) co (DOT) sapo.ptwrote:
Hi,
Jan 17, 2006, at 5:21 PM, Maciek Niedzielski wrote:
Hal Rottenberg wrote:
>Thank you, Google!
>>
>
>
It seems that I need to get subscription from gmail user to be able to
send them messages.
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
They don't have a socks5 proxy yet, though.
Best regards,No.9 | | 587 bytes |
| Hi,
Jan 17, 2006, at 5:49 PM, Maciek Niedzielski wrote:
Pedro Melo wrote:
It seems that I need to get subscription from gmail user to be
able to
send them messages.
>>
>No, I was able to send a message between my gmail and sapo account
>without subscribing first. It was blazing fast :)
>
Both ways?
I could send from gmail to "somewhere else", but sending to gmail
failed:
Yeah, right. Didn't try the other way around from gmail to sapo.
Best regards,No.10 | | 207 bytes |
| See:
The Google Talk Service uses dialback.
The Google Talk Service uses the roster as a whitelist. You must be in
the Google Talk user's roster to send messages to the user.No.11 | | 1043 bytes |
| Google are validating the incoming stanzas more than anyone else has
before. jabberd2 currently sends stanzas in the jabber:client
namespace.
I've chatted to Stephen, and opened a bug for jabberd2 here:
1/17/06, Maciek Niedzielski <machekku (AT) miroku (DOT) uaznia.netwrote:
PGP SIGNED MESSAGE
Hash: SHA1
Pedro Melo wrote:
>>
>It seems that I need to get subscription from gmail user to be able to
>send them messages.
>
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
Both ways?
I could send from gmail to "somewhere else", but sending to gmail failed:
<error type="cancel" code="503" >
<service-unavailable xmlns=""/>
</error>
- --
Maciek
xmpp:machekku (AT) chrome (DOT) pl
PGP SIGNATURE
Version: GnuPG v1.2.1-nr1 (Windows XP)
pYR799hSneY9LRG1IWs=
=LUZ
PGP SIGNATURENo.12 | | 1590 bytes |
| I've noticed some clients add xmlns='jabber:client' onto stanzas as
well, so servers may need to forcibly remove this namespace
declaration, not just decline to add it.
Jan 17, 2006, at 12:48 PM, Norman Rasmussen wrote:
Google are validating the incoming stanzas more than anyone else has
before. jabberd2 currently sends stanzas in the jabber:client
namespace.
I've chatted to Stephen, and opened a bug for jabberd2 here:
1/17/06, Maciek Niedzielski <machekku (AT) miroku (DOT) uaznia.netwrote:
>PGP SIGNED MESSAGE
>Hash: SHA1
>>
>Pedro Melo wrote:
It seems that I need to get subscription from gmail user to be
able to
send them messages.
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
>>
>Both ways?
>I could send from gmail to "somewhere else", but sending to gmail
>failed:
>>
><error type="cancel" code="503" >
><service-unavailable xmlns=""/>
></error>
>>
>- --
>Maciek
>xmpp:machekku (AT) chrome (DOT) pl
>PGP SIGNATURE
>Version: GnuPG v1.2.1-nr1 (Windows XP)
>>
>
>pYR799hSneY9LRG1IWs=
>=LUZ
>PGP SIGNATURE
>>
>
>No.13 | | 1942 bytes |
| Clients are allowed to add it, it still remains valid xml, but server
mustn't retransmit it.
It seems that servers with full blown xml parsers are okay, while the
hand built ones might be falling prey to this issue. (not that I've
checked what jabberd2 uses)
1/17/06, Joe Hildebrand <hildjj (AT) gmail (DOT) comwrote:
I've noticed some clients add xmlns='jabber:client' onto stanzas as
well, so servers may need to forcibly remove this namespace
declaration, not just decline to add it.
Jan 17, 2006, at 12:48 PM, Norman Rasmussen wrote:
Google are validating the incoming stanzas more than anyone else has
before. jabberd2 currently sends stanzas in the jabber:client
namespace.
I've chatted to Stephen, and opened a bug for jabberd2 here:
1/17/06, Maciek Niedzielski <machekku (AT) miroku (DOT) uaznia.netwrote:
>PGP SIGNED MESSAGE
>Hash: SHA1
>>
>Pedro Melo wrote:
It seems that I need to get subscription from gmail user to be
able to
send them messages.
No, I was able to send a message between my gmail and sapo account
without subscribing first. It was blazing fast :)
>>
>Both ways?
>I could send from gmail to "somewhere else", but sending to gmail
>failed:
>>
><error type="cancel" code="503" >
><service-unavailable xmlns=""/>
></error>
>>
>- --
>Maciek
>xmpp:machekku (AT) chrome (DOT) pl
>PGP SIGNATURE
>Version: GnuPG v1.2.1-nr1 (Windows XP)
>>
>
>pYR799hSneY9LRG1IWs=
>=LUZ
>PGP SIGNATURE
>>
>
>No.14 | | 820 bytes |
| Norman Rasmussen wrote:
Google are validating the incoming stanzas more than anyone else has
before. jabberd2 currently sends stanzas in the jabber:client
namespace.
I've chatted to Stephen, and opened a bug for jabberd2 here:
Aha. That explains why I could use disco to trypticon.org (which runs
ejabberd) but not to jabber.org.au (which runs jabberd2). It was a
mystery there for a second, particularly because no errors were coming
back from Google's server at all.
Is that another glitch? IQs are always supposed generate a response, so
I would figure if someone drops the response, they should send an error
on so that the initial requester at least knows that something went wrong.
It's very nice though hooray for Google. :-)
TXNo.15 | | 646 bytes |
| 1/18/06, Trejkaz <trejkaz (AT) trypticon (DOT) orgwrote:
Is that another glitch? IQs are always supposed generate a response, so
I would figure if someone drops the response, they should send an error
on so that the initial requester at least knows that something went wrong
well, the stanza _does_ get delivered to the google server - which
then terminates the stream because of invalid xml.
It's very nice though hooray for Google. :-)
yes, happily this will force servers to validate their streams better.
(I will test our jive messenger server at work as soon as I get the
multihoming working)No.16 | | 752 bytes |
| Norman Rasmussen wrote:
1/18/06, Trejkaz <trejkaz (AT) trypticon (DOT) orgwrote:
>Is that another glitch? IQs are always supposed generate a response, so
>I would figure if someone drops the response, they should send an error
>on so that the initial requester at least knows that something went wrong.
well, the stanza _does_ get delivered to the google server - which
then terminates the stream because of invalid xml.
Sure, but it doesn't currently return a response IQ to the user who sent
the request, so the user's client sits there, basically spinning its
wheels forever. Sending an error to the other server only solves half
the problem.
TXNo.17 | | 527 bytes |
| Regarding jabberd2
Adding this line to the top of the function out_packet(s2s_t s2s,
pkt_t pkt) in s2s/out.c seems to fix things:
nad_set_attr(pkt->nad, -1, 0, "xmlns", "jabber:server", sizeof
("jabber:server"));
Perhaps not the most ideal fix, but it seems to work.
Robert Quattlebaum
Mobile: +1(650) 223-4974
eMail: darco (AT) deepdarc (DOT) com
Jabber: darco (AT) deepdarc (DOT) com
MSN: darco (AT) deepdarc (DOT) com
AIM/ICQ:rquat2
yahoo: robert_quattlebaumNo.18 | | 770 bytes |
| Actually, this line seems to work much better:
nad_set_attr(pkt->nad, -1, 0, "xmlns", NULL,0);
Jan 17, 2006, at 4:43 PM, Robert B Quattlebaum, Jr. wrote:
Regarding jabberd2
Adding this line to the top of the function out_packet(s2s_t s2s,
pkt_t pkt) in s2s/out.c seems to fix things:
nad_set_attr(pkt->nad, -1, 0, "xmlns", "jabber:server", sizeof
("jabber:server"));
Perhaps not the most ideal fix, but it seems to work.
--
Robert Quattlebaum
Mobile: +1(650) 223-4974
eMail: darco (AT) deepdarc (DOT) com
Jabber: darco (AT) deepdarc (DOT) com
MSN: darco (AT) deepdarc (DOT) com
AIM/ICQ:rquat2
yahoo: robert_quattlebaum
>
>
>
>
QUESTION ON "Networking"
- New: enhance TimeoutIdle to all contexts
- Multiple value for userCertificate
- New: enhance TimeoutNoTransfer and TimeoutStalled to <Anonymous> context
- agent.circuit-id in dhcp request
- 1 Terabyte limit per backup
- DefaultTransferMode does not work with ftp -n
- snmpwalk or snmpget problem with IBM ESS
- Need to Upgrade Sun hardware and upgrade OS as well....
- Sending "authenticationFailure" trap
- How to dump Bayes
- Exim4 and SA: Overloading the system
- How to Auto Decode RFC2047 Messages
- GoDaddy.com shuts down entire data center?
- the new icdevgroup site..
- cfexecd enhancement to distinguish scheduled runs
- Which version of openldap is "rock solid"!
- Regular expressions from file for match{
- BGP route flap damping
- sysUpTime
- GoDaddy.com shuts down entire data center?