1318313 - Some services (wiki) use <[e-mail]> as envelope sender but it doesn't exist (550)

Status: RESOLVED WONTFIX

(Infrastructure & Operations :: Infrastructure: Mail, task)

Description

[Peter Gervai]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20161116030212

Steps to reproduce:

Tried to register on the wiki. 
Possibly other registrations use the same email.


Actual results:

sender verify fail for <[e-mail]>: response to "RCPT TO:<[e-mail]>" from aspmx.l.google.com [2a00:1450:400c:c0a::1a] 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  https://support.google.com/mail/?p=NoSuchUser x11si2702317wjd.121 - gsmtp                                                                                                                                                                                    



Expected results:

Well, receiving the mail. 
Resolution:
a) create [e-mail] and handle it (/dev/null, mailbox, else), or
b) use a sender which does exist.

Comment 1

[Greg Cox [:gcox]]

Just found this while looking over old bugs. I'm going to WONTFIX this.

From a mail perspective, no-reply@ "does what it says on the tin" - your mail didn't get in front of eyes. There's no fundamental difference between 'a mail that bounced as undeliverable' or 'a mail that went to /dev/null' in that regard. That said, I posit that no-reply@ being missing is more informative for a sending user: you know it didn't get received, as opposed to just ignored. In that regard, I decline to pursue this.

If the assertion is that a service should have a valid reply address, that is for each service to decide, rather than the mail system as a whole.

Sorry that this bug languished for this long without a traction.