all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Marshall <robert.marshall@codethink.co.uk>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 31145@debbugs.gnu.org
Subject: bug#31145: 27.0.50; forwarding an html email in gnus mungs the headers if they contain a blank line
Date: Wed, 18 Apr 2018 08:53:06 +0100	[thread overview]
Message-ID: <87r2ndymql.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <87zi23vsi3.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Mon, 16 Apr 2018 21:52:20 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Robert Marshall <robert.marshall@codethink.co.uk> writes:
>
>> Thanks Lars, emails have been forwarded off list
>
> Thanks.  I put it in an nndoc group and `C-c C-f'-d it
> (with (setq message-forward-as-mime t) as that's what it looked like),
> and I was unable to reproduce the bug.

So I see! I've seen this bug on a variety of emails normally hits me
when I'm trying to forward spammy emails (inevitably with html
components) to our spam collector.
>
> The line in question wasn't completely empty -- it had a space in there,
> and Message seemed to heed that as a continuation line, as it should.
>
> I'll forward it to you so that you can see.  :-)

Thanks, I'll look at my other settings and see if I can produce a
-Q'able test case.

Robert





  reply	other threads:[~2018-04-18  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 13:01 bug#31145: 27.0.50; forwarding an html email in gnus mungs the headers if they contain a blank line Robert Marshall
2018-04-13 21:32 ` Lars Ingebrigtsen
2018-04-16 12:33   ` Robert Marshall
2018-04-16 19:52     ` Lars Ingebrigtsen
2018-04-18  7:53       ` Robert Marshall [this message]
2019-06-22 13:50         ` Lars Ingebrigtsen
2019-09-27 15:21           ` Lars Ingebrigtsen

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=87r2ndymql.fsf@ctlt579.codethink.co.uk \
    --to=robert.marshall@codethink.co.uk \
    --cc=31145@debbugs.gnu.org \
    --cc=larsi@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. 
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.