User Tools

Site Tools


migration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
migration [2010/07/15 15:57]
SLUUG Administration
migration [2010/07/15 16:29] (current)
SLUUG Administration
Line 14: Line 14:
 == Mail == == Mail ==
  
-This includes postgrey, postfix, spamassassin,​ courier, mailscanner,​ and mailman. ​+This includes postgrey, postfix, spamassassin,​ courier, mailscanner,​ and mailman
 +  *We will need to make new certs for imaps/pop3s after installing the courier RPMs.  
 +  *Apache should be working before we try to configure mailman. 
 +  *When installing mailman, create a test list for '​amber.sluug.org'​ and verify that it works before creating DISCUSS, ANNOUNCE, etc. 
 +  *We may or may not be able to copy over the contents of /​usr/​local/​mailman/​archives from bud - if not, we'll have to use the import tool that comes with mailman. 
 +  *CentOS doesn'​t have courier RPMs available via yum. However, RPMs can be built from the courier source packages, which is documented at http://​www.courier-mta.org/​rpm.html. ​  
 +  *When we moved mail from michelob to bud, we used forwards to make sure that mail continued to go to michelob even though it was received on bud. Then when users confirmed they were able to fetch mail from bud, we turned off the forward. We might want to do the same thing again. 
 +  *Craig had a patch to a couple of files in the mailman source to correct a problem with date formatting. We need to find those patches, or their descriptions in the sysadmin list archives.
  
-CentOS doesn'​t have courier RPMs available via yum. However, RPMs can be built from the courier source packages, which is documented at http://​www.courier-mta.org/​rpm.html.  ​ 
- 
-== NTP == 
  
 == Apache == == Apache ==
Line 27: Line 31:
  
  
 +=== Other things requiring configuration ===
  
 +== Firewall ==
  
 +Unlike debian, CentOS comes with an integrated firewall configuration tool. This means we won't use Shorewall, but will configure iptables either with '​system-config-securitylevel-tui'​ or via /​etc/​sysconfig/​iptables.
 +
 +== SSL ==
 +
 +We may need to generate new SSL certificates,​ as clients may complain about mismatched FQDNs if we just copy the bud certs over to amber. We can either use the methods documented for bud, or use the Makefile or scripts in /​etc/​pki/​tls/​certs on amber. ​
 +
 +== NTP ==
  
 +Just run 'yum install ntp' and edit /​etc/​ntp.conf to use pool.ntp.org servers.
  
 +== User accounts ==
  
 +Go through /etc/passwd on bud and make sure that user and application accounts are created. We'll need to be careful to avoid conflicts with UIDs/GIDs reserved by CentOS. ​
migration.1279227438.txt.gz · Last modified: 2010/07/15 15:57 by SLUUG Administration