|Subject:||Having relibility problems with tidpop3 and tidsmtp|
|Posted by:||arthur hoornweg (firstname.lastname@example.org)|
|Date:||Sun, 05 Mar 2006|
Since upgrading my mail server from twsocket to indy 10 I have
major reliability problems. This transition was more or less
forced upon me because we use a new smtp relay that
needs smtp authentification.
I use a recent developer snapshot of indy 10 on BDS2006.
At least once or twice a week I hit the situation where either
component just hangs during a transmission, even if the
connecttimeout and readtimeout properties are set to 60000
Sometimes, when I check upon our mailserver on monday mornings,
I find it has been in this condition since the saturday before.
Our DSL connection is automatically closed once every 24 hours by
the internet provider (t-online in Germany).
So why doesn't the readtimeout kick in? If the transmission is
interrupted for any reason, the readtimeout should kick in sooner
or later, shouldn't it?
It is a terrible p.i.t.a. because people in my company no longer trust
the mail server, and call me to check up on it several times daily
when they're waiting for mail.
(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)