Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: ding@gnus.org
Subject: Re: create a message, have it in the holster?
Date: Mon, 25 Sep 2017 23:39:09 +0200	[thread overview]
Message-ID: <86mv5i31c2.fsf@zoho.com> (raw)
In-Reply-To: <87a81id16w.fsf@ericabrahamsen.net>

Eric Abrahamsen wrote:

> I think they all would have been recreated
> as-is, though I don't actually know if the
> Date is recomputed, or left as the date the
> first mail was sent.

Removing them isn't a big deal, and it is
a natural instinct as a programmer, to not have
incorrect data (e.g., the date hö hö) - but one
aspect is, I have Gnus configured to hide/show
certain headers. I wonder if that influences
this, and, in particular, if it could be that
there are incorrect "hidden header" data that
slips by because I don't see/remove them?

I'm going to run some test on this, if it can't
be found in the manual, the answer to the
question "What headers are
recreated/repopulated on send, and does it
influence if the user keeps/removes them prior
to sending?"

For example, there are spam headers. I suppose
spammers can't bypass that by adding a header
"Spam: NO"

:)

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2017-09-25 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  8:31 Emanuel Berg
2017-09-25 15:28 ` Eric Abrahamsen
2017-09-25 18:46   ` Emanuel Berg
2017-09-25 19:32     ` Eric Abrahamsen
2017-09-25 21:39       ` Emanuel Berg [this message]
2017-10-01  4:42   ` Emanuel Berg
2017-10-01 13:07     ` Emanuel Berg
2017-09-25 15:38 ` Eric Abrahamsen
2017-09-25 18:46   ` Emanuel Berg
2017-09-26 14:55   ` Harry Putnam
2017-09-26 16:53     ` Eric Abrahamsen
2017-09-26 17:19       ` Adam Sjøgren
2017-09-26 19:46         ` Eric Abrahamsen

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=86mv5i31c2.fsf@zoho.com \
    --to=moasen@zoho.com \
    --cc=ding@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.
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).