A quick test using a gmail e-mail account gives the following error:

Failed to connect to ssl://smtp.gmail.com:465 [SMTP: Failed to connect socket: fsockopen(): unable to connect to ssl://smtp.gmail.com:465 (Unknown error) (code: -1, response: )]

so we will also likely need to poke the firewall a bit.

T185879: Decide on url for wiki Is probably a blocker for this if we want to ensure that there is a clear connection between the e-mail address and the wiki.

Url has been decided and so has the e-mail address. Waiting for SU to figure out how they want to solve it on their end.

Can this task be included in the migration of the wiki so that when it is up and running again, the back end email is ready to go??

This task is being blocked by SU.

They have offered noreply[AT]su.se which can be used today. It however does not make it obvious that the wiki is the sender nor does it authenticate the sender, making phishing possible (but still unlikely).

At last contact SU were investigating samsynwiki[AT]su.se but had yet to figure out how to solve it. I've today sent them a reminder about this.

My suggestion is:

• If SU IT gets samsynwiki@ up and running before Kreablo migrates the wiki, then we ask Kreblo to make use of this when they set up the wiki.
• If SU IT haven't resolved the issue before then, then we ask Kreblo to make use of noreply@ when they set up the wiki.

SU IT got back to us and said we should use samsynwiki-noreply@ for this.

I've activated this using the settings below and verified that it works! (The relevant page on SU IT is this one.)

For now this uses unencrypted smtp, I've asked SU IT if STARTTLS is available for the noreply@ addresses.

$wgSMTP = array(
	"host"     => "smtp.su.se",
	"IDHost"   => "su.se",
	"port"     => 25,
	"auth"     => false,
	"username" => "samsynwiki-noreply@su.se",
);

Nope no SRARTTLS for us

Quick note that I set emergency contact to drift[AT]wikimedia.se since these are e-mails that we wish to receive.