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 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.
On Tue, Mar 12, 2013 at 10:02 AM, James B. Byrne byrnejb@harte-lyne.cawrote:
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
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
you need an IMAP server / MTA to handle login accounts since Postfix provides SMTP.
Dovecot? Cyrus-IMAP?
Craig
On Mar 12, 2013, at 7:55 PM, Austin Einter wrote:
Dear All I have got partial success with postfix setup. So far I am able to do
- Access the postfix admin
- Was able to login to postfix admin
- Created one more admin account
- 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
- 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
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hello, I was following a tutorial for setting up apache to work with more than one domain, virtual domains. So, I created a vhost.conf file in the folder /etc/httpd/conf.d/ When I saved that file, which gets called by the httpd.conf file inside the directory /etc/httpd/conf/, I tried to restart the server and it failed to start. I had to rename the vhost.conf file to vhost.conf.back to keep what I did and try to figure out how to get this to work. I'll copy that very short file below.
First, regarding the next issue, I want to figure out where, on which physical drive, a top level partition exists. Specifically /opt. I have the Centos installed on a drive that is 1TB, and on that drive the / root directory is mounted. I'm concerned that one drive might be going bad and it is the smaller drive anyway. So, I just don't know how to find this information. I can get information on some directories with a few commands that deal with partitions, but I don't see how to find the physical location of every single top level partition.
thanks in advance for help. I'll post the vhost.conf file that caused the server to not start.
NameVirtualHost *:80
<VirtualHost *:80> ServerAdmin webmaster@fwwebdev.dnsdynamic.com ServerName fwwebdev.dnsdynamic.com ServerAlias www.fwwebdev.dnsdynamic.com DocumentRoot /home/www/fwwebdev.dnsdynamic.com/public_html/ ErrorLog /home/www/fwwebdev.dnsdynamic.com/logs/error.log CustomLog /home/www/fwwebdev.dnsdynamic.com/logs/access.log combined </VirtualHost>
<VirtualHost *:80> ServerAdmin webmaster@futurewavewebdevelopment.com ServerName futurewavewebdevelopment.com ServerAlias www.futurewavewebdevelopment.com DocumentRoot /home/www/futurewavewebdevelopment.com/public_html/ ErrorLog /home/www/futurewavewebdevelopment.com/logs/error.log CustomLog /home/www/futurewavewebdevelopment.com/logs/access.log combined </VirtualHost>
Bruce
_______________________________________________________ Bruce Whealton - Web Design/Development/Programming Future Wave Web Development: http://futurewaveonline.com Developing for the Desktop as well as for Mobile Devices - Smartphones/Tablets Call 919-636-5809 _______________________________________________________
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, Mar 13, 2013 at 6:02 PM, Bruce Whealton bruce@futurewaveonline.comwrote:
Hello, I was following a tutorial for setting up apache to work with more than one domain, virtual domains. So, I created a vhost.conf file in the folder /etc/httpd/conf.d/ When I saved that file, which gets called by the httpd.conf file inside the directory /etc/httpd/conf/, I tried to restart the server and it failed to start. I had to rename the vhost.conf file to
Check your Apache logs in /var/log/httpd/
vhost.conf.back to keep what I did and try to figure out how to get this to work. I'll copy that very short file below.
First, regarding the next issue, I want to figure out where, on which physical drive, a top level partition exists. Specifically /opt. I have the Centos installed on a drive that is 1TB, and on that drive the / root directory is mounted. I'm concerned that one drive might be going bad and
Determine what your drives' block device names are: fdisk -l
Then dump the SMART log for each: smartctl -a /dev/sdX
it is the smaller drive anyway. So, I just don't know how to find this information. I can get information on some directories with a few commands that deal with partitions, but I don't see how to find the physical location of every single top level partition.
Try: mount
If utilizing LVM the following will also be helpful: lvdisplay
thanks in advance for help. I'll post the vhost.conf file that caused the server to not start.
NameVirtualHost *:80
<VirtualHost *:80> ServerAdmin webmaster@fwwebdev.dnsdynamic.com ServerName fwwebdev.dnsdynamic.com ServerAlias www.fwwebdev.dnsdynamic.com DocumentRoot /home/www/fwwebdev.dnsdynamic.com/public_html/ ErrorLog /home/www/fwwebdev.dnsdynamic.com/logs/error.log CustomLog /home/www/fwwebdev.dnsdynamic.com/logs/access.log combined
</VirtualHost>
<VirtualHost *:80> ServerAdmin webmaster@futurewavewebdevelopment.com ServerName futurewavewebdevelopment.com ServerAlias www.futurewavewebdevelopment.com DocumentRoot /home/www/futurewavewebdevelopment.com/public_html/ ErrorLog /home/www/futurewavewebdevelopment.com/logs/error.log CustomLog /home/www/futurewavewebdevelopment.com/logs/access.log combined
</VirtualHost>
Bruce
Bruce Whealton - Web Design/Development/Programming Future Wave Web Development: http://futurewaveonline.com Developing for the Desktop as well as for Mobile Devices - Smartphones/Tablets Call 919-636-5809 _______________________________________________________
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I had to go to /home/www/futurewavewebdevelopment.com/logs and in the error log, it just says that access is forbidden. I changed the permissions and ownership to apache:apache which is what was working before. If I remove that, I can get to the default page at /var/html/www and it displays my new test page and the php. Then I tried to have the vhost.conf file point to a directory underneath where the default location is in the /etc/httpd/conf/httpd.conf file - that is /var/www/html So, I changed the /home below to be /var and I created the respective directories, such as /var/www/futurewavewebdevelopment.com/public_html which is what I used in the /etc/httpd/conf.d/vhost.conf file. Now, the server won't restart. Maybe I need to put the errors into a pastbin and see if that helps. What I see does not help. Any ideas, Bruce
thanks in advance for help. I'll post the vhost.conf file that caused the server to not start.
NameVirtualHost *:80
<VirtualHost *:80> ServerAdmin webmaster@fwwebdev.dnsdynamic.com ServerName fwwebdev.dnsdynamic.com ServerAlias www.fwwebdev.dnsdynamic.com DocumentRoot /home/www/fwwebdev.dnsdynamic.com/public_html/ ErrorLog /home/www/fwwebdev.dnsdynamic.com/logs/error.log CustomLog /home/www/fwwebdev.dnsdynamic.com/logs/access.log combined </VirtualHost>
<VirtualHost *:80> ServerAdmin webmaster@futurewavewebdevelopment.com ServerName futurewavewebdevelopment.com ServerAlias www.futurewavewebdevelopment.com DocumentRoot /home/www/futurewavewebdevelopment.com/public_html/ ErrorLog /home/www/futurewavewebdevelopment.com/logs/error.log CustomLog /home/www/futurewavewebdevelopment.com/logs/access.log combined
</VirtualHost>
Bruce
Bruce Whealton - Web Design/Development/Programming Future Wave Web Development: http://futurewaveonline.com Developing for the Desktop as well as for Mobile Devices - Smartphones/Tablets Call 919-636-5809 _______________________________________________________
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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
Bruce Whealton wrote:
I had to go to /home/www/futurewavewebdevelopment.com/logs and in the error log, it just says that access is forbidden. I changed the permissions and ownership to apache:apache which is what was working before. If I remove that, I can get to the default page at /var/html/www and it displays my new test page and the php. Then I tried to have the vhost.conf file point to a directory underneath where the default location is in the /etc/httpd/conf/httpd.conf file - that is /var/www/html So, I changed the /home below to be /var and I created the respective directories, such as /var/www/futurewavewebdevelopment.com/public_html which is what I used in the /etc/httpd/conf.d/vhost.conf file. Now, the server won't restart. Maybe I need to put the errors into a pastbin and see if that helps. What I see does not help. Any ideas,
What's the DirectoryRoot?
Really, what's more common is /var/www/html (or whatever your company's practice is, and under *that* /var/www/html/mydomain1.com /var/www/html/mydomain2.com etc., with /var/www/html the overriding DirectoryRoot, but only /var/www/html/mydomain1.com as DirectoryRoot in each of the configuration files, /etc/httpd/conf.d/mydomain1.conf, etc.
mark
Oh, yes - what are the permissions on /etc/httpd/conf and /etc/httpd/conf.d?
mark
On Thu, Mar 14, 2013 at 2:00 PM, m.roth@5-cent.us wrote:
Oh, yes - what are the permissions on /etc/httpd/conf and /etc/httpd/conf.d?
And if selinux is enabled, do you see denials in /var/log/audit/audit.log for the files in question?
On 03/13/2013 03:03 PM, Dirk Olmes wrote:
On 03/13/2013 04:30 PM, Craig White wrote:
you need an IMAP server / MTA to handle login accounts since Postfix provides SMTP.
Dovecot? Cyrus-IMAP?
I'd go for dovecot - actively maintained, designed for security, easy to configure.
The OP is using dovecot, he just forgot to start it. I hope he has set chkconfig on for it...
-
Austin Einter -
Bruce Whealton -
Craig White -
Dirk Olmes -
James B. Byrne -
Les Mikesell -
m.roth＠5-cent.us -
Robert Moskowitz -
SilverTip257