Solved MailCow Command Line Reference
-
Any MailCow users know of a command line reference for MailCow to use for automating a large number of tasks with the system? The GUI works, but we normally do these things via the CLI shell. I'm not seeing anything in their docs about it.
-
The trick is to post a question, then I almost always find the answer right afterwards on my own, lol.
So they don't document it online, you install your MailCow instance, then go to...
Obviously where mymailcow.com is your own server, and the docs are hosted live by your own system so you always see your version of them.
-
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.
-
@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.
-
@Pete-S said in MailCow Command Line Reference:
If you don't intend to use the webinterface then what purpose does mailcow have?
The web interface isn't the main part. It's the complete package and API that we want.
-
@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.
-
@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?
-
@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.
