From: daniel@wagner-home.com (Daniel Wagner)
Subject: [sup-talk] header parsing
Date: Sun, 17 Feb 2008 14:44:34 -0800 [thread overview]
Message-ID: <1203288077-sup-526@buckwheat> (raw)
Hello,
Can sup be a bit more lax on parsing email headers? In particular, it
seems to discard any where the ':' is not immediately followed by a ' '.
I'm not totally sure of the spec, but I couldn't find anything in
<http://tools.ietf.org/html/rfc2822#section-2.2> that required a space
after the colon. (Granted, I did do a very cursory look.)
Thanks,
~d
next reply other threads:[~2008-02-17 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:44 Daniel Wagner [this message]
2008-02-18 14:33 ` William Morgan
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=1203288077-sup-526@buckwheat \
--to=daniel@wagner-home.com \
/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