Dear All I have got partial success with postfix setup. So far I am able to do
1. Access the postfix admin 2. Was able to login to postfix admin 3. Created one more admin account 4. From newly created admin account sent a mail to my gmail account, and I received that mail. 5. I am able to add a domain 6. I was able to add a virtual mailbox
However many things are NOT working. Things that I have observed NOT working are
1. Not able to login to mailbox through roundcube In link https://www.example.com/webmail/ (after security exception confirmation) , I entered the user@example.com and password. It says "*Connection to storage server failed.*".
Any idea why it happen?
I checked my /home/vmail path. I hope here there will be individual folder/file for individual mailboxes (not sure though). Did not see any file/folder as of now.
Kindly guide why it gives "*Connection to storage server failed.*".
Thanks Austin
On Wed, Mar 13, 2013 at 6:54 AM, SilverTip257 silvertip257@gmail.comwrote:
On Tue, Mar 12, 2013 at 10:02 AM, James B. Byrne <byrnejb@harte-lyne.ca
wrote:
On Mon, March 11, 2013 16:56, Craig White wrote:
develop good, consistent habits… postfix or whatever config files you edit, backup the distribution's version of the config file first before you ever edit…
cp main.cf main.cf-dist
Alternatively:
yum install postfix yum install git cd /etc/posfix git init git add ./ git commit -m"Postfix config file initial commit"
Now all the default config files are stored as hashed blobs in /etc/postfix/.git and you can modify them in place. Once you are
Nice. git-r-done ;)
I've been rather content with using RCS (as opposed to other version control systems) on the individual boxes.
Version control of some sort is a must. And backups ... multiple backups ... :D
satisfied with your latest set of changes do this (always issue git commands from the repository root, in this case /etc/postfix):
git add ./ or git add <filename> git commit -m"explanation of why the changes were made"
If you screw up and need to get back what was there originally do this:
git checkout <filename>
If you want to see what was different between this config and the previous version do this:
git diff <filename>
You can compare any previous version of any tracked file with any other version of the same file by specifying the commit ids.
git diff <commit1_sha>..<commit2_sha> -- <filename>
Git also provides a blow by blow history of all changes applied to a file and what logon id made them.
git blame <commit1_sha>..<commit2_sha> -- <filename>
See http://git-scm.com/ for details on what git is and how to use it. I use git for version control of system config files on all my uptime sensitive servers. It makes getting back to a working config trivial when things turn ugly following a change.
-- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- ---~~.~~--- Mike // SilverTip257 // _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos