From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: smtpmail and ~/.authinfo
Date: Sun, 25 Sep 2011 08:48:07 -0400 [thread overview]
Message-ID: <E1R7o7r-0007ZY-Uv@fencepost.gnu.org> (raw)
In-Reply-To: <87litc7qen.fsf@lifelogs.com> (message from Ted Zlatanov on Sun, 25 Sep 2011 07:33:20 -0500)
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Sun, 25 Sep 2011 07:33:20 -0500
> Reply-To: emacs-devel@gnu.org
>
> Thus the Emacs format is backwards compatible but older netrc consumers
> can't necessarily read our tokens, so I think it's OK that we go further
> and explicitly allow Unicode characters through UTF-8. Would it make
> sense, then, to explicitly use utf-8 or auto-guess for the encoding
> instead of raw-text?
Only if either (a) we encode the responses we send to the SMTP server
during handshake, or (b) SMTP servers support UTF-8 encoding in the
strings they expect to receive.
Lars said "encoding is local", which suggest that neither of the above
is true. raw-text leaves the byte stream unchanged, and only converts
the EOL, so a netrc file encoded in some locale-specific way has a
better chance with SMTP servers from the same locale.
IOW, to answer your question, someone who knows more than I do about
communications with SMTP servers should tell us how, if at all,
non-ASCII characters are supposed to be handled when communicating
with the server.
next prev parent reply other threads:[~2011-09-25 12:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 10:26 smtpmail and ~/.authinfo Eli Zaretskii
2011-08-21 4:39 ` Lars Magne Ingebrigtsen
2011-08-21 6:12 ` Eli Zaretskii
2011-08-21 19:25 ` Lars Magne Ingebrigtsen
2011-08-21 19:59 ` Eli Zaretskii
2011-08-21 20:17 ` Lars Magne Ingebrigtsen
2011-08-22 5:35 ` Eli Zaretskii
2011-09-10 19:01 ` Lars Magne Ingebrigtsen
2011-09-25 12:33 ` Ted Zlatanov
2011-09-25 12:48 ` Eli Zaretskii [this message]
2011-09-25 13:21 ` Ted Zlatanov
2011-09-25 17:08 ` Eli Zaretskii
2011-09-26 14:41 ` Ted Zlatanov
2011-09-26 16:18 ` Eli Zaretskii
2011-09-26 16:53 ` Ted Zlatanov
2011-09-26 17:15 ` Eli Zaretskii
2011-09-26 17:23 ` Eli Zaretskii
2011-09-26 17:31 ` Ted Zlatanov
2011-09-26 17:00 ` Stefan Monnier
2011-09-26 17:28 ` Ted Zlatanov
2011-09-26 21:27 ` Stefan Monnier
2011-09-26 18:04 ` Lars Magne Ingebrigtsen
2011-09-26 19:22 ` Ted Zlatanov
2011-09-26 19:30 ` Lars Magne Ingebrigtsen
2011-09-26 19:48 ` Ted Zlatanov
2011-09-26 21:31 ` Stefan Monnier
2011-09-26 21:43 ` Lars Magne Ingebrigtsen
2011-09-26 21:54 ` Ted Zlatanov
2011-09-27 4:07 ` Stephen J. Turnbull
2011-09-27 6:11 ` Lars Magne Ingebrigtsen
2011-09-27 10:29 ` Ted Zlatanov
2011-09-27 12:33 ` Stephen J. Turnbull
2011-09-27 20:15 ` Ted Zlatanov
2011-09-28 1:41 ` Stephen J. Turnbull
2011-09-28 8:38 ` Eli Zaretskii
2011-09-26 21:55 ` Ted Zlatanov
2011-09-27 2:57 ` Eli Zaretskii
2011-09-27 10:38 ` Ted Zlatanov
2011-09-27 11:31 ` Eli Zaretskii
2011-09-27 12:55 ` Stefan Monnier
2011-09-27 14:02 ` Jason Rumney
2011-09-26 19:34 ` Eli Zaretskii
2011-09-26 19:40 ` Ted Zlatanov
2011-09-27 2:51 ` Eli Zaretskii
2011-09-27 13:54 ` Jason Rumney
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=E1R7o7r-0007ZY-Uv@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).