Failed to query Postfix config command...

Posted January 31, 2014 10.1k views
Hello, I keep getting this in vertualmin: Failed to query Postfix config command to get the current value of parameter recipient_bcc_maps: I get it for different tasks when i do them. Anyone know why?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
8 answers
What's the value of recipient_bcc_maps? Is it commented out, by chance?
Hmm, i am not sure. This is all new to me. How can i check this ?
This is exactly why many people recommend against using a control panel, when first starting out... it simply adds (i) another layer of complexity and (ii) another possible point of failure. Besides, no control panel will give you the granular control you have at your disposal via the command line.

With that said: Did you check to make sure that you have the Postfix module installed? You may also want to check out the Virtualmin Documentation and the Virtualmin forums.
I know realise that. The only reason i used a control panel was because i am visual learner. But it is causing me more problems than solutions so i am going to start again with command line.

I want to install 2 Wordpress websites with 2 different domains. These using NGINX, is there a tutorial out there for this?
Just use this:

sudo apt-get install postfix

That will refix the whole problem!
I've just had a battle with this. I discovered this and a whole host of other problems is caused by a lack of RAM. You need at least 1GB to get Virtualmin to play nicely.

Add a swap file and it will work. it seems this error occurs in many different scenarios due to memory issues. adding a swap file solves it in most cases or like @andy.pixiesky said add more memory.

by Etel Sverdlov
Linux swaps allow a system to harness more memory than was originally physically available. Here's how to set up a linux swap file on Ubuntu 12.04

I got this error when i added one extra line in /etc/postfix/
Restoring to original fixed it.