From: jidanni@jidanni.org
To: bug-mime-tools@rt.cpan.org
Cc: ding@gnus.org
Subject: mulitpart/digest newlines around boundaries [rt.cpan.org #32273]
Date: Mon, 14 Jan 2008 13:17:03 +0800 [thread overview]
Message-ID: <87wsqdj8a8.fsf@jidanni.org> (raw)
In-Reply-To: <87k5mdks47.fsf@jidanni.org>
> $headers{$name} .= "X-Size: $size\nX-File: $name"; #be stingy:no \n
Now find I need \n\n here at EOL instead of none, for gnus. In other
words the environment around a boundary between messages in an
mulitpart/digest needs to at least be as below. Mutt is not as picky.
Note my mulitpart/digest are just collections of spam headers with no
bodies, see http://jidanni.org/comp/spam/ .
X-Spam-Langua
X-Size: 4116
X-File: Mail/
------------=
Date: Mon, 14
From: patdoud
Subject: GREE
parent reply other threads:[~2008-01-14 5:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87k5mdks47.fsf@jidanni.org>]
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=87wsqdj8a8.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=bug-mime-tools@rt.cpan.org \
--cc=ding@gnus.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).