element: <Timeout>

Value: positive integer (in seconds)

A single <Timeout> element may appear in any top-level or sub-level verifier. If you do not provide a <Timeout> element, then each verifier type uses its own default value.

A timeout begins when the application sends a request to the verification server. It stops when the server responds with a complete message. In addition, because the number of connections is limited, issuing a request to a busy server can result in an unlimited wait for a free connection to become available.

When a timeout does occur, it is treated as an error. This error always results in the application closing the particular connection on which the timeout occurred. However, the application may reissue the same request to a different server, or it may return a failure for the current operation.

For Multi verifiers, you can specify zero or one <Timeout> element in the <Multi> element itself, and also zero or one <Timeout> element in each sub-verifier. If the <Multi> element itself contains no timeout, then each sub-verifier has a default value that can be overridden with a locally scoped <Timeout> element. If the <Multi> element does have a <Timeout>, then that <Timeout> becomes the default for any sub-verifier that does not contain its own <Timeout> element.

In the following example, a request to the "My Multi Verifier" verifier results in the following queries (stopping at the first match or error):

• LDAP lookup on ldap-1.company.com with timeout of 3 seconds
• RcptTo lookup on mail.company.com with timeout of 4 seconds
• LDAP lookup on ldap-2.company.com with timeout of 5 seconds

  <Vrfy version = "101.4635"

  name = "My Multi Verifier"

  uid = "64378E86-A459-11DD-1273-09173F13E4C5">

  <Multi>

  <Timeout>4</Timeout>

  <LDAP>

  <Host>ldap-1.company.com</Host>

  <Timeout>3</Timeout>

  </LDAP>

  <RcptTo>

  <Host>mail.company.com</Host>

  </RcptTo>

  <LDAP>

  <Host>ldap-2.company.com</Host>

  <Timeout>5</Timeout>

  </LDAP>

  </Multi>

  </Vrfy>