This is the conduit by which you get header fields into
mh-invisible-header-fields-default. For every header field you submit,
please include the name of the software package that generates it, if
known.
Here's mine. No idea where these things came from, though some are kind of obvious:
"Accreditor:"
"Comment:"
"Followups-To:"
"DomainKey-Status:"
"DKIM-Signature:"
"Organization:"
"Seal-Send-Time:"
"User-Agent:"
"Authentication-Results:"
"Received-SPF:"
"X-"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This might be a simple opportunity for me to figure out how to make commits to MH-E now that it's part of Emacs. I'm not sure that I have made a single commit since the move!
Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Opps. That was a cut/paste error. I meant simply that "reply-to" is a header that we don't want to hide. The "Delivered-To" was added there by accident.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i think RFC822 is case-insensitive (though it's been a long time since i've looked at the spec), so i think Delivered-To == delivered-to == (all the other possibilities). my parenthetical comment was that the listing you see when you use "customize-variable" is sorted (which is good) but in a case-sensitive way (which makes it hard to have *my* list and the variable list in the same order).
cheers, Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Greg, I bought all of yours except Comments, Organization, Reply-To,
Sender, User-Agent, X-Mailer. I also just filtered out the entire
class of X-HPL-, X-J2-, X-IronPort- fields. Your suggestion about
using a case-insensitive sort is a good one and I've added a note
about setting sort-fold-case to t before sorting.
Peter, I bought all yours. Sorry :-).
Mike, I bought all of your except for the ones where you said that
they might be list-specific. If it turns out that these messages are
software-specific (and therefore apply to lists in general), then we
can put them in. Also, you used "fully-qualified" field names in most
cases (ending with colon). I'm assuming in the other cases, you meant
to eradicate a whole class of fields. Please review them and let me
know if any of them are really fully-qualified and were missing the
colon by accident.
Thanks for the feedback, all!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1722009
Originator: NO
Here's mine. No idea where these things came from, though some are kind of obvious:
"Accreditor:"
"Comment:"
"Followups-To:"
"DomainKey-Status:"
"DKIM-Signature:"
"Organization:"
"Seal-Send-Time:"
"User-Agent:"
"Authentication-Results:"
"Received-SPF:"
"X-"
Logged In: YES
user_id=93690
Originator: YES
Thanks for the input! I added all but the following:
Comment, DomainKey-Status, DKIM-Signature, Authentication-Results,
Received-SPF: We already ignore these :-). I really have to release
8.1!!!
Followups-To: We already ignore "Followup-To:". An ephemeral typo?
Organization: Some of us like to see this.
User-Agent: We display this along with X-Mailer.
X-: That's a bit aggressive :-).
Logged In: YES
user_id=1953169
Originator: NO
(by the way, MH Invisible Header Fields Default in Customize -- it might be nice if it were sorted case independent.)
here are mine:
accept-language
acceptlanguage
comments
delivered-to
msgid
organization
reply-to
sender
user-agent
x-dcc-usenix-metrics
x-hpl-mailscanner
x-hpl-mailscanner-from
X-ISI-4-30-3-MailScanner
x-j2-accounttype
x-j2-caller-id
x-j2-customerkey
x-j2-fax-bps
x-j2-fax-csid-remote
x-j2-fax-mode
x-j2-fax-pages
x-j2-header-version
x-j2-message-date
x-j2-message-duration
x-j2-message-format
x-j2-message-size
x-j2-message-type
x-j2-phone-number
x-j2-servicekey
x-j2-servicetype
x-mailer
x-organization
x-originalarrivaltime
x-proofpoint-spam-details
x-proofpoint-virus-version
x-pstn-addresses
x-pstn-levels
x-pstn-neptune
x-pstn-settings
X-Sun-Charset
Logged In: YES
user_id=31877
Originator: NO
I don't think that we want to exclude by default:
organization
reply-toDelivered-To:
X-Mailer
But "delivered-to" is basically the same as "Delivered-To:". I'm surprised that the matches are case-sensitive. Maybe that should be changed.
Lately I have been seeing:
X-SBRS:
X-IronPort-Anti-Spam-Filtered:
X-IronPort-Anti-Spam-Result:
This might be a simple opportunity for me to figure out how to make commits to MH-E now that it's part of Emacs. I'm not sure that I have made a single commit since the move!
Peter
Logged In: YES
user_id=31877
Originator: NO
> reply-toDelivered-To:
Opps. That was a cut/paste error. I meant simply that "reply-to" is a header that we don't want to hide. The "Delivered-To" was added there by accident.
Logged In: YES
user_id=1953169
Originator: NO
i think RFC822 is case-insensitive (though it's been a long time since i've looked at the spec), so i think Delivered-To == delivered-to == (all the other possibilities). my parenthetical comment was that the listing you see when you use "customize-variable" is sorted (which is good) but in a case-sensitive way (which makes it hard to have *my* list and the variable list in the same order).
cheers, Greg
Logged In: YES
user_id=574173
Originator: NO
Here are my entries in mh-invisible-header-fields. I don't know where
most of them come from, but I've commented a couple of them.
"Campaign-Id:" ; list-specific? a charity that I belong to?
"DKIM-Signature"
"DomainKey-Signature:"
"Received-SPF:"
"Thread-index:"
"Thread-topic:"
"X-Authority-Analysis:"
"X-Brightmail-" ; Brightmail spam filtering software?
"X-Content-Filtered-By:"
"X-DCC-Usenix-Metrics:" ; USENIX mailing list?
"X-dedicated:"
"X-DH-Virus-"
"X-domain:"
"X-Echelon-distraction"
"X-eid"
"X-Envelope-From:"
"X-Google-Sender-Auth:"
"X-Greylist:"
"X-HR-"
"X-IronPort"
"X-key:"
"X-MDaemon-Deliver-To:"
"X-MDRemoteIP:"
"X-message-type:"
"X-ORBL:"
"X-pid"
"X-PMX-Version:"
"X-pstn-"
"X-service-code:"
"X-Virus-"
"X-Xerox-" ; list- specific?
"X-Yahoo-Newman-")
Logged In: YES
user_id=93690
Originator: YES
Bumped priority to make this item easier to find.
Greg, I bought all of yours except Comments, Organization, Reply-To,
Sender, User-Agent, X-Mailer. I also just filtered out the entire
class of X-HPL-, X-J2-, X-IronPort- fields. Your suggestion about
using a case-insensitive sort is a good one and I've added a note
about setting sort-fold-case to t before sorting.
Peter, I bought all yours. Sorry :-).
Mike, I bought all of your except for the ones where you said that
they might be list-specific. If it turns out that these messages are
software-specific (and therefore apply to lists in general), then we
can put them in. Also, you used "fully-qualified" field names in most
cases (ending with colon). I'm assuming in the other cases, you meant
to eradicate a whole class of fields. Please review them and let me
know if any of them are really fully-qualified and were missing the
colon by accident.
Thanks for the feedback, all!
Logged In: YES
user_id=574173
Originator: NO
These 3 should be fully qualified (good catch, Bill):
DKIM-Signature
X-eid
X-pid
The other not-fully-qualified fields that I submitted should remain so.
Here are some more headers not hidden by 8.1:
"X-Authentication-Info:" ;verizon.net?
"X-Generated-By:" ;launchpad.net
"X-Junkmail-" ;RCN?
"X-Launchpad-" ;launchpad.net
Making this item very, very visible so that it can be addressed at every release.
Here are some Facebook header fields:
X-Facebook:
X-Facebook-Notify:
X-FACEBOOK-PRIORITY:
Here are a handful that I've accumulated over the years. I'll try to find their source before adding them.
X-Bayes-Prob: ; IEEE spam filter
X-CanIt-Geo: ; IEEE spam filter
X-IEEE-UCE- ; IEEE spam filter
X-Oracle-Calendar:
X-Policyd-Weight:
X-AnalysisOut:
X-Spam:
X-MXL-Hash:
Accept-Language:
X-Auto-Response-Suppress:
X-Proofpoint- ; Proofpoint email security
X-Jira-Fingerprint: ; JIRA
X-Ymail-Osg:
DKIM-Signature:
Here are the header fields from Google+ circle invites:
X-Forwarded-To:
X-Forwarded-For:
X-Notifications:
X-Notification-ID:
X-Sender-ID:
X-Notification-Category:
X-Notification-Type:
Here's one from Nick Dokos' messages:
X-Headers-End:
revno: 106737
committer: Bill Wohler <wohler@newt.com>
branch nick: mh-e
timestamp: Tue 2011-12-27 11:22:23 -0800
message:
* mh-e.el (mh-invisible-header-fields-internal): Add X-AnalysisOut,
X-Authentication-Info, X-Auto-Response-Suppress, X-Bayes-Prob, X-Cam-,
X-CanIt-Geo, X-Completed, X-Facebook, X-Forwarded-, X-Generated-By,
X-Headers-End, X-IEEE-UCE, X-Jira-Fingerprint, X-Junkmail-,
X-Launchpad-, X-MXL-Hash, X-Notification-, X-Notifications,
X-Oracle-Calendar. Replace X-DCC-Usenix-Metrics with X-DCC- (addresses
SF #1916032).
modified:
lisp/mh-e/ChangeLog
lisp/mh-e/mh-e.el