When replying to a Confluence notification email, customers receive a standard DSN failure return

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Summary

      When replying to a notification e-mail from Confluence, users receive a standard DSN failure message for non-delivery, this message could be replaced with an e-mail with a more friendly message to the users, advising them to not respond to Confluence notifications e-mails.

      Environment

      Confluence Cloud version 1000.842.0, all version.

      Steps to Reproduce

      1. Watch a page in Confluence
      2. Add something to the page, receive a notification, reply to the notification message and receive a DSN standard 550 5.1.1 failure to delivery.

      Expected Results

      Confluence e-mail server returns with a more friendly message.

      Actual Results

      The message returned from Confluence e-mail server.

      Delivery Status Notification (Failure)
      Mail Delivery Subsystem <mailer-daemon@googlemail.com>
      Address not found 
      Your message wasn't delivered because the address wiki@customerinstance.atlassian.net couldn't be found. Check for typos or unnecessary spaces and try again.
      The response from the remote server was:
      550 5.1.1 <wiki@customerinstance.atlassian.net>: Recipient address rejected: User unknown in virtual mailbox table
      -Attachment-
      Reporting-MTA: dns; googlemail.com
      Received-From-MTA: dns; customermail@customermail.com
      Arrival-Date: Thu, 19 Jan 2017 10:20:25 -0800 (PST)
      X-Original-Message-ID: <ID@customerinstance.com>
      Final-Recipient: rfc822; wiki@customerinstance.atlassian.net
      Action: failed
      Status: 5.1.1
      Remote-MTA: dns; mx-131XXXXX. (XXXXXXX, the server for the
      domain customerinstance.atlassian.net.)
      Diagnostic-Code: smtp; 550 5.1.1 <wiki@customerinstance.atlassian.net>: Recipient address rejected: User unknown in virtual mailbox table
      Last-Attempt-Date: Thu, 19 Jan 2017 10:20:28 -0800 (PST)
      

      Workaround

      No Workaround for Cloud at least.

            Assignee:
            Unassigned
            Reporter:
            rsendra
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: