Mechiel Lukkien 850f4444d4 when suggesting DNS records, leave "IN" out ... people will either paste the records in their zone file. in that case, the records will inherit "IN" from earlier records, and there will always be one record. if anyone uses a different class, their smart enough to know they need to add IN manually. plenty of people will add their records through some clunky web interface of their dns operator. they probably won't even have the choice to set the class, it'll always be IN.		2023-10-13 08:25:35 +02: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 DNS records, leave "IN" out	2023-10-13 08:25:35 +02:00
moxmail2.sh	when suggesting DNS records, leave "IN" out	2023-10-13 08:25:35 +02: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