appraisal-rb Logo by Aboling0, CC BY-SA 4.0 kettle-rb Logo by Aboling0, CC BY-SA 4.0 floss-funding Logo by Aboling0, CC BY-SA 4.0 galtzo-floss Logo by Aboling0, CC BY-SA 4.0 omniauth Logo by (presumed) tomeara, (presumed) MIT resque Logo by Resque development team, MIT rubocop-lts Logo by Aboling0, CC BY-SA 4.0 oauth Logo by Chris Messina, CC BY-SA 3.0 ruby-openid Logo by Aboling0, CC BY-SA 4.0

Preventing Accidental Emails in Development

Learn how to use sanitize_email to prevent accidentally sending emails to real users during development.

The Problem

During development, you might accidentally send emails to real users. This can be embarrassing and potentially harmful.

The Solution

sanitize_email intercepts and sanitizes all emails in non-production environments.

# config/initializers/sanitize_email.rb
SanitizeEmail::Config.configure do |config|
  config[:sanitized_to] = 'dev@example.com'
  config[:sanitized_cc] = 'dev@example.com'
  config[:sanitized_bcc] = nil
  
  config[:use_actual_email_prepended_to_subject] = true
  config[:use_actual_environment_prepended_to_subject] = true
  
  config[:activation_proc] = proc { !Rails.env.production? }
end

Features

Now you can develop with confidence!