I suspect it is the fact that the header is listed as a short header.  They 
did note in their listowner manual that sometimes that can break mime 
encoded email clients.  Just speculating.

They do have an 800 number.
----- Original Message ----- 
From: "Phil Scovell" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, February 10, 2014 8:15 PM
Subject: Re: Just keep the list muddling along as is.


> Ken,
>
> I forgot the person who helped me at listserv but it was one of the 
> managers
> of the system.  I found her by subscribing to their list owners support
> list.  I stated my problem and after I tried figuring it out, she offered 
> to
> fix it herself through the header command file.  My =20 stuff immediately
> went away.  I'd just subscribe to the owners list and ask there.  You 
> might
> also find a contact through their website for all the lists.  Just 
> subscribe
> to listowners at the same listserv icors address anyone does to join
> blind-hams.
>
> Phil.
> K0NX
>
>
>
>
> ----- Original Message ----- 
> From: "Ken Scott" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Monday, February 10, 2014 3:40 PM
> Subject: Re: Just keep the list muddling along as is.
>
>
>>I think possibly some people missed one key point in my message from very
>> early this morning. I said there, that if anyone was familiar with a way
>> to make Listserv perform better where these issues are concerned, that I
>> would do what I could to apply the fix. And when reading the last few
>> messages from last night, sent before I sent my own, I noticed that Phil
>> Scovell is possibly aware of just such a fix. So when he sees my first
>> message, or this one, and assuming he sends me whatever info I need for
>> making the appropriate change(s) to the list header, I will do that, and
>> we'll see how things go from there.
>>
>> --
>> Ken,
>> [log in to unmask]
>>