From: Dmitry Alexandrov <321942@gmail.com>
To: xiewensheng@gmail.com
Cc: info-gnus-english@gnu.org
Subject: Re: smtp outlook.com
Date: Thu, 30 Jun 2016 23:28:23 +0300 [thread overview]
Message-ID: <87r3beh15k.fsf@gmail.com> (raw)
In-Reply-To: <81f7ba65-0b7d-4412-8ec1-026c3fd31c5a@googlegroups.com> (xiewensheng's message of "Thu, 30 Jun 2016 00:37:34 -0700 (PDT)")
xiewensheng@gmail.com writes:
> Hi, I have similar problem.
> Fetching imap email is ok, but sending smtp email is not.
>
> I am working under windows + Emacs/gnus + gnutls.
>
> Have you solved the problem?
Well, I’ve got a registration at outlook.com purposefully to test it
with Gnus — and it just works with no problem. I’ve used the following
configuration:
--8<---------------cut here---------------start------------->8---
(setq send-mail-function 'smtpmail-send-it
message-send-mail-function send-mail-function
smtpmail-default-smtp-server "smtp-mail.outlook.com"
smtpmail-smtp-service 587
smtpmail-smtp-user "example@outlook.com")
--8<---------------cut here---------------end--------------->8---
and the following .authinfo:
--8<---------------cut here---------------start------------->8---
machine smtp-mail.outlook.com login example@outlook.com password eXamp1e port 587
--8<---------------cut here---------------end--------------->8---
Debian GNU/Linux Jessie, GnuTLS 3.3.8, GNU Emacs 25.1.50.
However, it was enough to send two letters through this SMTP server to
get enough experience to never deal with it again. Look:
— It adds erroneous headers, for example ‘Content-Language: en-US’,
while my test message was not in English.
— It does not allow you to write anything to ‘From’ header even outside
of angle brackets, e. g. I am not allowed to write my name as ‘Дмитрий
Александров <example@outlook.com>’ — it would be silently rewritten
with ‘Dmitry Alexandrov <example@outlook.com>’.
— It rewrites ‘Message-ID’, which means that unambiguous link between you
letter and replies to it would be lost for your MUA (if only you do
not ‘Bcc’ all outcoming mail to yourself).
— It just throw out useful headers, in particular ‘Mail-Followup-To’
and ‘Mail-Copies-To’.
As a bonus, it adds lots of weird headers and re-encodes the body of
message — both charset and transfer encoding: I’ve send a letter with
‘charset="utf-8"’ and received with ‘charset="iso-8859-1"’, I’ve send a
letter in ‘8bit’ encoding and received it in ‘base64’.
Any of listed ‘features’ on its own should be enough to not to use that
piece of Microsoft crap. Thus, I would just advice you choose another
SMTP server that does not break you mail.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2016-06-30 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 5:49 Zaam Wu
2016-02-15 8:10 ` Lars Ingebrigtsen
2016-02-15 9:00 ` Zaam Wu
2016-02-15 9:07 ` Lars Ingebrigtsen
2016-02-15 9:30 ` Zaam Wu
2016-02-15 9:46 ` Zaam Wu
2016-06-30 7:37 ` xiewensheng
2016-06-30 20:28 ` Dmitry Alexandrov [this message]
[not found] ` <mailman.344.1467318506.26859.info-gnus-english@gnu.org>
2016-07-01 5:32 ` xiewensheng
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=87r3beh15k.fsf@gmail.com \
--to=321942@gmail.com \
--cc=info-gnus-english@gnu.org \
--cc=xiewensheng@gmail.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).