Page MenuHomePhabricator

Ensure consistent use of function e-mail addresses
Open, Needs TriagePublic4 Story Points

Description

We have various functional e-mail addresses in use.

We should make sure that these are used instead of personal e-mail addresses, wherever applicable.

This task aims to:

  • Define when and how each functional address should be used.
  • List the places where such addresses should be put in use. Check boxes can be ticked once it has been ensured that they are in use.

This includes, but is not limited to:

  • betala@
  • betalning@
  • drift@

see the list of all of the addresses

Usage of drift@

  • LetsEncrypt
    • wikimedia.se
    • collabora.wikimedia.se
    • nextcloud.wikimedia.se
    • ...
  • Loopia (for tech issues)
  • Binero (for tech issues)
  • FsData (for tech issues)
  • GleSys (for tech issues)
  • Bahnhof (for tech issues)
  • ...

Usage of betala@

Usually, we use info@ when we order things, the only use I've found of betala@ is Kreablo.

  • Kreablo (invoices)
  • Paypal
  • Göteborgs litteraturhus (goes to evelina.bang@ today, so needs to be changed to something else)
  • SJ
  • Glesys (invoices)
  • IIS (invoices)
  • Loopia (invoices)
  • OCT
  • Benevity (information about donations)
  • Tranås resebyrå
  • Vistaprint
  • Bahnhof (invoices)
  • SWAJ Krubb & Kafé

See also T202270: Document use of drift@ email

Event Timeline

Lokal_Profil updated the task description. (Show Details)May 8 2018, 1:11 PM
Lokal_Profil added a subscriber: Sebastian_Berlin-WMSE.
Vvjjkkii renamed this task from Ensure consistent use of function e-mail addresses to vhdaaaaaaa.Jul 1 2018, 1:11 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
CommunityTechBot renamed this task from vhdaaaaaaa to Ensure consistent use of function e-mail addresses.Jul 2 2018, 4:23 PM
CommunityTechBot raised the priority of this task from High to Needs Triage.
CommunityTechBot updated the task description. (Show Details)
Jopparn set the point value for this task to 4.
Lokal_Profil updated the task description. (Show Details)Sep 13 2018, 1:28 PM

@Jopparn, @Evelina-Bang-WMSE note that I and @Sebastian_Berlin-WMSE can only deal with some of these. A bunch of them are related to billing etc.

@Sebastian_Berlin-WMSE Did you update letsencrypt to drift@ as you were handling updates to the certificates?

Lokal_Profil updated the task description. (Show Details)Sep 13 2018, 1:42 PM

@Sebastian_Berlin-WMSE Did you update letsencrypt to drift@ as you were handling updates to the certificates?

For Nextcloud and Collabora, yes. We did get email to drift@ when the previous certificate was running out, but there were multiple emails sent, one of them to info@. Not sure if this will be the case in the future.