@Pete-S said in MailCow Command Line Reference:
@scottalanmiller said in MailCow Command Line Reference:
@Dashrender said in MailCow Command Line Reference:
@Pete-S said in MailCow Command Line Reference:
If you don't intend to use the webinterface then what purpose does mailcow have?
You could just install dovecot, postfix etc for email and sogo for calendar and have the same thing without the middle man. I bet you have to tweak config files even with mailcow.
I'm assuming Scott is asking about management stuff - he wants to script that stuff, not GUI manage it.
Right. GUI is fine for low capacity sites. But we are looking at two use cases both in the 10K+ range.
But mailcow doesn't add any functionality that the original packages don't already have. It's just a wrapper. Is it not?
Mostly. But it is handling the testing and integration of the components, which is the hard bit. It's actually doing a fair amount of work. I've built an extremely similar system in the past and the effort was quite large for just the "wrapper" bits that they are doing 😉
And the central API is a huge deal.
