Helpscout cannot email to @wordpress.org…

Helpscout cannot email to wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ from wordpress.org

Occasionally there’s the need for Helpscout inboxes, which are @wordpress.org inboxes to send emails to other @wordpress.org email addresses, these might be just CC’ing a given WordPress.org user, or forwarding an email to a different Helpscout instance.

Unfortunately, it appears that this is currently blocked by the WordPress.org SMTP servers. Can we allow HelpScout to send-as wordpress.org to WordPress.org?

The relevant part from the bounce is: (noting, I’ve replaced the inboxes for spam purposes, dpo is the sender, and recipient was security in this case)

Final-Recipient: rfc822;mailbox-here@wordpresss.org
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;mail.wordpress.org (198.143.164.147)
Diagnostic-Code: smtp;554 5.7.1 <helpscout-inbox@wordpress.org>: Sender address rejected: Access denied
X-PowerMTA-BounceCategory: invalid-sender

The bounce email is available here: https://secure.helpscout.net/conversation/1966354976/301771 and stored in the private PasteBin as #184485 with ID of 2d0a5. (Alternatively, ask a Neso team member for a copy of the email if you’re unable to locate that and unable to locate the HS credentials)

#mail #helpscout #prio3

mail.wordcamp.org disk space

We’re getting low on disk space for mail.wordcamp.org again; it was down to ~2 GB today. I pruned some things and got it back up to ~6 GB, but wanted to get the ball rolling on a long-term solution.

The Community Team has discussed this in the past and decided that we’d strongly prefer to not delete old messages, because we sometimes need to go back and reference them. For Central’s accounts, there are also some legal restrictions around contracts, etc that need to be kept.

The last time this happened, sysmonk increased the space from 20 GB to 50 GB, but we’ve used that up in the past two years. We’re expecting to have about 125 WordCamps this year, and that’s growing 10% – 15% each year, so I don’t think the current solution is going to work for much longer, unless we can get a much larger chunk of the 300 GB available on the server.

What kind of options would you recommend? It might be good to answer the SSL/webmail question first, since we might end up migrating to Google Apps or something if modern webmail isn’t an option.

#disk-space, #mail, #wordcamp-org