From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: feature request: work around b0rked Pegasus Mail headers
Date: Tue, 20 Jun 2006 15:32:27 +0200 [thread overview]
Message-ID: <v9veqw0x78.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3slm59we9.fsf@merlin.emma.line.org>
On Fri, Jun 16 2006, Matthias Andree wrote:
> Pegasus Mail (a popular Window$ mail software) has, among others, for a
> long time up to and including the current 4.31 version, generated
> improper headers on replies; replying to a message with (header #1)
>
> Message-ID: <foo@example.org>
> References: <bar@example.org>
>
> It would generate (header #2):
>
> Message-ID: <new@example.org>
> References: <bar@example.org>
> In-Reply-To: <foo@example.org>
>
> Where the direct reference was missing from References.
> This causes Gnus to attach Pegasus Mail replies too early in the threads
> (of, for instance, mailing lists).
>
> May I suggest to change Gnus in a way that it checks if the In-Reply-To
> ID is present in References: and if it's not, internally treat header #2
> as though it had contained References: <bar@example.org> <foo@example.org>
> to ensure proper threading?
I think this could be done similar to `nnmail-fix-eudora-headers':
,----[ (info "(gnus)Washing Mail") ]
| `nnmail-fix-eudora-headers'
| Eudora produces broken `References' headers, but OK
| `In-Reply-To' headers. This function will get rid of the
| `References' headers.
`----
Would doing the same for Pegasus be sufficient? Could you please
provide some sample headers (including X-Mailer or User-Agent,
Reply-To and References) for such articles?
Would someone like to work on `nnmail-fix-pegasus-headers'?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-06-20 13:32 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 [this message]
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
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=v9veqw0x78.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).