Successful install - Proxmox

nutterpc

First off, loving the software. Coming from ClearOS and it’s heavily restricted SMTP implementation, this ones a godsend.

Now i know this goes against the general thing of it shouldn’t really work/isn’t really supported, but coming from a Linux/Admin background, i was up for the challenge.

Took me about a day to fully work the bugs i did have out and transition from our old mailserver to Mailcow. So while yes, it’s unsupported, it is actually possible, and has been running very very well. Configured with 8 Cores, 16Gb RAM & it’s own 440Gb NVME SSD for the server to work on.

What i would like to find out from the collective minds, is there ways to be able to tweak some of the security/configuration settings if needed, being that it’s running in a container. I know i found some commands for some of the functions, but not quite all yet

One of the features I’m finding myself taking a liking to is the RSPAMD Server. Especially when it comes to the greylisting of things like 2FA codes and i’m still waiting for it to allow it through, i can read the email body and still grab the code.

I probably gave it overkill resources to run on, but considering the server it runs on, why not lol

ETNyx

Well, sorry, but is there actually a question to respond to?

If I stick to your title and first part, the first thing I’d ask is: which button did you press when creating your VPS – “Create VM” or “Create CT”? This is a very common misunderstanding. You wrote that Proxmox is not supported, but that’s not what the documentation says. According to the docs:
Do not try to install mailcow on a Synology/QNAP device (any NAS), OpenVZ, LXC or other container platforms. KVM, ESX, Hyper-V and other full virtualization platforms are supported.

Since CT = LXC, this type of virtualization is indeed not supported.

But VM = KVM, which is supported. Unless you’re running a CPU without virtualization support, there’s no reason to pick CT (LXC) over VM (KVM) for Mailcow.

Another thing to check is how your VM is configured, especially the CPU settings. Proxmox usually applies conservative defaults, meaning the virtualized CPU may not expose modern instruction sets even if your physical CPU supports them. If the software depends on those instructions, it might look like “Proxmox is not supported,” but in reality it’s just a misconfiguration.

That said I do not run MC on Proxmox and/or I do not know if MC need modern instruction, but I would guess it could benefit from AVX while scanning mail in rspamd and clamd,…