Modify

#126 new defect

ICQ doesn't block correctly

Reported by: Tar-Minyatur Owned by: Jelmer Vernooij
Priority: normal Milestone:
Component: OSCAR Version: 1.0.1
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro: Ubuntu

Description

Currently there are stupid bots which send lots and lots of authorization requests via my icq account. If I decline it's sent again. So I tried to ignore the user using "block 0 icq-uin" but it seems to change exactly nothing. The bot keeps requesting always when I decline. I do not exactly know if it could be an error in icq itself and not in bitlbee. There's no other report in here it seems.

Attachments (0)

Change History (9)

comment:1 Changed at 2006-03-27T16:43:11Z by wilmer

I doubt if the block functionality is supposed to block them. But just ignore them, it's the best thing to do. Saying no is almost as bad as saying yes here.

comment:2 Changed at 2006-03-28T09:38:02Z by Tar-Minyatur

My point is: If I ignore the request, it will stay in the list and to accept another request I'll have to decline this one and it starts again. Should the block command not shut out the user completely? When I block him I also do not wish to add him, I think. But as I said I don't know if it's a "bug or feature" thing at icq itself...

comment:3 Changed at 2006-03-28T11:34:40Z by wilmer

Unfortunately blocking won't help you though, AFAIK the requests come from a different ICQ# pretty much every time.

With query_order (IIRC) set to lifo, this shouldn't be a problem. Just ignore the request, and when you get another request, you'll get it (which wasn't the case with old BitlBee versions, and with recent versions with query_order set to fifo).

And from time to time I usually disable and re-enable my ICQ account to flush the list of questions. Fortunately the ICQ spam went down a bit for me, lately.

comment:4 Changed at 2006-03-28T20:18:33Z by bitlbee@…

I've got the same problem, and in my case, the spamming UINs stay constant for quite some time - it would help me a lot to be able to block them.

comment:5 Changed at 2006-04-19T11:30:06Z by anonymous

I got a lot of such spam the last days, always from different UINs. Isn't there a possibility to set request filter? Ignore any requests for ICQ would be enough for me.

comment:6 Changed at 2006-07-31T12:47:36Z by Michał Nazarewicz <mina86@…>

Take a look at Ticket #191, as I believe it solves the problem at least partially.

comment:7 in reply to:  description Changed at 2006-08-09T20:45:55Z by hamsta@…

Blocking doesn't work at all! It only sends a "the user xyz has denied yoour request to add them to your buddy list for the following reason: no reasin given." to the blocked user. But the person is able to write me anyway!

I have got bitlbee version 1.0.3 and I am very confused! The user shouldn't be able to write me anymore - should he?!?

jule

comment:8 Changed at 2006-08-11T16:08:44Z by wilmer

For ICQ it just (officially) prevents the person from having you in his/her buddy list. And as said before, the best thing to do with authorization requests from spammers is to ignore them completely.

Unfortunately blocking people on AIM/ICQ doesn't work very well yet in BitlBee. This probably has something to do with the support for server-side contact lists that got added later. I hope to get this fixed one day too, so then you can use the block command to get rid of this stuff. Until then the /ignore command of your IRC client should do a great job too.

comment:9 Changed at 2008-05-23T22:30:22Z by rcvyman73_womensfeet@…

Couple of weeks ago, my account for icq was disabled. I wanted to be able to re-enable my e-mail so that I could write them. I tried to e-mail the member support; however, it kept getting errors. I was requesting newsletters from different websites. They ended up into my spam mailbox. I wonder why is it happening? I would like to keep up with everything.

Modify Ticket

Action
as new The owner will remain Jelmer Vernooij.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.