I've had several reports that g.d.o mails are getting into spam folders and/or being rejected by recipient's mail servers because the address no-reply@groups.drupal.org doesn't exist and therefore fails a requirement of "reject_unverified_sender". I believe this is or was also true for no-reply@drupal.org

Could someone create these mail accounts and just set them to delete any incoming mail?

Comments

scottprive’s picture

scottprive commented

Another improvement would be to remove graylisting on the mailbox.
When I tested noreply@drupal.org I got a graylist (451) response:

...
rcpt to:noreply@drupal.org
451 4.7.1 : Recipient address rejected: Greylisted for 5 minutes
quit

I would take a guess that you graylist by IP address, automatically.
Depending on your provider, it may or may not be possible to globally exempt just 1 mailbox from graylisting.

If you can not exempt the noreply@ mailbox from graylisting, you might have different outcomes depending on the user's MX policies.

a) the sender verify can not complete, due to the graylist, and the Drupal user's MX accepts the message and tags it as possible spam.
b) the sender verify can not complete, due to the graylist, and the Drupal user's MX issues a defer/graylist on the Drupal.org email. Eventually it works when Drupal.org lifts the graylist, then the user's mailserver will allow itself to accept the next delivery attempt by drupal.org.

I expect "a" more often than "b" but you could get both problem report types. If you DO, ask the users for the FULL email headers of that message (assuming they actually got it, not blackholed, of course). Or PM me the headers/example. I could maybe suggest something based on that, but I don't want to confuse the issue by getting ahead. :-)

TEST:
scott@stout:~$ telnet smtp3.osuosl.org 25
Trying 140.211.166.136...
Connected to smtp3.osuosl.org.
Escape character is '^]'.
220 silver.osuosl.org ESMTP Postfix
helo xyz
250 silver.osuosl.org
mail from:[redacted]
250 2.1.0 Ok
rcpt to:noreply@drupal.org
451 4.7.1 : Recipient address rejected: Greylisted for 5 minutes
quit
221 2.0.0 Bye
Connection closed by foreign host.

I also tried a second test, using SMTP "VRFY" command, but the Drupal.org server does not recognize this command. If that worked it is an alternate method of sender verify callback verification. VRFY failing is perfectly normal (many servers disable it).

gerhard killesreiter’s picture

gerhard killesreiter commented

noreply@ accounts have been created.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Fixed

I've checked with the OSL and we annot remove the graylisting from these addresses. Marking this fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

basic’s picture

basic commented
Issue summary: View changes
Status: Closed (fixed) » Active
Related issues: +#2087411: [Meta] Integrate CDN with *.drupal.org

Setting this up for groups.drupal.org required moving the site from a CNAME to an A record, which blocks moving groups.drupal.org behind our CDN. noreply@drupal.org is fine, but noreply@groups.drupal.org is problematic due to the use of the subdomain.

Can we get the site from address for groups.drupal.org updated to noreply+groups@drupal.org? This should make it easy for people to continue filtering these emails, meanwhile letting us remove the MX records on the subdomain.

This is a new problem because it prevents us from deploying the CDN behind sites which are not CNAMEs: https://tools.ietf.org/html/rfc2181#section-10.3

sreynen’s picture

sreynen commented
Status: Active » Fixed

I updated the site from address to noreply+groups@drupal.org.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Component: Mail » Servers