Email forwarding for git.wordpress.org

Would it be possible to add email forwarding for username@git.wordpress.org like we have for username@chat.wordpress.org for emails from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/?

We currently request committers do it, but there’s a proposal to use Co-Authored-By: .....@git.wordpress.org which would benefit from being able to actually verify the email on GitHub.

In my opinion, this forwarder could be shared with the @chat forwarder, unless it’s super easy to split allowed senders by domain.

#prio3 #email #github

Email rejected as ‘high probability of spam’

There’s been multiple reports over the last few weeks of emails from Gsuite being rejected due to the below details, I’ve been unable to verify it from a gsuite account.

The response from the remote server was:
554 5.7.1 High probability of spam

Here’s one example of it, including the full email headers of the rejection:
https://wordpress.slack.com/archives/C02QB8GMM/p1704295191477689

#email #prio1

Email Forward for forum-moderation

Can we please setup an email redirect for forum-moderation@wordpress.org to support.83653.37ec7bb06f4500a7@helpscout.net?

This is the same destination as the forum-password-resets@ email address.

Thank you in advance.

cc @clorith

#email #prio2 #helpscout

Email forward for Memorials.

Can we please setup an email redirect for memorials@wordpress.org to memorials@mu.helpscoutapp.com?

Thank you!

cc @poliuk

#email #prio2 #helpscout

Spam on mailing lists

Occasionally the WordPress tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. mailing lists (wp-metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., wp-trac, wp-svn) get a spam email slip through.

This one came through yesterday:
https://lists.wordpress.org/pipermail/wp-meta/2023-February/052414.html
Screenshot 2023 02 06 at 12 04 40 pm

After the recent email changes, can the rules for the trac-related mailing lists be tightened to only accept definite 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/ emails?

#email #trac #prio3

FreeScout for WordCamp events

A proposal/idea was put forward from the WordCamp community for us to provide a shared open-source FreeScout instance, in addition to GSuite accounts, rather than every event which wishes to use it setting it up themselves.

Using HelpScout for these is not currently viable due to the cost of provisioning accounts for all events, although larger events may already budget for it themselves (Such as WCUS, WCAsia uses a self-hosted FreeScout instance).

Before any further investigation is put in from our side, I’d like input from Systems on whether this is something that we can provide on our infrastructure, if there are any security concerns, or if this is something we should look at hosting outside of the primary 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/ infrastructure/domains.

Ideally, we’d probably want to host it on a wordcamp.org subdomain, but wordpress.net, or a new domain such as wordcamp-email.com wouldn’t be out of the question.
Authentication would likely be handled through WordPress.org/WordCamp.org, rather than duplicate accounts. We could potentially limit all access to the host with an authentication check that requires a WordCamp.org role, limiting any potential security aspects to those we trust to have WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. access.

FreeScout would require an often-run cron task (PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.), php (with IMAP), and mysqlMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/..

Email ingestion would be similar to how SupportPress/SupportFlow used to work, the cron task uses IMAP to poll the accounts. This could become problematic if we have a lot of inboxes provisioned. It remains to be seen if this is viable with how Google Inboxes are configured as to how IMAP access works.
Email sending would either be direct from the host, via Google SMTP, or via WordPress.org SMTP.

Ongoing maintenance, such as software upgrades, would likely need to be handled by the WordCamp development team. Systems involvement would hopefully be minimal.

This isn’t intended on replacing our usage of HelpScout, unless it proved to be as stable and feature-complete, then that may be looked at later on.

#email #freescout #wordcamp-org #feedback #prio3

Email forwarder hosting@wordpress.org for HelpScout

Can we please have an email forwarder from hosting@wordpress.org to hosting@wordpress.helpscoutapp.com

Ref: https://meta.trac.wordpress.org/ticket/6226

#email #helpscout #prio2

Email forwarder reports@wordpress.org for HelpScout

Can we please have an email forwarder set up from reports@wordpress.org to wp-project-reports@mu.helpscoutapp.com.

This is for some upcoming code-of-conduct stuff. I’ve set up a mailbox on the helpscout side (this is in the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more./Foundation HS instance).

cc @angelasjin.

#email #helpscout #prio2

Update getinvolved@ email forwarder

Can we please update the forwarder for getinvolved@wordpress.org from support@wordcampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. to get-involved-wordpress@mu.helpscoutapp.com

Thanks!

Not high-priority as I’ve got a forward in place on the Helpscout side until changed.

#email #helpscout #prio2

Google Search Console domain access + Postmaster tools

A few of us have access to Google Webmaster/Search tools for https://wordpress.org/ and https://wordpress.org/, but we do not have access for the entire wordpress.org domain which would grant us access to https?://*.wordpress.org/ (ie. what we have + subdomains).

Additionally, The marketing team would like access to Postmaster tools for the email deliverability data, which also requires domain verification.

I can see that there’s two existing Google domain authorisations (dig +short TXT wordpress.org) but I’ve been unable to locate whose Google accounts have access to that when asking around.

Can I please have access granted to the domain-level Search Tools / Postmaster tools so that I can provide access to those who need it?

In the event that systems do not have domain-level access, here’s some instructions to get it:
1. Grant my a8c account verification access and I’ll deal giving those who need it; add wordpress.org TXT google-site-verification=RLa_vaBBembqlBHv2iGePxw7Cw2nQhbYjKLX7HWpSks (I’ll add systems a8c account for future uses. If option 2 is taken, I’ll remove this auth attempt from my account)
or
2. Visit Postmaster tools, Add a domain, get the TXT record and add it. Grant my a8c google account access + plus that of @eidolonnight to Postmaster + Search Console (Full access please). Verifying the domain for postmaster tools will also grant search console verification.

#prio1 #email #google