Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: mail-header-separator starting with whitespace fails
Date: Wed, 28 Jan 2015 16:49:25 +1100	[thread overview]
Message-ID: <87y4onwj2y.fsf@building.gnus.org> (raw)
In-Reply-To: <b4mfvkdb399.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 14 May 2014 09:41:38 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> I tried this, confirmed it causes a mail corruption, and found
> at least one cause.  Could you try replacing the function definition
> of `rfc822-goto-eoh' with this?  (I.e., eval this form?)
>
> (defun rfc822-goto-eoh ()
>   "If the buffer starts with a mail header, move point to the header's end.
> Otherwise, moves to `point-min'.
> The end of the header is the start of the next line, if there is one,
> else the end of the last line.  This function obeys RFC822."
>   (goto-char (point-min))
>   (when (re-search-forward
> 	 (concat "^" (regexp-quote mail-header-separator) "\n\\|"
> 		 "^\\([:\n]\\|[^: \t\n]+[ \t\n]\\)")
> 	 nil 'move)
>     (goto-char (match-beginning 0))))
>
> This function is used by `smtpmail-send-it' by way of
> `mail-sendmail-undelimit-header' to delete the separator, but
> the original one doesn't respect `mail-header-separator'.

The mail header separator should have been stripped before the message
was passed to smtpmail, though, so I think something else must be wrong
somewhere...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  parent reply	other threads:[~2015-01-28  5:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 16:31 Russ Allbery
2014-05-14  0:41 ` Katsumi Yamaoka
2014-05-16 23:35   ` Russ Allbery
2015-01-28  5:49   ` Lars Ingebrigtsen [this message]
2015-01-28  8:33     ` Katsumi Yamaoka
2015-01-29  1:47       ` Lars Ingebrigtsen
2015-01-29  2:31         ` Katsumi Yamaoka

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=87y4onwj2y.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).