Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: feature request: work around b0rked Pegasus Mail headers
Date: Sun, 25 Jun 2006 14:17:44 +0200	[thread overview]
Message-ID: <v9ac81zaxj.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3veqp1sax.fsf@merlin.emma.line.org>

On Sun, Jun 25 2006, Matthias Andree wrote:

> If I understand this correctly, it is laundering incoming messages that
> are being moved via the mailsource to the final location; 

Yes.

> however, my system presorts messages with maildrop and
> .forward+... files, 

I don't know maildrop, but maybe it'd  `ignore-broken-references'

> thus the "ignoring of broken references" needs to be done when the
> Group buffer is assembled and not as incoming messages are sorted.

I couldn't quickly locate the right place where this could be done
(probably you'd need to add In-Reply-To to `gnus-extra-headers').
Anyone?

> BTW, is the regexp (...broken-references-mailers) case sensitive?
> Pegasus uses "X-mailer: Pegasus ..." with lower-case m (but testing with
> upper-case M in an existing IMAP folder doesn't help either).

'nnmail-prepare-incoming-header-hook' is called with
`case-fold-search' bound to t in `nnmail-process-unix-mail-format'
(and other places).  So it's not treated case sensitively.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2006-06-25 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 11:23 Matthias Andree
2006-06-20 13:32 ` Reiner Steib
2006-06-22  9:17   ` Reiner Steib
2006-06-25  9:46     ` Matthias Andree
2006-06-25 12:17       ` Reiner Steib [this message]
2006-06-25 13:48         ` Reiner Steib
2006-06-25 17:29           ` Matthias Andree

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=v9ac81zaxj.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.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).