all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: better not have a non-header line after Subject
Date: Fri, 16 Jun 2006 20:47:46 +0900	[thread overview]
Message-ID: <b4m4pylb9ul.fsf@jpl.org> (raw)
In-Reply-To: 87odwuz2mb.fsf@stupidchicken.com

>>>>> In <87odwuz2mb.fsf@stupidchicken.com> Chong Yidong wrote:

> 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).

Thanks.  Gnus checks for continuation header lines only when
posting news articles.  I've made it do so for mail messages as
well in the Gnus CVS repository.  The changes will be merged to
the Emacs CVS after a while.

(As for blank header lines, Gnus removes them silently using
`message-cleanup-headers'.)

>> 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).

  reply	other threads:[~2006-06-16 11:47 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 ` better not have a non-header line after Subject Chong Yidong
2006-06-16 11:47   ` Katsumi Yamaoka [this message]
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=b4m4pylb9ul.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.