Re: Mailman is broken

2017-06-09 Thread Tim
Allegedly, on or about 09 June 2017, Ed Greshko sent: > Probably, eventually. After I study the differences between the > headers of an S/MIME message to the list compared with the headers of > a PGP/MIME message (which I have verified does survive) and determine > if it is a case of real breakag

Re: Mailman is broken

2017-06-08 Thread Dave Stevens
e. > > So, thanks much for letting me know and making things easier to nail > down. > de nada! ;-) d -- In modern fantasy (literary or governmental), killing people is the usual solution to the so-called war between good and evil. My books are not conceived in terms of such a war, and offer

Re: Mailman is broken

2017-06-08 Thread Ed Greshko
On 06/09/17 06:12, Dave Stevens wrote: > On Fri, 9 Jun 2017 05:55:41 +0800 > Ed Greshko wrote: > >> On 06/09/17 05:47, Dave Stevens wrote: >>> wouldn't it be useful to post this on the mailman users list? >> >> Probably, eventually. After I study the differences between the >> headers of an S/

Re: Mailman is broken

2017-06-08 Thread Dave Stevens
On Fri, 9 Jun 2017 05:55:41 +0800 Ed Greshko wrote: > On 06/09/17 05:47, Dave Stevens wrote: > > wouldn't it be useful to post this on the mailman users list? > > > Probably, eventually. After I study the differences between the > headers of an S/MIME message to the list compared with the h

Re: Mailman is broken

2017-06-08 Thread Ed Greshko
On 06/09/17 05:47, Dave Stevens wrote: > wouldn't it be useful to post this on the mailman users list? Probably, eventually. After I study the differences between the headers of an S/MIME message to the list compared with the headers of a PGP/MIME message (which I have verified does survive) an

Re: Mailman is broken

2017-06-08 Thread Dave Stevens
On Fri, 9 Jun 2017 05:41:21 +0800 Ed Greshko wrote: > On 06/09/17 02:39, Walter H. wrote: > > On 08.06.2017 15:44, Ed Greshko wrote: > >> > >> I don't recall putting out any headers that showed your message > >> containing HTML. > > of copurse not, I guessed this from multipart/mixed ... >

Re: Mailman is broken

2017-06-08 Thread Ed Greshko
On 06/09/17 02:39, Walter H. wrote: > On 08.06.2017 15:44, Ed Greshko wrote: >> >> I don't recall putting out any headers that showed your message >> containing HTML. > of copurse not, I guessed this from multipart/mixed ... >> >>> I do see what you mean about S/MIME. I've not used that in quite s

Re: Mailman is broken

2017-06-08 Thread Walter H.
On 08.06.2017 15:44, Ed Greshko wrote: I don't recall putting out any headers that showed your message containing HTML. of copurse not, I guessed this from multipart/mixed ... I do see what you mean about S/MIME. I've not used that in quite some time so I'd have to look to see how/why it ge

Re: Mailman is broken

2017-06-08 Thread Ed Greshko
On 06/08/17 20:07, Walter H. wrote: > On Thu, June 8, 2017 09:00, Ed Greshko wrote: >> On 06/08/17 14:23, Walter H. wrote: >>> right, I had once configured to only send HTML mail to specific >>> domains, >>> which means to any other it is plain-text >>> >>> it seems that the mailinglist-mailman is

Re: Mailman is broken

2017-06-08 Thread Walter H.
On Thu, June 8, 2017 09:00, Ed Greshko wrote: > On 06/08/17 14:23, Walter H. wrote: >> right, I had once configured to only send HTML mail to specific >> domains, >> which means to any other it is plain-text >> >> it seems that the mailinglist-mailman is broken ... > > So, how is it broken? where

Re: Mailman is broken

2017-06-08 Thread Ed Greshko
On 06/08/17 14:23, Walter H. wrote: > right, I had once configured to only send HTML mail to specific domains, > which means to any other it is plain-text > > it seems that the mailinglist-mailman is broken ... So, how is it broken? I mean other than now forcing me to remember to hit "Reply Lis