Help:Toolforge/Email

Toolforge

• Cloud Services overview
• Toolforge user docs
• Toolforge changelog

Get started

• Quickstart: set up and get access
• How Toolforge works
• Rules you must follow
• Tutorials

Build and run tools

• Navigate tool accounts and files
• Build container images for tools
• Run a web service
• Schedule and manage jobs
• Manage tool runtime configuration (envvars)
• Deploy your tool on every push (beta)
• Language-specific details:
  • Python
  • Pywikibot
  • Node.js
  • PHP
  • ...more languages/frameworks
• Use Redis for caching
• Index content with Elasticsearch

Access shared storage and databases

• Access shared storage and public wiki dumps
• Access the Wiki Replicas databases
• Access replica search indices
• Manage tool databases
• Sending and receiving email as tools

Share and maintain tools

• Set up version control and code review
• Develop successful tools
• Find and share tools on Toolhub
• Delete a tool

Get help

• How and where to get help
• Troubleshooting
• Contribute to Toolforge

Useful links

• Toolforge admin docs
• List of tools
• Toolforge Admin Console (toolsadmin)
• Toolforge API

[]

This page covers using sending email to users, tools, and from programs running in Toolforge.

Please note that Toolforge emails servers enforce ratelimits per email address.

Mail to users

Mail sent to user@toolforge.org (where user is a shell account) will be forwarded to the email address that user has set in their developer account preferences. You can update your email address using idm.wikimedia.org.

Any existing .forward in the user's home will be ignored.

Mail to a Tool

Mail can also be sent "to a tool" with:

toolname.anything@toolforge.org

Where "anything" is an arbitrary alphanumeric string. Mail will be forwarded to the first of:

• The email addresses listed in the tool's $HOME/.forward.anything, if present;
• The email addresses listed in the tool's $HOME/.forward, if present; or
• The email addresses of the tool's maintainers.

Additionally, tools.toolname@toolforge.org is an alias pointing to toolname.maintainers@toolforge.org mostly useful for automated email generating from within Cloud VPS.

$HOME/.forward and $HOME/.forward.anything need to be readable by the user Debian-exim; to achieve that, you probably need to explicitly make the file world readable with a shell command like chmod o+r $HOME/.forward*.

All of these addresses can also be used via the legacy tools.wmflabs.org domain

Mail from Tools

The Toolforge mail servers are primarily intended for transactional mail from applications running in Toolforge. You must receive approval from the Toolforge admin team before using the Toolforge mail servers to send bulk mail.

The SMTP protocol can be used to send outbound emails from a tool running in Toolforge. The mail.tools.wmcloud.org service name is used as the public mail exchange (MX) host for inbound SMTP messages to the toolforge.org (and the old tools.wmflabs.org domain) domain and points to a server that can process both inbound and outbound email for Toolforge.

Containers running on the Toolforge Kubernetes cluster do not install and configure a local mailer service. Tools should instead send email using an external SMTP server. The mail.tools.wmcloud.org service name should be used as the target SMTP server.

You should use an email address controlled by your tool as the From: address for outgoing email.

See also

• Help:Email in Cloud VPS

Communication and support

Support and administration of the WMCS resources is provided by the Wikimedia Foundation Cloud Services team and Wikimedia movement volunteers. Please reach out with questions and join the conversation:

Discuss and receive general support

• Chat in real time in the IRC channel #wikimedia-cloud ^connect or the bridged Telegram group
• Discuss via email after you have subscribed to the cloud@ mailing list

Stay aware of critical changes and plans

• Subscribe to the cloud-announce@ mailing list (all messages are also mirrored to the cloud@ list)
• Read the News wiki page

Track work tasks and report bugs

Use a subproject of the #Cloud-Services Phabricator project to track confirmed bug reports and feature requests about the Cloud Services infrastructure itself

Read stories and WMCS blog posts

Read the Cloud Services Blog (for the broader Wikimedia movement, see the Wikimedia Technical Blog)