The following reply was made to PR bin/37226; it has been noted by GNATS.

From: jnemeth@victoria.tc.ca (John Nemeth)
To: gnats-bugs@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org, cross+netbsd@distal.com
Cc: 
Subject: Re: bin/37226
Date: Sun, 28 Oct 2007 02:49:42 -0700

 On Feb 11, 11:52pm, Martin Husemann wrote:
 }
 } The following reply was made to PR bin/37226; it has been noted by GNATS.
 } 
 } From: Martin Husemann <martin@duskware.de>
 } To: gnats-bugs@NetBSD.org
 } Date: Sat, 27 Oct 2007 13:40:07 +0200
 } 
 }  I think we should just drop the "read timeout" option.
 
      It's not a "read timeout".  The comment is wrong.  The option is a
 general option that sets a bunch of timeouts.  To set a specific
 timeout, you need '-O Timeout.<whatever>'.  In particular, '-or...'
 sets mail, rcpt, datainit, datablock, datafinal, command, ident,
 fileopen, control, hoststatus, resolver.retrans,
 resolver.retrans.first, resolver,retrans.normal, resolver.retry,
 resolver,retry.first, and resolver.retry.normal.  The commnet indicates
 that the idea is to not timeout.  That obviously isn't happening.  I
 would be okay with simply eliminating it and letting the configured
 timeouts apply.
 
 }-- End of excerpt from Martin Husemann