supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: supervision@list.skarnet.org
Subject: problem with mailing list and multipart/mime?
Date: Fri, 21 Oct 2011 09:44:02 -0700	[thread overview]
Message-ID: <87y5we8fcd.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87vcrja2xj.fsf@servo.finestructure.net>

It seems that my multipart/signed messages sent to the list have had
their MIME structure destroyed somewhere along the way.  It looks like
the initial content boundary between the header and the body has been
stripped.

Has anyone else noticed this behavior?  I've never had this issue with
any other mailing list.  Would someone else mind sending at
multipart/signed message to the list?  I would be curious to see if the
same thing happens to anyone else.

jamie.


  parent reply	other threads:[~2011-10-21 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 16:26 Per-user service managers Mike Buland
2011-10-20 17:40 ` Jameson Graef Rollins
2011-10-20 18:11   ` Mike Buland
2011-10-20 19:16     ` Jameson Graef Rollins
2011-10-20 19:21       ` Mike Buland
2011-10-21 16:44       ` Jameson Graef Rollins [this message]
2011-10-21 18:55         ` problem with mailing list and multipart/mime? Uffe Jakobsen
2011-10-22  1:31         ` Alex Efros
2011-10-22  2:01           ` Jameson Graef Rollins
2011-10-22 10:43             ` Alex Efros
2011-10-22 11:47               ` Laurent Bercot
2011-10-22 19:43                 ` Jameson Graef Rollins
2011-10-22 19:49                   ` Jameson Graef Rollins
2012-03-10 16:34                   ` Laurent Bercot
2011-10-22 19:16             ` Jameson Graef Rollins
2011-10-22  7:24         ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5we8fcd.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).