It's the builtin MS smtp server that come with win2000 internet services. I
couldn't find logs for it, but I forgot to look in the stupid Event viewer.
Here's what I just found:
"Message delivery to the remote domain 'marketwatchmail.com' failed. The
error message is 'The connection was dropped by the remote host.'."
Any ideas why it would drop the connection after only receiving one message?
I couldn't find any errors on the qmail box.
Jay
-----Original Message-----
From: Aaron L. Meehan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 11, 2000 5:37 PM
To: '[EMAIL PROTECTED]'
Subject: Re: smtp speed limit??
Quoting Austad, Jay ([EMAIL PROTECTED]):
> We have a little script that sends 5 different messages in rapid
succession
> to one email address. When it gets pointed at our mailserver running MS
> Exchange, it works fine, however, when pointed at the qmail box, only the
> first message makes it through, the other 4 get delayed or deffered and
put
> back into the queue (MS Exchange or some MS mailserver thing).
Fascinating. I wonder if your exchange server bothers to log the
response from the remote mail server upon delivery, failure, or
deferral? That would help (and even more to show them to us --
I think that shall be my mantra from now on).
> Does qmail limit how fast one host can send messages via smtp?
>
> Here's my tcpserver line:
> tcpserver -q -c 500 -x /etc/smtp.cdb -H -l mail.marketwatchmail.com -R -u
> 503 -g 503 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 |
/var/qmail/bin/splogger
> smtpd 3 &
Since tcpserver is handling the smtp connection, the proper question
would be whether tcpserver itself can limit how fast it will receive
mail. The answer to the question as you put it is "no." However,
tcpserver can limit the number of smtp connections it will accept.
The default is 40 simultaneous connections, and you have actually
specified 500. You would not seem to be crossing that threshold, but
I'm just guessing without seeing any logs--tcpserver's logging will
show if you're going over 500 connections.
Personally, my bet is that the exchange server is puking. Five messages
in rapid succession.. that must put real stress on the bloatware.
Aaron
