However, you may be missing the procmail-wrapper package, which is available in the Virtualmin repo. I have first installed virtualmin GPL of course with the script mentioned. I installed the package with dpkg and changed perms to Still get the same error in virtaulmin.
Okay, that looks good. Just to be sure, can you paste in the specific error that you're getting? Changing the group to root didn't success. Even when I chmod procmail to the error still persists. Whatever procmail-wrapper is doing with procmail, it should be allowed, or not? Maybe I'm doing a fresh reinstall I'm loosing some configuration work, but the server is not yet in production phase. The fact that it was not installed during the run of install.
I'm almost certain you have other problems on the system--there's no reason procmail-wrapper wouldn't exist that doesn't make me think the install script failed there should have been some errors during the run or in the virtualmin-install.
Check out the forum guidelines! Oh, wait You'll want to change the mail delivery command in Postfix to procmail-wrapper. This will make this specific error go away, though others might show up.
Once tested, I'll post any mail. You must log in or sign up to reply here. Show Ignored Content. Share This Page Tweet. Your name or email address: Do you already have an account? So I'd start by installing those packages. For each package, I just followed the standard installation instructions from the web pages, with one exception.
This software has a problem with how it handles errno that will cause it to eventually break with newer versions of Linux, but thankfully it's easy to fix. This is generally as easy as running:. Then proceed with the regular build and installation instructions. Note that after installing daemontools, you may want to reboot to make sure that everything is consistent, although you may not have to. Now that you have daemontools installed, you can use it only for qmail, but it's also generally a pretty useful way of installing services.
You can find out more about it from the above-mentioned web site, but basically it's a system for starting and monitoring services to keep them running. In each subdirectory that contains an executable file named run , that file is executed. If that process ever exits, it's restarted. There are a few other bits related to services that log messages to stdout, where you can set up a log subdirectory of the service directory with its own run script to handle those log messages, but that's basically it.
Obviously, this can't be used for services that background themselves after starting, since the monitor and restart system doesn't work right. By default it expects to be able to use exim4 to submit bug reports. You will then be asked for the SMTP server to be used for submitting bug reports. If you would like your system to also handle external e-mail, you will need to reconfigure the exim4 package [21] :. After entering that command as root , you will be asked if you want split the configuration into small files.
If you are unsure, select the default option. Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs. Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online.
0コメント