From: David Abrahams <dave@boost-consulting.com>
Subject: Re: NTEmacs, smptpmail-queue-mail, and line-endings
Date: 06 Nov 2002 14:17:44 -0500 [thread overview]
Message-ID: <uheeucxt3.fsf@boost-consulting.com> (raw)
In-Reply-To: <ufzuekaqz.fsf@boost-consulting.com>
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
next prev parent reply other threads:[~2002-11-06 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 14:56 David Abrahams
2002-11-06 19:17 ` David Abrahams [this message]
2002-11-08 11:36 ` Kai Großjohann
2002-11-10 2:58 ` David Abrahams
2002-11-10 4:52 ` David Abrahams
2002-11-11 16:35 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uheeucxt3.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).