From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Bizarre problem - lockup sending mail
Date: Fri, 27 Jun 2003 09:10:05 +0200 [thread overview]
Message-ID: <84vfusro6q.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <u1xxg8otk.fsf@swbell.net>
Peter Lee <pete_lee@swbell.net> writes:
> Once my smtp server identifies itself everything happens very quickly.
> For some reason after the initial connection is made the smtp server
> hangs for 3-4 mins... I did some testing via telnet as well and it
> was always within 3-4 mins. No idea what it's doing in that time, but
> in my case it looks like it's definitely the remote server as I first
> suspected.
Hm. So maybe what you want now is something that does the sending in
the background. People report that Hamster is a nice program. Its
main purpose is to act as a local NNTP server, but it also groks POP3
and SMTP I think. I guess that you can just tell Gnus to send mail
to Hamster and let it take care of sending the stuff out.
Another alternative might be to queue the mail using smtpmail.el,
maybe then you don't have to wait 3 mins for every mail. But maybe
you do.
--
~/.signature
next prev parent reply other threads:[~2003-06-27 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r85lvs74.fsf@arkenstone.demon.co.uk>
[not found] ` <844r2hdhzu.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <of0pn7hy.fsf@yahoo.co.uk>
[not found] ` <84of0pcm4o.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <smq078qr.fsf@yahoo.co.uk>
[not found] ` <ur85jwl2p.fsf@swbell.net>
2003-06-26 20:13 ` Paul Moore
[not found] ` <ptl0d3pk.fsf@yahoo.co.uk>
[not found] ` <ubrwkwnlp.fsf@swbell.net>
2003-06-26 22:17 ` Paul Moore
[not found] ` <u1xxg8otk.fsf@swbell.net>
2003-06-27 7:10 ` Kai Großjohann [this message]
2003-06-27 15:40 ` Peter Lee
[not found] ` <843chveavh.fsf@lucy.is.informatik.uni-duisburg.de>
2003-06-28 7:02 ` Frank Schmitt
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=84vfusro6q.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).