<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [ga] CC's and BCC's
- To: ga@xxxxxxxxxxxxxx
- Subject: RE: [ga] CC's and BCC's
- From: jwkckid1@xxxxxxxxxxxxx
- Date: Tue, 24 Jul 2007 18:49:14 -0500 (GMT-05:00)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=oBoPwEjbkTs56pZsAFGz4cxtlQ5/rT/EkfU3HD3rxHOrBPC52Q/DmYz00NBgiSTc; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Transfer-Encoding:X-Mailer:Content-Type:X-ELNK-Trace:X-Originating-IP;
- Reply-to: jwkckid1@xxxxxxxxxxxxx
- Sender: owner-ga@xxxxxxxxxxxxxx
<HEAD>
<STYLE>body{font-family: Geneva,Arial,Helvetica,sans-serif;font-size:9pt;background-color: #ffffff;color: black;}</STYLE>
<META content="MSHTML 6.00.2900.3132" name=GENERATOR></HEAD>
<BODY id=compText>
<STYLE>body{font-family: Geneva,Arial,Helvetica,sans-serif;font-size:9pt;background-color: #ffffff;color: black;}</STYLE>
<META content="MSHTML 6.00.2900.3132" name=GENERATOR>
<P>Debbie and all,</P>
<P> </P>
<P> Your parogative regarding CC's and BCC's is contrary to the development</P>
<P>of eMail applications and eMail useage. If one does not want to recieve</P>
<P>CC's and BCC's all one needs to do is deploy a filter for their eMail</P>
<P>account. Ergo making inane rule suggestions such as yours Debbie</P>
<P>is counter productive to the intent of eMail usage.<BR><BR><BR></P>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 0px; BORDER-LEFT: #0000ff 2px solid">-----Original Message----- <BR>From: Debbie Garside <DEBBIE@xxxxxxxxxxxxxxxxxx><BR>Sent: Jul 24, 2007 12:05 PM <BR>To: 'GA' <GA@xxxxxxxxxxxxxx><BR>Subject: RE: [ga] CC's and BCC's <BR><BR><ZZZHTML><ZZZHEAD><ZZZMETA content="text/html; charset=us-ascii" http-equiv="Content-Type"><ZZZMETA content="MSHTML 6.00.2800.1561" name="GENERATOR"></ZZZHEAD><ZZZBODY>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>In doing some research into this issue I came across some old DNSO Cross Posting rules (copied below). Should we adapt and adopt within our draft List Rules?</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>Apologies for the format, I could not find the original.</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>BTW, do we have a secretariat? (and, no, I do not want the job!)</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>My motto: Never re-invent the wheel - always re-design and modify. I would be grateful for any links to documents that will assist in the re-writing of the rules of participation.</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>Best</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>Debbie</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2>---</FONT></SPAN></DIV>
<DIV><SPAN class=123115916-24072007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=123115916-24072007>This is the summary of NO CROSS POSTING practices implemented<BR>> > on the DNSO server.<BR>> ><BR>> > A. NO CROSS POSTING Rules - implementation for the DNSO GA lists<BR>> > (Main List and Specific Purposes Lists):<BR>> ><BR>> > 1. The no cross posting apply to ALL GA lists as well as<BR>> > several well known other lists.<BR>> > 2. The end user (and maths) perspective prevails: if a person<BR>> > subscribe to List-One, but NOT to List-Two, he/she does not<BR>> > wish to get an e-mail from List-Two.<BR>> > 3. It was suggested each list to appoint a "rapporteur"<BR>> > to provide periodic updates to the Main List.<BR>> ><BR>> > B. NO CROSS POSTING Rules - implementation for NC WGs lists:<BR>> ><BR>> > 1. The no cross posting apply to ALL WGs lists.<BR>> > 2. The end user (and maths) perspective prevails: if a person<BR>> > subscribe to List-One, but NOT to List-Two, he/she does not<BR>> > wish to get an e-mail from List-Two.<BR>> > 3. Each WGs has two Co-Chairs, one from the NC and one elected<BR>> > by the group. The NC Co-Chair acts as liaison with the NC.<BR>> ><BR>> > C. POSTING Rules for the NC lists<BR>> > (Main List and Specific Purposes Lists):<BR>> ><BR>> > 1. Only the NC members, DNSO Secretariat and Scribe, ICANN Board<BR>> > and Staff, and the GA Chair and Alternate Chair are allowed<BR>> > to post to the Names Council lists.<BR>> > 2. The NC Working Groups shall communicate with the NC through<BR>> > "liaison co-Chair", who is the NC member.<BR>> > 3. The GA shall communicate with the NC through Chair or Alternate<BR>> > Chair.<BR>> > 4. The NC may decide to adapt these posting rules at any time.<BR>> ><BR>> > D. POSTING Rules for the special purpose announce@xxxxxxxx list:<BR>> ><BR>> > 1. Only the DNSO Secretariat may write to announce@xxxxxxxx list.<BR>> ><BR>> ><BR>> ><BR>> > EASY TO REMEMBER:<BR>> > 1. In summary: more CC and To, less chances it gets to any of list.<BR>> > 2. If somebody is member to many lists and wishes to share some<BR>> > topic with any of them he/she shall write to all of them separately.<BR>> ><BR>> > DNSO Secretariat<BR></SPAN></DIV><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-ga@xxxxxxxxxxxxxx [mailto:owner-ga@xxxxxxxxxxxxxx] <B>On Behalf Of </B>Hugh Dierker<BR><B>Sent:</B> 24 July 2007 14:38<BR><B>To:</B> GA<BR><B>Subject:</B> [ga] CC's and BCC's<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>I have come to dislike putting a whole string of addresses (translates- real people) in posts to the list. Recently I did some posting to the list and then simply did a second email to some folks I wanted to address. Recently I also followed suit on a poster's string because I wanted to reach them also. The fist one was right. The second method was lazy and really did not feel right.</DIV>
<DIV> </DIV>
<DIV>Thoughts or nonthoughts on this would be appreciated.</DIV>
<DIV> </DIV>
<DIV>Eric</DIV>
<DIV>as GA Chair</DIV>
<P></P>Regards,<BR>Jeffrey A. Williams<BR>Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)<BR>"Obedience of the law is the greatest freedom" -<BR> Abraham Lincoln<BR><BR>"Credit should go with the performance of duty and not with what is very<BR>often the accident of glory" - Theodore Roosevelt<BR><BR>"If the probability be called P; the injury, L; and the burden, B; liability<BR>depends upon whether B is less than L multiplied by<BR>P: i.e., whether B is less than PL."<BR>United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947]<BR>===============================================================<BR>Updated 1/26/04<BR>CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of<BR>Information Network Eng. INEG. INC.<BR>ABA member in good standing member ID 01257402 E-Mail jwkckid1@xxxxxxxxxxxxx<BR>Registered Email addr with the USPS Contact Number: 214-244-4827<BR></ZZZBODY></BLOCKQUOTE></BLOCKQUOTE></BODY>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|