Fair point.
Chuck
--------------------------------------------------
From: "Pat Byrne" <[log in to unmask]>
Sent: Monday, February 29, 2016 8:51 PM
To: <[log in to unmask]>
Subject: Re: List Posting Garbage
> But we're doing positive about it Chuck!
> Pat, K9JAUAt 06:14 PM 2/29/2016, you wrote:
>>Wow, we're just like the republican party, falling apart. Sorry guys, I
>>couldn't resist.
>>
>>Chuck wa8vmo
>>
>>--------------------------------------------------
>>From: "Butch Bussen" <[log in to unmask]>
>>Sent: Monday, February 29, 2016 3:23 PM
>>To: <[log in to unmask]>
>>Subject: Re: List Posting Garbage
>>
>> > I don't know either. I'll likely not subscribe to a new list. It
>> > becomes a problem, which list to post to, who does and doesn't move and
>> > 73
>> > Butch
>> > WA0VJR
>> > Node 3148
>> > Wallace, ks.
>> >
>> >
>> > so forth. yech!!! On Mon, 29 Feb 2016, Steve Forst wrote:
>> >
>> >> We went through this a number of years ago. After some never ending
>> >> off
>> >> topic threads, someone started a new list just for ham topics.
>> >>
>> >> Soon after, someone (who I will call person A) posted an off topic
>> >> message to the new list which brought equally off topic replies from
>> >> persons B through F.
>> >>
>> >> This upset the list owner so much that he publicly jumped all over
>> >> person A with both feet, causing person A to unsubscribe from the new
>> >> list. The new list owner was so mad that he left his own list, and
>> >> it
>> >> languishes in the cyber backwaters until this day.
>> >>
>> >> I don't want to go through that again, and I really don't want to
>> >> belong
>> >> to 2 lists, with the inevitable double postings.
>> >>
>> >> I don't know what the answer is,and I'm not against a new list, but
>> >> I'll wait and see what direction things move.
>> >>
>> >>
>> >> 73, Steve KW3A
>> >> On 2/29/2016 9:21 AM, Richard B. McDonald wrote:
>> >>> Hi All!
>> >>>
>> >>> Generally, I agree with others that 1) the list admin should be given
>> >>> a
>> >>> reasonable amount of time to fix these pesky problems but that 2) if
>> >>> these
>> >>> problems cannot be or do not get fixed then the list should move.
>> >>> The
>> >>> list
>> >>> admin should participate in a change-over, if that becomes necessary.
>> >>> A
>> >>> blanket email from him to the list alerting all to a change-over
>> >>> could
>> >>> be
>> >>> sent and then the entire data base of subscribers uploaded into the
>> >>> new
>> >>> list-serve - none of this requires positive consent by each
>> >>> subscriber.
>> >>>
>> >>> In fact, many here may have noticed that the JAWS user list recently
>> >>> did
>> >>> exactly this. And, I believe the JAWS user list was previously on
>> >>> the
>> >>> same
>> >>> list serve that this list is presently on; and that it changed over
>> >>> to
>> >>> its
>> >>> current, new list serve because of administrative problems with that
>> >>> previous (i.e., this) list serve akin to the problems we see here and
>> >>> now.
>> >>>
>> >>> All that said, I seriously doubt that the problems we are having on
>> >>> this
>> >>> list are beyond repair. It does, however, require a bit of focused,
>> >>> knowledgeable attention.
>> >>>
>> >>> 73,
>> >>> Richard KK6MRH
>> >>>
>> >>> -----Original Message-----
>> >>> From: For blind ham radio operators
>> >>> [mailto:[log in to unmask]]
>> >>> On Behalf Of Steve
>> >>> Sent: Sunday, February 28, 2016 9:05 PM
>> >>> To: [log in to unmask]
>> >>> Subject: List Posting Garbage
>> >>>
>> >>> This is a multi-part message in MIME format.
>> >>>
>> >>> ------=_NextPart_000_0010_01D17284.E6876EE0
>> >>> Content-Type: text/plain;
>> >>> charset="Windows-1252"
>> >>> Content-Transfer-Encoding: 7bit
>> >>>
>> >>> Bob, I have noticed since Phil said his friend was going to help
>> >>> with
>> >>> how
>> >>> the list is configured, that the people posting with a lot of
>> >>> extraneous
>> >>> headers and characters has worsened.
>> >>>
>> >>> If people are interested, I'd be glad to set up this list on a
>> >>> different
>> >>> group server that is stable. Since the ListAdmin of this list isn't
>> >>> really
>> >>> active, and therefore, since I don't have email addresses for the
>> >>> members,
>> >>> everyone would have to move their on their own volition.
>> >>>
>> >>> I've kind of thought about doing this for quite awhile, but didn't
>> >>> see
>> >>> any
>> >>> sense in duplicating the list. But, since these issues keep
>> >>> festering
>> >>> and
>> >>> apparently won't be corrected, I'm leaning toward creating a list if
>> >>> people
>> >>> are interested.
>> >>>
>> >>> Steve, K8SP
>> >>> ----- Original Message -----
>> >>> From: Bob Martin
>> >>> To: [log in to unmask]
>> >>> Sent: Sunday, February 28, 2016 5:09 PM
>> >>> Subject: My Earlier Posting Regarding ARRL ARES Newsletter
>> >>>
>> >>>
>> >>> This is a multi-part message in MIME format.
>> >>>
>> >>> ------=_NextPart_000_0003_01D1724A.D59D0980
>> >>> Content-Type: text/plain;
>> >>> charset="utf-8"
>> >>> Content-Transfer-Encoding: quoted-printable
>> >>>
>> >>> I just looked at it and it is a mess; MINE format or something like =
>> >>> that. Have no idea how that happened as I don=E2=80=99t thing I have
>> >>> =
>> >>> changed any settings lately. Does anyone have a clue. Several months
>> >>> =
>> >>> ago, I did make a font change to eliminate lots of equal signs in my
>> >>> =
>> >>> email.
>> >>> 73:
>> >>> Bob Martin
>> >>>
>> >>> ------=_NextPart_000_0003_01D1724A.D59D0980
>> >>> Content-Type: text/html;
>> >>> charset="utf-8"
>> >>> Content-Transfer-Encoding: quoted-printable
>> >>>
>> >>> <HTML><HEAD></HEAD>
>> >>> <BODY dir=3Dltr>
>> >>> <DIV dir=3Dltr>
>> >>> <DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR:
>> >>> #000000">
>> >>> <DIV>I just looked at it and it is a mess; MINE format or something
>> >>> like
>> >>> =
>> >>>
>> >>> that. Have no idea how that happened as I don=E2=80=99t thing I
>> >>> =
>> >>> have changed any=20
>> >>> settings lately. Does anyone have a clue. Several months ago, I did
>> >>> make
>> >>> =
>> >>> a font=20
>> >>> change to eliminate lots of equal signs in my email.</DIV>
>> >>> <DIV>73:</DIV>
>> >>> <DIV>Bob Martin</DIV>
>> >>> <DIV> </DIV></DIV></DIV></BODY></HTML>
>> >>>
>> >>> ------=_NextPart_000_0003_01D1724A.D59D0980--
>> >>>
>> >>> ------=_NextPart_000_0010_01D17284.E6876EE0
>> >>> Content-Type: text/html;
>> >>> charset="Windows-1252"
>> >>> Content-Transfer-Encoding: quoted-printable
>> >>>
>> >>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> >>> <HTML><HEAD>
>> >>> <META content=3D"text/html; charset=3Dwindows-1252" =
>> >>> http-equiv=3DContent-Type>
>> >>> <META name=3DGENERATOR content=3D"MSHTML 11.00.9600.18125">
>> >>> <STYLE></STYLE>
>> >>> </HEAD>
>> >>> <BODY bgColor=3D#ffffff>
>> >>> <DIV><FONT color=3D#08000a size=3D2>Bob, I have noticed since
>> >>> Phil
>> >>> =
>> >>> said his=20
>> >>> friend was going to help with how the list is configured, that the =
>> >>> people=20
>> >>> posting with a lot of extraneous headers and characters has=20
>> >>> worsened.</FONT></DIV>
>> >>> <DIV><FONT color=3D#08000a></FONT> </DIV>
>> >>> <DIV><FONT color=3D#08000a>If people are interested, I'd be glad to
>> >>> set
>> >>> =
>> >>> up this=20
>> >>> list on a different group server that is stable. Since the =
>> >>> ListAdmin of=20
>> >>> this list isn't really active, and therefore, since I don't have
>> >>> email =
>> >>> addresses=20
>> >>> for the members, everyone would have to move their on their own =
>> >>> volition. =20
>> >>> </FONT></DIV>
>> >>> <DIV><FONT color=3D#08000a></FONT> </DIV>
>> >>> <DIV><FONT color=3D#08000a>I've kind of thought about doing this for
>> >>> =
>> >>> quite awhile,=20
>> >>> but didn't see any sense in duplicating the list. But, since
>> >>> these
>> >>> =
>> >>> issues=20
>> >>> keep festering and apparently won't be corrected, I'm leaning toward
>> >>> =
>> >>> creating a=20
>> >>> list if people are interested.</FONT></DIV>
>> >>> <DIV><FONT color=3D#08000a></FONT> </DIV>
>> >>> <DIV><FONT color=3D#08000a>Steve, K8SP</FONT></DIV>
>> >>> <DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
>> >>> <DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
>> >>> <A=20
>> >>> [log in to unmask] href=3D"mailto:[log in to unmask]">Bob =
>> >>> Martin</A> </DIV>
>> >>> <DIV><B>To:</B> <A [log in to unmask]
>> >>>
>> href=3D"mailto:[log in to unmask]">[log in to unmask]
>> >>> RG</A>=20
>> >>> </DIV>
>> >>> <DIV><B>Sent:</B> Sunday, February 28, 2016 5:09 PM</DIV>
>> >>> <DIV><B>Subject:</B> My Earlier Posting Regarding ARRL ARES=20
>> >>> Newsletter</DIV></DIV>
>> >>> <DIV><FONT color=3D#08000a size=3D2></FONT><BR></DIV>This is a =
>> >>> multi-part message in=20
>> >>> MIME =
>> >>>
>> format.<BR><BR>------=3D_NextPart_000_0003_01D1724A.D59D0980<BR>Content-T=
>> >>> ype:=20
>> >>> text/plain;<BR>charset=3D"utf-8"<BR>Content-Transfer-Encoding:=20
>> >>> quoted-printable<BR><BR>I just looked at it and it is a mess; MINE =
>> >>> format or=20
>> >>> something like =3D<BR>that. Have no idea how that happened as
>> >>> I=20
>> >>> don=3DE2=3D80=3D99t thing I have =3D<BR>changed any settings lately.
>> >>> =
>> >>> Does anyone have a=20
>> >>> clue. Several months =3D<BR>ago, I did make a font change to
>> >>> eliminate =
>> >>> lots of=20
>> >>> equal signs in my =3D<BR>email.<BR>73:<BR>Bob=20
>> >>>
>> Martin<BR><BR>------=3D_NextPart_000_0003_01D1724A.D59D0980<BR>Content-Ty=
>> >>> pe:=20
>> >>> text/html;<BR>charset=3D"utf-8"<BR>Content-Transfer-Encoding:=20
>> >>>
>> quoted-printable<BR><BR><HTML><HEAD></HEAD><BR><BODY=
>> >>> =20
>> >>> dir=3D3Dltr><BR><DIV dir=3D3Dltr><BR><DIV =
>> >>> style=3D3D"FONT-SIZE: 12pt;=20
>> >>> FONT-FAMILY: 'Calibri'; COLOR: #000000"><BR><DIV>I just
>> >>> looked
>> >>> =
>> >>> at it=20
>> >>> and it is a mess; MINE format or something like =
>> >>> =3D<BR><BR>that.&nbsp; Have no=20
>> >>> idea how that happened as I don=3DE2=3D80=3D99t thing I =3D<BR>have =
>> >>> changed=20
>> >>> any=3D20<BR>settings lately. Does anyone have a clue. Several months
>> >>> =
>> >>> ago, I did=20
>> >>> make =3D<BR>a font=3D20<BR>change to eliminate lots of equal signs in
>> >>> my
>> >>> =
>> >>>
>> >>> email.</DIV><BR><DIV>73:</DIV><BR><DIV>Bob=20
>> >>>
>> Martin</DIV><BR><DIV>&nbsp;</DIV></DIV></D=
>> >>>
>> IV></BODY></HTML><BR><BR>------=3D_NextPart_000_0003_01D17=
>> >>> 24A.D59D0980--</BODY></HTML>
>> >>>
>> >>> ------=_NextPart_000_0010_01D17284.E6876EE0--
>> >>>
>> >>
>> >>
|
