NTEmacs, smtpmail-queue-mail, and line-endings

NTEmacs, smtpmail-queue-mail, and line-endings

[David Abrahams]

Hi,

I'm not sure I'm posting this to the right places, but I hope someone
here can help.

I'm using NTEmacs 21.2 with a very recent smtpmail.el (from GNU emacs
CVS, I think), and I'm setting smtpmail-queue-mail so that I don't
have to wait for the server each time I finish composing a message.

In order to get queueing to work, I had to set:

  (setq smtpmail-mail-address "dave@boost-consulting.com")

Which seems wrong because it isn't documented, but without it my
outgoing messages were being rejected as having no sender.

However, I've received a number of complaints from people I'm
corresponding with. For example, Microsoft Outlook users (I'm sure
some of you will say they deserve what they get, but I need to
correspond with them anyway) all say:

    Not sure what's up w/ your mailer.  All email from you has no
    subject, and the cc: line appears in the body.  On top of that,
    it's double spaced.

Other people simply never see my emails; presumably they're being
silently rejected by their server somewhere.

And some Linux users have problems, too (see bottom of this
message). The email looks fine to me on its way out; my best guess is
that the DOS '\r\n' line ending convention is messing things up. The
files stored in ~/Mail/queued-mail, waiting to go out. do indeed have
DOS line-endings.

Any clues about how to repair this would be much-appreciated!

TIA,
Dave

--


Dave,

My mail client fails to parse a lot of your mails headers. I think this is due 
to a blank line in the references section. See attached header for details. I 
am not a mail guru, but the blank line looks suspicious.

--Thomas

On Thursday 01 January 1970 00:59, you wrote:
> Return-Path:
> <sentto-4392937-2097-1036532252-witt=ive.uni-hannover.de@returns.groups.yah
>oo.com> X-Sieve: cmu-sieve 2.0
> Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3])
>         by mail.ive.uni-hannover.de (Postfix on SuSE Linux 7.2 (i386)) with
> ESMTP id 7843010910 for <witt@ive.uni-hannover.de>; Tue,  5 Nov 2002
> 23:06:26 +0100 (MET) Received: from n15.grp.scd.yahoo.com by
> mgate.uni-hannover.de
>           (PP) with SMTP; Tue, 5 Nov 2002 23:06:02 +0100
> X-eGroups-Return:
> sentto-4392937-2097-1036532252-witt=ive.uni-hannover.de@returns.groups.yaho
>o.com Received: from [66.218.67.200] by n15.grp.scd.yahoo.com with NNFMP; 05
> Nov 2002 21:37:32 -0000 X-Sender: dave@boost-consulting.com
> X-Apparently-To: jamboost@yahoogroups.com
> Received: (EGP: mail-8_2_3_0); 5 Nov 2002 21:37:30 -0000
> Received: (qmail 23018 invoked from network); 5 Nov 2002 21:37:30 -0000
> Received: from unknown (66.218.66.218)
>   by m8.grp.scd.yahoo.com with QMQP; 5 Nov 2002 21:37:30 -0000
> Received: from unknown (HELO smtp-hub2.mrf.mail.rcn.net) (207.172.4.76)
>   by mta3.grp.scd.yahoo.com with SMTP; 5 Nov 2002 21:37:30 -0000
> Received: from smtp03.mrf.mail.rcn.net ([207.172.4.62])
>         by smtp-hub2.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
>         id 189BO5-00001t-00
>         for jamboost@yahoogroups.com; Tue, 05 Nov 2002 16:37:29 -0500
> Received: from 146-115-123-43.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com
> ([146.115.123.43] helo=NEFARIOUS.boost-consulting.com) by
> smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
>         id 189BO5-0000D1-00
>         for jamboost@yahoogroups.com; Tue, 05 Nov 2002 16:37:29 -0500
> To: jamboost@yahoogroups.com
> References: <usmyfx44t.fsf@boost-consulting.com>
>
>         <uiszbvlbg.fsf@boost-consulting.com>
> In-Reply-To: <uiszbvlbg.fsf@boost-consulting.com>
> Message-ID: <uk7jrr9r8.fsf@boost-consulting.com>
> Lines: 43
> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
> From: David Abrahams <dave@boost-consulting.com>
> MIME-Version: 1.0
> Mailing-List: list jamboost@yahoogroups.com; contact
> jamboost-owner@yahoogroups.com Delivered-To: mailing list
> jamboost@yahoogroups.com
> Precedence: bulk
> List-Unsubscribe: <mailto:jamboost-unsubscribe@yahoogroups.com>
> Date: 05 Nov 2002 16:23:39 -0500
> Subject: Re: [jamboost] Re: Sane regression testing
> Reply-To: jamboost@yahoogroups.com
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit




-- 
                    David Abrahams
dave@boost-consulting.com * http://www.boost-consulting.com

Re: NTEmacs, smtpmail-queue-mail, and line-endings

[David Abrahams]

David Abrahams <dave@boost-consulting.com> writes:

> Hi,
> 
> I'm not sure I'm posting this to the right places, but I hope someone
> here can help.
> 
> I'm using NTEmacs 21.2 with a very recent smtpmail.el (from GNU emacs
> CVS, I think), and I'm setting smtpmail-queue-mail so that I don't
> have to wait for the server each time I finish composing a message.
> 
> In order to get queueing to work, I had to set:
> 
>   (setq smtpmail-mail-address "dave@boost-consulting.com")
> 
> Which seems wrong because it isn't documented, but without it my
> outgoing messages were being rejected as having no sender.
> 
> However, I've received a number of complaints from people I'm
> corresponding with. For example, Microsoft Outlook users (I'm sure
> some of you will say they deserve what they get, but I need to
> correspond with them anyway) all say:
> 
>     Not sure what's up w/ your mailer.  All email from you has no
>     subject, and the cc: line appears in the body.  On top of that,
>     it's double spaced.
> 
> Other people simply never see my emails; presumably they're being
> silently rejected by their server somewhere.
> 
> And some Linux users have problems, too (see bottom of this
> message). The email looks fine to me on its way out; my best guess is
> that the DOS '\r\n' line ending convention is messing things up. The
> files stored in ~/Mail/queued-mail, waiting to go out. do indeed have
> DOS line-endings.
> 
> Any clues about how to repair this would be much-appreciated!

One further piece of information: if I manually go into the
queued-mail/ folder and change the coding system in the messages to
'undecided-unix, people seem to get the right thing. I could probably
hack my smtpmail.el to do that for me at some point in the chain, but
I am a bit clueless about coding systems, so I'd have no idea if
that's really the right thing to do. In particular, it seems like it
could mess up embedded MIME attachments.

-- 
                    David Abrahams
dave@boost-consulting.com * http://www.boost-consulting.com