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: Header Fields and Split Fancy
Date: 18 Apr 2000 12:57:27 +0200	[thread overview]
Message-ID: <vafvh1f3cdk.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Holger Sparr's message of "18 Apr 2000 12:00:39 +0200"

Holger Sparr <sparr@mfkrs1.mw.tu-dresden.de> writes:

> I tried to set up nnmail-split-fancy. I encountered a problem caused
> by the capitals in the header fields of my messages.

Did you really see a problem with these abbrevs, ie did you see wrong
splitting because of header case?

If so, then Gnus should set case-fold-search to t while matching the
header names.

kai
-- 
Beware of flying birch trees.



  reply	other threads:[~2000-04-18 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-18 10:00 Holger Sparr
2000-04-18 10:57 ` Kai Großjohann [this message]
2000-04-18 11:29   ` Holger Sparr
2000-04-19 13:36     ` Per Abrahamsen
2000-04-18 11:52 ` Kai Großjohann
2000-04-18 14:28   ` Holger Sparr
2000-04-18 14:43     ` Kai Großjohann
2000-04-19 13:34 ` Per Abrahamsen
2000-04-19 13:47   ` Karl Kleinpaste

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=vafvh1f3cdk.fsf@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).