Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: feature request: work around b0rked Pegasus Mail headers
Date: Sun, 25 Jun 2006 11:46:30 +0200	[thread overview]
Message-ID: <m3veqp1sax.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <v9mzc58s74.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 22 Jun 2006 11:17:51 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Tue, Jun 20 2006, Reiner Steib wrote:
>
>> 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'?
>
> Done:
>
> ,----[ lisp/ChangeLog ]
> | 	* nnmail.el (nnmail-broken-references-mailers): New variable.
> | 	(nnmail-ignore-broken-references): New function generalizing
> | 	nnmail-fix-eudora-headers.
> | 	(nnmail-fix-eudora-headers): Now obsolete.
> `----
>
> ,----[ (info "(gnus)Washing Mail") ]
> |     `nnmail-ignore-broken-references'
> |           Some mail user agents (e.g. Eudora and Pegasus) produces
> |           broken `References' headers, but correct `In-Reply-To'
> |           headers.  This function will get rid of the `References'
> |           header if the headers contain a line matching the regular
> |           expression `nnmail-broken-references-mailers'.
> `----
>
> I don't use nnmail-fix-eudora-headers/nnmail-ignore-broken-references
> so please test if it works correctly.

Hm - this appears to be limited in effect.

If I understand this correctly, it is laundering incoming messages that
are being moved via the mailsource to the final location; however, my
system presorts messages with maildrop and .forward+... files, thus the
"ignoring of broken references" needs to be done when the Group buffer
is assembled and not as incoming messages are sorted.

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).

-- 
Matthias Andree



  reply	other threads:[~2006-06-25  9:46 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 [this message]
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=m3veqp1sax.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).