mrowdy / styx Goto Github PK

For a small PoC we should have a minimal web based client.
The client should at least show:

• a live log of current enqueues (websockets?)
• a live log of current sent mails (websockets?)
• integrated kibana charts?

extract api part and worker part into two seperate go files that will be called from main.go

add all mail fields except body

clients by type concat ", "

All sent mails should be RFC Conform https://tools.ietf.org/html/rfc4021

At the moment we are missing bc and return-path headers.
We also need custom headers for our mail context and the mail id

Proposal:

• karriere-mail-context
• karriere-mail-id

These features are not supported by mailyak (or i'm just to stupid to use it).
We either find a way with mailyak or change to another library (we should be fine with de default mailer)

Da es ja eine API ist sollten wir auch CORS/Custom-Headers berücksichtigen welche die API versteht.

Wie das ganze aussehen kann weis ich jetzt noch nicht - Ticket is eher gedacht als platzhalter

In order to resend mails or to create "view in browser" links we must be able to store all mails in filesystem.

It's probably a good idea to use a hashed form of the file as filename since a lot of mails are identical.

we should be able to send mail. In order for this project to work like intendet

send mail as json to rabbitmq queue with MailID as Message ID

one worker for queue consume -> sends mail to smtp worker -> sends mail to success worker (db status update)

What if a mail from queue can't be sent? Either because of an invalid format, missing information or a not responding smtp?

At the moment wie panic.

POST /api/mail-attachment

• store attachment on disk
• should return a unique attachment identifier that can be used as attachment reference in POST /api/mail