Bug 286326 - [NEW PORT] mail/stalwart-mail: Secure & Modern All-in-One Mail Server (IMAP, JMAP, POP3, SMTP)
Summary: [NEW PORT] mail/stalwart-mail: Secure & Modern All-in-One Mail Server (IMAP, ...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-24 16:50 UTC by Orville Q. Song
Modified: 2025-05-09 09:56 UTC (History)
2 users (show)

See Also:


Attachments
mail/stalwart-mail 0.11.7 (148.01 KB, patch)
2025-04-24 16:50 UTC, Orville Q. Song
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Orville Q. Song 2025-04-24 16:50:29 UTC
Created attachment 259837 [details]
mail/stalwart-mail 0.11.7

Stalwart Mail Server is an open-source mail server solution with
JMAP, IMAP4, POP3, and SMTP support and a wide range of modern
features. It is written in Rust and designed to be secure, fast,
robust and scalable.

https://stalw.art/
Comment 1 Herbert J. Skuhra 2025-04-26 12:07:24 UTC
Thanks. I want to test Stalwart Mail soon. 
Is it really necessary to set admin secret in rc.d script instead of config.toml? The file is probably world readable (755). Why do you set PORTREVISION?
Comment 2 Orville Q. Song 2025-04-27 11:41:18 UTC
Hello!

Thank you for your interest in this port.

The reason for placing ADMIN_SECRET in the rc.d file is because retrieving the value from the corresponding environment variable is the expected behavior in the default configuration of Stalwart Mail. I did overlook the permission issue with the rc.d script — thank you for pointing it out. I will fix it as soon as possible.

As for the PORTREVISION, it was left over from my own testing process to verify whether the port could properly run its business logic. It seems I forgot to remove it, and I will also clean it up in the next update.
Comment 3 Yonas Yanfa 2025-05-09 09:56:54 UTC
How's this coming along?