Installation

[steamaccpw]

Hi,

I've installed mailcleaner via debian-bootstrap/install.sh
after I run /usr/mailcleaner/scripts/installer/installer.pl

All went OK.
But I cannot access any web (tryed port 4242 also)

What am I missing?

[JohnMertz]

Hi,

There is no more port 4242 configurator UI for MailCleaner Next. Each of the steps that was performed via the configurator (eg. setting the database password) have been merged into installer.pl. Since it was always necessary to use installer.pl to configure anyways, I didn't think that it made sense to have a separate UI for the last few setup steps.

The regular UI will be available on port 80/443. However, it is very likely that this will not simply work on first boot. It's been a while since I did a fresh install, so I'm not sure what the exact state is. At this stage there are existing problems, especially with the SystemD configuration which result in some services failing to start automatically, or at all. These can be overcome with manual configuration or manual commands run on each boot, but since the goal is to just fix these problems I have not taken the time to document these. The goal with this "Alpha" phase is to give savvy developers who are interested in helping fix these core issues a chance to contribute.

When we are at a state where the appliance can be installed and have a functional web interface and mail flow we will provide "Beta" VM images.

If you have knowledge necessary to help prior to the "Beta", I greatly appreciate any pull requests. Otherwise, I hope that the "Beta" will be available in the next few weeks. I've been saying that for a while, but I keep getting side-tracked with other support and infrastructure tasks, so fingers crossed!

[steamaccpw]

Ok, Thanks.
I will wait for VM images :)

Could you ad an option if antispam is disabled in config that would also disable services (less RAM needed).
I just need mailcleaner for mail relay. (i like interface and tracking :) and I am currently using old one)

[JohnMertz]

The biggest impact on RAM is the number of concurrent MailScanner processes (these go on to spawn concurrent ClamAV scans, SpamC scans, etc.). This number automatically scaled according to the available memory size in /usr/mailcleaner/bin/dump_mailscanner_config.pl like:

  $config{'__NBPROCESSES__'} = 5;
  if ($memsize > 0 && $memsize < 520000) { $config{'__NBPROCESSES__'} = 2; }
  if ($memsize > 1000000) { $config{'__NBPROCESSES__'} = 3; }
  if ($memsize > 1500000) { $config{'__NBPROCESSES__'} = 4; }
  if ($memsize > 2000000) { $config{'__NBPROCESSES__'} = 5; }
  if ($memsize > 3000000) { $config{'__NBPROCESSES__'} = 6; }
  if ($memsize > 4000000) { $config{'__NBPROCESSES__'} = 10; }
  if ($memsize > 5000000) { $config{'__NBPROCESSES__'} = 12; }
  if ($memsize > 20000000) { $config{'__NBPROCESSES__'} = 20; }

So, if you provide less RAM, it will automatically become more lightweight. Otherwise, you could hard-code the number of processes by replacing __NBPROCESSES__ in /usr/mailcleaner/etc/mailscanner/MailScanner.conf_template with the number you prefer.

In the current version, if you are just using it as an outgoing relay, you could somehow just disable exim_stage2, exim_stage4, mailscanner and potentially others, although most others are started by mailscanner. Outgoing relayed messages are relayed directly from exim_stage1. For example, by just adding exit at the beginning of the start sections of each of the init files in /usr/mailcleaner/etc/init.d/. The web interface would probably constantly have the warning at the top and on the Monitoring->Status page that services need to be started, however.

I'm not sure if that will remain possible in the Next release, since SystemD is being configured to automatically restart any service that has stopped and various services are bound together, so stopping one can cause others not to start. I would certainly not expect to be able to individually disable services at the outset using the Beta since the SystemD configurations will be the minimum viable solution to get MailCleaner running in the default configuration. It's possible that a more mature set of configuration files could conditionally run services in the future, but it won't be my priority. SystemD is already enough of a pain as it is :)

Honestly, I think that there is probably a better product out there if you just want relaying without filtering. Perhaps CPanel? I have not used it myself, but it is similarly based on Exim and has a WebUI, but does not have as robust of filtering features (out of the box, anyways).