Il 01/03/2013 13:47, Kim Alvefur ha scritto:
Hi,On 2013-02-13 09:48, Per Gustafsson wrote:I work with Google's chat service, and we are seeing lots of spammy invites from users on various federated domains, (...), otherwise we will have to institute very tight limits of invites per day being sent from federated domains.How are you replying in this case? We are hearing complaints from prosody users about not being able to send invites, which I'm guessing is this. It could be that the current rate limit is overzealous or something. Something I noticed as a sever developer is that people are seeing presence bounced with an error on the *outgoing* connection, which is not valid*. And this is the error element reported: <error type='cancel' code='503'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error> If this is the rate limiting then I would suggest some more appropriate error, or at least some descriptive text. * Unless bidirectional (xep-288) streams are used. -- Kim "Zash" Alvefur Prosody dev
Additionally,If the presence subscription request comes from a gmail account, mutual presence subscription is still impossible because the google xmpp server still rejects any presence of type='subscribe' with a service-unavailable error, which as stated above, is even sent on the wrong stream. Of course, that doesn't leave much choice but editing the roster directly to see the gmail account status...
Perhaps if you guys want to employ limitations at least do it accordingly and possibly in a way that <<speaks proper xmpp>> and doesn't violate rfcs.
Thank you.
smime.p7s
Description: Firma crittografica S/MIME
