From: Chong Yidong <cyd@stupidchicken.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: better not have a non-header line after Subject
Date: Thu, 15 Jun 2006 14:37:48 -0400 [thread overview]
Message-ID: <87odwuz2mb.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1FofIZ-0003wp-Id@fencepost.gnu.org> (Richard Stallman's message of "Fri, 09 Jun 2006 07:37:07 -0400")
Richard Stallman <rms@gnu.org> writes:
> Could someone please debug this?
I checked in the required fix to sendmail.el. Thanks.
(I think message-mode needs to be fixed too; CC'ing ding@gnus.org).
> From: Kevin Rodgers <ihs_4664@yahoo.com>
> Subject: Re: better not have a non-header line after Subject
> To: bug-gnu-emacs@gnu.org
>
> Dan Jacobson wrote:
>> Both plain emacs 22 or "No gnus", send differently mangled mail when given
>>
>> Subject: bla, and
>> a second non header line starting in column 1
>>
>> Garbage in, garbage out, but not caught.
>
> There is code in mail-send to detect that:
>
> ;; Complain about any invalid line.
> (goto-char (point-min))
> (while (< (point) (mail-header-end))
> (unless (looking-at "[ \t]\\|.*:\\|$")
> (push-mark opoint)
> (error "Invalid header line (maybe a continuation line
> lacks initial whitespace)"))
> (forward-line 1))
>
> But mail-header-end seems to be broken: it calls rfc822-goto-eoh instead
> of searching for the mail-header-separator (either the text on a line by
> itself or the category text property value).
next prev parent reply other threads:[~2006-06-15 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 11:37 [ihs_4664@yahoo.com: Re: better not have a non-header line after Subject] Richard Stallman
2006-06-15 18:37 ` Chong Yidong [this message]
2006-06-16 11:47 ` better not have a non-header line after Subject Katsumi Yamaoka
2006-06-19 9:10 ` Katsumi Yamaoka
2006-06-16 15:06 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 17:09 Dan Jacobson
2006-06-08 15:29 ` Kevin Rodgers
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=87odwuz2mb.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.