View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001467 | unreal | ircd | public | 2004-01-02 22:57 | 2004-01-06 00:46 |
| Reporter | rizencom | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta19 | ||||
| Summary | 0001467: Cross-server badwords not blocked | ||||
| Description | Assumptions: 1. If one user is on server a.network.net and the other is on b.network.net 2. Both servers have the following lines in their conf files: badword all { word "test"; action block; }; 3. User A (on server a) privmsgs user B (on server b) the message "this is a test" User B will still receive the cross-server message. It's blocked however, if user A sends the word to a user that is on the same server as himself. We use the profanity controls to help limit the spread of spam and viruses. | ||||
| 3rd party modules | |||||
|
|
I'm unable to reproduce this here (on CVS), 2 servers linked and 2 users msging each other "this is a test". make sure.. * .."test" shows up in the output of '/stats badword' on both servers * ..it is at both servers blocked locally * ..neither one is oper * ..the "receiver" is +G Since beta18 (or 19, I forgot), all badwords checking is done by the local server so that makes it even more weird/""impossible"". |
|
|
no response / bogus. |
