Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: nnmail-pop-password, and nnheader-temp-write
Date: 18 Jun 1999 12:51:58 +0200	[thread overview]
Message-ID: <vafogid233l.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Shaun Lipscombe's message of "18 Jun 1999 09:56:32 +0100"

Shaun Lipscombe <shaun.lipscombe@gasops.co.uk> writes:

  > [...] Is there a way (yet) to insert file contents into arbitrary
  > headers?

Does this work?

(defun my-message-header-hook ()
  (save-excursion
    (goto-char (point-min))
    (insert-file-contents "/tmp/foo")))
(add-hook 'message-header-hook 'my-message-header-hook)

  > Once I get this sorted, I'll be fully pgnus, instead of using it just
  > for MIME.

The above ought to work for many different Gnusae, I can't see why it
would be different for Gnus 5.6 versus pgnus, say.

kai
-- 
Life is hard and then you die.


  reply	other threads:[~1999-06-18 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-17 16:43 Shaun Lipscombe
1999-06-17 17:11 ` Shaun Lipscombe
1999-06-18  2:51 ` Stainless Steel Rat
1999-06-18  8:56   ` Shaun Lipscombe
1999-06-18 10:51     ` Kai.Grossjohann [this message]
1999-06-21 14:53       ` Shaun Lipscombe

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=vafogid233l.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).