Issue #8413 resolved

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

Holger (stars-h) avatarHolger (stars-h) created an issue

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):

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'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):

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'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.

Comments (7)

  1. FWT User

    ddbennett: Erik has "resolved" this issue without any explanation ... we also see bounces, so the Envelope Sender address notifications-noreply@bitbucket.org IS being used by Bitbucket:

    2013-12-02 21:51:35 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.66.26] 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'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 eg8si4468738wib.7 - gsmtp
    
    2013-12-02 21:51:35 H=lb01-ash.bitbucket.org (lb01.bitbucket.org) [131.103.20.165] F=<notifications-noreply@bitbucket.org> rejected RCPT <...>: Sender verify failed
    

    Could you please fix your incoming mail server, just like you kindly did for issue 8409 - many thanks.

  2. Dan Bennett

    Our Ops guy added those email address aliases and Erik closed the issue at my request. I'll reopen and follow up with ops. I apologize for the confusion.

  3. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.