poul-list/Cargo.lock, branch master

Replace std socket IO with tokio socket IO

2026-04-13T04:56:11Z

Since the TcpListener (and related) operations are blocking, they would prevent other tasks from running by monopolizing CPU time. This should've been done from the start but I'm not used to directly using low level primitives in an async environment as I would normally use a high level library for this, so I forgot. Signed-off-by: Mroik

Do not propagate TcpListener.accept() errors

2026-04-13T04:56:11Z

Errors produced by the socket may not be necessarily fatal, meaning that while a connection might be dropped the process should be able to resume execution as if nothing happened and accept the next connection. Error handling for accept() has been copied from NGINX's [1]. [1] https://stackoverflow.com/questions/76955978/which-socket-accept-errors-are-fatal Signed-off-by: Mroik

Add SMTP server scaffolding

2026-04-13T04:56:10Z

Signed-off-by: Mroik

Add scaffolding for DB interactions

2026-04-13T04:55:04Z

The mailing list will need to save various data to operate for things such as the subscriber's email. Add database interaction machanism. Signed-off-by: Mroik

Initial commit

2026-04-13T04:54:57Z

A mailing list implementation by POuL for POuL that aims to be minimal but use SMTP to deliver receiving emails instead of LMTP. This is because mailing list software that use LMTP as their delivery mechanism make achieving modularized container environments harder. This is due to the fact that mailing lists that use LMTP require it and the main MTA to live on the same machine. This implementation aims to be good enough to be used as the mailing list for POuL in its kubernetes infrastructure (and frankly, it was about time that someone implemented a mailing list that could be "standalone" in containers). Signed-off-by: Mroik