Hi Eric,
I copied and pasted the following from another Email I received on this
list. The folks on the new list appear to be having a wonderful time, and I
am sure they would love to have you on the list too. The info is as follows:
"putting subscribe in the body of an email to
[log in to unmask]
"
Well, I put subscribe in the subject line and left the body blank, and that
seemed to do the trick. Smile.
I hope this helps.
God bless,
Rev. Mark
God Loves You!
Get your house or apartment Blessed today:
http://rockford.ebayclassifieds.com/v/41148783
-----Original Message-----
From: Eric Oyen
Sent: Tuesday, March 1, 2016 9:18 PM
To: [log in to unmask]
Subject: Re: List Posting Garbage
I have been hearing about another blind hams list. only problem, I never =
got it's location. any info would be appreciated.
thanks.
DE n7zzt Eric
On Mar 1, 2016, at 6:25 PM, George Smith wrote:
> i agree with steve.
> ----- Original Message -----=20
> From: "Steve Forst" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Monday, February 29, 2016 10:03 AM
> Subject: Re: List Posting Garbage
>=20
>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
>>=20
>>=20
>> 73, Steve KW3A
>> On 2/29/2016 9:21 AM, Richard B. McDonald wrote:
>>> Hi All!
>>>=20
>>> 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=20=
>>> these
>>> problems cannot be or do not get fixed then the list should move. =
The=20
>>> 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.
>>>=20
>>> 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=20
>>> same
>>> list serve that this list is presently on; and that it changed over =
to=20
>>> 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=20
>>> now.
>>>=20
>>> 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.
>>>=20
>>> 73,
>>> Richard KK6MRH
>>>=20
>>> -----Original Message-----
>>> From: For blind ham radio operators=20
>>> [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
>>>=20
>>> This is a multi-part message in MIME format.
>>>=20
>>> ------=3D_NextPart_000_0010_01D17284.E6876EE0
>>> Content-Type: text/plain;
>>> charset=3D"Windows-1252"
>>> Content-Transfer-Encoding: 7bit
>>>=20
>>> Bob, I have noticed since Phil said his friend was going to help =
with=20
>>> how
>>> the list is configured, that the people posting with a lot of =
extraneous
>>> headers and characters has worsened.
>>>=20
>>> 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=20=
>>> really
>>> active, and therefore, since I don't have email addresses for the=20
>>> members,
>>> everyone would have to move their on their own volition.
>>>=20
>>> I've kind of thought about doing this for quite awhile, but didn't =
see=20
>>> any
>>> sense in duplicating the list. But, since these issues keep =
festering=20
>>> and
>>> apparently won't be corrected, I'm leaning toward creating a list if=20=
>>> people
>>> are interested.
>>>=20
>>> 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
>>>=20
>>>=20
>>> This is a multi-part message in MIME format.
>>>=20
>>> ------=3D_NextPart_000_0003_01D1724A.D59D0980
>>> Content-Type: text/plain;
>>> charset=3D"utf-8"
>>> Content-Transfer-Encoding: quoted-printable
>>>=20
>>> I just looked at it and it is a mess; MINE format or something like =
=3D
>>> that. Have no idea how that happened as I don=3DE2=3D80=3D99t thing =
I have =3D
>>> changed any settings lately. Does anyone have a clue. Several months =
=3D
>>> ago, I did make a font change to eliminate lots of equal signs in my =
=3D
>>> email.
>>> 73:
>>> Bob Martin
>>>=20
>>> ------=3D_NextPart_000_0003_01D1724A.D59D0980
>>> Content-Type: text/html;
>>> charset=3D"utf-8"
>>> Content-Transfer-Encoding: quoted-printable
>>>=20
>>> <HTML><HEAD></HEAD>
>>> <BODY dir=3D3Dltr>
>>> <DIV dir=3D3Dltr>
>>> <DIV style=3D3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: =
#000000">
>>> <DIV>I just looked at it and it is a mess; MINE format or something =
like=20
>>> =3D
>>>=20
>>> that. Have no idea how that happened as I don=3DE2=3D80=3D99t =
thing I =3D
>>> have changed any=3D20
>>> settings lately. Does anyone have a clue. Several months ago, I did =
make=20
>>> =3D
>>> a font=3D20
>>> change to eliminate lots of equal signs in my email.</DIV>
>>> <DIV>73:</DIV>
>>> <DIV>Bob Martin</DIV>
>>> <DIV> </DIV></DIV></DIV></BODY></HTML>
>>>=20
>>> ------=3D_NextPart_000_0003_01D1724A.D59D0980--
>>>=20
>>> ------=3D_NextPart_000_0010_01D17284.E6876EE0
>>> Content-Type: text/html;
>>> charset=3D"Windows-1252"
>>> Content-Transfer-Encoding: quoted-printable
>>>=20
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>> <HTML><HEAD>
>>> <META content=3D3D"text/html; charset=3D3Dwindows-1252" =3D
>>> http-equiv=3D3DContent-Type>
>>> <META name=3D3DGENERATOR content=3D3D"MSHTML 11.00.9600.18125">
>>> <STYLE></STYLE>
>>> </HEAD>
>>> <BODY bgColor=3D3D#ffffff>
>>> <DIV><FONT color=3D3D#08000a size=3D3D2>Bob, I have noticed =
since Phil=20
>>> =3D
>>> said his=3D20
>>> friend was going to help with how the list is configured, that the =3D=
>>> people=3D20
>>> posting with a lot of extraneous headers and characters has=3D20
>>> worsened.</FONT></DIV>
>>> <DIV><FONT color=3D3D#08000a></FONT> </DIV>
>>> <DIV><FONT color=3D3D#08000a>If people are interested, I'd be glad =
to set =3D
>>> up this=3D20
>>> list on a different group server that is stable. Since the =3D
>>> ListAdmin of=3D20
>>> this list isn't really active, and therefore, since I don't have =
email =3D
>>> addresses=3D20
>>> for the members, everyone would have to move their on their own =3D
>>> volition. =3D20
>>> </FONT></DIV>
>>> <DIV><FONT color=3D3D#08000a></FONT> </DIV>
>>> <DIV><FONT color=3D3D#08000a>I've kind of thought about doing this =
for =3D
>>> quite awhile,=3D20
>>> but didn't see any sense in duplicating the list. But, since =
these=20
>>> =3D
>>> issues=3D20
>>> keep festering and apparently won't be corrected, I'm leaning toward =
=3D
>>> creating a=3D20
>>> list if people are interested.</FONT></DIV>
>>> <DIV><FONT color=3D3D#08000a></FONT> </DIV>
>>> <DIV><FONT color=3D3D#08000a>Steve, K8SP</FONT></DIV>
>>> <DIV style=3D3D"FONT: 10pt arial">----- Original Message -----=3D20
>>> <DIV style=3D3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> =
<A=3D20
>>> [log in to unmask] href=3D3D"mailto:[log in to unmask]">Bob =
=3D
>>> Martin</A> </DIV>
>>> <DIV><B>To:</B> <A [log in to unmask]
>>> =
href=3D3D"mailto:[log in to unmask]">[log in to unmask]
O=3D
>>> RG</A>=3D20
>>> </DIV>
>>> <DIV><B>Sent:</B> Sunday, February 28, 2016 5:09 PM</DIV>
>>> <DIV><B>Subject:</B> My Earlier Posting Regarding ARRL ARES=3D20
>>> Newsletter</DIV></DIV>
>>> <DIV><FONT color=3D3D#08000a size=3D3D2></FONT><BR></DIV>This is a =3D=
>>> multi-part message in=3D20
>>> MIME =3D
>>> =
format.<BR><BR>------=3D3D_NextPart_000_0003_01D1724A.D59D0980<BR>Content-=
T=3D
>>> ype:=3D20
>>> text/plain;<BR>charset=3D3D"utf-8"<BR>Content-Transfer-Encoding:=3D20
>>> quoted-printable<BR><BR>I just looked at it and it is a mess; MINE =3D=
>>> format or=3D20
>>> something like =3D3D<BR>that. Have no idea how that happened =
as I=3D20
>>> don=3D3DE2=3D3D80=3D3D99t thing I have =3D3D<BR>changed any settings =
lately. =3D
>>> Does anyone have a=3D20
>>> clue. Several months =3D3D<BR>ago, I did make a font change to =
eliminate =3D
>>> lots of=3D20
>>> equal signs in my =3D3D<BR>email.<BR>73:<BR>Bob=3D20
>>> =
Martin<BR><BR>------=3D3D_NextPart_000_0003_01D1724A.D59D0980<BR>Content-T=
y=3D
>>> pe:=3D20
>>> text/html;<BR>charset=3D3D"utf-8"<BR>Content-Transfer-Encoding:=3D20
>>> =
quoted-printable<BR><BR><HTML><HEAD></HEAD><BR><BODY=3D=
>>> =3D20
>>> dir=3D3D3Dltr><BR><DIV dir=3D3D3Dltr><BR><DIV =3D
>>> style=3D3D3D"FONT-SIZE: 12pt;=3D20
>>> FONT-FAMILY: 'Calibri'; COLOR: #000000"><BR><DIV>I just =
looked =3D
>>> at it=3D20
>>> and it is a mess; MINE format or something like =3D
>>> =3D3D<BR><BR>that.&nbsp; Have no=3D20
>>> idea how that happened as I don=3D3DE2=3D3D80=3D3D99t thing I =
=3D3D<BR>have =3D
>>> changed=3D20
>>> any=3D3D20<BR>settings lately. Does anyone have a clue. Several =
months =3D
>>> ago, I did=3D20
>>> make =3D3D<BR>a font=3D3D20<BR>change to eliminate lots of equal =
signs in my=20
>>> =3D
>>>=20
>>> =
email.</DIV><BR><DIV>73:</DIV><BR><DIV>Bob=3D20
>>> =
Martin</DIV><BR><DIV>&nbsp;</DIV></DIV></D=3D=
>>> =
IV></BODY></HTML><BR><BR>------=3D3D_NextPart_000_0003_01D1=
7=3D
>>> 24A.D59D0980--</BODY></HTML>
>>>=20
>>> ------=3D_NextPart_000_0010_01D17284.E6876EE0--
>>>=20
>=20
>=20
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
|
