projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] Idea for 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%20for%20services&In-Reply-To=5.2.0.9.2.20030106114647.034acde8%40mail.musichat.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="001851.html"> | |
| 11 | <LINK REL="Next" HREF="001844.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] Idea for services</H1> | |
| 15 | <B>Ballsy</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Idea%20for%20services&In-Reply-To=5.2.0.9.2.20030106114647.034acde8%40mail.musichat.net" | |
| 17 | TITLE="[IRCServices Coding] Idea for services">ballsy at mystical.net | |
| 18 | </A><BR> | |
| 19 | <I>Mon Jan 6 05:07:18 PST 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="001851.html">[IRCServices Coding] Idea for services | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="001844.html">[IRCServices Coding] Unreal3.2-beta13 and the Unreal protocol | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#1852">[ date ]</a> | |
| 27 | <a href="thread.html#1852">[ thread ]</a> | |
| 28 | <a href="subject.html#1852">[ subject ]</a> | |
| 29 | <a href="author.html#1852">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE> This sounds to me like something an external mailing list would | |
| 35 | 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 | |
| 36 | list that all users could (optionally) subscribe to, and you could send | |
| 37 | any notices out that way. Might I recommend Mailman (www.list.org) as a | |
| 38 | decent mailing list manager. | |
| 39 | ||
| 40 | David | |
| 41 | ||
| 42 | ||
| 43 | Quoth Ciappei Alessandro (las3r) on Jan 6 at 11:52, | |
| 44 | ||
| 45 | ><i> | |
| 46 | </I>><i> | |
| 47 | </I>><i> Hi all, | |
| 48 | </I>><i> | |
| 49 | </I>><i> my idea, is that to be able to send an email and a global memo to everybody | |
| 50 | </I>><i> the recorded nick, for particular events, as for example, the move of a | |
| 51 | </I>><i> server or the upgrade of the software. | |
| 52 | </I>><i> In this way all the user also those not connected they will know what is | |
| 53 | </I>><i> happening, in case of a possible malfunction owed to a wanted technical | |
| 54 | </I>><i> intervention. | |
| 55 | </I>><i> | |
| 56 | </I>><i> regards | |
| 57 | </I>><i> | |
| 58 | </I>><i> Alex | |
| 59 | </I>><i> ----------------------------------------------------------------------------- | |
| 60 | </I>><i> Chi riceve il presente messaggio e` tenuto a verificare se lo stesso non gli | |
| 61 | </I>><i> sia pervenuto per errore. In tal caso e` pregato di avvisare immediatamente | |
| 62 | </I>><i> il mittente e, tenuto conto delle responsabilita` connesse all'indebito | |
| 63 | </I>><i> utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso | |
| 64 | </I>><i> contenute, voglia cancellare l'originale e distruggere le varie copie o | |
| 65 | </I>><i> stampe. | |
| 66 | </I>><i> | |
| 67 | </I>><i> The receiver of this message is required to check if he/she has received it | |
| 68 | </I>><i> erroneously. If so, the receiver is requested to immediately inform the | |
| 69 | </I>><i> sender and - in consideration of the responsibilities arising from undue use | |
| 70 | </I>><i> and/or disclosure of the message and/or the information contained therein - | |
| 71 | </I>><i> destroy the original message and any copy or printout thereof. | |
| 72 | </I>><i> ----------------------------------------------------------------------------- | |
| 73 | </I>><i> | |
| 74 | </I>><i> ------------------------------------------------------------------ | |
| 75 | </I>><i> To unsubscribe or change your subscription options, visit: | |
| 76 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
| 77 | </I>><i> | |
| 78 | </I> | |
| 79 | ||
| 80 | </PRE> | |
| 81 | ||
| 82 | <!--endarticle--> | |
| 83 | <HR> | |
| 84 | <P><UL> | |
| 85 | <!--threads--> | |
| 86 | <LI>Previous message: <A HREF="001851.html">[IRCServices Coding] Idea for services | |
| 87 | </A></li> | |
| 88 | <LI>Next message: <A HREF="001844.html">[IRCServices Coding] Unreal3.2-beta13 and the Unreal protocol | |
| 89 | </A></li> | |
| 90 | <LI> <B>Messages sorted by:</B> | |
| 91 | <a href="date.html#1852">[ date ]</a> | |
| 92 | <a href="thread.html#1852">[ thread ]</a> | |
| 93 | <a href="subject.html#1852">[ subject ]</a> | |
| 94 | <a href="author.html#1852">[ author ]</a> | |
| 95 | </LI> | |
| 96 | </UL> | |
| 97 | ||
| 98 | </body></html> |