discourse/app/mailers/test_mailer.rb

# frozen_string_literal: true

class TestMailer < ActionMailer::Base
  include Email::BuildEmailHelper

  def send_test(to_address, opts = {})
    build_email(to_address, template: 'test_mailer', **opts)
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 18:17:27 -04:00			`# frozen_string_literal: true`

Initial release of Discourse 2013-02-05 14:16:51 -05:00			`class TestMailer < ActionMailer::Base`
Work in Progress: Reply By Email: - Add support classes and settings to enable reply by email - Split out Email builder to be more OO, add many specs 2013-06-10 16:46:08 -04:00			`include Email::BuildEmailHelper`
Initial release of Discourse 2013-02-05 14:16:51 -05:00
FIX: Use our header value instead of custom header on duplicates (#16711) When we build and send emails using MessageBuilder and Email::Sender we add custom headers defined in SiteSetting.email_custom_headers. However this was causing errors in cases where the custom headers defined a header that we already specify in outbound emails (e.g. the Precedence: list header for topic/post emails). This commit makes it so we always use the header value defined in Discourse core if there is a duplicate, discarding the custom header value from the site setting. cf. https://meta.discourse.org/t/email-notifications-fail-if-duplicate-headers-exist/222960/14 2022-05-10 23:47:12 -04:00			`def send_test(to_address, opts = {})`
			`build_email(to_address, template: 'test_mailer', **opts)`
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`end`
			`end`