Hi,
I have to deal with email going through an Exchange server on
a daily basis. A few months back that server started mangling
email my email message content. I'm trying to use nmh to craft my
emails such that Exchange won't mangle it.
SOME BACKGROUND (skip to QUESTION, if you wish)
The
Hi,
I'm trying to get just a little better result in crafting a reply
draft message. I'm using Ken's very nice 'replyfilter' script and
recipe, which formats nearly all of the body of the message perfectly.
But, I still get a little cruft in the body, thus
On 15 August 2012 at 15:36,
On Thu, Aug 16, 2012 at 12:11 PM, Kevin Cosgrove kev...@cosgroves.us wrote:
Is there a better way to use mhn to unpack the attachments,
converting DOS form back to UNIX form? I suppose I could write a
shell script to alter the files after mhn unpacks them.
It doesn't fix the actual problem,
On 16 August 2012 at 12:55, Howard Bampton howard.bamp...@gmail.com wrote:
On Thu, Aug 16, 2012 at 12:11 PM, Kevin Cosgrove kev...@cosgroves.us wrote:
Is there a better way to use mhn to unpack the attachments,
converting DOS form back to UNIX form? I suppose I could write a
shell
send(1) says that when constructing the headers for the BCC recipient,
that it:
Prior to sending the message, the fields From: user@local, and
Date: now will be appended to the headers in the message. If the
environment variable $SIGNATURE is set, then its value
Michael wrote:
send(1) says that when constructing the headers for the
BCC recipient, that it:
Prior to sending the message, the fields From:
user@local, and Date: now will be appended to the
headers in the message. If the environment variable
$SIGNATURE is set, then its value is used as
Kevin wrote:
I'm trying to use nmh to craft my emails such that
Exchange won't mangle it.
Good luck with that :-/ I've given up, I've found Exchange
to be unpredictable.
Is there a better way to use mhn to unpack the
attachments, converting DOS form back to UNIX form? I
suppose I could
On 2012-08-16, at 17:38 PM, David Levine wrote:
I think that's the best way to handle it. Howard mentioned
dos2unix, which I use also.
tr -d \015
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Nmh-workers mailing list
On Thu, 16 Aug 2012 18:37:17 -0700, Lyndon Nerenberg said:
tr -d \015
Almost, but not quite correct.
Unfortunately, that will corrupt a file that happened to have a bare
carriage-return
character that wasn't part of a CR/LF pair. (Of course, having such a character
embedded in the middle of
I'm running:
ii nmh 1.5-release-0.2
from debian wheezy. (testing)
David == David Levine levin...@acm.org writes:
David Prior to sending the message, the Date: now field will be
David appended to the headers in the message.
David With nmh
On 2012-08-16, at 19:03 PM, valdis.kletni...@vt.edu wrote:
Almost, but not quite correct.
Unfortunately, that will corrupt a file that happened to have a bare
carriage-return
character that wasn't part of a CR/LF pair. (Of course, having such a
character
embedded in the middle of a
Michael wrote:
I'm running:
ii nmh 1.5-release-0.2
from debian wheezy. (testing)
I don't do debian so I can't readily look at it. But
how could the send(1) man page be from 1.4?
Yeah, but that's *in* my Components... and it did use that for the
main
I wrote:
= MAIL FROM:sen...@example.com
= 250 2.1.0 sen...@example.com... Sender ok
and sure enough, the received bcc has that From:. If I add
a To: address, both have that From:, as I expect.
My sendmail adds those From: headers. Does (your) postfix?
Maybe we shouldn't rely on that?
13 matches
Mail list logo
