Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
On 17 March 2015 at 11:05, Ken Hornstein k...@pobox.com wrote: When instead it should have really been $htmlconv[0]. So you need to install w3m? Or change @htmlconv. I installed w3m and replyfilter succeeds. Great! I've fixed that on master. Wow. If all software could be fixed that easily quickly, I wonder what the technical world would be like. I've run into 5-6 open source, and 2-3 commercial, projects with this kind of responsiveness. Thanks again... -- Kevin ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
On 16 March 2015 at 23:32, Ken Hornstein k...@pobox.com wrote: In my OP I left out the fact that I have par installed, AND replyfilter works on all of my email replies except for those from the XFINITY mobile app. Whoops, that's a bug in replyfilter; specifically, the error message is: exec (@conv) || die Unable to exec $filterprogram: $!\n; When instead it should have really been $htmlconv[0]. So you need to install w3m? Or change @htmlconv. I installed w3m and replyfilter succeeds. Thanks Ken! -- Kevin ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
When instead it should have really been $htmlconv[0]. So you need to install w3m? Or change @htmlconv. I installed w3m and replyfilter succeeds. Great! I've fixed that on master. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
Wow. If all software could be fixed that easily quickly, I wonder what the technical world would be like. I've run into 5-6 open source, and 2-3 commercial, projects with this kind of responsiveness. Well I had a free moment and I wanted to take care of it before I forgot. And it was easy. Other stuff ... has been lingering. I wish we could do that for everything, but we all have to put food on the table. Historically ... nmh 1.3 was released in June 2008, nmh 1.4 was January 2012, nmh 1.5 was in June 2012, and nmh 1.6 was in June 2014. Not bad compared to other volunteer open-source projects, but room for improvement. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
On 17 March 2015 at 11:28, Ken Hornstein k...@pobox.com wrote: Well I had a free moment and I wanted to take care of it before I forgot. And it was easy. Other stuff ... has been lingering. I wish we could do that for everything, but we all have to put food on the table. I'm glad the timing worked out. Enjoy the meal. ;-) Historically ... nmh 1.3 was released in June 2008, nmh 1.4 was January 2012, nmh 1.5 was in June 2012, and nmh 1.6 was in June 2014. Not bad compared to other volunteer open-source projects, but room for improvement. [n]mh is still my favorite email client in combination with exmh, and I've tried a LOT of clients. I started with MH-3 from Rand. At some point I need to figure out some way to be mobile with nmh. Wmh demonstrates a possibility. See http://wmh.sourceforge.net/ The would seem to be room for an Android client, using exmh as a functional spec. Cheerio... -- Kevin ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
Kevin wrote: I get this message from the contributed replyfilter script Unable to exec par: No such file or directory HTML converter process exited with 2 You'll need to install par. It's available for some Linux distributions and Cygwin, at least. Source code is available from http://www.nicemice.net/par/. Alternatively, you could modify the script to use a different text formatter, or none at all. Another alternative, if you're using the latest nmh available from the git repo, would be to use repl's new convertargs support. The man page has details. It uses par if it was installed when nmh was installed. If not, if falls back to fmt(1), if that was installed. David ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
On 16 March 2015 at 22:59, David Levine levin...@acm.org wrote: Kevin wrote: I get this message from the contributed replyfilter script Unable to exec par: No such file or directory HTML converter process exited with 2 You'll need to install par. It's available for some Linux distributions and Cygwin, at least. Source code is available from http://www.nicemice.net/par/. In my OP I left out the fact that I have par installed, AND replyfilter works on all of my email replies except for those from the XFINITY mobile app. Thanks -- Kevin ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
[Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
Hi folks, I get this message from the contributed replyfilter script Unable to exec par: No such file or directory HTML converter process exited with 2 When I try to reply to a message containing === Date: Mon, 16 Mar 2015 23:22:44 + (UTC) From: badmess...@comcast.net To: kevin Message-ID: 1868643915.7062540.1426548164135.javamail.zim...@comcast.net Subject: Re: Please reply to this from your phone ... MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_Part_7062539_1892048492.1426548164135 X-Originating-IP: [:::69.252.207.145] Thread-Topic: Please reply to this from your phone ... Thread-Index: McPgm6x+IrIwPxqLZMhQE01Uv+WyJQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1426548164; bh=8RLwZ6xfKjgQ9buNk8RoZuz6D12XlAR2sB15Zl+OCio=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=Oq7hnL5ESX6d3sDn2juhMlGLQMKZxWWx8IDGI62pLSrJSOQFfuGJ5K2L+R0iV2cAQ T+9beXYw/mgKluBvNghypaHK7BtiuZ0x6HJCzsdwETEl0Jp0tT2miFK3GQ6fUnn4Vh oi4srjGKIQ1fZ2Wk76nHNftXG+s5n3ss4s5A3errktEz3IqMXSpn0k0oVCxNdEt3nE 8JFQNWp/0bJJeIey3ext8PnwC/lAaNxkjfX9ZtWMTNtrs6tlvUF7Awc4Bw+8lNJOnO cBu24jlM21OlR/2fIy/Pzze6YGjLY+mZxM2hhE3D8xhnhjihwCOrn/S2PKgmUmmI3m LCAIVXJXDguNg== --=_Part_7062539_1892048492.1426548164135 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Reply from my phone. brbrI didn't know I was getting garbled.brbrKbrbrbrSent from XFINITY Connect Mobile Appbr --=_Part_7062539_1892048492.1426548164135-- = Has anyone ran into this themselves? Or, does anyone have a debug pointer before I delve into the script? Thanks much... -- Kevin ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] replyfilter trouble with messages from XFINITY Connect Mobile App
In my OP I left out the fact that I have par installed, AND replyfilter works on all of my email replies except for those from the XFINITY mobile app. Whoops, that's a bug in replyfilter; specifically, the error message is: exec (@conv) || die Unable to exec $filterprogram: $!\n; When instead it should have really been $htmlconv[0]. So you need to install w3m? Or change @htmlconv. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
