We could use the human-readable wiki name messages that we created for cross-wiki notifications.

@jmatazzoni , @Pginer-WMF

We need to decide where we display the wiki name and what is the language around it.

One option is to use the human-readable wiki names and come up with a standard prefix or suffix in the email subject or body. That would clarify it for all notification types at once.

We need to decide where we display the wiki name and what is the language around it.

For the where question, can someone post a screenshot of what the email looks like now?

For the language question, can we use the human-readable names that we worked out for the x-wiki bundles in the panel?

Here's a screenshot:

(I blanked the admin's name for privacy.) The only way to find out which Wikipedia this comes from is to hover over or click on the links in the message.

It seems that the issue is that while on the notification panel/page the context on which actions take place is clear (you know in which Wikipedia you are), all email notifications end up in the same inbox making it hard to know which wiki they refer to.

I think it makes sense to indicate the project in email notifications by using the human-readable names and without adding complexity to the regular notifications.

Including the project+language text as part of either:

• The email subject. In the example it could be "Your user rights have changed on English Wikipedia". However, integrating the human-readable text as part of another sentence may not be easy due to localisation (i.e., the "English Wikipedia" part requiring grammar adjustments when it is part of a sentence in some languages). A more structured construction can be considered if that is the case: "Your user rights have changed (English Wikipedia)" or "English Wikipedia: Your user rights have changed"
• The sender name. Currently the sender seems to be named just "Wikipedia", it could be more specific ("English Wikipedia") to provide the missing context.

In both cases the user receiving an email would be aware of the context even before opening it since sender and subject are surfaced by email clients.

I like the idea of using the human-readable site name as the sender's name.

It's kind of what we do already except better. We use the message emailsender, which contains {{SITENAME}}.

{{SITENAME}} is not enough, and that appears to be the sole contents of emailsender. {{SITENAME}} is just "Wikipedia", not "English Wikipedia".

Both Notifications and watchlist-related e-mail messages arrive from "Wikipedia" (or Wikipédia", or Википедия or Վիքիպեդիա or whatever the local language is. But sending me a message in a script that I can read is a separate Phab ticket).

In T122229#2410874, @Whatamidoing-WMF wrote:

{{SITENAME}} is not enough, and that appears to be the sole contents of emailsender. {{SITENAME}} is just "Wikipedia", not "English Wikipedia".

Yes, we realize that. "English Wikipedia" is what we call the "human-readable site name". Stephane observed that we currently use {{SITENAME}} but that we could use the human-readable site name instead.

In T122229#2410874, @Whatamidoing-WMF wrote:

But sending me a message in a script that I can read is a separate Phab ticket).

This change would actually fix that in some cases as well: the human-readable site names are translatable (although not all languages have translated all ~800 of them), while {{SITENAME}} is not. So if you have customized your language preference on a wiki, that wiki would use your language for the wiki name as well as the rest of the message. Without global preferences, though, there will still be many wikis where your language preference is still set to that wiki's language because you never changed it.