discourse/spec/jobs/process_email_spec.rb

# frozen_string_literal: true

describe Jobs::ProcessEmail do

  let(:mail) { "From: foo@bar.com\nTo: bar@foo.com\nSubject: FOO BAR\n\nFoo foo bar bar?" }

  it "process an email without retry" do
    Email::Processor.expects(:process!).with(mail, retry_on_rate_limit: false, source: nil)
    Jobs::ProcessEmail.new.execute(mail: mail)
  end

end
DEV: use #frozen_string_literal: true on all spec This change both speeds up specs (less strings to allocate) and helps catch cases where methods in Discourse are mutating inputs. Overall we will be migrating everything to use #frozen_string_literal: true it will take a while, but this is the first and safest move in this direction 2019-04-30 08:27:42 +08:00			`# frozen_string_literal: true`

FEATURE: retry processing incoming emails on rate limit 2016-08-09 04:28:27 +08:00			`describe Jobs::ProcessEmail do`

			`let(:mail) { "From: foo@bar.com\nTo: bar@foo.com\nSubject: FOO BAR\n\nFoo foo bar bar?" }`

			`it "process an email without retry" do`
DEV: Add created_via column to IncomingEmail (#11751) This should make it easier to track down how the incoming email was created, which is one of four locations: The POP3 poller (which picks up reply via email replies) The admin email controller #handle_mail (which is where hosted mail is sent) The IMAP sync tool The group SMTP mailer, which sends emails when replying to IMAP topics, pre-emptively creating IncomingEmail records to avoid double syncing 2021-01-20 11:22:41 +08:00			`Email::Processor.expects(:process!).with(mail, retry_on_rate_limit: false, source: nil)`
FEATURE: retry processing incoming emails on rate limit 2016-08-09 04:28:27 +08:00			`Jobs::ProcessEmail.new.execute(mail: mail)`
			`end`

			`end`