Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Anyone using DCC to block spam? How to config Gnus based on X-DCC-* ?
Date: Sat, 12 Jan 2002 10:56:55 +0100	[thread overview]
Message-ID: <vaf8zb3evtk.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87advkpu46.fsf@thanatos.shenton.org> (Chris Shenton's message of "11 Jan 2002 14:26:01 -0500")

Chris Shenton <chris@shenton.org> writes:

> More immediately is how to examine the entire header, even though it
> runs across multiple lines.  Or is Gnus smart enough to grab the
> entire header somewhere I can play with it? 

Gnus converts each header to a single line before
nnmail-split-methods is invoked.  So ".*" does what you need.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



  reply	other threads:[~2002-01-12  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 19:18 Agent as cache ShengHuo ZHU
2002-01-10 21:02 ` Bjørn Mork
2002-01-11  2:47   ` ShengHuo ZHU
2002-01-11  2:10 ` Harry Putnam
2002-01-11  2:36   ` ShengHuo ZHU
2002-01-11  8:53     ` Kai Großjohann
2002-01-11 15:28       ` ShengHuo ZHU
2002-01-11 18:10         ` Kai Großjohann
2002-01-12  1:49           ` Harry Putnam
2002-01-11 19:26 ` Anyone using DCC to block spam? How to config Gnus based on X-DCC-* ? Chris Shenton
2002-01-12  9:56   ` Kai Großjohann [this message]
2002-01-12 15:33     ` Chris Shenton
     [not found]       ` <86ofjyx0hf.fsf@duchess.twilley.org>
2002-01-15  1:23         ` Howto on using DCC with qmail and Gnus [was: Anyone using DCC to block spam? How to config Gnus based on X-DCC-* ?] Chris Shenton
2002-01-12 13:13   ` Anyone using DCC to block spam? How to config Gnus based on X-DCC-* ? Daniel Pittman

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=vaf8zb3evtk.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).