From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: gnus doesn't obey header settings.
Date: Tue, 03 Dec 2002 18:56:16 +0100 [thread overview]
Message-ID: <84smxf3s1r.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <hhptsjrri7.fsf@blah.pl>
Maciej Matysiak <phoner.ding@blah.pl> writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> What's your value for gnus-visible-headers and gnus-ignored-headers
>> now?
>
> `gnus-ignored-headers' is a variable declared in Lisp.
> -- loaded from "gnus-art"
>
> Value: "^Received:"
>
> Documentation:
> *All headers that start with this regexp will be hidden.
> This variable can also be a list of regexps of headers to be ignored.
> If `gnus-visible-headers' is non-nil, this variable will be ignored.
>
> despite the setting, gnus shows the received headers in articles.
Hm. What happens when you type `t' on a message? Does that make the
headers go away? And does another `t' bring them back?
>> I have a setting for gnus-visible-headers and gnus-sorted-header-list.
>> This appears to work.
>
> well, i must have really bad luck then.
>
> btw., you don't set the "mail-followup-to" header, do you really want to
> get a copy of reply to your mails?
Eek. I'm reading this via the news group on quimby. Hm. Do I have
an MCT header? Maybe the gateway should convert betwene MCT and MFT?
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-03 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 21:33 Maciej Matysiak
2002-12-03 3:10 ` Jesper Harder
2002-12-03 7:28 ` Kai Großjohann
2002-12-03 14:19 ` Maciej Matysiak
2002-12-03 15:37 ` Kai Großjohann
2002-12-03 16:34 ` Maciej Matysiak
2002-12-03 17:56 ` Kai Großjohann [this message]
2002-12-03 21:58 ` Josh Huber
2003-01-23 22:54 ` Paul Jarc
2003-01-24 6:43 ` Vasily Korytov
2003-01-24 21:19 ` Paul Jarc
2002-12-03 18:04 ` Jesper Harder
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=84smxf3s1r.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.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).