#6 Resolve timeout race condition between resolver and MTA

v0.4.0
closed
5
2007-05-04
2006-04-19
No

If the asynchronous resolver starts up a query with a
10-second timeout and the MTA's milter read timeout is
also 10 seconds, we're guaranteed timeouts when DNS
will fail. This means it's necessary to either have
shorter timeouts on the resolver or longer timeouts on
the MTA.

One solution to this is a shorter default timeout for
the resolver. Another solution is longer milter
timeouts in the MTA. Yet another solution is to call
ar_waitreply() with a shorter wait value so it comes
back part-way through the timeout, use smfi_progress()
to reset the MTA's milter read timeout, and then go
back into ar_waitreply().

Discussion

  • Anonymous - 2006-05-03

    Logged In: YES
    user_id=1048957

    _FFR_SET_DNS_CALLBACK added in v0.4.1 which will arrange to
    use smfi_progress() every few seconds while waiting for DNS
    replies.

    Leaving "open" until this is active code.

     
  • Anonymous - 2007-05-04
    • status: open --> closed
     
  • Anonymous - 2007-05-04

    Logged In: YES
    user_id=1048957
    Originator: YES

    FFR activated as part of 0.7.0, which has now been released.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks