]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] Idea fo services | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Idea%20fo%20services&In-Reply-To="> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="001860.html"> | |
11 | <LINK REL="Next" HREF="001862.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] Idea fo services</H1> | |
15 | <B>Martin Pels</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Idea%20fo%20services&In-Reply-To=" | |
17 | TITLE="[IRCServices Coding] Idea fo services">martinpels at hotmail.com | |
18 | </A><BR> | |
19 | <I>Tue Jan 7 04:52:55 PST 2003</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001860.html">[IRCServices Coding] Idea fo services | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001862.html">[IRCServices Coding] idea for services | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1861">[ date ]</a> | |
27 | <a href="thread.html#1861">[ thread ]</a> | |
28 | <a href="subject.html#1861">[ subject ]</a> | |
29 | <a href="author.html#1861">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Some people would consider that as spam... | |
35 | ||
36 | ><i> | |
37 | </I>><i>Yes, would work as a mailinglist. | |
38 | </I>><i>However my idea was that to include all email address of the recorded nick | |
39 | </I>><i>in an inside mailinglist to the serviceses. | |
40 | </I>><i>This way we avoid: | |
41 | </I>><i> | |
42 | </I>><i>1) to insert to hand all the emails from the serviceses admin | |
43 | </I>><i>2) to wait that the people are undersigned to a possible external | |
44 | </I>><i>mailinglist | |
45 | </I>><i> | |
46 | </I>><i>Alex | |
47 | </I>><i> | |
48 | </I>>><i> This sounds to me like something an external mailing list would handle | |
49 | </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 | |
50 | </I>>><i>that all users could (optionally) subscribe to, and you could send any | |
51 | </I>>><i>notices out that way. Might I recommend Mailman (www.list.org) as a | |
52 | </I>>><i>decent mailing list manager. | |
53 | </I>>><i> | |
54 | </I>>><i>David | |
55 | </I>>><i> | |
56 | </I>>><i> | |
57 | </I>>><i>Quoth Ciappei Alessandro (las3r) on Jan 6 at 11:52, | |
58 | </I>>><i> | |
59 | </I>>>><i> | |
60 | </I>>>><i> | |
61 | </I>>>><i>Hi all, | |
62 | </I>>>><i> | |
63 | </I>>>><i>my idea, is that to be able to send an email and a global memo to | |
64 | </I>>>><i>everybody the recorded nick, for particular events, as for example, the | |
65 | </I>>>><i>move of a server or the upgrade of the software. | |
66 | </I>>>><i>In this way all the user also those not connected they will know what is | |
67 | </I>>>><i>happening, in case of a possible malfunction owed to a wanted technical | |
68 | </I>>>><i>intervention. | |
69 | </I>>>><i> | |
70 | </I>>>><i>regards | |
71 | </I>>>><i> | |
72 | </I>>>><i>Alex | |
73 | </I>>>><i>----------------------------------------------------------------------------- | |
74 | </I>>>><i>Chi riceve il presente messaggio e` tenuto a verificare se lo stesso non | |
75 | </I>>>><i>gli | |
76 | </I>>>><i>sia pervenuto per errore. In tal caso e` pregato di avvisare | |
77 | </I>>>><i>immediatamente | |
78 | </I>>>><i>il mittente e, tenuto conto delle responsabilita` connesse | |
79 | </I>>>><i>all'indebito | |
80 | </I>>>><i>utilizzo e/o divulgazione del messaggio e/o delle informazioni in | |
81 | </I>>>><i>esso | |
82 | </I>>>><i>contenute, voglia cancellare l'originale e distruggere le varie | |
83 | </I>>>><i>copie o | |
84 | </I>>>><i>stampe. | |
85 | </I>>>><i> | |
86 | </I>>>><i>The receiver of this message is required to check if he/she has | |
87 | </I>>>><i>received it | |
88 | </I>>>><i>erroneously. If so, the receiver is requested to immediately inform | |
89 | </I>>>><i>the | |
90 | </I>>>><i>sender and - in consideration of the responsibilities arising from undue | |
91 | </I>>>><i>use | |
92 | </I>>>><i>and/or disclosure of the message and/or the information contained | |
93 | </I>>>><i>therein - | |
94 | </I>>>><i>destroy the original message and any copy or printout thereof. | |
95 | </I>>>><i>----------------------------------------------------------------------------- | |
96 | </I>><i>------------------------------------------------------------------ | |
97 | </I>><i>To unsubscribe or change your subscription options, visit: | |
98 | </I>><i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
99 | </I> | |
100 | ||
101 | _________________________________________________________________ | |
102 | Protect your PC - get McAfee.com VirusScan Online | |
103 | <A HREF="http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963">http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963</A> | |
104 | ||
105 | ||
106 | </PRE> | |
107 | ||
108 | <!--endarticle--> | |
109 | <HR> | |
110 | <P><UL> | |
111 | <!--threads--> | |
112 | <LI>Previous message: <A HREF="001860.html">[IRCServices Coding] Idea fo services | |
113 | </A></li> | |
114 | <LI>Next message: <A HREF="001862.html">[IRCServices Coding] idea for services | |
115 | </A></li> | |
116 | <LI> <B>Messages sorted by:</B> | |
117 | <a href="date.html#1861">[ date ]</a> | |
118 | <a href="thread.html#1861">[ thread ]</a> | |
119 | <a href="subject.html#1861">[ subject ]</a> | |
120 | <a href="author.html#1861">[ author ]</a> | |
121 | </LI> | |
122 | </UL> | |
123 | ||
124 | </body></html> |