Artur Hefczyc opened 5 years ago
-
Ok, I did some more checking and there is no bug. The contact is blocked on kobit@tigase.org account but the new message came to artur.hefczyc@tigase.org account...
-
Actually, no. The message came to the kobit@tigase.org account. So there is a problem somewhere.
-
From what I can see in logs, this is not a second message, but a message "resent" by StreamManagement when a connection to one of your clients (WebSocket connected one) was broken. They were connected to different cluster nodes, so the privacy list was out of sync (I do not see a code to sync it within a cluster).
As a result, when you blocked spammer in Beagle, it got blocked on
node-1, butnode-2was not aware of that. When WebSocket based client (Parrot?) was disconnected it had unacked messages which were resent. Those messages were redelivered to newly connected Parrot and somehow caused redelivery to Beagle (skipped privacy check - maybe carbons caused that?). It would also explain why Beagle ignored "delay" timestamp as it does that in messages sent with carbons - as normally carbons are never delayed.
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Spent time |
0
|
Maybe this is actually not Beagle but the server issue. I have just noticed a new chat on my list, from a spammer. As you can see on the screenshot the chat has the red icon on it, meaning the contact is blocked. But if it is blocked how did I receive it? I even remember blocking this specific spammer a few days ago.