Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34817

Notification not being sent by email from the Project Notification scheme

XMLWordPrintable

      Steps to Reproduce:
      Set an email address different than the Outgoing mail server email in the Project Notification Scheme
      Send an email message to the Incoming mail server

      Expected Results:
      Issue is created and notification is sent by the different email address changed in the Project Notification scheme as mentioned here

      Actual Results:
      Issue is created correctly, but notification is sent by the default address from the Outgoing mail server

          Form Name

            [JRASERVER-34817] Notification not being sent by email from the Project Notification scheme

            Oswaldo Hernandez (Inactive) added a comment -

            Hi matt.doar,

            I understand where you are coming from. In order to completely address, we would have had to rewrite the whole way JIRA stores email accounts per project and how it sends such email, basically a feature rewrite, which falls outside of the scope of what we can do in terms of bugfixing. Therefore, we decided to warn the user clearly about the situation such that the problem is less likely to reoccur in the future.

            Following on, I will raise a "suggestion" issue and link it to here for the refactor/rewrite mentioned above.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - Hi matt.doar , I understand where you are coming from. In order to completely address, we would have had to rewrite the whole way JIRA stores email accounts per project and how it sends such email, basically a feature rewrite, which falls outside of the scope of what we can do in terms of bugfixing. Therefore, we decided to warn the user clearly about the situation such that the problem is less likely to reoccur in the future. Following on, I will raise a "suggestion" issue and link it to here for the refactor/rewrite mentioned above. Cheers, Os.

            MattS added a comment -

            A better resolution might be something such as "Incomplete" since the underlying problem still exists

            MattS added a comment - A better resolution might be something such as "Incomplete" since the underlying problem still exists

            Michelle Zeng added a comment -

            After investigation, we found the problem is caused by some public email services(e.g.: Gmail, hotmail ) prevent using a from address other than the one which account has been authenticated. This is a security measure to avoid the attach known as spoofing. To solve this issue properly, we need to re-design the outgoing email config module which would take quite an effort. For the moment, we’ll add a message to warn the user that this function might not work with some email services.

            Michelle Zeng added a comment - After investigation, we found the problem is caused by some public email services(e.g.: Gmail, hotmail ) prevent using a from address other than the one which account has been authenticated. This is a security measure to avoid the attach known as spoofing. To solve this issue properly, we need to re-design the outgoing email config module which would take quite an effort. For the moment, we’ll add a message to warn the user that this function might not work with some email services.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              malmeida Marcus Silveira
              Affected customers:
              4 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: