aboutsummaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAge
* Do not propagate TcpListener.accept() errorsMroik2026-04-13
| | | | | | | | | | | | 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 <mroik@delayed.space>
* Add SMTP server scaffoldingMroik2026-04-13
| | | | Signed-off-by: Mroik <mroik@delayed.space>
* Add scaffolding for DB interactionsMroik2026-04-13
| | | | | | | | | 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 <mroik@delayed.space>
* Initial commitMroik2026-04-13
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 <mroik@delayed.space>
XMR address: 854DmXNrxULU3ZFJVs4Wc8PFhbq29RhqHhY8W6cdWrtFN3qmooKyyeYPcDzZTNRxphhJ5UzASQfAdEMwSteVqymk28aLhqj