- Posts: 18
- Joined: Mon Apr 22, 2013 10:48 pm
- How did you hear about Mailcleaner: Googling and reading articles about mail gateways.
- Posts: 501
- Joined: Tue Aug 26, 2008 3:01 am
- How did you hear about Mailcleaner: I dont remember probably google?
- Location: Spokane, WA
FlorianB wrote:4) We have to fill /etc/issue with links to documentation etc... as MailCleaner will now come without installer but as a ready to use VM.
5) KVM VM will be the first to be available probably as we works with it, but they should be convertible, and we'll soon provide some for Hyper-V or VmWare
Please make Mailcleaner available as ISO installer as for some KVM virtualization there is no possibility to import a virtual disk or .ova file.
In the past Mailcleaner could be installed on many providers vServers because it had an ISO file that could be mounted/uploaded to the providers storage/infrastructure. With templates only it would be impossible to do so.
It would be enough if the installer distributes a clean Jessie and then extracts all components that are required. You could even include all required moduels in the ISO files, so it requires no additionaly download for the setup and can be installed fast in a matter of minutes.
Another option would be to be able to install Mailcleaner into a clean Jessie by just running an install script that you could provide. With it's code beeing on git this should be simple to do and simple to maintain the installer script.
One liner e.g.:
bash <(wget -qO- https://raw.githubusercontent.com/Mailc ... _script.sh)
Thanks for considering!
To say it simply: I would be happy if we could install it with a one liner without days of work
For differents reasons (company policy or technical), we have to keep the existing base, and there was an installer built for the iso, some shell script for installing perl module, packages including multiple and different softwares (mc-httpd: apache, mpm-itk, apr, apr-utils, php, openssl, curl and probably one other I forgot recompiled together). So to keep that and progress, we have to analyse existing, redo newer version trying to improve each occurences.
So we will publish an ISO. When ? I don't know. All i know is we are working with KVM and we already created a version (call it alpha) of the VM we deploy each time we use it so KVM Vm will be ready first and VMWare HyperV should follow. After that (or at the same time), we'll publish for our professionnal and probably everyone a migration script to migrate from MC Squeeze to MC Jessie. The iso will need more work as an installer has to be added (to install packages, make partitions, launch shell script for all requirements etc...).
Again, I'm not against an ISO, simply, most people would prefer to deploy a VM in 5 minutes, or install an AWS or Softlayer instance than download and use the ISO. Next step after VM will be iso, and a bonus step will probably a docker container (I had one, but there was garbage on, and i didn't touch it since one year....)
ISO is no priority but a nice to have. Totally fine with me if it comes later.
Most important part from my point of view is that Mailcleaner updates are pushed more or less automatically or via github (similar). So that upgrading the installation is just pressing some button(s), if there is no OS upgrade in place.
When creating the VMware Image, please use the open VMware Tools and not the original VMware tools. Even VMware says that the open tools are the better choice for Linux/Unix systems.
Wow I'm so late on this topic
All has been anounced for version 2017, tools to migrate etc...
And yes as there is only one version for Enterprise and Community now we'll support this version to avoid security flaw etc...
Exim has been update to 4.88 in this sense.
And about VMWare tools (it looks like we talked about this too), as the kernel is not custom anymore you can install open-vm-tools:
apt-get update && apt-get install open-vm-tools
How is your upgrade path to Stretch?
Official Support for Jessie will be dropped next year and we don't want to fall into the same hole again, won't we?
Wow wow calm !!!!
From Debian site about the long term support:
Debian 8 « Jessie » i386, amd64, armel et armhf (?) de juin 2018 jusqu'à fin avril 2020
So even if I want to stay more updated than we were until here, there is nothing imperative about 2018 !
You have to consider too what bring a new version each year or two years except some difficult migration ?
Exim is already 4.88, Debian will not have a fresher package than that. Apache is the last one too.
So we have to balance our time between migration to stretch and development of detection engine (after all this is our core goal).
didn't want to speed things up. Just asking... That's why I put the Smilie ==>
As long as an system updated is released for the latest Debian at least 6 month before the official support stop it's fine. Just wanted to check on your plan, since Debian 6 was overdue to a long time.
Thanks for your great work!
When will Let's Encrypt be working?
Who is online
Users browsing this forum: No registered users and 3 guests