notifications-noreply@bitbucket.org no longer working - Bitbucket using a fake/non-existing Envelope Sender address causes e-mail rejections (BB-9552)

XMLWordPrintable

      Please fix the e-mail address notifications-noreply@bitbucket.org - it currently does not exist.

      Up until last month, the e-mail address notifications-noreply@bitbucket.org was working fine - your incoming mail server accepted DSNs for this address, for example, on these two occasions (extracts from our e-mail service provider's mail server log):

      #!text

2013-10-15 19:33:51 1VW9RG-00081a-65 <= notifications-noreply@bitbucket.org H=lb01-ash.bitbucket.org (lb01.bitbucket.org) [131.103.20.165] S=9926 id=20131015183340.13526.83736@app03.ash-private.bitbucket.org T="You&#x27;ve been invited to collaborate on ... on Bitbucket" from <notifications-noreply@bitbucket.org> for ...

2013-10-15 19:35:18 1VW9Sg-00081r-43 <= notifications-noreply@bitbucket.org H=lb01-ash.bitbucket.org (lb01.bitbucket.org) [131.103.20.165] S=5542 id=20131015183505.25704.55902@app04.ash-private.bitbucket.org T="[Bitbucket] You have been given write access to ..." from <notifications-noreply@bitbucket.org> for ...

      However, today it appears that the address notifications-noreply@bitbucket.org no longer exists but is still used for your outgoing e-mails, e.g. for repository access invitation messages. As a result many users with stricter spam filtering will be unable to receive these messages from Bitbucket (extract from our e-mail service provider's mail server log):

      #!text

2013-11-09 07:17:47 H=lb01-ash.bitbucket.org (lb01.bitbucket.org) [131.103.20.165] sender verify fail for <notifications-noreply@bitbucket.org>: response to "RCPT TO:<notifications-noreply@bitbucket.org>" from aspmx.l.google.com [173.194.78.27] was: 550-5.1.1 The email account that you tried to reach does not exist. Please try\n550-5.1.1 double-checking the recipient&#x27;s email address for typos or\n550-5.1.1 unnecessary spaces. Learn more at\n550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 ba8si2515662wib.6 - gsmtp

2013-11-09 07:17:47 H=lb01-ash.bitbucket.org (lb01.bitbucket.org) [131.103.20.165] F=<notifications-noreply@bitbucket.org> rejected RCPT <...>: Sender verify failed

      I can understand that you do not want to receive things like bounce messages and auto-replies, but please do not reject DSNs after "RCPT TO" during the SMTP conversation. Either accept DSNs and route them to the bin or reject them after the "DATA" stage during the SMTP conversation.

      I hope this bug report helps to bring your system back to the usual reliability we are used to.

            Assignee:
            Unassigned
            Reporter:
            stars-h
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: