From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: hanging while sending mail
Date: Mon, 16 Feb 2004 09:15:16 +0100 [thread overview]
Message-ID: <87smhbv3sb.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <uhdxrlgnq.fsf@flash.net>
correira@flash.net (Alfred J Correira) writes:
> After poking around a bit in the code and
> reviewing the SMTP trace buffer ... I'm hanging
> at the end of smtpmail-via-smtp: the "QUIT" is
> sent and processed, but the succeeding call to
> smtpmail-read-response never returns (it just
> churns away in the while loop looking for a "\r\n"
> that it never receives): if I comment out that
> last call to smtpmail-read-response, of course,
> the delete-process at the end of smtpmail-via-smtp
> runs, I get my "done" and my Gcc copy, etc.. I
> suppose I can live with that, since I don't need
> the final return value from smtpmail-read-response
> and the delete-process should take care of any
> leftover output from the SMTP server, but ...
What happens when you speak SMTP manually, with telnet?
Kai
prev parent reply other threads:[~2004-02-16 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 5:47 Alfred J Correira
2004-02-16 8:15 ` Kai Grossjohann [this message]
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=87smhbv3sb.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).