software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/001860.html

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