Functional Design: E-mail report

[TwistMeister]

• [x] ~Think about and document the desired flow te create a report~ : look at the designs that were made earlier
• [ ] Find out what a user wants to find in this report?
• [ ] -- Overview of E-mail related DNS-records and their configs
• [ ] -- Mailserver status
• [ ] -- "Rijkseisen"?
• [ ] Content proposal (wireframes)
• [ ] Review with Noemi (optional?)

[stephanie0x00]

I think the following components should definitely be in this report:

Email report:

• Open ports (IMAP, SMTP, POP3)
• TLS/SSL config of the services (to check if the server supports secure ciphers)
• MX records
• IPv4/IPv6 connectivity (mandatory for e-mail by Forum Standaardisatie for the Dutch government)
• STARTTLS/DANE/DMARC/DKIM/SPF (mandatory for e-mail by Forum Standaardisatie for the Dutch government)
• IMAP/SMTP are recommended by Forum Standaardisatie. These are government specific checks, for other environments the use of POP3 (below) could be acceptable. Thus some kind of selection criteria for the organisation could be used, eg. on the organisation page you specify your country and organisation type maybe. If available configs are present, these could be applied.
• POP3 is archived and should not be used based on the recommendation from Forum Standaardisatie
• Have I been pwned overview?