EmailConfiguration » History » Version 36
- Email Configuration
- Configuration Directives
- Example configuration.yml Configurations
- More information
This page is a work in progress, the following configuration directives are only a partial list. Please consult Action Mailer Configuration
for detailed information.
The type of authentication method expected by your service provider.Valid settings:
nil(or omit the key) for no authentication
(note: if you set this to
nil or omit it, you must not include the
The mail transport method to be used.Valid settings:
:async_sendmail use asynchronous sends, which means Redmine does not wait for the email to be sent to display the next page. See Asynchronous Email Delivery for more details. Some SMTP servers have delay period before processing takes place as anti-spam feature, during which time synchronous method will block Redmine (10 seconds could be default value, see also #11376 for more information) .
With this delivery method, smtp configuration is specified using
development: email_delivery: delivery_method: :async_smtp async_smtp_settings: ...
Example configuration.yml Configurations¶
Simple Login Authentication (default settings)¶
# Outgoing email settings production: email_delivery: delivery_method: :smtp smtp_settings: address: smtp.example.net port: 25 domain: example.net authentication: :login user_name: email@example.com password: redmine development: email_delivery: delivery_method: :smtp smtp_settings: address: 127.0.0.1 port: 25 domain: example.net authentication: :login user_name: firstname.lastname@example.org password: redmine
If you want to use GMail/Google Apps and other TLS-requiring SMTP servers, you'll have to add some TLS-related settings :
production: email_delivery: delivery_method: :smtp smtp_settings: enable_starttls_auto: true address: "smtp.gmail.com" port: '587' domain: "smtp.gmail.com" authentication: :plain user_name: "email@example.com" password: "your_password"
However, this will only work with "recent" enough ruby and rails versions (1.8.7 patchset 2xx and 2.3.5).
(See #5814 )
Example for an SMTP service provider with no authentication.
production: email_delivery: delivery_method: :smtp smtp_settings: address: smtp.knology.net port: 25 domain: cybersprocket.com
Using sendmail command¶
Example for a unix system that uses the
production: email_delivery: delivery_method: :sendmail
Error: "hostname was not match with the server certificate"¶
If you get this error, there's probably a problem verifying the SSL certificate of your smtp relay. As a temporary fix, you can set this option in the appropriate "email_delivery" section:
Error: "Mail failure - no recipient addresses"¶
When this error happens, the notification is not delivered to the destination address. Instead, you will probably receive a rejection message on your sender address, where you can see the header of the message sent, containing "From:" fields but not containing any "To:" fields.
This error is common on Debian boxes, due to way exim4 is configured by default, trying to find the destination address inside the header of the message. Instead, we need to configure exim4 so that the destination address will be retrieved from the command line.
The solution consists on editing your config/configuration.yml and making sure you define
sendmail_settings as shown below:
# default configuration options for all environments default: email_delivery: delivery_method: :sendmail sendmail_settings: arguments: "-i"