I’m having a rough go at setting up postfix/procmail. It seems as I cure each issue, a different set of error are produced. Below is what I’m getting now.
Jul 25 10:27:24 secure postfix/qmgr[25388]: DF89F375006E: from=<myAccount@clearwire.net>, size=881, nrcpt=1 (queue active)
Jul 25 10:27:24 secure postfix/local[27071]: DF89F375006E: to=<admin.domain.org@secure.domain.org>, orig_to=<admin@domain.org>, relay=local, delay=0.25, delays=0.23/0.01/0/0.02, dsn=5.3.0, status=bounced (Command died with status 127: "/usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME". Command output: sh: /usr/bin/procmail-wrapper: No such file or directory )
Jul 25 10:27:24 secure postfix/cleanup[27070]: 18FFD3750070: message-id=<20080725152724.18FFD3750070@secure.domain.org>
Jul 25 10:27:24 secure postfix/bounce[27073]: DF89F375006E: sender non-delivery notification: 18FFD3750070
Any insight would be appreciated.
Operating system CentOS Linux 5.2
Webmin version 1.420
Virtualmin version 3.59 (Pro)<br><br>Post edited by: webwzrd, at: 2008/07/25 13:28
This looks like an incomplete installation–procmail-wrapper is missing on your system. The install.sh should have installed that for you…but if you are installing Virtualmin manually onto an existing production system, it’s more complicated.
I just upgraded from within the GPL control panel a couple days ago. The server is not yet in use, as I am getting ready to migrate 160+ Ensim accounts. It won’t be a big deal if I need to start from scratch.
I just upgraded from within the GPL control panel a couple days ago
You installed Virtualmin GPL somehow, though, right? That’s what I need to know. Both Professional and GPL can be installed via the automated install script, or via a complicated and long manual process. I need to know which method you used.
If you went the manual route, and this is not yet in production, I’d suggest running the install script now. There are just so many steps involved in getting things working nicely via the manual process that I don’t want to encourage anyone to go that route.
I might need to clarify here, because after researching your install scripts, I’m don’t think I used the install script you referred to.
I first install webmin, httpd, maybe couple other things separately. Then I installed virtual-server-3.60.gpl.wbm.gz. After playing with the GPL a week setting up a couple test domains and using sendmail, I upgraded and decided to switch to postfix.
Maybe it’s the route I took, but several things have been challenging. Like setting up Joomla with the install script leaves me with a 500 error. I now read that it’s better to let apache install with virtualmin.
Unless it’s a bad idea, there would never be a better time to reinstall the full Virtualmin stack. If you agree, do I need to uninstall anything or just overwrite? I assume I would install the GPL version and then add my license for the Pro.
if the server is not in use yet and you have the possibility, I would reinstall the OS, do a yum update, and install the VM pro install.sh on a clean server
Since you’re thinking of starting over anyhow – when you install, you might want to use the Pro installer rather than the GPL one you mentioned. They both lead to the same place, but the Pro installer does so in less steps
yeah to tell you the truth
when i started I first spend 3 months on an old PC at home installing all kinds of distros and Control Panels.
In the end I came to centos 5 and VMPro and like you said, works out of the box.
now comes finetuning to your needs and some security, the work is never done
