change "mox setaccountpassword" to use an account name as parameter, not email address

because with the name you would expect an account name.
and the email-resolving behaviour is surprising: with wildcard addresses you
can use any address, including a typo. you would change the password of the
address with the wildcard, without any warning. accounts are more precise and
less error-prone.

for issue #68 by x8x
This commit is contained in:
Mechiel Lukkien
2023-09-23 17:18:49 +02:00
parent 8c2814df89
commit f1f3135135
7 changed files with 19 additions and 15 deletions

View File

@ -33,7 +33,7 @@ CURL_CA_BUNDLE=/integration/tls/ca.pem curl -o /integration/tmp-pebble-ca.pem ht
mox -checkconsistency serve &
while true; do
if test -e data/ctl; then
echo -n accountpass1234 | mox setaccountpassword moxtest1@mox1.example
echo -n accountpass1234 | mox setaccountpassword moxtest1
break
fi
sleep 0.1

View File

@ -29,7 +29,7 @@ unbound-control -s 172.28.1.30 reload # reload unbound with zone file changes
mox -checkconsistency serve &
while true; do
if test -e data/ctl; then
echo -n accountpass4321 | mox setaccountpassword moxtest2@mox2.example
echo -n accountpass4321 | mox setaccountpassword moxtest2
break
fi
sleep 0.1