Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

2015-03-02 Thread Bob Carragher
The saga is not yet over. One domain in particular, @stanford.edu, is now tagging my emails even more strongly as spam. I'm seeing replies from folks there with the Subject: line changed to: Re: [SPAM:#] original-subject with the number of #s indicating how strongly the tagging is.

Re: [Nmh-workers] Default setup broken on Debian?

2015-03-02 Thread Conrad Hughes
Ken MessageName is totally documented in mhl(1) Oops; I was looking in mh-format(5). Ken I can't speak for anyone else ... but at least for me, I've found that Ken the text parts are ones I want to see, and non-text parts? Yeah I'm curious about non-text options though. When I ssh in from my

Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

2015-03-02 Thread Ken Hornstein
There are three occurrences of the following, associated with Received: entries, in the header: (No client certificate requested) I'm guessing that those are harmless. Yeah, I suspect that's from a TLS connection between client and server, and the client didn't provide a certificate which

Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

2015-03-02 Thread Ken Hornstein
Re: [SPAM:#] original-subject with the number of #s indicating how strongly the tagging is. (This had happened previously, but the number of #s never exceeded 3.) Also, their list servers are now silently rejecting my posts, whereas that had never occurred previously. (If I switch back

Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

2015-03-02 Thread Bob Carragher
On Mon, 02 Mar 2015 20:57:10 -0500 Ken Hornstein k...@pobox.com sez: Re: [SPAM:#] original-subject with the number of #s indicating how strongly the tagging is. (This had happened previously, but the number of #s never exceeded 3.) Also, their list servers are now silently

Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

2015-03-02 Thread Bob Carragher
On Mon, 02 Mar 2015 22:19:42 -0500 Ken Hornstein k...@pobox.com sez: There are three occurrences of the following, associated with Received: entries, in the header: (No client certificate requested) I'm guessing that those are harmless. Yeah, I suspect that's from a TLS connection

[Nmh-workers] Default setup broken on Debian?

2015-03-02 Thread Conrad Hughes
Hi there, Short version: - How do I get a canonical good inline-everything-into-the-pager version of mhn.defaults for Nmh 1.6? Debian's version sends everything (although sometimes there's no-such-file, causing failures) to GUI helper applications, which feels like something of

Re: [Nmh-workers] Default setup broken on Debian?

2015-03-02 Thread Ken Hornstein
I'm having some trouble with the default setup of nmh 1.6-2 on Debian, upgrading from 1.5-release-0.2 (i.e. switching from wheezy to jessie). Where previously show'ing an email with HTML and text would bring up something in a pager in my terminal window, I'm now getting a range of behaviours, from

Re: [Nmh-workers] Default setup broken on Debian?

2015-03-02 Thread Conrad Hughes
Ken BEFORE 1.6 it certainly wouldn't do that out of the box. Er I think the key word there was that it'd bring up something in a pager. Not necessarily something useful, but it was less aggravating than throwing up a new window for every message part in the 100 emails I was skimming :-/ I had