]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001351.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001351.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] NS SET KILL not working?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20NS%20SET%20KILL%20not%20working%3F&In-Reply-To=20020903193054.GA1199%40phat.za.net">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001345.html">
11 <LINK REL="Next" HREF="001362.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] NS SET KILL not working?</H1>
15 <B>V13</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20NS%20SET%20KILL%20not%20working%3F&In-Reply-To=20020903193054.GA1199%40phat.za.net"
17 TITLE="[IRCServices Coding] NS SET KILL not working?">v13 at it.teithe.gr
18 </A><BR>
19 <I>Tue Sep 3 13:49:50 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001345.html">[IRCServices Coding] NS SET KILL not working?
22 </A></li>
23 <LI>Next message: <A HREF="001362.html">[IRCServices Coding] (no subject)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1351">[ date ]</a>
27 <a href="thread.html#1351">[ thread ]</a>
28 <a href="subject.html#1351">[ subject ]</a>
29 <a href="author.html#1351">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On Tuesday 03 September 2002 22:30, Aragon Gouveia wrote:
35
36 &gt;<i> This only applies if the Security option is unset. And as shown below,
37 </I>&gt;<i> security is set.
38 </I>&gt;<i>
39 </I>&gt;<i> Not sure why it isn't enforcing nick kills. Vax, have you tried changing
40 </I>&gt;<i> the kill option to quick and/or immediate? (be careful with immediate!!)
41 </I>
42 Afaik:
43 If secure is on:
44 (a) If user matches access list, a warning is send without
45 saying anything about kill/nick change.
46 (b) If user doesn't match access list, a warning is send
47 notifying about upcoming kill.
48
49 In case of (a):
50 There is no timeout. The user will not be enforced but he will never
51 be recognized. He will stay unindentified.
52
53 In case of (b):
54 We all know...
55
56 When secure is off, the (a) case will change the user status from
57 unidentified to recognized. (Use /ns status to check the current state)
58
59 &gt;<i> Aragon
60 </I>&lt;&lt;V13&gt;&gt;
61
62 p.s. How are we supposed to reply to this upside down reply-chain without
63 reordering the mail?
64
65 </PRE>
66
67 <!--endarticle-->
68 <HR>
69 <P><UL>
70 <!--threads-->
71 <LI>Previous message: <A HREF="001345.html">[IRCServices Coding] NS SET KILL not working?
72 </A></li>
73 <LI>Next message: <A HREF="001362.html">[IRCServices Coding] (no subject)
74 </A></li>
75 <LI> <B>Messages sorted by:</B>
76 <a href="date.html#1351">[ date ]</a>
77 <a href="thread.html#1351">[ thread ]</a>
78 <a href="subject.html#1351">[ subject ]</a>
79 <a href="author.html#1351">[ author ]</a>
80 </LI>
81 </UL>
82
83 </body></html>