| | 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 | need_ipv4 |
| | 6 | # |
| | 7 | exim -DSERVER=server -bd -oX PORT_D |
| | 8 | **** |
| | 9 | exim -odi userx@test.ex |
| | 10 | Test message |
| | 11 | **** |
| | 12 | # defers from both |
| | 13 | dump retry |
| | 14 | millisleep 2100 |
| | 15 | # At this point, the primary host retry rule ehould have timed out |
| | 16 | # and the secondary is ready for a retry |
| | 17 | exim -q |
| | 18 | **** |
| | 19 | dump retry |
| | 20 | millisleep 2100 |
| | 21 | # This should be similar |
| | 22 | exim -q |
| | 23 | **** |
| | 24 | dump retry |
| | 25 | # with luck this is tried within a second after the previous |
| | 26 | # so the primary gets tried (it's a new RCPT so the existing retry record is irrelevant) |
| | 27 | # but the secondary is not yet ready for a retry (host record) |
| | 28 | exim -odi usery@test.ex |
| | 29 | Test message 2. |
| | 30 | **** |
| | 31 | dump retry |
| | 32 | millisleep 2000 |
| | 33 | exim -q |
| | 34 | **** |
| | 35 | killdaemon |
| | 36 | no_msglog_check |
projects / exim.git / blame_incremental