rails_mailersend 0.4.0 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2b230567dfd55a4b5874d501dd4c25ff67cea0fc2cb80972001c97f37e81bde1
-  data.tar.gz: c1cd9f9a8031b4457299aa5c5d38bb3e693efdbf2fed4284aa629f8f2df27a24
+  metadata.gz: 5b4c703aa4d7b7e591afbbd9057724fb3e095793b8f397440530574674c5aa27
+  data.tar.gz: ce5a58c4991426b929aa3803f4df5544cb7df3f32bf378521107008bb452bfe0
 SHA512:
-  metadata.gz: e840f9652bfc94d57480738c8642b50be72af6dafc689f5e79c0ed41c1866b57ddc569c6d9de53d0bb3f854303ce7bb4c6b4f767886c8dc740f8bf615334e15f
-  data.tar.gz: 0375b493a5bec2b0782c224d7fe74951426fc132a08888d78464d5f7beda3345d43e21a8109420803a88a1bf4ed0a458c80f5d269406e95fa2cc5f91539eb098
+  metadata.gz: 20eb45ed0f10c76612bc6ef36bf08bb7f2b9e593c91a2a9fc314c0c10846dc936386195e110449963ed7074c1e161195f2ac71ef1ba533afc67fe4fda9582008
+  data.tar.gz: 2cd89e459177774bafec016712206a9e22d3512b827be5c1cd8164900a1d2cdcc43860330565632793dbedfb9befd3c5555f3445f2efceed86e8d297d66cdc5c

data/README.md

@@ -65,6 +65,21 @@ than returning quietly, so the enqueuing job retries and the failure is visible.
 For an app where sign-in is by magic link, a swallowed delivery error looks
 exactly like a broken app to the person waiting.
 
+`In-Reply-To` and `References` are carried across to MailerSend's own
+`in_reply_to` and `references` fields, so a reply lands under the message it
+answers instead of opening a conversation of its own:
+
+```ruby
+mail(to: person.email_address, subject: "Re: #{parent_subject}",
+     in_reply_to: parent_message_id, references: [parent_message_id])
+```
+
+Angle brackets are put back on, since the `mail` gem strips them and MailerSend
+validates against the RFC 5322 form. Every other header is dropped: the API takes
+fields rather than a MIME message, and these are the two worth translating. Both
+are paid-plan only at MailerSend, which answers a free account carrying them with
+a 422 — loudly, rather than with an unthreaded reply nobody can account for.
+
 ## Inbound mail
 
 Optional, and only loads when the app has Action Mailbox. MailerSend posts the

data/lib/mailersend_rails/delivery_method.rb

@@ -55,10 +55,41 @@ module MailersendRails
           "reply_to" => Array(mail.reply_to).empty? ? {} : address_in(mail[:reply_to]),
           "subject" => mail.subject,
           "text" => mail.text_part&.body&.decoded,
-          "html" => html_for(mail)
+          "html" => html_for(mail),
+          "in_reply_to" => message_ids_in(mail[:in_reply_to]).first,
+          "references" => message_ids_in(mail[:references])
         }.reject { |_, value| omit?(value) }
       end
 
+      # In-Reply-To and References, in the form MailerSend asks for them.
+      #
+      # Threading is what puts a reply under the message it answers rather than
+      # in a conversation of its own, and these two headers are the whole of it.
+      # They need carrying by hand because the API takes fields rather than a
+      # MIME message: every header Action Mailer set that isn't named in
+      # #payload_for is dropped here, and a mailer that sets In-Reply-To and
+      # then watches its reply arrive as a new thread has nowhere to look for
+      # where it went. Both fields are paid-plan only at MailerSend, which
+      # answers a request carrying them on a free account with a 422 -- loudly,
+      # like every other delivery failure.
+      #
+      # The `mail` gem hands ids back with the angle brackets stripped and
+      # MailerSend validates against the RFC 5322 form, so they go back on. A
+      # field too malformed to parse falls back to splitting on whitespace,
+      # which is the shape of both headers.
+      def message_ids_in(field)
+        return [] if field.nil?
+
+        ids = field.respond_to?(:message_ids) ? field.message_ids : field.to_s.split
+        Array(ids).filter_map { |id| bracketed(id) }
+      end
+
+      def bracketed(id)
+        id = id.to_s.strip.delete_prefix("<").delete_suffix(">").strip
+
+        "<#{id}>" unless id.empty?
+      end
+
       def html_for(mail)
         mail.html_part&.body&.decoded || mail.body.decoded
       end

data/lib/mailersend_rails/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module MailersendRails
-  VERSION = "0.4.0"
+  VERSION = "0.5.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails_mailersend
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.5.0
 platform: ruby
 authors:
 - Dan Loman
@@ -58,12 +58,12 @@ files:
 - lib/mailersend_rails/railtie.rb
 - lib/mailersend_rails/version.rb
 - lib/rails_mailersend.rb
-homepage: https://github.com/namolnad/mailersend-rails
+homepage: https://github.com/namolnad/rails_mailersend
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://github.com/namolnad/mailersend-rails
-  source_code_uri: https://github.com/namolnad/mailersend-rails
+  homepage_uri: https://github.com/namolnad/rails_mailersend
+  source_code_uri: https://github.com/namolnad/rails_mailersend
 rdoc_options: []
 require_paths:
 - lib