Email delivery

Keep Redmine notifications out of spam folders

Customize the sender address and publish an SPF record so every workflow update reaches the intended inbox reliably.

German hosting · Daily backups · DNS-friendly SPF guidance
Redmine email configuration

Why change the sender?

Redmine creates emails for every issue update, but different inbox providers treat those emails as spam when the sender address does not match your domain. A mismatched sender also prevents replies from reaching your team.

  • Set a recognizable from-address that matches your domain name
  • Send both notifications and replies to a monitored mailbox
  • Publish an SPF record so recipients trust the server that ships the email

Quick steps

  1. Open Administration -> Settings -> Email notifications
  2. Change the sender address to name@yourdomain.com and save
  3. Click Send a test email and confirm delivery

Still blocked?

Create an SPF record that authorizes our hosting server so recipients accept your messages.

Change the default sender

Go to Administration -> Settings -> Email notifications. Replace the default emission address with an email you control (for example name@xyz.org) and press Save.

After saving, scroll to the bottom of the tab and click Send a test email. Redmine will confirm success in green; if it shows an error, double-check the address spelling.

Even when the test succeeds, DNS changes keep your sender trusted when providers update their spam filters.

Redmine email notification settings

Open the email notification settings, set your sender address, and verify delivery with a test email.

Publish an SPF record

Ask your DNS provider to add a TXT entry that authorizes our host to send emails on your behalf. Using your assigned Redmine domain name is safer than pinning a specific IP address, because IPs can change without notice.

@ IN TXT "v=spf1 a:saas1605qo.saas-secure.com -all"

If you already have an SPF entry that covers your mail server, add our domain as an additional mechanism:

@ IN TXT "v=spf1 ip4:192.168.1.1 a:saas1605qo.saas-secure.com -all"

After DNS propagation (which can take up to 24 hours) re-run the test email. Then consider polishing the sender label (for example Project Management Administration <name@xyz.org>) so recipients see your brand when the notification lands.

Need more Redmine help?

Read the Redmine Hosting FAQ

Find answers about setup, access, backups, and managed hosting details.