Opened 13 years ago
Closed 13 years ago
#199 closed defect (fixed)
Don't send -O ping to -c message -i personal
Reported by: | kchen@mit.edu | Owned by: | andersk@mit.edu |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | internals | Keywords: | |
Cc: |
Description
I'm guessing this bug still exists, since -c message -i personal received a few -O ping zephyrs today, but don't actually want to test right now to cause more traffic. In any case, when someone sends a zephyr to -c message -i personal *, barnowl should not send a -O ping zephyr.
Change History (5)
comment:1 Changed 13 years ago by kchen@mit.edu
comment:2 Changed 13 years ago by kchen@mit.edu
Fixing formatting:
geofft says that the following cause pings:
-c message -i personal * @
and the following do not cause pings:
-c message -i personal -c geofft -i test *
comment:3 Changed 13 years ago by andersk@mit.edu
I’ve been seeing a bunch of cross-realm pings to -c message -i personal recently, and I bet it’s because people typo zwrite person @ATHENA.MIT.EDU instead of zwrite person@ATHENA.MIT.EDU.
comment:4 Changed 13 years ago by andersk@mit.edu
- Owner set to andersk@mit.edu
- Status changed from new to assigned
comment:5 Changed 13 years ago by andersk@mit.edu
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in commit 9d206c685b0a401f9708cacf15e19ce52899cf61.
geofft says that the following cause pings: -c message -i personal * @
and the following do not cause pings: -c message -i personal -c geofft -i test *