mfashby / henrymail Goto Github PK

Configure travis build & status passing required for pull requests

more testing is required (unit & integration & end2end ideally)
hoping for 100% unit / integration coverage,
main features covered by a few e2es

The server can self-test a variety of things in addition to SPF and DKIM records:

• Check MX record
• Connect on ports 25, 143, 443, 587 & ensure protocol availability

Currently only linux-x64 is built, everyone else must get from source.
It would be great if we could compile and release binaries for every reasonable platform.

Look at https://github.com/karalabe/xgo and see if it suits

Seems a really easy way for admins to deploy a new instance. Look into it

see https://tools.ietf.org/html/rfc8314#section-3
It's now preferred that port 993 is used for IMAP with SSL negotiation expected upfront, instead of using STARTTLS. Similar for port 465 and SMTP submissions.

Ports 143 and 587 with STARTTLS should still be supported for now; but they are seen as deprecated.

Healthchecks should be updated as well to warn if the ports are not exposed.

It doesn't work for some reason

figure out a retry & failure reporting policy for failed mail (n retries at x interval, then undeliverable report to the sender?)

should configure something like travis or circle ci to build this project (& release when I tag it)

This repository is a mirror of my main working repository over at
https://gogs.mfashby.net/martin/henrymail

Having an admin set your password isn't ideal for security, instead provide an invitation link that someone can accept.

testing outbound from my server, I receive 2 emails on someone else's.

Check if you meet web content accessibility guidelines
Make new tickets where you need to change

As per RFC-6186, srv records can be used to allow auto-discovery of email servers. The health checks page should check for these records. If DNS auto configuration is built, it should automatically configure these records.

Particularly from health checks page

backups should happen (should be quite easy just copy 3 files!)

backups should be uploaded to a configurable location (FTP server, G drive, dropbox, )

backups should be encrypted.

install should present the option to restore from a backup

The server should provide a guide for common mail clients (values for fields, screenshots)

Go http server doesn't add CSRF protection by default. We should probably add this.

A reasonably simple implementation is described here: https://golangexample.com/csrf-protection-middleware-for-go/

Some servers may desire open sign-ups, it should be easy to implement this