From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7789@debbugs.gnu.org
Subject: bug#7789: cannot send smtpmail using gmail & tls on woe32
Date: Fri, 7 Jan 2011 13:55:25 -0500 [thread overview]
Message-ID: <AANLkTinernXsaYPSyfCaj3aJmSdo4of8k7r9dN1F+=9x@mail.gmail.com> (raw)
In-Reply-To: <83r5cpkvkj.fsf@gnu.org>
On Fri, Jan 7, 2011 at 2:43 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 6 Jan 2011 18:13:40 -0500
>> From: Sam Steingold <sds@gnu.org>
>> Cc: jasonr@gnu.org, 7789@debbugs.gnu.org
>>
>> I am still having this problem (native bzr tip emacs; both cygwin &
>> mingw gnutls-cli).
>> any suggestions are welcome.
>
> You posted the contents of the trace buffer on Windows. What does
> that buffer show on Ubuntu, where you say it works? The differences
> might give a clue for what's wrong on Windows.
the major difference is the conspicuous presence of ^M ("\r") chars in
the smtp trace buffer on windows.
when I use cygwin gnutls-cli, _all_ lines contain it.
when I use the native port, only _some_ lines do.
I wonder if the unconditional setting of coding-system in smtpmail.el
is the culprit.
--
Sam Steingold <http://sds.podval.org>
next prev parent reply other threads:[~2011-01-07 18:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 15:05 bug#7789: cannot send smtpmail using gmail & tls on woe32 Sam Steingold
2011-01-05 16:16 ` Eli Zaretskii
2011-01-05 17:55 ` Sam Steingold
2011-01-05 20:06 ` Sam Steingold
2011-01-05 21:02 ` Eli Zaretskii
2011-06-26 1:52 ` Glenn Morris
2011-01-05 23:09 ` Jason Rumney
2011-01-05 23:31 ` Sam Steingold
2011-01-06 9:29 ` Eli Zaretskii
2011-01-06 23:13 ` Sam Steingold
2011-01-07 7:43 ` Eli Zaretskii
2011-01-07 18:55 ` Sam Steingold [this message]
2011-01-07 20:09 ` Eli Zaretskii
2011-01-17 8:09 ` Claudio Bley
2011-01-17 22:47 ` Eli Zaretskii
2011-01-18 15:33 ` Claudio Bley
2011-01-18 22:45 ` Eli Zaretskii
2011-01-21 14:32 ` Claudio Bley
2011-02-06 21:42 ` Claudio Bley
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinernXsaYPSyfCaj3aJmSdo4of8k7r9dN1F+=9x@mail.gmail.com' \
--to=sds@gnu.org \
--cc=7789@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).