use gwdg smtp

[maxheld83]

medium term, we're always going to get a pretty bad rating for our emails unless we get SPF/DKIM (see eg. mailjet docs), which in turn we can only get if:

• we get a verified (sub)domain to use (unlikely / lots of work / unclear why GWDG would agree to that)
• we use the gwdg smtp server

so we should probably do the latter medium term, though it's a hassle to set up (need a special-purpose function email address).

[maxheld83]

doing smtp isn't ideal, generally speaking, because:

• has lots of dependencies (but we need blastula anyway, so not too bad)
• VM/CaaS must allow SMTP. As per these azure docs, we should be alright as long as we use authenticated SMTP over TCP port 587, which gwdg supports

[maxheld83]

there's also the issue that mailjet records the outgoing email addresses, which may cause gdpr issues

[maxheld83]

as discussed with @njahn82 this is becoming a bit of a priority, because, as expected/explained above, lacking SPF/DKIM, some of our emails never make it through.

So GWDG it is; I'll get us the "Funktionsadresse" for this purpose.

I think to protect the GWDG Mailserver, at the least, we'll also have to implement #23 as a precursor for this.

[maxheld83]

just checked back with GWDG what the status is under ticket G#2020120410000619

[hwhw]

This is most probably "DB", as in the department DB. In any case I don't think public github issues are the right place to discuss organizational info including mail addresses.

[maxheld83]

thanks for the pointer. I'm not sure how a non-personal email address is sensitive information (or the organisational structure of SUB, which is public anyway) -- but sure, I've deleted the comment in question. I'm trying to concentrate all information in one place excluding anything personal of course.

The user was not "DB", but the other one (now deleted).

My confusion stems from the fact, that I don't recall/know how/why "x" is involved in co-signing the request, or who "x" even is, but this is probably all on my end.