From: Xavier Maillard <zedek@gnu-rox.org>
Subject: smtpmail.el oddities
Date: Fri, 04 Feb 2005 15:24:15 +0100 [thread overview]
Message-ID: <plop87wtto5row.fsf@gnu-rox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Hello,
I already talked about this problem.
It occurs I can't send mail using smtpmail.el package when I am
using a WiFi connection.
I don't really see what the problem is.
The trace goes well until the 'QUIT' command but no answer is
emitted by the SMTP server whereas when using a cable connection,
the server is well answering a 221 bye command.
Please, can someone explain me what can be the spin here because
I really can't live that way.
For the pessimistic, I tested I could send mail using either WiFi
or Cable using two other tools:
1. telnet
2. mutt
All went well so I really suspect something in smtpmail but don't
have the clue to prove anything...
--
Xavier Maillard, zedek@gnu-rox.org
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2005-02-04 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 14:24 Xavier Maillard [this message]
2005-02-05 18:07 ` Xavier Maillard
2005-02-09 22:43 ` [SOLVED] (was: smtpmail.el oddities) Xavier Maillard
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=plop87wtto5row.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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.
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).