Re: Mailman is broken

[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 broken ...
> > So, how is it broken?
>  where is the digital signature (S/MIME) shown?
>
> > I mean other than now forcing me to remember to
> > hit "Reply List".  :-)
>  of course stripping off HTML is a feature, but ...
>
>  that I send both text/plain and text/html was a guess of mine, because of
>  the lines inside the mail source you gave earlier; 
I don't recall putting out any headers that showed your message
containing HTML.

Now, looking back in the list I do see messages with HTML formatting. 
In those cases, as per the RFC's, they do have an initial header of

Content-Type: multipart/mixed; boundary="===============6657248435458859845==

But then you have 

Content-Type: multipart/alternative; boundary="f403045c3978a173c20550995890"

With the alternative forms of the same content bounded by what is specified in the
"boundary"
 

>  I only send text/plain, and this signed ...
>
>  the mails, that I send are
>
>  e.g.
>  multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1;
>  boundary="------------ms090300020904060901010406"
>
>  and not
>
>  e.g.
>  multipart/mixed; boundary="===============5882133914592620319=="
>  
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 gets broken.  I've used
PGP/MIME on this list before, and I will sign this message, and it
didn't get broken.  Guess I'll have to get a free S/MIME cert for
testing at some point.  :-) :-)

-- 
Fedora Users List - The place to go to speculate endlessly