Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16106

Add Precedence: bulk header to notification emails

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • mailer-plugin
    • None

      To avoid triggering vacation autoresponders, it would be good citizenship to add the appropriate Precedence header to the notification emails Jenkins sends.

          [JENKINS-16106] Add Precedence: bulk header to notification emails

          Brian Egge added a comment -

          Additionally, one should have "Auto-Submitted: auto-generated" and "Return-Path: <>"

          http://tools.ietf.org/search/rfc3834

          Brian Egge added a comment - Additionally, one should have "Auto-Submitted: auto-generated" and "Return-Path: <>" http://tools.ietf.org/search/rfc3834

          Setting the sender at SMTP level to <> is not a good idea, as the notifications about invalid email addresses, or rather addresses which were valid but are not valid anymore, will get lost. As there will be no information which addresses got invalid, notifications to those addresses will be sent forever. Some providers tend to mark sending servers as spammers, if they continuously insist to send emails to invalid addresses. This could leave to marking the emails sent from the MTA behind Jenkins to valid addresses as spam, just because the sending server is spamming, according to the rule above.

          The header

          Auto-Submitted: auto-generated

          is enough. The last paragraph of RFC 5230 "Sieve Email Filtering: Vacation Extension", section 4.6. "Restricting Replies to Automated Processes and Mailing Lists" explicitly suppresses sending out-of-office messages to emails containing the above header.

          Дилян Палаузов added a comment - Setting the sender at SMTP level to <> is not a good idea, as the notifications about invalid email addresses, or rather addresses which were valid but are not valid anymore, will get lost. As there will be no information which addresses got invalid, notifications to those addresses will be sent forever. Some providers tend to mark sending servers as spammers, if they continuously insist to send emails to invalid addresses. This could leave to marking the emails sent from the MTA behind Jenkins to valid addresses as spam, just because the sending server is spamming, according to the rule above. The header Auto-Submitted: auto-generated is enough. The last paragraph of RFC 5230 "Sieve Email Filtering: Vacation Extension", section 4.6. "Restricting Replies to Automated Processes and Mailing Lists" explicitly suppresses sending out-of-office messages to emails containing the above header.

          About the Return-Path header, as of RFC 5321, Section 4.4. Trace Information, page 58 says, among other things:

          A message-originating SMTP system SHOULD NOT send a message that
          already contains a Return-path header field.

          Effectively, the Return-Path MIME header is added by the Mail Delivery Agent, and not by the Mail Submission Agent. Further information is spread over the whole section 4.4.

          Дилян Палаузов added a comment - About the Return-Path header, as of RFC 5321, Section 4.4. Trace Information, page 58 says, among other things: A message-originating SMTP system SHOULD NOT send a message that already contains a Return-path header field. Effectively, the Return-Path MIME header is added by the Mail Delivery Agent, and not by the Mail Submission Agent. Further information is spread over the whole section 4.4.

            Unassigned Unassigned
            wosc Wolfgang Schnerring
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: