4 ms·

Looks good, but since it's a young project I would suggest to anyone interested to consider Mailu [1], which is a mature project and looks easier to configure.

by GTP 4y ago

Looks good, but since it's a young project I would suggest to anyone interested to consider Mailu [1], which is a mature project and looks easier to configure. [1] https://mailu.io https://mailu.io

creshal 4y ago
Mailu, like poste, zimbra, univention, and a dozen other projects like it, suffers from being just a layer of glue scripts and leaky abstractions on top of very complicated dedicated software stacks – dovecot, postfix, rspamd, etc. are all complex beasts on their own, and have 30 years worth of accumulated configuration knobs to fiddle with. Postfix and dovecot in particular are also service orchestration frameworks of their own and don't reaaaally mesh well with docker, nor do the authors care about "this silly new fad". Don't dare asking about help with it on the postfix mailing list e.g., Wietse will rip your head off and beat you with it. So, no, after messing around with these sorts of stacks for over a decade now, I can't in good faith recommend it to anyone. Sooner or later the leaky abstractions flood your basement and you have to clean up the mess on your own. Mox's approach of cutting out 95% of the complexity by rolling their own good enough solutions into one monolith is far saner for small setups.
- dspillett 4y ago
  > nor do the authors care about "this silly new fad" In fairness, if you have chosen a platform that potentially introduces its own issues that isn't their problem unless they want it to be. A friend of mine has a project out there that only has official builds and build instructions for plain debian-based Linux, and he finds demands for direct docker support to be irritating (far worse than demands for a supported native Windows build ever were). And demand is the right word: many don't just ask, and some seem to get personally offended when he responds that he doesn't use docker much himself so wouldn't be comfortable offering support for it directly.
  - creshal 4y ago
    Sure, it's the author's right to choose what to support and what not. But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup, if the alternative is a single golang binary designed for use with docker.
    - GTP 4y ago
      > But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup What are you referring to? Because Mailu isn't Docker-hostile, quite the opposite: it is distributed as a set of Docker containers. And dspillett didn't mention what was his friend's project about, it could be totally unrelated to email.
      - creshal 4y ago
        > What are you referring to? Because Mailu isn't Docker-hostile Mailu uses postfix at the very bottom of its jenga tower software stack.

by GTP 4y ago

Looks good, but since it's a young project I would suggest to anyone interested to consider Mailu [1], which is a mature project and looks easier to configure. [1] https://mailu.io https://mailu.io

creshal 4y ago

Mailu, like poste, zimbra, univention, and a dozen other projects like it, suffers from being just a layer of glue scripts and leaky abstractions on top of very complicated dedicated software stacks – dovecot, postfix, rspamd, etc. are all complex beasts on their own, and have 30 years worth of accumulated configuration knobs to fiddle with. Postfix and dovecot in particular are also service orchestration frameworks of their own and don't reaaaally mesh well with docker, nor do the authors care about "this silly new fad". Don't dare asking about help with it on the postfix mailing list e.g., Wietse will rip your head off and beat you with it. So, no, after messing around with these sorts of stacks for over a decade now, I can't in good faith recommend it to anyone. Sooner or later the leaky abstractions flood your basement and you have to clean up the mess on your own. Mox's approach of cutting out 95% of the complexity by rolling their own good enough solutions into one monolith is far saner for small setups.

dspillett 4y ago
> nor do the authors care about "this silly new fad" In fairness, if you have chosen a platform that potentially introduces its own issues that isn't their problem unless they want it to be. A friend of mine has a project out there that only has official builds and build instructions for plain debian-based Linux, and he finds demands for direct docker support to be irritating (far worse than demands for a supported native Windows build ever were). And demand is the right word: many don't just ask, and some seem to get personally offended when he responds that he doesn't use docker much himself so wouldn't be comfortable offering support for it directly.
- creshal 4y ago
  Sure, it's the author's right to choose what to support and what not. But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup, if the alternative is a single golang binary designed for use with docker.
  - GTP 4y ago
    > But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup What are you referring to? Because Mailu isn't Docker-hostile, quite the opposite: it is distributed as a set of Docker containers. And dspillett didn't mention what was his friend's project about, it could be totally unrelated to email.
    - creshal 4y ago
      > What are you referring to? Because Mailu isn't Docker-hostile Mailu uses postfix at the very bottom of its jenga tower software stack.