Enable password resets, invitation emails, shift reminders, and notifications.
Field Day Commander works fine without email. By default, all email features are hidden from the UI so nobody sees broken "forgot password" links or grayed-out notification checkboxes. The admin creates accounts and sets passwords manually, and operators manage their own shifts through the web interface.
If your club wants password resets, invitation emails, shift reminders, or security alerts, point Field Day Commander at an SMTP server. Once it's configured, the hidden features will appear automatically.
Configuring SMTP makes these five controls available:
Field Day Commander checks the MAIL_MAILER value in your .env file. If it's set to log or array (the defaults when email isn't configured), all email features are disabled. Setting it to smtp enables them.
SSH into the server and edit the .env file in the Field Day Commander directory:
sudo nano /var/www/fd-commander/.env
Find the mail section and update it with your SMTP credentials:
# Mail configuration
MAIL_MAILER=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=587
MAIL_USERNAME=your-smtp-username
MAIL_PASSWORD=your-smtp-password
MAIL_FROM_ADDRESS=fieldday@yourcallsign.com
MAIL_FROM_NAME="Field Day Commander"
You don't need an encryption setting. Field Day Commander picks it from the port: port 587 upgrades the connection with STARTTLS, and port 465 uses TLS from the start.
After saving the file, rebuild the cached configuration as the fdcommander user, then restart the web server and the queue worker so they load the new settings:
cd /var/www/fd-commander && sudo -u fdcommander php artisan optimize sudo systemctl restart fdcommander fdcommander-queue fdcommander-scheduler
The email features will appear in the UI on the next page load.
Put the same MAIL_* lines in the .env file next to docker-compose.yml, then run docker compose up -d. The container picks up the new settings when it's recreated.
Any SMTP-capable service works. Here are settings for a few common options:
MAIL_HOST=smtp.gmail.com MAIL_PORT=587
For SMTP username/password authentication, follow Google’s App Password instructions. App passwords require 2-Step Verification and may be unavailable under your account’s security settings or organization policy. Use another SMTP service if your account does not offer them.
Use SES through its SMTP interface. Follow AWS’s SES SMTP credential instructions to create region-specific SMTP credentials in the SES console, set MAIL_HOST to your region's SMTP endpoint (for example, email-smtp.us-east-1.amazonaws.com), and keep MAIL_MAILER=smtp. Field Day Commander doesn't include the AWS SDK, so MAIL_MAILER=ses won't work.
Use the provider's SMTP relay credentials with the standard smtp mailer. Check your account's sending limits before the event.
Use an SMTP service your club already manages. Confirm that it allows the sender address you plan to use.
The quickest way to confirm email is working is to test a password reset. Sign out, click the "Forgot password?" link on the login page (it should now be visible), enter an email address, and check for the reset email. If it arrives, everything is wired up.
If the email doesn't arrive, check the application log for errors:
sudo tail -50 /var/www/fd-commander/storage/logs/laravel.log
Common problems: wrong SMTP port (try 465 if 587 doesn't work), incorrect App Password, or the "from" address not being verified with your email provider.
If you want to turn email features back off, set MAIL_MAILER=log in your .env file, then run the same optimize and restart commands. The UI elements will disappear and no emails will be sent.