From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: proper hook for message body transform?
Date: Mon, 12 Sep 2011 08:56:31 +0200 [thread overview]
Message-ID: <87hb4iw8o0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87d3f96f0h.fsf@ericabrahamsen.net>
On Fri, Sep 09 2011, Eric Abrahamsen wrote:
> On Fri, Sep 09 2011, Leo wrote:
>> Put a new header name (e.g. X-Org-Tags) in message-default-headers. Add
>> a message-send-hook that does whatever you want to do.
>
> Yes! I had the same idea, but it seemed conceptually wrong -- this
> information is never leaving my local machine, and no mail servers or
> mail recipients would ever know what to do with such a header.
See `message-ignored-mail-headers´ and `message-ignored-news-headers´.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2011-09-12 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 11:35 Eric Abrahamsen
2011-09-09 11:46 ` Leo
2011-09-09 13:07 ` Eric Abrahamsen
2011-09-12 6:56 ` Reiner Steib [this message]
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=87hb4iw8o0.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).