Files
LambdaMail/Makefile
T
Lucas RayanandClaude Opus 5 c7251211b5 #29: add reset-mfa, so a broken enrolment does not cost the mailbox
An enrolment can end up confirmed against a secret the authenticator no longer
holds - the account is then locked behind codes nobody can produce, and the
only documented recovery was a DELETE against mfa_totp. That SQL was also
incomplete: it left the recovery codes valid and the sessions live.

reset-mfa removes the authenticator secrets and the recovery codes, and signs
the account's sessions out, because a live session would keep the console open
without the factor that was just removed. The password is untouched, so the
command alone grants nobody access.

The alternative people reach for - delete the mailbox and create it again -
takes its mail, folders and aliases with it, and none of those are the problem.
The docs now say so.

Also corrects the advice printed after create-admin, which still told the
operator to enrol from the webmail settings before the console would open. The
console has enrolled inline since #23.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-03 10:20:21 -03:00

67 lines
2.6 KiB
Makefile

.PHONY: up down logs test lint migrate-up migrate-down gen-dev-cert seed preflight create-admin reset-password reset-mfa
# Local development builds from source; production pulls what CI published.
up:
docker compose -f docker-compose.yaml -f docker-compose.build.yaml --env-file .env up --build
down:
docker compose down -v
logs:
docker compose logs -f
test:
cd services/protocols && go test ./...
cd services/auth && npm test
cd services/storage && npm test
cd services/webmail && npm test
lint:
cd services/protocols && go vet ./...
node scripts/lang-lint.mjs
migrate-up:
docker run --rm -v $(PWD)/migrations:/migrations --network host \
migrate/migrate -path=/migrations -database "$$DATABASE_URL" up
migrate-down:
docker run --rm -v $(PWD)/migrations:/migrations --network host \
migrate/migrate -path=/migrations -database "$$DATABASE_URL" down 1
gen-dev-cert:
mkdir -p local/certs
openssl req -x509 -newkey ec -pkeyopt ec_paramgen_curve:prime256v1 \
-keyout local/certs/key.pem -out local/certs/cert.pem \
-days 365 -nodes -subj "/CN=mail.localhost"
seed:
docker compose exec -T db psql -U $${POSTGRES_USER:-lambdamail} -d $${POSTGRES_DB:-lambdamail} < scripts/dev-seed.sql
# Environment diagnostics (PLAN.md section 15). Run this before pointing DNS at
# the host: it reports outbound port 25, PTR/FCrDNS, RBL listings and the
# Cloudflare token scope.
preflight:
docker compose run --rm --entrypoint /app/lambdamail-protocols protocols preflight
# First login on a fresh deployment. Nothing else creates a mailbox, so without
# this there is no way into the admin console.
# make create-admin EMAIL=you@example.com PASSWORD='...'
create-admin:
@test -n "$(EMAIL)" || (echo "EMAIL is required" && exit 1)
@test -n "$(PASSWORD)" || (echo "PASSWORD is required" && exit 1)
docker compose run --rm --entrypoint node auth dist/cli.js create-admin "$(EMAIL)" "$(PASSWORD)"
# Recovers a locked-out account. Every session it had is signed out.
reset-password:
@test -n "$(EMAIL)" || (echo "EMAIL is required" && exit 1)
@test -n "$(PASSWORD)" || (echo "PASSWORD is required" && exit 1)
docker compose run --rm --entrypoint node auth dist/cli.js reset-password "$(EMAIL)" "$(PASSWORD)"
# Clears every second factor from an account: the lost-phone case, and the one
# where an enrollment was confirmed against a secret the authenticator does not
# have. The password is untouched, so this alone grants nobody access.
# make reset-mfa EMAIL=you@example.com
reset-mfa:
@test -n "$(EMAIL)" || (echo "EMAIL is required" && exit 1)
docker compose run --rm --entrypoint node auth dist/cli.js reset-mfa "$(EMAIL)"