You must login to view /lordwelch/chasquid/commit/a3f7914e292dd4e2499701e2e68c255f499b1ecc?files=internal%2Fsts.
The GitHub option should be usable for most people, it only links via username.

Files
chasquid/test/t-09-loop/run.sh
Alberto Bertogli 5eded4edc3 test: Unify (most) SMTP client calls
To send mails, today some tests use msmtp and others our internal smtpc.py.

This works, but msmtp slows down the tests significantly, and smtpc.py
is also not particularly fast, and also has some limitations.

This patch introduces a new SMTP client tool written in Go, and makes
almost all the tests use it.

Some tests still remain on msmtp, mainly for client-check compatibility.
It's likely that this will be moved in later patches to a separate
special-purpose test.

With this patch, integration tests take ~20% less time than before.
2024-03-12 20:43:21 +00:00

89 lines
2.7 KiB
Bash
Executable File

#!/bin/bash
set -e
. "$(dirname "$0")/../util/lib.sh"
init
check_hostaliases
rm -rf .data-A .data-B .mail
# Build with the DNS override, so we can fake DNS records.
export GOTAGS="dnsoverride"
# Launch minidns in the background using our configuration.
minidns_bg --addr=":9053" -zones=zones >> .minidns.log 2>&1
# Two servers:
# A - listens on :1025, hosts srv-A
# B - listens on :2015, hosts srv-B
#
# We cause the following loop:
# userA -> aliasB -> aliasA -> aliasB -> ...
CONFDIR=A generate_certs_for srv-A
CONFDIR=A add_user usera@srv-A userA
CONFDIR=B generate_certs_for srv-B
mkdir -p .logs-A .logs-B
chasquid -v=2 --logfile=.logs-A/chasquid.log --config_dir=A \
--testing__dns_addr=127.0.0.1:9053 \
--testing__max_received_headers=5 \
--testing__outgoing_smtp_port=2025 &
chasquid -v=2 --logfile=.logs-B/chasquid.log --config_dir=B \
--testing__dns_addr=127.0.0.1:9053 \
--testing__outgoing_smtp_port=1025 &
wait_until_ready 1025
wait_until_ready 2025
wait_until_ready 9053
smtpc aliasB@srv-B < content
# Get some of the debugging pages, for troubleshooting, and to make sure they
# work reasonably well.
function fexp_gt10() {
fexp "$1" -save "$2" && \
[ "$( wc -l < "$2" )" -gt 10 ]
}
fexp_gt10 http://localhost:1099/ .data-A/dbg-root \
|| fail "failed to fetch /"
fexp_gt10 http://localhost:1099/debug/flags .data-A/dbg-flags \
|| fail "failed to fetch /debug/flags"
fexp http://localhost:1099/debug/queue -save .data-A/dbg-queue \
|| fail "failed to fetch /debug/queue"
fexp_gt10 http://localhost:1099/debug/config .data-A/dbg-config \
|| fail "failed to fetch /debug/config"
fexp http://localhost:1099/404 -status 404 \
|| fail "fetch /404 worked, should have failed"
fexp_gt10 http://localhost:1099/metrics .data-A/metrics \
|| fail "failed to fetch /metrics"
# Quick sanity-check of the /metrics page, just in case.
grep -q '^chasquid_queue_itemsWritten [0-9]\+$' .data-A/metrics \
|| fail "A /metrics is missing the chasquid_queue_itemsWritten counter"
# Wait until one of them has noticed and stopped the loop.
while sleep 0.1; do
fexp http://localhost:1099/debug/vars -save .data-A/vars
fexp http://localhost:2099/debug/vars -save .data-B/vars
# Allow for up to 2 loops to be detected, because if chasquid is fast
# enough the DSN will also loop before this check notices it.
if grep -q '"chasquid/smtpIn/loopsDetected": [12],' .data-?/vars; then
break
fi
done
# Test that A has outgoing domaininfo for srv-b.
# This is unrelated to the loop itself, but serves as an end-to-end
# verification that outgoing domaininfo works.
if ! grep -q 'outgoing_sec_level:\s*TLS_INSECURE' ".data-A/domaininfo/s:srv-b";
then
fail "A is missing the domaininfo for srv-b"
fi
success