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

Support for HTML emails with plaintext alternative only available when configured per project

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • email-ext-plugin
    • None

      It is useful to send HTML e-mails with a plaintext alternative. Using HTML-only mails causes SpamAssassin to increase the spam score for those e-mails via the rule MIME_HTML_ONLY BODY.

      The sending of HTML mails with automatically generated plaintext alternatives was introduced with JENKINS-23126 . It is possible to configure a project to use a Content Type of "Both HTML and Plain Text". However, this option isn't available on the Jenkins-wide configuration page (i.e. the one reachable via "Manage System").

       This seems like an oversight to me. Allowing this option on the system-wide page would allow all projects to inherit it by selecting the choice "Default Content Type" for Content Type in their configuration.

       

          [JENKINS-41473] Support for HTML emails with plaintext alternative only available when configured per project

          Erik Brangs created issue -

          Erik Brangs added a comment -

          I edited the issue to reflect the fact that the support is actually available but not where I expected to find it.

          Erik Brangs added a comment - I edited the issue to reflect the fact that the support is actually available but not where I expected to find it.
          Erik Brangs made changes -
          Description Original: The HTML e-mails that are sent with the email ext plugin currently don't have a plaintext alternative. This causes SpamAssassin to increase the spam score for those e-mails via the rule {{MIME_HTML_ONLY BODY}}.

          It would be nice if it were possible to define a plaintext alternative for HTML mails. I suppose this would fit under a new content type "multipart/mixed" in the UI.

          This seems to have been previously reported as JENKINS-19252 but AFAICT the reasons for the request were different back then.
          New: It is useful to send HTML e-mails with a plaintext alternative. Using HTML-only mails causes SpamAssassin to increase the spam score for those e-mails via the rule {{MIME_HTML_ONLY BODY}}.

          The sending of HTML mails with automatically generated plaintext alternatives was introduced with JENKINS-23126 . It is possible to configure a project to use a Content Type of "Both HTML and Plain Text". However, this option isn't available on the Jenkins-wide configuration page (i.e. the one reachable via "Manage System").

           

          This seems like an oversight to me. Allowing this option on the system-wide page would allow all projects to inherit it by selecting the choice "Default Content Type" for Content Type in their configuration.

           
          Issue Type Original: Improvement [ 4 ] New: Bug [ 1 ]
          Priority Original: Trivial [ 5 ] New: Minor [ 4 ]
          Summary Original: Add support for HTML emails with plaintext alternative New: Support for HTML emails with plaintext alternative only available when configured per project
          Erik Brangs made changes -
          Description Original: It is useful to send HTML e-mails with a plaintext alternative. Using HTML-only mails causes SpamAssassin to increase the spam score for those e-mails via the rule {{MIME_HTML_ONLY BODY}}.

          The sending of HTML mails with automatically generated plaintext alternatives was introduced with JENKINS-23126 . It is possible to configure a project to use a Content Type of "Both HTML and Plain Text". However, this option isn't available on the Jenkins-wide configuration page (i.e. the one reachable via "Manage System").

           

          This seems like an oversight to me. Allowing this option on the system-wide page would allow all projects to inherit it by selecting the choice "Default Content Type" for Content Type in their configuration.

           
          New: It is useful to send HTML e-mails with a plaintext alternative. Using HTML-only mails causes SpamAssassin to increase the spam score for those e-mails via the rule {{MIME_HTML_ONLY BODY}}.

          The sending of HTML mails with automatically generated plaintext alternatives was introduced with -JENKINS-23126- . It is possible to configure a project to use a Content Type of "Both HTML and Plain Text". However, this option isn't available on the Jenkins-wide configuration page (i.e. the one reachable via "Manage System").

           This seems like an oversight to me. Allowing this option on the system-wide page would allow all projects to inherit it by selecting the choice "Default Content Type" for Content Type in their configuration.

           
          Basil Crow made changes -
          Assignee Original: David van Laatum [ davidvanlaatum ]
          Basil Crow made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]

            Unassigned Unassigned
            ebrangs Erik Brangs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: