Reverse DNS for WordCamp.org

Transactional emails coming from the WordCamp.org web server are getting dinged on their SpamAssassin score for not having correct Reverse DNS.

https://mxtoolbox.com/SuperTool.aspx?action=ptr:198.143.164.106

Presumably, the PTR should point to wordcamp.org instead of wordpress.org. This is the SpamAssassin rule message:

0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

0.8 is almost 20% of the default spam threshold of 5, which gives us a lot less of a buffer, and we believe it’s contributing to ongoing reports of messages being flagged as spam.

Could we get the PTR record amended to address this issue?

Related: https://make.wordpress.org/systems/2016/11/23/wordcamp-forwarder-emails-blocked/

#prio2

WordCamp Deployments broken

Deploys were initially working after they were setup, but the past few days it it looks like they’ve stopped working, or are only partially working. The script still reports that it finished successfully, but the effects of commits are not showing up anymore.

It used to take about a minute to finish, but now it finished almost immediately, so I wonder if part of it is dying early or something. If I svn up on my sandbox, the commits are there; it’s just production that doesn’t have them.

Here’s two examples:

  • https://meta.trac.wordpress.org/changeset/6625

Browse to https://central.wordcamp.org/wp-admin/post.php?post=3044783&action=edit&classic-editor, look at the Contact Information metabox. If the commit is applied, you’ll see * at the end of most of the input fields.

  • https://github.com/coreymckrill/wordcamp-reports/commit/31c6f66566fde5e3986b44a845798df622977cf7

This is setup as an svn:external to plugins/wordcamp-reports. We’ve never had problems using GitHub as an external before.

Browse to https://central.wordcamp.org/wp-admin/index.php?page=wordcamp-reports&report=ticket-revenue, you should see a field instead of the field

#prio1

PDF generation doesn’t work on new WordCamp server

Hi, it doesn’t look like wkhtmltopdf has all of its dependencies on the new server:

wkhtmltopdf -d 300 -T ’10’ -R ’10’ -B ’10’ -L ’10’ ‘/tmp/wcdocs_5a831fa5c3b96/sponsorship-agreement.pdf.html’ ‘/tmp/wcdocs_5a831fa5c3b96/sponsorship-agreement.pdf’

wkhtmltopdf: error while loading shared libraries: libXrender.so.1: cannot open shared object file: No such file or directory

#prio1

Access to WordCamp error logs

With the new sandbox setup, we no longer have direct access to the error logs on production, which will make it difficult to learn about and reproduce errors in order to fix them.

I have a couple ideas about potential solutions, but I’d like to know if Systems has any thoughts or preferences.

1) Pipe errors into Slack, the same way that w.org does. This would require setting up object caching (to rate limit the API hits, per Slack’s ToS). IIRC, @kovshenin looked into this a few years ago, and determined that there was a non-trivial amount of code that would need to be refactored in order to make it work. Konstantin, do you remember the details there?

2) Setup a cron job on production to parse the raw error log on disk, reduce it to the relevant/limited entries, and push those to Slack.

3) Setup a cron job on production to copy the raw error logs from production to sandboxes every ~60 seconds. They’d need a different name than the sandbox error logs, so that we could have both.

@coreymckrill and I could write any scripts that are necessary, etc.

Do you see any problems with any of those, or have any other ideas or suggestions?

#prio2

Announce WordCamp deployments in Slack

This is a low priority, but it’d be helpful to announce wordcamp.org deployments in Slack, like we do with wordpress.org.

I added support for it to deployed.php in [dotorg13900], and tested the necessary changes to the deploy script in ~/deploy-wordcamp-tmp.sh on my sandbox.

Someone from Systems will need to commit/deploy those to the actual script, though.

Thanks 🙂

#prio3

Hello, can you please setup…

Hello, can you please setup proxy access for @nao and @chantalc? As polyglots mentors they’ll be helping out with managing rosetta sites and need access to the global.wordpress.org network.

For @nao you can use her a8c key, for @chantalc:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCwrC2ENYnWN3DKyMLRMjx2frHCAx5An+CDHQHPE7fdJux8F4pW7ACkioLBDK7gLRIf2OsszlN7ERMth8QiIP5hytKQJg+qoBUy4rSsvfMZx096EcybHP6yPc9BhvQJsEIy+PFFXeT9btcKHDpdBLrv6oiSo+WyW3YzBefuZoCygHXQwIYauNohsZKJkYX3g1PU4CyLny9TBFHPeizv9Endoreye5YJvGkPnsePGc14Ght8pmeGS/V1R6KCJ5r4AbEpZv1Wu6uPMEyKmKuNXj/Ur42qK6bN+Wb/L1HTcqENSsnbzR/bcRpU/tYOfzJYr/gMPlkLp7HEsiVh9oP6j5/98iywzQ8DNotnj2Hsv7DfS7EvvlMCI1Ih8l3MIzBfKFUEMlbQXrIsk4Y5vV9PP4NguYZReGo2kf7aDh5J9W36Oc43KIdmLectHjakrcMoHuFWA/d8xlhI2IQrequZjnrsLqY9YTCoSQ2zuDFHTRt/vaXDV/TvdCdIbTU0DIgsxHa/HEwp2PdcBopeL9MMU0mOAWfONtj1KjZ4iOzpsSz0K72iGxs6Di2WqS0TI7Yg3lkYPgkg3PVkey7HJ9PeKeJ3BxomNlkfU8EUMOPfWNUnAfK8Ou/AatqZSWr/9nvBNimEEaRqblRkdE4lgClOahrNuJBlZlv3y0xlPdg/o3Bycw== chantal@webpressed.nl

Thank you!

#prio2

Could you please forward `http://word.press`/`https://word.press`…

Could you please forward http://word.press/https://word.press to https://wordpress.org? @matt okay’d the change.

See https://meta.trac.wordpress.org/ticket/2726

#prio3

wp15.wordpress.net

Could you please create a site for wp15.wordpress.net?

We’ll also need a MySQL database, and SSH for @coreymckrill and myself, but if cPanel allows then I can do those myself.

Thank you 🙂

#prio2

Could you please add a…

Could you please add a redirect from wordpress.org/blog to wordpress.org/news, to not have that be a dead end anymore?

See https://meta.trac.wordpress.org/ticket/1416

Thanks!

#prio3

Can I please have commit…

Can I please have commit access granted to both buddypress.svn.wordpress.org and bbpress.svn.wordpress.org for the WordPress.org username espellcaste?

Renato is a several-year contributor to both projects. He will be working on merging his WP-CLI work into the bb’s, and I expect him to stick around once that work is complete.

We had the Uncle Ben call together last week to set expectations, and he has secure passwords on all of the relevant things.

#buddypress, #bbpress, #commit, #prio3