From: "Vida Gábor" <vidagabor@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7589@debbugs.gnu.org
Subject: bug#7589: smtpmail: bad line endings in queued mails on Windows
Date: Sun, 12 Dec 2010 20:40:45 +0100 [thread overview]
Message-ID: <kod0d3p6230i.fsf@gmail.com> (raw)
In-Reply-To: <83d3p8vd04.fsf@gnu.org>
Hi Eli!
The correction works fine now according to the SMTP trace. Tomorrow I
will try it with an Exchange server (Postfix eated the previous, invalid
^M^M line ending), and notify you about the result, but I'm sure there
won't be any problem).
Thanks and regards,
Gábor
next prev parent reply other threads:[~2010-12-12 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 23:26 bug#7589: smtpmail: bad line endings in queued mails on Windows Vida Gábor
2010-12-10 14:36 ` Eli Zaretskii
2010-12-11 9:43 ` Vida Gábor
2010-12-11 10:07 ` Eli Zaretskii
2010-12-12 19:40 ` Vida Gábor [this message]
2010-12-12 20:12 ` Eli Zaretskii
2010-12-13 8:59 ` Vida Gábor
2010-12-13 15:13 ` Eli Zaretskii
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=kod0d3p6230i.fsf@gmail.com \
--to=vidagabor@gmail.com \
--cc=7589@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).