NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      Attempting to configure mail in a shared mailbox setting fails with an authentication error.

      Steps to Reproduce

      This was reproduced with Office365, however will also occur on other mail servers.

      1. Setup a shared Office365 mailbox.
      2. Attempt to setup an Email Channel using JIRA Service Desk with the below configuration:
        • username: <O365 user name>/<shared mailbox name>
        • password: <O365 user password>

      Expected Results

      JIRA Service Desk is able to connect to the mailbox.

      Actual Results

      The below error is presented in the logs and the authentication fails:

      2015-02-26 20:35:20,904 http-bio-8080-exec-2 ERROR captain.planet 1235x15715x1 j7sdem 192.168.16.91 /rest/servicedesk/1/servicedesk/PEWPEW/incomingemail/validateemailforcreation [servicedesk.squalor.email.MailServerVerifier] Unable to connect to the server at outlook.office365.com due to the following exception: Unfortunately JIRA Service Desk couldn't connect to the mail server. Here is what the mail server said: "AUTHENTICATE failed."
      

      Additionally the below error can occur during configuration:

            [JSDSERVER-1596] Unable to use a shared mailbox

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304542 ] New: JAC Bug Workflow v3 [ 3125035 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058320 ] New: JSD Bug Workflow v5 - TEMP [ 2304542 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2055375 ] New: JSD Bug Workflow v5 [ 2058320 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956174 ] New: JSD Bug Workflow v5 - TEMP [ 2055375 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615578 ] New: JSD Bug Workflow v5 [ 1956174 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary

            Attempting to configure mail in a shared mailbox setting fails with an authentication error.

            h3. Steps to Reproduce

            This was reproduced with Office365, however will also occur on other mail servers.

            # Setup a shared Office365 mailbox.
            # Attempt to setup an Email Channel using JIRA Service Desk with the below configuration:
            #* *username:* {{<O365 user name>/<shared mailbox name>}}
            #* *password:* {{<O365 user password>}}

            h3. Expected Results

            JIRA Service Desk is able to connect to the mailbox.

            h3. Actual Results

            The below error is presented in the logs and the authentication fails:

            {noformat}
            2015-02-26 20:35:20,904 http-bio-8080-exec-2 ERROR captain.planet 1235x15715x1 j7sdem 192.168.16.91 /rest/servicedesk/1/servicedesk/PEWPEW/incomingemail/validateemailforcreation [servicedesk.squalor.email.MailServerVerifier] Unable to connect to the server at outlook.office365.com due to the following exception: Unfortunately JIRA Service Desk couldn't connect to the mail server. Here is what the mail server said: "AUTHENTICATE failed."
            {noformat}

            h3.

            Additionally the below error can occur during configuration:
            !Office365 Shared Mailbox - Not working.jpg|thumbnail!
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1596].
              {panel}

            h3. Summary

            Attempting to configure mail in a shared mailbox setting fails with an authentication error.

            h3. Steps to Reproduce

            This was reproduced with Office365, however will also occur on other mail servers.

            # Setup a shared Office365 mailbox.
            # Attempt to setup an Email Channel using JIRA Service Desk with the below configuration:
            #* *username:* {{<O365 user name>/<shared mailbox name>}}
            #* *password:* {{<O365 user password>}}

            h3. Expected Results

            JIRA Service Desk is able to connect to the mailbox.

            h3. Actual Results

            The below error is presented in the logs and the authentication fails:

            {noformat}
            2015-02-26 20:35:20,904 http-bio-8080-exec-2 ERROR captain.planet 1235x15715x1 j7sdem 192.168.16.91 /rest/servicedesk/1/servicedesk/PEWPEW/incomingemail/validateemailforcreation [servicedesk.squalor.email.MailServerVerifier] Unable to connect to the server at outlook.office365.com due to the following exception: Unfortunately JIRA Service Desk couldn't connect to the mail server. Here is what the mail server said: "AUTHENTICATE failed."
            {noformat}

            h3.

            Additionally the below error can occur during configuration:
            !Office365 Shared Mailbox - Not working.jpg|thumbnail!
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1596 [ JSDCLOUD-1596 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-cloud pm warranty New: affects-cloud affects-server pm warranty
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: pm warranty New: affects-cloud pm warranty
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603091 ] New: JSD Bug Workflow v4 [ 1615578 ]

              cnguyen Chuong Nam Nguyen (Inactive)
              dcurrie@atlassian.com Dave C
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: