5 ms·

WildDuck, a modern email server implementation with Unicode and REST API

21 points by andris9 5y ago

sneak 5y ago
The fact that this uses Mongo as a backend makes it a total nonstarter for me.
- andris9 5y ago
  The largest WildDuck setup has been running for 4 years, and its MongoDB cluster stores about 100TB of data, hundreds of millions of emails for 100k+ users. There are some quirks but so far the setup has been quite reliable. It is probably far easier to upgrade a single MongoDB instance in a cluster than to upgrade a "normal" email server with a large maildir folder structure.
  - chrisandchris 5y ago
    I'm not OP but a guess would not be that it's because it is MongoDB, but because of the license MongoDB has, which will put some restrictions to your usage and also - if you are going to provide services to a 3rd party - will require legal assistance.
    - erk__ 5y ago
      I don't think that is the case as you are not providing MongoDB as a service but an application that uses it as a database, that said it is under the EUPL license so you will have to share any modifications you make.
      - chrisandchris 5y ago
        Yes, sure. The question would be if/when do you habe to make modifications? Given the statement > You should consider using WildDuck when you have a large number of email accounts (1000+) with large quotas as WildDuck is designed to scale horizontally. Do you want to use a service that, if you grow and if you would make adjustments to the source, you are required to provide the source to the public?
        erk__ 5y ago
        That is whole idea behind EUPL or AGPL the new license for MongoDB does not change much in this case. Though you are right that if you are trying to generate a profit with the service you might want to use something else, but it should be fine if it was for something like a company wide mail server.
    - redwood 5y ago
      You're misunderstanding the SSPL: if you're delivering an email service (not a database service) then you can do whatever you want
    - sneak 5y ago
      No, it's because MongoDB is a crap datastore that will eat your data. It's insane that new projects would choose it as a backend over a reliable datastore, of which there are many good ones available (postgres comes to mind). Mongo's being not-open-source anymore doesn't affect using it as a backing store in a service.
      - redwood 5y ago
        Your information is about 8 years out of date
  - deleted 5y ago
    [deleted]

21 points by andris9 5y ago

sneak 5y ago

The fact that this uses Mongo as a backend makes it a total nonstarter for me.

andris9 5y ago
The largest WildDuck setup has been running for 4 years, and its MongoDB cluster stores about 100TB of data, hundreds of millions of emails for 100k+ users. There are some quirks but so far the setup has been quite reliable. It is probably far easier to upgrade a single MongoDB instance in a cluster than to upgrade a "normal" email server with a large maildir folder structure.
- chrisandchris 5y ago
  I'm not OP but a guess would not be that it's because it is MongoDB, but because of the license MongoDB has, which will put some restrictions to your usage and also - if you are going to provide services to a 3rd party - will require legal assistance.
  - erk__ 5y ago
    I don't think that is the case as you are not providing MongoDB as a service but an application that uses it as a database, that said it is under the EUPL license so you will have to share any modifications you make.
    - chrisandchris 5y ago
      Yes, sure. The question would be if/when do you habe to make modifications? Given the statement > You should consider using WildDuck when you have a large number of email accounts (1000+) with large quotas as WildDuck is designed to scale horizontally. Do you want to use a service that, if you grow and if you would make adjustments to the source, you are required to provide the source to the public?
      - erk__ 5y ago
        That is whole idea behind EUPL or AGPL the new license for MongoDB does not change much in this case. Though you are right that if you are trying to generate a profit with the service you might want to use something else, but it should be fine if it was for something like a company wide mail server.
  - redwood 5y ago
    You're misunderstanding the SSPL: if you're delivering an email service (not a database service) then you can do whatever you want
  - sneak 5y ago
    No, it's because MongoDB is a crap datastore that will eat your data. It's insane that new projects would choose it as a backend over a reliable datastore, of which there are many good ones available (postgres comes to mind). Mongo's being not-open-source anymore doesn't affect using it as a backing store in a service.
    - redwood 5y ago
      Your information is about 8 years out of date
- deleted 5y ago
  [deleted]