Il 08/09/2010 12:18, Evgeniy Khramtsov ha scritto:
08.09.2010 20:07, Arsimael wrote:
I think the easiest and most effective way is a small Question:
The Jabber Clients want to register a new Account. before the Server
grants the new Account he opens a small textfile with 10 (or 20 or
10.000)
On 09/08/2010 11:29 AM, Evgeniy Khramtsov wrote:
09.09.2010 02:19, Jesse Thompson wrote:
Do you mean that spammers could flood users with subscription
requests? I suppose that would be difficult to deal with. Could it be
solved with UI improvements? e.g., a queue listing of pending
requests, as
09.09.2010 02:19, Jesse Thompson wrote:
Do you mean that spammers could flood users with subscription
requests? I suppose that would be difficult to deal with. Could it
be solved with UI improvements? e.g., a queue listing of pending
requests, as opposed to a pop-up for each request.
Curre
On 09/08/2010 10:30 AM, Evgeniy Khramtsov wrote:
09.09.2010 01:22, Jesse Thompson пишет:
Has anyone ever suggested the idea of clients and/or servers
implementing features to not deliver, or segregate, messages from
users that aren't subscribed to each others presences?
There is a problem with
09.09.2010 01:37, Dave Cridland wrote:
On Wed Sep 8 16:30:08 2010, Evgeniy Khramtsov wrote:
09.09.2010 01:22, Jesse Thompson пишет:
Has anyone ever suggested the idea of clients and/or servers
implementing features to not deliver, or segregate, messages from
users that aren't subscribed to ea
On Wed Sep 8 16:30:08 2010, Evgeniy Khramtsov wrote:
09.09.2010 01:22, Jesse Thompson пишет:
Has anyone ever suggested the idea of clients and/or servers
implementing features to not deliver, or segregate, messages from
users that aren't subscribed to each others presences?
There is a prob
09.09.2010 01:22, Jesse Thompson пишет:
Has anyone ever suggested the idea of clients and/or servers
implementing features to not deliver, or segregate, messages from
users that aren't subscribed to each others presences?
There is a problem with subscriptions: you cannot block them efficiently
On 09/07/2010 03:22 AM, Mathias Ertl wrote:
I still think that _good_ anti-spam solutions now are vital to the XMPP
community. The fact that XMPP has almost nothing to fight this, worries
me greatly. In that respect XMPP is not superior to email at all
Rather than re-hash the exact path that em
08.09.2010 20:07, Arsimael wrote:
I think the easiest and most effective way is a small Question:
The Jabber Clients want to register a new Account. before the Server
grants the new Account he opens a small textfile with 10 (or 20 or
10.000) Questions and Answeres. He Picks andsom a Question a
I think the easiest and most effective way is a small Question:
The Jabber Clients want to register a new Account. before the Server
grants the new Account he opens a small textfile with 10 (or 20 or
10.000) Questions and Answeres. He Picks andsom a Question and sends
it to the client. Like "what
I remember that we already discussed XMPP SPAM messages on the end of last
year. Unfortunately I do not know what will be best procedure for these type
of accounts/messages.
My proposal was that we could implement something like SPAM-ratio for
accounts as it was already discussed in 'How-to fight w
08.09.2010 17:47, Peter Viskup wrote:
I configured restriction for account creation based on regexp and filter
these account names.
I think administrators of other affected jabber servers should follow this
approach.
{acl, jabber_sk_bad_users, {user_regexp,
"^[40tman_rullez,ws_conference_jabber_
Hi,
just wanted to say that for now it seems servers like mine can not be targeted
by this bot, perhaps until the "nice guy" reads this: I have only 2 domains
with iq:register allowed (linuxlovers.at / 0nl1ne.at), which need both DNS SRV
lookup to find my xmpp service - could it be that only D
Small correction in regexp:
"^(40tman_rullez|ws_conference_jabber_ru)"
and the name in access rule should be jabber_sk_bad_users of course.
On Wed, Sep 8, 2010 at 9:47 AM, Peter Viskup wrote:
> I configured restriction for account creation based on regexp and filter
> these account names.
> I th
I configured restriction for account creation based on regexp and filter
these account names.
I think administrators of other affected jabber servers should follow this
approach.
{acl, jabber_sk_bad_users, {user_regexp,
"^[40tman_rullez,ws_conference_jabber_ru]", "jabber.sk"}}.
{access, register_j
15 matches
Mail list logo
