1 # pipelined-connect, cache invalidation
4 # Not attempted without a cache entry
5 exim -bd -DSERVER=server -DCONNECTCOND=* -oX PORT_D
12 exim -DCONTROL=127.0.0.1 -q
14 exim -DNOTDAEMON -DSERVER=server -q
19 # Go for it. This one should do early-pipelinng.
24 exim -DCONTROL=127.0.0.1 -q
26 exim -DNOTDAEMON -DSERVER=server -q
30 # Check that client doesn't try when the cache entry is too old
31 # It will however create a new entry
34 exim client_old@test.ex
38 exim -DRETRY=1s -DCONTROL=127.0.0.1 -q
40 exim -DNOTDAEMON -DSERVER=server -q
47 sudo rm DIR/spool/db/misc
49 # Check that the cache is invalidated on SMTP errors from the server for the banner
59 >250 mail-from accepted
76 >250 mail-from accepted
91 >450 sorry no banner for you today
100 exim -DCONTROL=127.0.0.1 -odi nocache2@test.ex withcache2@test.ex badbanner@test.ex
104 # Check that the cache is not invalidated on SMTP errors from the server after early-pipelining
114 >250 mail-from accepted
116 >250 rcpt-to accepted
120 >250 message accepted
131 >250 mail-from accepted
133 >250 rcpt-to accepted
137 >250 message accepted
153 >550 obscure data error
169 >550 data cmd rejected - no valid recipient
183 >550 mail cmd refused
184 >550 rcpt cmd rejected - no valid mail
185 >550 data cmd rejected - no valid mail
197 >250 mail-from accepted
199 >250 rcpt-to accepted
203 >250 message accepted
208 exim -DCONTROL=127.0.0.1 -odi nocache@test.ex withcache@test.ex baddata@test.ex badrcpt@test.ex badmail@test.ex withcache2@test.ex
213 # Check that the cache is updated on a change of advertised extensions
214 # The conn will be made pipelined anyway (because we don't find out early)
215 # but it's the DB dump that matters. Unfortunately the dump doesn't show
216 # us the (binary) record content, only the key. So you need to look at the
217 # debug output after all.
227 >250 mail-from accepted
229 >250 rcpt-to accepted
233 >250 message accepted
238 exim -d-all+transport -DCONTROL=127.0.0.1 -odi extchange@test.ex