Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
D

diego

@diego
About
Posts
2
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Using the native mail server
    D diego

    Hello @james ,

    Thanks for the response.

    My question is more about architecture and best practices for running Cloudron as a more serious mail server setup.

    Until now my usage was mostly hobby-level, with small mailboxes. Now I need to host around 60 accounts totaling ~1TB, so I'm trying to design the setup properly before deploying it.

    What I'm trying to understand is mainly:

    1. Storage layout

    I understand I could simply expand the primary disk of the VM. That is straightforward in Proxmox.

    However, from a system design perspective, I was wondering if it would be better to:

    • keep the system disk small (OS + Cloudron core)
    • attach a separate disk dedicated to mail storage

    For example mounting something like:

    /home/yellowtent/boxdata/mail

    on a dedicated volume.

    The idea behind this would be:

    • better separation between system and mail data
    • easier capacity management
    • possibility of using a filesystem with compression (e.g. zstd) to maximize storage efficiency
    • simpler disk replacement or migration in the future

    But at the same time I don't want to diverge from the recommended Cloudron layout, because I would like to keep the installation as "standard" as possible in case I ever need support.

    So the main question is:
    Is expanding the main disk considered the recommended production setup for Cloudron mail servers?

    Or is using a dedicated volume for mail storage also a common and supported approach?


    2. Backups

    Regarding backups, my doubt is specifically about data located on a secondary disk.

    If I move /home/yellowtent/boxdata/mail to another mounted disk:

    • Will the Cloudron backup system still include it normally?
    • Or are there caveats when the data directory is located on another filesystem / mount point?

    I'm not trying to customize Cloudron unnecessarily — I'm mainly trying to understand what a good production storage design looks like when Cloudron is used as a mail server with ~1TB of mail data.

    Any recommendations or real-world setups from other users would also be very helpful.

    Best regards,
    Diego

    Support mail server mail

  • Using the native mail server
    D diego

    Hello guys,

    I've been using Cloudron for many years, mainly using the native email feature with the SoGo app. I'm very grateful to the Cloudron team 😊
    Using it installed as a guest in a Proxmox environment.

    Now I have a new need to host about 60 email accounts.
    I need to provision about 1TB of space.

    I would like your opinion on this.

    Currently, the main disk where the system runs is 100GB. I would like to attach a second 1TB disk to it.

    What backup strategy should I use?
    Does the PRO license already cover this scenario? Or should I use the Business license?

    Which filesystem should I use in this new disk for better management and security of these emails?

    How do I allocate this new disk/partition/volume for the Cloudron email function?

    Best regards,
    Diego

    Support mail server mail
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search