Gnus development mailing list
 help / color / mirror / Atom feed
From: davidk@lysator.liu.se (David Kågedal)
Subject: Re: resending message & adding new headers
Date: 23 Feb 1999 18:02:03 +0100	[thread overview]
Message-ID: <jpr9rhuk8k.fsf@sanna.lysator.liu.se> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Feb 1999 22:09:40 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> 
> > when resending a message which does not contain MIME-Version and
> > Content-Type headers, gnus seems to add them. Is this correct?
> 
> Hm.  Well...  Er.  I'm not sure.  :-)

On a related note, I have lots of trouble moderating a
SmartList-managed mailing list.

What happens is that I get the mail for approval. I should then add an
"Approved:" header and resend it to the list.

My first way of doing it has been to hit 'e', add the header manually,
mark the whole buffer and then do a shell-command-on-region, invoking
sendmail.

My next approach to make life easier for me was to write a little
script that added the header and use '|' to pipe the mail through it.

But alas!  The mail being resent is not the same as the one I got.
For text/plain mails it doesn't matter, but for multipart/* what gets
sent is simply what I was seeing in by *Article* buffer, which can be
something much less that the whole message.

How do I get to the raw message?

(pgnus 0.66)

-- 
David Kågedal        <davidk@lysator.liu.se> http://www.lysator.liu.se/~davidk/


  reply	other threads:[~1999-02-23 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-31 18:32 Vladimir Volovich
1999-02-01 21:09 ` Lars Magne Ingebrigtsen
1999-02-23 17:02   ` David Kågedal [this message]
1999-02-23 17:16     ` Kai.Grossjohann
1999-02-24 14:16       ` David Kågedal
1999-02-23 19:25     ` Jason L Tibbitts III
1999-02-23 21:07       ` Justin Sheehy
1999-02-23 21:25         ` Hrvoje Niksic
1999-02-23 22:31           ` Justin Sheehy

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=jpr9rhuk8k.fsf@sanna.lysator.liu.se \
    --to=davidk@lysator.liu.se \
    /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).