mox/testdata/integration
Mechiel Lukkien db3fef4981
when suggesting CAA records for a domain, suggest variants that bind to the account id and with validation methods used by mox
should prevent potential mitm attacks. especially when done close to the
machine itself (where a http/tls challenge is intercepted to get a valid
certificate), as seen on the internet last month.
2023-12-21 15:53:32 +01:00
..
dkim merge docker-compose-based quickstart and integration tests into a single integration test 2023-07-23 23:32:02 +02:00
tls merge docker-compose-based quickstart and integration tests into a single integration test 2023-07-23 23:32:02 +02:00
Dockerfile.dns mox! 2023-01-30 14:27:06 +01:00
Dockerfile.postfix mox! 2023-01-30 14:27:06 +01:00
Dockerfile.test merge docker-compose-based quickstart and integration tests into a single integration test 2023-07-23 23:32:02 +02:00
example.zone when suggesting DNS records, leave "IN" out 2023-10-13 08:25:35 +02:00
moxacmepebble.sh when suggesting CAA records for a domain, suggest variants that bind to the account id and with validation methods used by mox 2023-12-21 15:53:32 +01:00
moxmail2.sh when suggesting CAA records for a domain, suggest variants that bind to the account id and with validation methods used by mox 2023-12-21 15:53:32 +01:00
moxsubmit.conf more integration tests: start "mox localserve" and submit a message with smtpclient and with "mox sendmail", check that we receive it 2023-07-01 18:48:29 +02:00
pebble-config.json merge docker-compose-based quickstart and integration tests into a single integration test 2023-07-23 23:32:02 +02:00
resolv.conf mox! 2023-01-30 14:27:06 +01:00
reverse.zone when suggesting DNS records, leave "IN" out 2023-10-13 08:25:35 +02:00
unbound.conf merge docker-compose-based quickstart and integration tests into a single integration test 2023-07-23 23:32:02 +02:00