# pipelined-connect, cache invalidation # # # Not attempted without a cache entry exim -bd -DSERVER=server -DCONNECTCOND=* -oX PORT_D **** # exim nocache@test.ex Subject test 1 **** exim -DCONTROL=127.0.0.1 -q **** exim -DNOTDAEMON -DSERVER=server -q **** # # # # Go for it. This one should do early-pipelinng. exim hascache@test.ex Subject test 2 **** exim -DCONTROL=127.0.0.1 -q **** exim -DNOTDAEMON -DSERVER=server -q **** # # # Check that client doesn't try when the cache entry is too old # It will however create a new entry sleep 2 # exim client_old@test.ex Subject test 3 **** exim -DRETRY=1s -DCONTROL=127.0.0.1 -q **** exim -DNOTDAEMON -DSERVER=server -q **** # killdaemon # # # sudo rm DIR/spool/db/misc # # Check that the cache is invalidated on SMTP errors from the server for the banner # server PORT_D >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi nocache2@test.ex body 2 **** server PORT_D >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi withcache2@test.ex body 2a **** server PORT_D *sleep 2 450 sorry no banner for you today >550 sync error >550 sync error >550 sync error >550 sync error >220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi badbanner@test.ex body 2b **** # # Check that the cache is not invalidated on SMTP errors from the server after early-pipelining # server PORT_D >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi nocache3@test.ex body **** server PORT_D >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi withcache3@test.ex body **** server PORT_D *sleep 2 220 banner >250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok >250 mail good >250 rcpt good >550 obscure data error >220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi baddata3@test.ex body **** server PORT_D *sleep 2 220 banner >250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok >250 mail good >550 rcpt refused >550 data cmd rejected - no valid recipient >220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi badrcpt3@test.ex body **** server PORT_D *sleep 2 220 banner >250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok >550 mail cmd refused >550 rcpt cmd rejected - no valid mail >550 data cmd rejected - no valid mail >220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi badmail3@test.ex body **** server PORT_D *sleep 2 >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -DCONTROL=127.0.0.1 -odi withcache23@test.ex body **** # # # Check that the cache is updated on a change of advertised extensions # The conn will be made pipelined anyway (because we don't find out early) # but it's the DB dump that matters. Unfortunately the dump doesn't show # us the (binary) record content, only the key. So you need to look at the # debug output after all. # This server offers SIZE where the previous did not; we should see in # test-stderr a line "EHLO cleartext extensions changed" then another # "writing clr 0160/0000 cry 0000/0000" server PORT_D 1 >220 banner 250-esmtp-resp >250-PIPELINING >250-PIPE_CONNECT >250-SIZE >250 ok 250 mail-from accepted 250 rcpt-to accepted 354 data go-ahead . >250 message accepted 220 bye *eof **** exim -d-all+transport -DCONTROL=127.0.0.1 -odi extchange@test.ex body **** dump misc # no_msglog_check