-
Improvement
-
Resolution: Fixed
-
Minor
-
None
The Amazon Simple Email Service (AWS SES) rewrites the Message-ID header of outgoing emails. That means subsequent failure/success notifications will not be in the same thread, because they reference a non-existing message id in the In-Reply-To header.
The rewritten message id is returned as last message of the SMTP transaction, e.g.
250 Ok <00000123456abcde-1234abcd-abcd-1234-1234-1234abcd1234-000000@eu-west-1.amazonses.com>
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html
I have written a proof-of-concept patch that updates the rewritten message id in case AWS SES is used for sending mails.
Would you be willing to accept such a patch? It is kind of ugly to include provider-specific code like this, but it has no downside for people not using AWS SES and can probably be encapsulated so that it doesn't get in the way.
[JENKINS-30854] Support AWS SES Message IDs for In-Reply-To header
Johannes W
created issue -
Johannes W
made changes -
| Summary | Original: Support AWS SES Message IDs for Reply-To header | New: Support AWS SES Message IDs for In-Reply-To header |
Johannes W
made changes -
| Description |
Original:
The Amazon Simple Email Service ([AWS SES|https://aws.amazon.com/ses/]) rewrites the Message-ID header of outgoing emails. That means subsequent failure/success notifications will not be in the same thread, because they reference a non-existing message id in the In-Reply-To header. The rewritten message id is returned as last message of the SMTP transaction, e.g. {noformat} 250 Ok <00000123456abcde-1234abcd-abcd-1234-1234-1234abcd1234-000000@eu-west-1.amazonses.com> {noformat} http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html I have written a [proof-of-concept patch|https://github.com/weisslj/email-ext-plugin/commit/ea00c77afa8c151e2ee8931ccf99cad5f0286b73] that updates the rewritten message id in case AWS SES is used for sending mails. Would you be willing to accept such a patch? It is kind of ugly to include provider-specific code like this, but it has no downside for people not using AWS SES and can probably be encapsulated to that it doesn't get in the way. |
New:
The Amazon Simple Email Service ([AWS SES|https://aws.amazon.com/ses/]) rewrites the Message-ID header of outgoing emails. That means subsequent failure/success notifications will not be in the same thread, because they reference a non-existing message id in the In-Reply-To header. The rewritten message id is returned as last message of the SMTP transaction, e.g. {noformat} 250 Ok <00000123456abcde-1234abcd-abcd-1234-1234-1234abcd1234-000000@eu-west-1.amazonses.com> {noformat} http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html I have written a [proof-of-concept patch|https://github.com/weisslj/email-ext-plugin/commit/ea00c77afa8c151e2ee8931ccf99cad5f0286b73] that updates the rewritten message id in case AWS SES is used for sending mails. Would you be willing to accept such a patch? It is kind of ugly to include provider-specific code like this, but it has no downside for people not using AWS SES and can probably be encapsulated so that it doesn't get in the way. |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 165981 ] | New: JNJira + In-Review [ 197865 ] |