1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] idea for services
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20idea%20for%20services&In-Reply-To=20030108100011.99840.29095.Mailman%40snow.fingers.co.za">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001861.html">
11 <LINK REL=
"Next" HREF=
"001863.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] idea for services
</H1>
15 <B>laser at musichat.net
</B>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20idea%20for%20services&In-Reply-To=20030108100011.99840.29095.Mailman%40snow.fingers.co.za"
17 TITLE=
"[IRCServices Coding] idea for services">laser at musichat.net
19 <I>Wed Jan
8 02:
13:
50 PST
2003</I>
21 <LI>Previous message:
<A HREF=
"001861.html">[IRCServices Coding] Idea fo services
23 <LI>Next message:
<A HREF=
"001863.html">[IRCServices Coding] idea for xml part
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1862">[ date ]
</a>
27 <a href=
"thread.html#1862">[ thread ]
</a>
28 <a href=
"subject.html#1862">[ subject ]
</a>
29 <a href=
"author.html#1862">[ author ]
</a>
34 <PRE>Some people could also see it as spam,
35 but according to me, to be able to tell own users on things of the net IRC,
36 would be excellent, if then, an admin wants, can take the emails from the
37 infos of the nick and to make themselves a ml to make spam. But all
38 intelligence of every person is not to misuse.
41 in these days in my net we are moving the servers, and this will cause some
42 poor service, wanting to tell all, also those that don't enter for reading
43 the global notices or the messages of logon I am not able, causing so a
46 This is then one idea of mine fairies you.
52 ><i> However my idea was that to include all email address of the recorded nick
53 </I>><i> in an inside mailinglist to the serviceses.
54 </I>><i> This way we avoid:
56 </I>><i> 1) to insert to hand all the emails from the serviceses admin
57 </I>><i> 2) to wait that the people are undersigned to a possible external
58 </I>><i> mailinglist
62 </I>>><i> This sounds to me like something an external mailing list would
63 </I>>><i> handle quite well. For example,
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">users at yourdomain.com
</A> would be a mailing
64 </I>>><i> list that all users could (optionally) subscribe to, and you could send
65 </I>>><i> any notices out that way. Might I recommend Mailman (www.list.org) as a
66 </I>>><i> decent mailing list manager.
71 </I>>><i> Quoth Ciappei Alessandro (las3r) on Jan
6 at
11:
52,
75 </I>>>><i> Hi all,
77 </I>>>><i> my idea, is that to be able to send an email and a global memo to everybody
78 </I>>>><i> the recorded nick, for particular events, as for example, the move of a
79 </I>>>><i> server or the upgrade of the software.
80 </I>>>><i> In this way all the user also those not connected they will know what is
81 </I>>>><i> happening, in case of a possible malfunction owed to a wanted technical
82 </I>>>><i> intervention.
84 </I>>>><i> regards
86 </I>>>><i> Alex
87 </I>>>><i> -----------------------------------------------------------------------------
88 </I>>>><i> Chi riceve il presente messaggio e` tenuto a verificare se lo stesso non gli
89 </I>>>><i> sia pervenuto per errore. In tal caso e` pregato di avvisare immediatamente
90 </I>>>><i> il mittente e, tenuto conto delle responsabilita` connesse all'indebito
91 </I>>>><i> utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso
92 </I>>>><i> contenute, voglia cancellare l'originale e distruggere le varie copie o
93 </I>>>><i> stampe.
95 </I>>>><i> The receiver of this message is required to check if he/she has received it
96 </I>>>><i> erroneously. If so, the receiver is requested to immediately inform the
97 </I>>>><i> sender and - in consideration of the responsibilities arising from undue use
98 </I>>>><i> and/or disclosure of the message and/or the information contained therein -
99 </I>>>><i> destroy the original message and any copy or printout thereof.
100 </I>>>><i> -----------------------------------------------------------------------------
102 </I>><i> --__--__--
104 </I>><i> Message:
2
105 </I>><i> From:
"Martin Pels
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">martinpels at hotmail.com
</A>>
106 </I>><i> To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net
</A>
107 </I>><i> Subject: Re: [IRCServices Coding] Idea fo services
108 </I>><i> Date: Tue,
07 Jan
2003 13:
52:
55 +
0100
109 </I>><i> Reply-To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net
</A>
111 </I>><i> Some people would consider that as spam...
114 </I>>><i>Yes, would work as a mailinglist.
115 </I>>><i>However my idea was that to include all email address of the recorded nick
116 </I>>><i>in an inside mailinglist to the serviceses.
117 </I>>><i>This way we avoid:
119 </I>>><i>1) to insert to hand all the emails from the serviceses admin
120 </I>>><i>2) to wait that the people are undersigned to a possible external
121 </I>>><i>mailinglist
125 </I>>>><i> This sounds to me like something an external mailing list would handle
126 </I>>>><i>quite well. For example,
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">users at yourdomain.com
</A> would be a mailing list
127 </I>>>><i>that all users could (optionally) subscribe to, and you could send any
128 </I>>>><i>notices out that way. Might I recommend Mailman (www.list.org) as a
129 </I>>>><i>decent mailing list manager.
131 </I>>>><i>David
134 </I>>>><i>Quoth Ciappei Alessandro (las3r) on Jan
6 at
11:
52,
136 </I>>>>><i>
137 </I>>>>><i>
138 </I>>>>><i>Hi all,
139 </I>>>>><i>
140 </I>>>>><i>my idea, is that to be able to send an email and a global memo to
141 </I>>>>><i>everybody the recorded nick, for particular events, as for example, the
142 </I>>>>><i>move of a server or the upgrade of the software.
143 </I>>>>><i>In this way all the user also those not connected they will know what is
144 </I>>>>><i>happening, in case of a possible malfunction owed to a wanted technical
145 </I>>>>><i>intervention.
146 </I>>>>><i>
147 </I>>>>><i>regards
148 </I>>>>><i>
149 </I>>>>><i>Alex
157 <LI>Previous message:
<A HREF=
"001861.html">[IRCServices Coding] Idea fo services
159 <LI>Next message:
<A HREF=
"001863.html">[IRCServices Coding] idea for xml part
161 <LI> <B>Messages sorted by:
</B>
162 <a href=
"date.html#1862">[ date ]
</a>
163 <a href=
"thread.html#1862">[ thread ]
</a>
164 <a href=
"subject.html#1862">[ subject ]
</a>
165 <a href=
"author.html#1862">[ author ]
</a>
projects / irc.git / blob