From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: feature request: work around b0rked Pegasus Mail headers
Date: Sun, 25 Jun 2006 19:29:13 +0200 [thread overview]
Message-ID: <m3ac81m9ee.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <v9u069xs5w.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 25 Jun 2006 15:48:27 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Sun, Jun 25 2006, Reiner Steib wrote:
>
>> On Sun, Jun 25 2006, Matthias Andree wrote:
>>> however, my system presorts messages with maildrop and
>>> .forward+... files,
>>
>> I don't know maildrop, [...]
>
> ... but maybe it's possible to ignore the broken references on mail
> delivery? Using reformail?
Well, I don't plan to modify the messages, I just want Gnus to ignore
(or correct) broken references internally when threading.
--
Matthias Andree
prev parent reply other threads:[~2006-06-25 17:29 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
2006-06-25 13:48 ` Reiner Steib
2006-06-25 17:29 ` Matthias Andree [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=m3ac81m9ee.fsf@merlin.emma.line.org \
--to=matthias.andree@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).