When you sign up for a Mastodon account, the instance sends an email confirmation link to verify your address. Many new users report that this email never arrives in their inbox, leaving them stuck on the registration page. The issue is usually caused by the Mastodon instance being blocked by your email provider or by a misconfiguration on the instance server. This article explains why the confirmation email fails to deliver and provides step-by-step fixes you can apply on your end and on your Mastodon instance.
Key Takeaways: Mastodon Email Confirmation Fix
- Check spam or junk folder: Mastodon confirmation emails are often flagged as spam by Gmail, Outlook, or Yahoo.
- Whitelist the instance domain: Add the Mastodon server domain to your email provider’s safe senders list to bypass filters.
- Resend the confirmation email: Use the Mastodon resend link on the login page to trigger a new delivery attempt.
Why the Mastodon Confirmation Email Does Not Arrive
Mastodon instances send confirmation emails using the SMTP server configured by the instance administrator. The email sender address is usually something like noreply@instance.domain. Many public email providers such as Gmail, Outlook, and Yahoo apply strict spam filtering rules to bulk or automated mail. If the instance domain has a low reputation score or the email content triggers a spam rule, the provider silently discards the message without sending it to the spam folder.
Another common cause is that the Mastodon instance itself is not configured to send email at all. Some small or personal instances run without an SMTP relay, so the confirmation email is never generated. In that case, the instance administrator must set up an SMTP service such as Mailgun, SendGrid, or a self-hosted mail server.
Email Provider Filtering
Gmail, Outlook, and Yahoo each use proprietary algorithms to classify incoming mail. If the Mastodon instance shares an IP address with known spam senders, the provider may reject the email entirely. The user never sees a bounce message because the instance does not receive a delivery failure notification for filtered mail.
Instance SMTP Misconfiguration
The Mastodon server must have valid SMTP credentials, a correct sender domain, and a properly set envelope-from address. If any of these fields are missing or incorrect, the email will fail to send. The Mastodon logs at log/production.log will show an error such as “Net::SMTPAuthenticationError” or “Errno::ECONNREFUSED.”
Steps to Fix Missing Mastodon Confirmation Email
- Check your spam and junk folder
Open your email provider and look in the spam, junk, or promotions tab. Search for the sender address noreply@ followed by the Mastodon instance domain. If you find the email there, mark it as “Not spam” to train the filter. - Add the instance domain to your safe senders list
In Gmail, go to Settings > Filters and Blocked Addresses > Create a new filter. Enter the instance domain in the “From” field and select “Never send it to Spam.” In Outlook, right-click the email if you can find it and select “Add to Safe Senders.” If you cannot find the email, add the domain manually under Settings > Mail > Junk email > Safe senders. - Resend the confirmation email from the Mastodon login page
Go to the Mastodon instance login page. Click the link labeled “Resend confirmation email” or “Didn’t receive confirmation instructions?” Enter your email address and submit. Mastodon will attempt to send a new confirmation link. - Use a different email address
If the resend fails, sign out and start a new registration with a different email provider. For example, if you used Gmail, try using a ProtonMail or Outlook account. This bypasses the specific filter rules of the original provider. - Check the Mastodon instance status
Visit the instance’s status page or search for the instance name on Mastodon’s official instances list. If the instance is marked as “limited” or “suspended,” email delivery may be disabled. Choose a different instance if the current one is unreliable. - Contact the instance administrator
Find the admin contact email or Mastodon account on the instance’s about page. Send a message explaining that the confirmation email never arrived. The admin can check the server logs for SMTP errors and resend the confirmation from the admin panel.
If You Are the Instance Administrator
If you run a Mastodon instance and users report missing confirmation emails, follow these steps to verify and fix the SMTP configuration.
- Check the SMTP settings in the .env.production file
Open the .env.production file located in the Mastodon root directory. Verify that the variables SMTP_SERVER, SMTP_PORT, SMTP_LOGIN, SMTP_PASSWORD, and SMTP_FROM_ADDRESS are set correctly. For example, if you use Mailgun, the SMTP server is smtp.mailgun.org on port 587. - Test SMTP connectivity from the server
SSH into your server and run the command openssl s_client -starttls smtp -connect smtp.yourprovider.com:587. If the connection fails, your firewall or provider is blocking outbound SMTP traffic. - Restart the Mastodon sidekiq and web processes
After correcting the SMTP settings, run systemctl restart mastodon-sidekiq and systemctl restart mastodon-web to apply the changes. - Manually send a test email
Use the Rails console to send a test email: cd /home/mastodon/live && RAILS_ENV=production bin/tootctl email test your-email@example.com. If you receive the email, the SMTP configuration is working.
Common Issues After the Main Fix
Confirmation Email Arrives but Link Does Not Work
If you receive the email but clicking the link leads to an error page, the link may have expired. Mastodon confirmation links expire after 24 hours. Request a new confirmation email from the login page. If the error persists, the instance may have a broken URL routing configuration. Contact the administrator.
Email Bounces Back to the Instance
If the instance administrator sees bounce messages, the recipient email address is invalid or the mail server rejected the message. Ask the user to verify they typed the email address correctly during registration. If the address is correct, the user’s email provider is blocking the instance IP. The admin can add SPF and DKIM DNS records to improve deliverability.
Multiple Users Affected on the Same Instance
When many users report missing confirmation emails, the instance SMTP configuration is almost certainly broken. Follow the administrator steps above to verify the SMTP settings. If the settings are correct, the SMTP relay provider may have suspended the account due to spam complaints. Check the relay provider dashboard for warnings.
Mastodon Email Confirmation vs Manual Account Approval
| Item | Email Confirmation | Manual Approval |
|---|---|---|
| Purpose | Verifies the user owns the email address | Allows the admin to review each signup |
| Trigger | Sent automatically after registration | Admin reviews pending accounts in the dashboard |
| User action needed | Click the link in the email | Wait for admin to approve the account |
| Common failure | Email filtered or SMTP misconfigured | Admin does not check pending list |
An instance that uses manual approval does not send a confirmation email. Instead, the admin must manually approve each account from the administration panel. If you registered on such an instance, you will not receive a confirmation email at all. Check the instance registration page for a note about manual approval.
If you cannot resolve the missing email issue, consider choosing a different Mastodon instance that uses a reliable email service. Large instances such as mastodon.social use professional SMTP relays and rarely experience delivery problems. After you confirm your email, you can customize your profile settings and start following accounts.