From: Greg Stark <gsstark@MIT.EDU>
Subject: feature request: handle broken From headers that include signature
Date: 06 Jan 1996 23:01:42 -0500 [thread overview]
Message-ID: <9601071359.AA12136@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: craffert@sps.ml.com's message of Thu, 7 Dec 95 14:52:03 EST
There's a particular configuration error some people make that causes their
mailer to use their .signature file as their mail signature. That is, use
their 5+ line signature in the From header of their mail messages.
Gnus doesn't simplify the header in any way when this happens, it does
something like this:
+[ 26: --------------------] Cockatrices, Basilisks and other Gargoyle Manufacturers
From: ------------------------------------------------------------------------------ <name-witheld@MIT.EDU>
Obviously the best it can do is some kind of heuristic, but it seems like Gnus
should be able to tell at least sometimes that it's not looking at the
author's name. I would need to see a few more examples before I even had a
decent suggestion for what the heuristic should be.
--
greg
reply other threads:[~1996-01-07 4:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9601071359.AA12136@fierce-bad-rabbit.MIT.EDU \
--to=gsstark@mit.edu \
/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).