| | 1 | # recipient and host defer interactions |
| | 2 | # In this test, the primary host (normal IP address) defers the recipient, and |
| | 3 | # the secondary host (loopback address) defers the connection. |
| | 4 | # |
| | 5 | #XXX the test is relying on one-second accuracy, which is too tight. |
| | 6 | # The measured time is only one-second precision, so certain to sometime |
| | 7 | # straddle a boundary, even ignoring scheduling and I/O-wait issues. |
| | 8 | # Consider a factor of (?) two, in the retry section of the conf/ file |
| | 9 | # and +1 /2 after the diff operation (runtest:463). |
| | 10 | # |
| | 11 | need_ipv4 |
| | 12 | # |
| | 13 | exim -DSERVER=server -bd -oX PORT_D |
| | 14 | **** |
| | 15 | exim -odi userx@test.ex |
| | 16 | Test message |
| | 17 | **** |
| | 18 | # defers from both |
| | 19 | dump retry |
| | 20 | millisleep 4200 |
| | 21 | # At this point, the primary host retry rule ehould have timed out |
| | 22 | # and the secondary is ready for a retry |
| | 23 | exim -q |
| | 24 | **** |
| | 25 | dump retry |
| | 26 | millisleep 4200 |
| | 27 | # This should be similar |
| | 28 | exim -q |
| | 29 | **** |
| | 30 | dump retry |
| | 31 | # with luck this is tried within a second after the previous |
| | 32 | # so the primary gets tried (it's a new RCPT so the existing retry record is irrelevant) |
| | 33 | # but the secondary is not yet ready for a retry (host record) |
| | 34 | exim -odi usery@test.ex |
| | 35 | Test message 2. |
| | 36 | **** |
| | 37 | dump retry |
| | 38 | millisleep 4000 |
| | 39 | exim -q |
| | 40 | **** |
| | 41 | killdaemon |
| | 42 | no_msglog_check |
projects / exim.git / blame_incremental