TetraWiki - User contributions [en]

Architecture Details of MiraExim

2013-03-02T11:55:27Z

Navdeep: /* Architecture Details and Diagram of Miraexim Ltd. Noida */

[[category:Mira Exim]]

== Architecture Details and Diagram of Miraexim Ltd. Noida ==

'''DC = MAIN SERVER'''

'''DR = DR SITE'''

# There are two qmail servers , one is for DC and other is for DR(Disaster Recovery)
# Two MX records are pointed for all domains ( groupwama.com, miraexim.com, vogueserv.com, cdc.uk.net) one is for DC-Local and other is for DR.
# If DC goes down then automatically mails coming on DR.
# '''But important is If DC is running then DR must be off.'''
# Only need to change A record of mail.domain.com ,By default it is pointed towards DC but when DC goes down it change to the DR IP.
# Implementation of both qmail servers are same.
# This qmail server has two instance , first instance for incoming and local outgoings, and second instance is for remote outgoing with disclaimer, all outgoing remote mails were copied into the [mailto:log@groupvama.com log@groupvama.com] through second instance.
# Mails archiving is done by forwarding for all domains have different archiving mailbox

For groupvama.com [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

For miraexim.com [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

For vogueserv.com [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

For cdc.uk.net [mailto:archive.cdc@cdc.uk.net archive.cdc@cdc.uk.net]

For vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com

For missangel.com [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# All remote outgoing mails save into the [mailto:log@groupvama.com log@groupvama.com]
# Openldap is in master slave mode, LDAP Master is DC and slave is DR.
# Chat server – openfire3.6 server installed
# Chat server LDAP BIND with “ou=jabber-users,dc=groupvama,dc=com”
# As for user management ldap account manager is installed

Details : '''182.71.29.139/lam'''

# Both Squirrelmail and roundcube is installed in DC Qmail server

Details :

mail.groupvama.com ----- For Roundcude

mail.groupvama.com/mail ------ For Squirrelmail

# Only squirrelmail installed in DR Site

182.50.142.178 -- For squirrelmail

16. LAM ldap account manager pro is installed in both DC and DR.

17. DC LAM have read/write permissions nut DR LAM have only read only permissions.

# Openfire is installed in DC Only
# Users on openfire is integrated with LDAP and groups is also integrated with LDAP
# As openfire client , they are using pidgin.

== ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP ==

[[Image:Architecture Diagram of MiraExim1.jpg|700px]]

Category:Mira Exim/Architecture Diagram

2013-03-02T11:51:44Z

Navdeep: Blanked the page

Category:Mira Exim/Architecture Diagram

2013-03-02T11:51:22Z

Navdeep: /* ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP */

[[category:Mira Exim]]

Architecture Details of MiraExim

2013-03-02T11:50:08Z

Navdeep:

[[category:Mira Exim]]

== Architecture Details and Diagram of Miraexim Ltd. Noida ==

'''DC = MAIN SERVER'''

'''DR = DR SITE'''

# There are two qmail servers , one is for DC and other is for DR(Disaster Recovery)
# Two MX records are pointed for all domains ( groupwama.com, miraexim.com, vogueserv.com, cdc.uk.net) one is for DC-Local and other is for DR.
# If DC goes down then automatically mails coming on DR.
# '''But important is If DC is running then DR must be off.'''
# Only need to change A record of mail.domain.com ,By default it is pointed towards DC but when DC goes down it change to the DR IP.
# Implementation of both qmail servers are same.
# This qmail server has two instance , first instance for incoming and local outgoings, and second instance is for remote outgoing with disclaimer, all outgoing remote mails were copied into the [mailto:log@groupvama.com log@groupvama.com] through second instance.
# Mails archiving is done by forwarding for all domains have different archiving mailbox

For groupvama.com [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

For miraexim.com [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

For vogueserv.com [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

For cdc.uk.net [mailto:archive.cdc@cdc.uk.net archive.cdc@cdc.uk.net]

For vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com

For missangel.com [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# All remote outgoing mails save into the [mailto:log@groupvama.com log@groupvama.com]
# Openldap is in master slave mode, LDAP Master is DC and slave is DR.
# Chat server – openfire3.6 server installed
# Chat server LDAP BIND with “ou=jabber-users,dc=groupvama,dc=com”
# As for user management ldap account manager is installed

Details : '''182.71.29.139/lam'''

# Both Squirrelmail and roundcube is installed in DC Qmail server

Details :

mail.groupvama.com ----- For Roundcude

mail.groupvama.com------ For Squirrelmail

# Only squirrelmail installed in DR Site

182.50.142.178 --For squittelmail

16. LAM ldap account manager is installed in both DC and DR.

# Openfire is installed in DC Only
# Users on openfire is integrated with LDAP and groups is also integrated with LDAP
# As openfire client , they are using pidgin.

== ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP ==

[[Image:Architecture Diagram of MiraExim1.jpg|700px]]

Category:Mira Exim/Architecture Diagram

2013-03-02T11:24:26Z

Navdeep:

[[category:Mira Exim]]

== ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP ==

[[Image:Architecture Diagram of MiraExim1.jpg]]

Category:Mira Exim/Architecture Diagram

2013-03-02T11:20:31Z

Navdeep: Created page with "category:Mira Exim == ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP == Image:Architecture Diagram of MiraExim1.jpg"

[[category:Mira Exim]]

== ARCHITECTURE DIAGRAM OF MIRAEXIM GROUP ==

[[Image:Architecture Diagram of MiraExim1.jpg]]

Category:Mira Exim/MiraExim Architecture

2013-03-02T11:11:27Z

Navdeep: Created page with "http://192.168.1.15/wiki/images/thumb/f/fb/Architecture_Diagram_of_MiraExim1.jpg/776px-Architecture_Diagram_of_MiraExim1.jpg"

http://192.168.1.15/wiki/images/thumb/f/fb/Architecture_Diagram_of_MiraExim1.jpg/776px-Architecture_Diagram_of_MiraExim1.jpg

File:Architecture Diagram of MiraExim1.jpg

2013-03-02T11:07:23Z

Navdeep:

IP details of MiraExim Hosted on godaddy

2013-03-02T10:53:24Z

Navdeep:

[[category:Mira Exim]]

<center>'''IP DETAILS OF MIRAEXIM HOSTED ON GODADDY :'''</center>

'''DC SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.71.29.139'''

'''DR SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.50.142.178'''

'''LDAP DN : cn=Manager,dc=groupvama,dc=com'''

'''Jabber/Openfire Details:'''

'''Admin Pannel : '''

[http://182.71.29.139:9090/ http://182.71.29.139:9090]

Architecture Details of MiraExim

2013-03-02T10:50:25Z

Navdeep:

[[category:Mira Exim]]

<center>'''Architecture Details of Miraexim Ltd. Noida'''</center>

'''DC = MAIN SERVER'''

'''DR = DR SITE'''

# There are two qmail servers , one is for DC and other is for DR(Disaster Recovery)
# Two MX records are pointed for all domains ( groupwama.com, miraexim.com, vogueserv.com, cdc.uk.net) one is for DC-Local and other is for DR.
# If DC goes down then automatically mails coming on DR.
# '''But important is If DC is running then DR must be off.'''
# Only need to change A record of mail.domain.com ,By default it is pointed towards DC but when DC goes down it change to the DR IP.
# Implementation of both qmail servers are same.
# This qmail server has two instance , first instance for incoming and local outgoings, and second instance is for remote outgoing with disclaimer, all outgoing remote mails were copied into the [mailto:log@groupvama.com log@groupvama.com] through second instance.
# Mails archiving is done by forwarding for all domains have different archiving mailbox

For groupvama.com [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

For miraexim.com [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

For vogueserv.com [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

For cdc.uk.net [mailto:archive.cdc@cdc.uk.net archive.cdc@cdc.uk.net]

For vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com

For missangel.com [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# All remote outgoing mails save into the [mailto:log@groupvama.com log@groupvama.com]
# Openldap is in master slave mode, LDAP Master is DC and slave is DR.
# Chat server – openfire3.6 server installed
# Chat server LDAP BIND with “ou=jabber-users,dc=groupvama,dc=com”
# As for user management ldap account manager is installed

Details : '''182.71.29.139/lam'''

# Both Squirrelmail and roundcube is installed in DC Qmail server

Details :

mail.groupvama.com ----- For Roundcude

mail.groupvama.com------ For Squirrelmail

# Only squirrelmail installed in DR Site

182.50.142.178 --For squittelmail

16. LAM ldap account manager is installed in both DC and DR.

# Openfire is installed in DC Only
# Users on openfire is integrated with LDAP and groups is also integrated with LDAP
# As openfire client , they are using pidgin.

IP details of MiraExim Hosted on godaddy

2013-03-02T10:49:46Z

Navdeep:

[[category:Mira Exim]]

<center>'''IP DETAILS OF MIRAEXIM HOSTED ON GODADDY :'''</center>

'''DC SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.71.29.139'''
# '''USERNAME = ROOT '''
# '''PASSWORD = asd1234f'''
# '''Port=8470'''

'''DR SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.50.142.178'''
# '''USERNAME = ROOT'''
# '''PASSWORD = Mira1234@'''
# '''Port=22'''

'''LDAP DN : cn=Manager,dc=groupvama,dc=com'''

'''Password = MiraE#1920'''

'''Jebber/Openfire Details:'''

'''Admin Pannel : '''

[http://182.71.29.139:9090/ http://182.71.29.139:9090]

'''user : chatadmin'''

'''password : star123'''

DR-DC-DR CHANGE PROCESS FOR MiraExim

2013-03-02T10:48:49Z

Navdeep:

[[category:Mira Exim]]

<center>'''DC TO DR CHANGE PROCESS'''</center>

'''STEPS : '''

# '''First down the DC'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports are now closed'''

# '''Then on the DR Site'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash out the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports now opened'''

# '''Check logs at DR /var/log/qmail/qmail-send/current'''

<center>'''DRTO DC CHANGE PROCESS'''</center>

'''STEPS:'''

# '''First Down the DR'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports are now closed'''

'''And manually run one script “/root/scripts/sync.sh'''

'''Then all archived are copied into DC'''

# '''Then on the DC site'''
# '''Then on the DR Site'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash out the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports now opened'''

Implementation and customization of qmail for MiraExim

2013-03-02T10:45:44Z

Navdeep:

[[category:Mira Exim]]

<center>'''IMPLEMENTATIONS and CUSTOMIZATIONS FOR MIRAEXIM'''</center>

# '''Qmail with Disclaimer.'''

# '''LDAP Master-Slave with courier imap'''

# '''Mail Archiving (Done by forwarding) “ALL INCOMMIG MAILS”'''

'''For “Miraexim.com” Domain incoming mails forwarded to [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

'''For “groupvama.com’ Domain incoming mails forwarded to [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

'''For “vogueserv.com” Domain incoming mails forwarded to [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

'''For “cdc.uk.net” Domain incoming mails forwarded to [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

'''For “vikramadityaexports.com” Domain incoming mails forwarded to [mailto:archive.vikramadityaexports@vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com]

'''For “missangel.com” Domain incoming mails forwarded to [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# '''Mail Archiving “ALL OUTGOING MAILS”'''

'''All outgoing remote mails were copied to [mailto:log@groupvama.com log@groupvama.com], from qmail2'''

# '''SSL integration with smtp,pop3,imap and http.'''

# '''“catchall” account activated for all the domains.'''

# '''How to activate “catchall” account'''

* '''First create normal account on ldap ,ex : catch@domain.com'''
* '''Then give “mailAlternateAddress” as a [mailto:catchall@domain.com catchall@domain.com]
* '''Then all spams and unwanted received this catchall.'''

# '''DR Site is a backup copy of qmail DC.'''

# '''If DC is down then require to manually up DR by start qmail service from inittab.'''

# '''DR is an LDAP Slave.'''

# '''Openfire is implemented on DC qmail server'''

Satyam Cineplexes

2013-02-26T12:54:58Z

Navdeep: Created page with " == Problem : Mails were not getting delivered to some domain like "saviorstj.com". == Solution : This problem is because of TLS connection not creating at satyam cineplexe..."

== Problem : Mails were not getting delivered to some domain like "saviorstj.com". ==

Solution : This problem is because of TLS connection not creating at satyam cineplexes.

Step 1 : vim /var/qmail/control/smtproutes

saviorstj.com:122.180.25.62

: save and exit

saviorstj.com is domain and 122.180.25.62 is an IP address of modelama , from here we are relaying some domains from satyam cineplexes to modelama.

Step 2 : Now login into 122.180.25.62 and make entry inside /etc/tcp.smtp

119.226.41.70:allow,RELAYCLIENT=""

:save and exit

"119.226.41.70" is an Ip address of satyam cineplexes and we are allowing to accept connections from "119.226.41.70"

Step 3 : Run command on 122.180.25.62

tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp

Then check send mails from satyam and see then the logs at modelama.

Architecture Details of MiraExim

2013-02-16T08:12:50Z

Navdeep: Created page with "<center>'''Architecture Details of Miraexim Ltd. Noida'''</center> '''DC = MAIN SERVER''' '''DR = DR SITE''' # There are two qmail servers , one is for DC and other is for ..."

<center>'''Architecture Details of Miraexim Ltd. Noida'''</center>

'''DC = MAIN SERVER'''

'''DR = DR SITE'''

# There are two qmail servers , one is for DC and other is for DR(Disaster Recovery)
# Two MX records are pointed for all domains ( groupwama.com, miraexim.com, vogueserv.com, cdc.uk.net) one is for DC-Local and other is for DR.
# If DC goes down then automatically mails coming on DR.
# '''But important is If DC is running then DR must be off.'''
# Only need to change A record of mail.domain.com ,By default it is pointed towards DC but when DC goes down it change to the DR IP.
# Implementation of both qmail servers are same.
# This qmail server has two instance , first instance for incoming and local outgoings, and second instance is for remote outgoing with disclaimer, all outgoing remote mails were copied into the [mailto:log@groupvama.com log@groupvama.com] through second instance.
# Mails archiving is done by forwarding for all domains have different archiving mailbox

For groupvama.com [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

For miraexim.com [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

For vogueserv.com [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

For cdc.uk.net [mailto:archive.cdc@cdc.uk.net archive.cdc@cdc.uk.net]

For vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com

For missangel.com [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# All remote outgoing mails save into the [mailto:log@groupvama.com log@groupvama.com]
# Openldap is in master slave mode, LDAP Master is DC and slave is DR.
# Chat server – openfire3.6 server installed
# Chat server LDAP BIND with “ou=jabber-users,dc=groupvama,dc=com”
# As for user management ldap account manager is installed

Details : '''182.71.29.139/lam'''

# Both Squirrelmail and roundcube is installed in DC Qmail server

Details :

mail.groupvama.com ----- For Roundcude

mail.groupvama.com------ For Squirrelmail

# Only squirrelmail installed in DR Site

182.50.142.178 --For squittelmail

16. LAM ldap account manager is installed in both DC and DR.

# Openfire is installed in DC Only
# Users on openfire is integrated with LDAP and groups is also integrated with LDAP
# As openfire client , they are using pidgin.

DR-DC-DR CHANGE PROCESS FOR MiraExim

2013-02-16T07:57:12Z

Navdeep: Created page with "<center>'''DC TO DR CHANGE PROCESS'''</center> '''STEPS : ''' # '''First down the DC''' '''<nowiki># vim /etc/inittab</nowiki>''' '''Hash the SV:123456:respawn:/command/s..."

<center>'''DC TO DR CHANGE PROCESS'''</center>

'''STEPS : '''

# '''First down the DC'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports are now closed'''

# '''Then on the DR Site'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash out the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports now opened'''

# '''Check logs at DR /var/log/qmail/qmail-send/current'''

<center>'''DRTO DC CHANGE PROCESS'''</center>

'''STEPS:'''

# '''First Down the DR'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports are now closed'''

'''And manually run one script “/root/scripts/sync.sh'''

'''Then all archived are copied into DC'''

# '''Then on the DC site'''
# '''Then on the DR Site'''

'''<nowiki># vim /etc/inittab</nowiki>'''

'''Hash out the SV:123456:respawn:/command/svscanboot'''

'''Then save'''

'''<nowiki># </nowiki>init q'''

'''<nowiki># netstat –tunlp | grep tcpserver</nowiki>'''

'''All ports now opened'''

File:Architecture Diagram of MiraExim.pdf

2013-02-16T07:43:16Z

Navdeep:

Implementation and customization of qmail for MiraExim

2013-02-16T07:36:04Z

Navdeep:

<center>'''IMPLEMENTATIONS and CUSTOMIZATIONS FOR MIRAEXIM'''</center>

# '''Qmail with Disclaimer.'''

# '''LDAP Master-Slave with courier imap'''

# '''Mail Archiving (Done by forwarding) “ALL INCOMMIG MAILS”'''

'''For “Miraexim.com” Domain incoming mails forwarded to [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

'''For “groupvama.com’ Domain incoming mails forwarded to [mailto:archive.groupvama@groupvama.com archive.groupvama@groupvama.com]

'''For “vogueserv.com” Domain incoming mails forwarded to [mailto:archive.vogueserv@vogueserv.com archive.vogueserv@vogueserv.com]

'''For “cdc.uk.net” Domain incoming mails forwarded to [mailto:archive.miraexim@miraexim.com archive.miraexim@miraexim.com]

'''For “vikramadityaexports.com” Domain incoming mails forwarded to [mailto:archive.vikramadityaexports@vikramadityaexports.com archive.vikramadityaexports@vikramadityaexports.com]

'''For “missangel.com” Domain incoming mails forwarded to [mailto:archive.missangel@missangel.com archive.missangel@missangel.com]

# '''Mail Archiving “ALL OUTGOING MAILS”'''

'''All outgoing remote mails were copied to [mailto:log@groupvama.com log@groupvama.com], from qmail2'''

# '''SSL integration with smtp,pop3,imap and http.'''

# '''“catchall” account activated for all the domains.'''

# '''How to activate “catchall” account'''

* '''First create normal account on ldap ,ex : catch@domain.com'''
* '''Then give “mailAlternateAddress” as a [mailto:catchall@domain.com catchall@domain.com]
* '''Then all spams and unwanted received this catchall.'''

# '''DR Site is a backup copy of qmail DC.'''

# '''If DC is down then require to manually up DR by start qmail service from inittab.'''

# '''DR is an LDAP Slave.'''

# '''Openfire is implemented on DC qmail server'''

Implementation and customization of qmail for MiraExim

2013-02-16T07:34:26Z

Navdeep: Created page with "<center>'''IMPLEMENTATIONS and CUSTOMIZATIONS FOR MIRAEXIM'''</center> # '''Qmail with Disclaimer.''' # '''LDAP Master-Slave with courier imap''' # '''Mail Archiving (Done ..."

IP details of MiraExim Hosted on godaddy

2013-02-16T07:32:24Z

Navdeep: Created page with "<center>'''IP DETAILS OF MIRAEXIM HOSTED ON GODADDY :'''</center> '''DC SERVER :''' # '''Hostname : mail.groupvama.com''' # '''IP : 182.71.29.139''' # '''USERNAME = ROOT..."

<center>'''IP DETAILS OF MIRAEXIM HOSTED ON GODADDY :'''</center>

'''DC SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.71.29.139'''
# '''USERNAME = ROOT '''
# '''PASSWORD = asd1234f'''
# '''Port=8470'''

'''DR SERVER :'''

# '''Hostname : mail.groupvama.com'''
# '''IP : 182.50.142.178'''
# '''USERNAME = ROOT'''
# '''PASSWORD = Mira1234@'''
# '''Port=22'''

'''LDAP DN : cn=Manager,dc=groupvama,dc=com'''

'''Password = MiraE#1920'''

'''Jebber/Openfire Details:'''

'''Admin Pannel : '''

[http://182.71.29.139:9090/ http://182.71.29.139:9090]

'''user : chatadmin'''

'''password : star123'''

Qmail Server with Courier IMAP with Master/Slave LDAP for MiraExim

2013-02-16T07:11:04Z

Navdeep: Created page with "<center>'''Qmail Implementation with Courier IMAP,Master-Slave Openldap'''</center> <center>'''MIRAEXIM LTD. NOIDA'''</center> <center>'''BY- NAVDEEP MATHUR'''</center> <c..."

<center>'''Qmail Implementation with Courier IMAP,Master-Slave Openldap'''</center>

<center>'''MIRAEXIM LTD. NOIDA'''</center>

<center>'''BY- NAVDEEP MATHUR'''</center>

<center>'''IMPLEMENTING FIRST INSTANCE OF QMAIL'''</center>

'''Ensure rpmforge and epel repos are enabled.'''

* Switch off SELinux
* Flush Iptables rules

'''Create directory for downloading required packages '''

* mkdir /downloads
* cd /downloads

<center>'''DOWNLOAD AND EXTRACT PACKAGES'''</center>

'''Download all required packages for qmail-ldap installation '''

* wget http://www.qmailrocks.org/downloads/qmailrocks.tar.gz
* wget http://cr.yp.to/software/qmail-1.03.tar.gz
* wget http://cr.yp.to/ucspi-tcp/ucspi-tcp-0.88.tar.gz
* wget http://www.qmailrocks.org/downloads/patches/ucspi-tcp-0.88.errno.patch
* wget http://cr.yp.to/daemontools/daemontools-0.76.tar.gz
* wget http://www.qmail.org/moni.csi.hu/pub/glibc-2.3.1/daemontools-0.76.errno.patch
* wget http://www.nrg4u.com/qmail/qmail-ldap-1.03-20060201.patch.gz
* wget http://lifewithqmail.org/inst_check
* wget https://sourceforge.net/projects/courier/files/maildrop/2.5.4/maildrop-2.5.4.tar.bz2/download --no-check-certificate
* wget http://prdownloads.sourceforge.net/qmail-scanner/qmail-scanner-2.08.tgz?download
* wget http://www.qmailrocks.org/downloads/scripts/finalize/qmailctl
* wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm

'''Extract all packages : '''

* tar -xvzf qmailrocks.tar.gz
* tar -xvzf squirrelmail-webmail-1.4.22.tar.gz
* tar -xvjf maildrop-2.5.4.tar.bz2
* tar -xvzf qmail-scanner-2.08.tgz
* tar -xvzf qmailrocks/autorespond-2.0.5.tar.gz

<center>'''INSTALLATION OF PACKAGES AND CREATING USERS ,GROUPS'''</center>

'''Install all required packages before qmail-ldap installation '''

yum install vim-enhanced httpd php* php-ldap perl gcc* gcc-c++ gcc44* openssl openssl-devel kernel-headers openssl-devel kernel-headers patch pcre* db4* openldap* glibc* zlib* glib* gdbm* php

'''Create initial qmail '''

* mkdir /usr/src/qmail

'''Creating all needed users and groups '''

* groupadd nofiles
* useradd -g nofiles -d /var/qmail/alias -s /sbin/nologin -p'*' alias
* useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaild
* useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaill
* useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmailp
* groupadd qmail
* useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailq
* useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailr
* useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmails
* groupadd vmail
* useradd -g vmail -s /bin/true vmail

'''Unpack qmail and apply the qmail-ldap patch '''

* cd /usr/src/qmail
* tar -xvzf /downloads/qmail-1.03.tar.gz
* gunzip /downloads/qmail-ldap-1.03-20060201.patch.gz
* cd qmail-1.03
* <nowiki>patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch</nowiki>

'''Make changes on "Makefile" to qmail work properly with ldap'''

Make these entries :

LDAPFLAGS=-DQLDAP_CLUSTER -DEXTERNAL_TODO -DDASH_EXT -DDATA_COMPRESS -DQMQP_COMPRESS -DSMTPEXECCHECK -DALTQUEUE

<nowiki># ZLIB needed for -DDATA_COMPRESS and -DQMQP_COMPRESS</nowiki>

ZLIB=-lz

<nowiki># to enable the auto-maildir-make feature</nowiki>

MDIRMAKE=-DAUTOMAILDIRMAKE

<nowiki># to enable the auto-homedir-make feature</nowiki>

HDIRMAKE=-DAUTOHOMEDIRMAKE

<nowiki># on most systems we need this to make auth_pop and auth_imap</nowiki>

SHADOWLIBS=-lcrypt

<nowiki># to enable the possibility to log and debug imap and pop</nowiki>

DEBUG=-DDEBUG

* make man
* make setup check

'''Creating qmail control files '''

* cd /var/qmail/control
* echo 100 > concurrencyincoming
* echo 255 > concurrencyremote
* echo ./Maildir/ > defaultdelivery
* echo /var/qmail/bin/dirmaker > dirmaker
* echo 0 > ldapcluster
* id -g vmail > ldapgid
* echo /home/vmail > ldapmessagestore
* echo qmailUser > ldapobjectclass
* echo secret > ldappassword
* echo 127.0.0.1 > ldapserver
* id -u vmail > ldapuid
* echo 80000000 > qmail-smtpd-softlimit
* echo 80000000 > qmail-pop3d-softlimit
* echo 3 > qmail-pop3d-loglevel
* echo 3 > qmail-start-loglevel
* echo groupvama.com > defaultdomain
* echo dc=groupvama,dc=com > ldapbasedn
* echo cn=Manager,dc=groupvama,dc=com > ldaplogin
* echo mail.groupvama.com > me
* echo groupvama.com > rcpthosts
* echo miraexim.com > rcpthosts
* echo vogueserv.com > rcpthosts
* ln -s rcpthosts locals

'''Unpacking ucspi-tcpi and apply the error patch '''

* cd /usr/src/qmail
* tar -xvzf /downloads/ucspi-tcp-0.88.tar.gz
* cd ucspi-tcp-0.88
* <nowiki>patch < /downloads/ucspi-tcp-0.88.errno.patch</nowiki>
* make && make setup check

'''Unpacking daemontools and apply daemontools-error patch'''

* mkdir -p /package
* chmod 1755 /package
* cd /package
* tar -xvzf /downloads/daemontools-0.76.tar.gz
* cd /package/admin/daemontools-0.76/src
* <nowiki>patch < /downloads/daemontools-0.76.errno.patch</nowiki>
* cd /package/admin/daemontools-0.76
* package/install

'''Creating the supervise script directories'''

* mkdir /var/qmail/supervise
* cd /var/qmail/supervise
* mkdir -p qmail-smtpd/log qmail-send/log qmail-pop3d/log
* chmod +t qmail-smtpd qmail-send qmail-pop3d

'''Creating qmail-smtpd run supervise '''

* vim qmail-smtpd/run

<nowiki>#!/bin/sh</nowiki>

QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" ; export QMAILQUEUE

QUID=`id -u qmaild`

QGID=`id -g qmaild`

MAXD=`head -1 /var/qmail/control/concurrencyincoming`

HOST=`head -1 /var/qmail/control/me`

SOFT=`head -1 /var/qmail/control/qmail-smtpd-softlimit`

CDBF="/etc/tcp.smtp.cdb"

<nowiki>if [ -z "$QUID" -o -z "$QGID" -o -z "$MAXD" -o -z "$HOST" ]; then</nowiki>

echo QUID, QGID, MAXD, or HOST is unset in

echo /var/qmail/supervise/qmail-smtpd/run

exit 1

fi

exec /usr/local/bin/softlimit -m $SOFT \

/usr/local/bin/tcpserver -v \

-H \

-R \

-l $HOST \

-x $CDBF \

-c $MAXD \

-u $QUID \

-g $QGID \

0 \

smtp \

/var/qmail/bin/qmail-smtpd \

/var/qmail/bin/auth_smtp /usr/bin/true 2>&1

'''Creating qmail-smtpd log run supervise script'''

* vim qmail-smtpd/log/run

<nowiki>#!/bin/sh</nowiki>

export PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail/qmail-smtpd 2>&1

'''Creating qmail rc supervise script'''

* vim /var/qmail/rc

<nowiki>#!/bin/sh</nowiki>

QLOG="`cat /var/qmail/control/qmail-start-loglevel`"

DEFD="`cat /var/qmail/control/defaultdelivery`"

exec env - PATH="/var/qmail/bin:$PATH" LOGLEVEL="$QLOG" qmail-start "$DEFD"

'''Creating qmail-send run supervise script'''

* vim qmail-send/run

<nowiki>#!/bin/sh</nowiki>

exec /var/qmail/rc

'''Creating qmail-send log run supervise script '''

* vim qmail-send/log/run

<nowiki>#!/bin/sh</nowiki>

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail/qmail-send 2>&1

'''Creating qmail-pop3d run supervise script '''

* vim qmail-pop3d/run

<nowiki>#!/bin/sh</nowiki>

IP=`head -1 /var/qmail/control/me`

LL=`head -1 /var/qmail/control/qmail-pop3d-loglevel`

SL=`head -1 /var/qmail/control/qmail-pop3d-softlimit`

exec \

env LOGLEVEL=$LL \

softlimit -m $SL \

/usr/local/bin/tcpserver -v -R -H -l 0 0 pop3 \

/var/qmail/bin/qmail-popup $IP \

/var/qmail/bin/tcp-env \

/var/qmail/bin/auth_pop \

/var/qmail/bin/qmail-pop3d Maildir 2>&1

'''Creating qmail-pop3d log run supervise script'''

* vim qmail-pop3d/log/run

<nowiki>#!/bin/sh</nowiki>

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail/qmail-pop3d 2>&1

'''Creating auto directory maker script'''

* vim /var/qmail/bin/dirmaker

<nowiki>#!/bin/sh</nowiki>

echo '----------------------------------------------' >> /tmp/dirmaker

date >> /tmp/dirmaker

echo $1 >> /tmp/dirmaker

id >> /tmp/dirmaker

mkdir --parents -m 700 -p $1/Maildir

mkdir --parents -m 700 -p $1/Maildir/tmp

mkdir --parents -m 700 -p $1/Maildir/cur

mkdir --parents -m 700 -p $1/Maildir/new

chown -R vmail:vmail $1

'''Set permissions of all qmail supervise run scripts'''

* chmod 755 qmail-pop3d/run qmail-smtpd/run qmail-send/run
* chmod 755 qmail-pop3d/log/run qmail-smtpd/log/run qmail-send/log/run
* chmod 755 /var/qmail/rc /var/qmail/bin/dirmaker

'''Create tcp.smtp file to appy tcprules'''

* vim /etc/tcp.smtp

127.:allow,RELAYCLIENT="",MAXRCPTCOUNT="200"

192.168.:allow,BLOCKRELAYPROBE="",RCPTCHECK="",SENDERCHECK="",AUTHPREPEND="Authenticated user:",SANITYCHECK="",SMTPAUTH="",LOGLEVEL="3",AUTHREQUIRED="",MAXRCPTCOUNT="100"

:allow,BLOCKRELAYPROBE="",RCPTCHECK="",SANITYCHECK="",RETURNMXCHECK="STRICT",RBL="",REJECTEXEC="",LOGLEVEL="3",TARPITCOUNT="10",TARPITDELAY="10",SMTPAUTH="",MAXRCPTCOUNT="25"

'''Creating qmail logging directories and set permissions'''

* mkdir /var/log/qmail
* cd /var/log/qmail
* mkdir qmail-send qmail-smtpd qmail-pop3d
* chown -R qmaill:root /var/log/qmail
* chmod -R 750 /var/log/qmail

'''Creating qmail alias users, links and set permissions'''

* cd /var/qmail
* cp -p /downloads/qmailctl /var/qmail/bin/.
* chmod 755 /var/qmail/bin/qmailctl
* ln -s /var/qmail/bin/qmailctl /usr/bin/
* qmailctl cdb

'''Creating links of supervise scripts'''

* mkdir -p /service
* cd /service/
* ln -s /var/qmail/supervise/qmail-* .

'''Creating aliases '''

* echo qmailadmin@groupvama.com > /var/qmail/alias/.qmail-root
* echo qmailadmin@ groupvama.com > /var/qmail/alias/.qmail-postmaster
* echo qmailadmin@ groupvama.com > /var/qmail/alias/.qmail-mailer-daemon
* ln -s /var/qmail/alias/.qmail-root /var/qmail/alias/.qmail-anonymous
* chmod 644 /var/qmail/alias/.qmail*

'''Stop sendmail and remove all related files'''

* /etc/init.d/sendmail stop
* chkconfig sendmail off
* mv /usr/lib/sendmail /usr/lib/sendmail.org
* mv /usr/sbin/sendmail /usr/sbin/sendmail.org
* ln -s /var/qmail/bin/sendmail /usr/lib/sendmail
* ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail

<center>'''COURIER IMAP INSTALLATION'''</center>

'''Compile courier-authlib and install'''

* cd /downloads/qmailrocks/
* tar jxvf courier-authlib-0.55.tar.bz2
* cd courier-authlib-0.55
* ./configure --prefix=/usr/local --exec-prefix=/usr/local --with-authldap --without-authmysql --disable-root-check --with-ssl –with-authchangepwdir=/usr/local/libexec/authlib --with-redhat
* make && make check
* make install-strip && make install-configure

'''Create IMAP certificate and make changes on configuration files '''

* vim /usr/local/etc/imapd.cnf

(Change postmaser@example.com an administrative email address)

emailAddress=qmailadmin@groupvama.com

* vim /usr/local/etc/imapd

IMAPDSTART=YES

* vim /usr/local/etc/imapd-ssl

IMAPDSSLSTART=YES

TLS_CERTFILE=/var/qmail/control/clientcert.pem

* vim /usr/local/etc/authlib/authdaemonrc

authmodulelist="authldap"

authmodulelistorig="authldap"

* vim /usr/local/etc/authlib/authldaprc

LDAP_SERVER 127.0.0.1

LDAP_PORT 389

LDAP_BASEDN dc=groupvama,dc=com

LDAP_BINDDN cn=Manager,dc=groupvama,dc=com

LDAP_BINDPW MiraE#1920

LDAP_TIMEOUT 5

LDAP_AUTHBIND 1

LDAP_MAIL uid

LDAP_GLOB_UID vmail

LDAP_GLOB_GID vmail

LDAP_HOMEDIR mailMessageStore

LDAP_MAILROOT /home/vmail

LDAP_MAILDIR mailbox

LDAP_DEFAULTDELIVERY defaultDelivery

LDAP_FULLNAME cn

LDAP_CLEARPW clearPassword

LDAP_CRYPTPW userPassword

LDAP_DEREF never

LDAP_TLS 0

'''Copy imap and imaps script in init.d directory'''

cp /usr/local/libexec/imapd.rc /etc/rc.d/init.d/imap

cp /usr/local/libexec/imapd-ssl.rc /etc/rc.d/init.d/imaps

'''Make imap and imaps services start on boot'''

* vim /etc/rc.local

/usr/local/sbin/authdaemond start

/etc/rc.d/init.d/imap start

/etc/rc.d/init.d/imaps start

'''Restart authdaemon and imap services'''

* /usr/local/sbin/authdaemond stop
* /usr/local/sbin/authdaemond start
* /etc/rc.d/init.d/imap stop
* /etc/rc.d/init.d/imaps stop
* /etc/rc.d/init.d/imap start
* /etc/rc.d/init.d/imaps start

'''Install autoresponder and maildrop '''

* cd /downloads/autorespond-2.0.5/
* make && make install

* cd /downloads/maildrop-2.5.4
* ./configure --prefix=/usr/local --exec-prefix=/usr/local --enable-maildrop-uid=root
* make && make install-strip && make install-man

'''Install all required packages for Qmail-Scanner '''

* yum perl-suidperl perl-Digest-SHA1 perl-Digest-HMAC perl-Net-DNS perl-Time-HiRes* perl-HTML-Tagset perl-HTML-Parser perl-Pod-Usage* perl-Parse-Syslog perl-Statistics-Distributions spamassassin clamav clamd

'''Add user "qscand" for scanning '''

* useradd -c "Qmail-Scanner Account" -s /bin/false -m qscand

'''Change user clamav to qscand '''

* vim /etc/logrotate.d/clamav<nowiki>[Change clamav to qscand]</nowiki>

/var/log/clamav/clamd.log {

missingok

notifempty

create 644 qscand qscand

postrotate

killall -HUP clamd 2>/dev/null || :

endscript

}

* vim /etc/logrotate.d/freshclam<nowiki>[Change clamav to qscand]</nowiki>

/var/log/clamav/freshclam.log {

missingok

notifempty

create 644 qscand qscand

}

* vim /etc/clamd.conf

User qscand

* vim /etc/freshclam.conf

DatabaseOwner qscand

* chown qscand.qscand /var/log/clamav/ -R
* chown -R qscand.qscand /var/run/clamav/
* /etc/init.d/clamd restart
* /etc/init.d/spamassassin restart

'''Install Qmail-Scanner '''

* cd /downloads/qmail-scanner-2.08
* ./configure --admin admin --domain groupvama.com
* mkdir -p /var/spool/qscan
* mkdir -p /var/spool/qscan/quarantine/viruses/tmp /var/spool/qscan/quarantine/viruses/cur /var/spool/qscan/quarantine/viruses/new
* mkdir -p /var/spool/qscan/quarantine/spam/tmp /var/spool/qscan/quarantine/spam/cur /var/spool/qscan/quarantine/spam/new
* mkdir -p /var/spool/qscan/quarantine/policy/tmp /var/spool/qscan/quarantine/policy/cur /var/spool/qscan/quarantine/policy/new
* mkdir -p /var/spool/qscan/working/tmp /var/spool/qscan/working/cur /var/spool/qscan/working/new
* mkdir -p /var/spool/qscan/archive/tmp /var/spool/qscan/archive/cur /var/spool/qscan/archive/new
* cp /downloads/qmail-scanner-2.08/quarantine-events.txt /var/spool/qscan/
* chown -R qscand:qscand /var/spool/qscan/
* cp -pv /downloads/qmail-scanner-2.08/qmail-scanner-queue.pl /var/qmail/bin/
* chown qscand.qscand /var/qmail/bin/qmail-scanner-queue.pl
* chmod 4755 /var/qmail/bin/qmail-scanner-queue.pl
* /var/qmail/bin/qmail-scanner-queue.pl -z
* /var/qmail/bin/qmail-scanner-queue.pl -g
* cp -v /downloads/qmail-scanner-2.08/contrib/logrotate.qmail-scanner /etc/logrotate.d/qmail-scanner
* /etc/init.d/syslog restart

'''Integrate Qmail-scanner with qmail queue'''

* vim /var/qmail/supervise/qmail-smtpd/run

QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" ; export QMAILQUEUE

<center>'''IMPLEMENTING SECOND INSTANCE OF QMAIL WITH DISCLAIMER AND COPY OF ALL OUTGOING MESSAGES'''</center>

<center>'''CONCEPT'''</center>

Disclaimer on Qmail is Added to the Second Instance so that only Out going mails to different domains are uploaded with Common Signature / Disclaimer. Here this is used for multiple domains. Also second instance use to copy of all outgoing messages at log@groupvama.com.

<center>'''IMPLEMENTAION PROCESS'''</center>

* Implement Qmail-2 , i.e Second Qmail Instance
* Define Qmail-send and Qmail-smtpd daemons
* Define 2nd Qmail smtp port ( say 900)
* Install Qmail-qfilter , altermime and bglibs to satisfy the requirement.
* Define Multiple domain's text and HTML disclaimer
* Integrate Qmail's both the instances

<center>'''INSTALLATION OF QMAIL2'''</center>

'''Creating directories for installing qmail2'''

* mkdir -p /var/qmail2
* mkdir /usr/src/qmail2
* cd /usr/src/qmail2

'''Unpack qmail in /usr/src/qmail2 and apply qmail-ldap patch(this patch contain qmail queue and qmail error patch)'''

* tar xvzf /downloads/qmailrocks/qmail-1.03.tar.gz ( Assuming that you have downloaded Qmailrocks earlier )
* cd qmail-1.03
* <nowiki>patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch</nowiki>
* echo 255 > /usr/src/qmail2/qmail-1.03/conf-spwan
* echo 211 > /usr/src/qmail2/qmail-1.03/conf-split

'''Make changes on "Makefile" to qmail work properly with ldap'''

Make these entries :

LDAPFLAGS=-DQLDAP_CLUSTER -DEXTERNAL_TODO -DDASH_EXT -DDATA_COMPRESS -DQMQP_COMPRESS -DSMTPEXECCHECK -DALTQUEUE

ZLIB=-lz

SHADOWLIBS=-lcrypt

DEBUG=-DDEBUG

* vim conf-qmail

( replace qmail with qmail2 )

'''Caution:''' This is very critical Step as, not doing do will cause the main Qmail instance will get over written .

'''Keep a copy of all outgoing mail messages '''

* vim extra.h

QUEUE_EXTRA "Tlog\0"

QUEUE_EXTRALEN 5

* make man
* make setup check

'''Qmail2 Control Files'''

* cd /var/qmail2/control/

* echo 100 > concurrencyincoming
* echo 255 > concurrencyremote
* echo ./Maildir/ > defaultdelivery
* echo /var/qmail/bin/dirmaker > dirmaker
* echo 0 > ldapcluster
* id -g vmail > ldapgid
* echo /home/vmail > ldapmessagestore
* echo qmailUser > ldapobjectclass
* echo secret > ldappassword
* echo 127.0.0.1 > ldapserver
* id -u vmail > ldapuid
* echo 80000000 > qmail-smtpd-softlimit
* echo 80000000 > qmail-pop3d-softlimit
* echo 3 > qmail-pop3d-loglevel
* echo 3 > qmail-start-loglevel
* echo groupvama.com > defaultdomain
* echo dc=groupvama,dc=com > ldapbasedn
* echo cn=Manager,dc=groupvama,dc=com > ldaplogin
* echo mail.groupvama.com > me

'''Qmail2 Daemons '''

Now create qmail2-smtpd and qmail2-send daemons

* Create /var/qmail2/rc

<nowiki>#!/bin/sh</nowiki>

QLOG="`cat /var/qmail2/control/qmail-start-loglevel`"

DEFD="`cat /var/qmail2/control/defaultdelivery`"

exec env - PATH="/var/qmail2/bin:$PATH" LOGLEVEL="$QLOG" qmail-start "$DEFD"

* chmod 755 /var/qmail2/rc

'''Create supervise directories for Qmail2-send and Qmail2-smtpd and log directories '''

* mkdir -p /var/qmail2/supervise/qmail2-smtpd/log
* mkdir -p /var/qmail2/supervise/qmail2-send/log
* mkdir -p /var/log/qmail2/qmail2-smtpd/
* mkdir -p /var/log/qmail2/qmail2-send/
* chown -R qmaill.nofiles /var/log/qmail2/

'''Daemon for Qmail2-send '''

* vim /var/qmail2/supervise/qmail2-send/run

<nowiki>#!/bin/sh</nowiki>

exec /var/qmail2/rc

* chmod 755 /var/qmail2/supervise/qmail2-send/run

'''Log daemon for Qmail2-send '''

* vim/var/qmail2/supervise/qmail2-send/log/run

<nowiki>#!/bin/sh</nowiki>

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail2/qmail2-send 2>&1

'''Daemon for Qmail2-smtpd '''

* vim /var/qmail2/supervise/qmail2-smtpd/run

<nowiki>#!/bin/sh</nowiki>

QMAILQUEUE="/var/qmail2/bin/qmail-tail"; export QMAILQUEUE

QUID=`id -u qmaild`

QGID=`id -g qmaild`

MAXD=`head -1 /var/qmail2/control/concurrencyincoming`

HOST=`head -1 /var/qmail2/control/me`

SOFT=`head -1 /var/qmail2/control/qmail-smtpd-softlimit`

CDBF="/etc/tcp.smtp.cdb"

<nowiki>if [ -z "$QUID" -o -z "$QGID" -o -z "$MAXD" -o -z "$HOST" ]; then</nowiki>

echo QUID, QGID, MAXD, or HOST is unset in

echo /var/qmail/supervise/qmail-smtpd/run

exit 1

fi

exec /usr/local/bin/softlimit -m $SOFT \

/usr/local/bin/tcpserver -v \

-H \

-R \

-l $HOST \

-x $CDBF \

-c $MAXD \

-u $QUID \

-g $QGID \

0 \

qmail-second \

/var/qmail2/bin/qmail-smtpd \

/var/qmail2/bin/auth_smtp /usr/bin/true 2>&1

* chmod 755 /var/qmail2/supervise/qmail2-smtpd/run

'''Log daemon for Qmail2-smtpd '''

* vim /var/qmail2/supervise/qmail2-smtpd/log/run

<nowiki>#!/bin/sh</nowiki>

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail2/qmail2-smtpd 2>&1

* chmod 755 /var/qmail2/supervise/qmail2-smtpd/log/run

'''Link these file to /service '''

* ln -s /var/qmail2/supervise/qmail2-smtpd /service/
* ln -s /var/qmail2/supervise/qmail2-send /service/

'''Restart the Qmail via inttab process '''

<center>'''Testing of Qmail - Second instance'''</center>

* telnet to port 900 and send the mail .
* check for logs /var/log/qmail2/qmail2-send/current or /var/log/qmail2/qmail2-smtpd/current

= Disclaimer Related Implementation =
'''Install bglibs for qmail2'''

* cd /downloads/
* rpm –Uvh bglibs-1.022-1.i386.rpm ( get it from [http://untroubled.org/bglibs/ http://untroubled.org/bglibs/] )

or

* tar -xvfz bglibs-1.022-1.tar.gz
* cd bglibs-1.022-1
* make
* make install

'''Install altermime for qmail2'''

* tar xvzf altermime-0.3.6.tar.gz (get it from [http://www.pldaniels.com/altermime/ http://www.pldaniels.com/altermime/] )
* cd altermime-0.3.6
* make
* make install

'''Install qmail-qfilter for qmail2'''

* tar xvzf qmail-qfilter-2.1.tar.gz ([http://untroubled.org/qmail-qfilter/ http://untroubled.org/qmail-qfilter/])
* cd qmail-qfilter-2.1
* vi qmail-qfilter.c

( change qmail into qmail2 )

<nowiki>#ifndef QMAIL_QUEUE </nowiki>

<nowiki>#define QMAIL_QUEUE "/var/</nowiki>qmail2/bin/qmail-queue"

<nowiki>#endif </nowiki>

* make
* make install
* chmod 777 /usr/local/bin/qmail-qfilter
* chown root:qmail /usr/local/bin/qmail-qfilter

'''Disclaimer Settings'''

* vi /var/qmail2/bin/qmail-tail

<nowiki>#!/bin/sh</nowiki>

exec /usr/local/bin/qmail-qfilter /var/qmail2/bin/qmail-disclaimer

* chown root:qmail /var/qmail2/bin/qmail-tail
* chmod 777 /var/qmail2/bin/qmail-tail
* mkdir /var/qmail2/control/disclaimer/
* cd /var/qmail2/control/disclaimer
* vim groupvama.com.html

<nowiki><html></nowiki>

<nowiki><body></nowiki>

DISCLAIMER:

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorised use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

<nowiki></body></nowiki>

<nowiki></html></nowiki>

* vim gropvama.com.txt

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

* chown root:qmail /var/qmail2/control/disclaimer/*
* chmod 777 /var/qmail2/control/disclaimer/*
* mkdir /var/tmp/qmail-qfilter
* chown root:qmail /var/tmp/qmail-qfilter
* chmod 777 /var/tmp/qmail-qfilter
* vi /var/qmail2/bin/qmail-disclaimer

<nowiki>#!/bin/sh</nowiki>

QMAILHOST=groupvama.com

INSPECT_DIR=/var/tmp/qmail-qfilter

<nowiki>if [ ! -f /var/qmail2/control/disclaimer/$QMAILHOST.txt ]</nowiki>

then

cat

exit 0

fi

EX_TEMPFAIL=31

EX_UNAVAILABLE=31

trap "rm -f /var/tmp/qmail-qfilter/in.$$" 0 1 2 3 15

cd $INSPECT_DIR || { echo Error: $INSPECT_DIR does not exist; exit $EX_TEMPFAIL; }

cat >$INSPECT_DIR/in.$$ || { echo Error: Cannot write to disk; exit $EX_TEMPFAIL; }

/usr/local/bin/altermime --input=$INSPECT_DIR/in.$$ \

--xheader="X-Disclaimer: $QMAILHOST" \

--disclaimer=/var/qmail2/control/disclaimer/$QMAILHOST.txt \

--disclaimer-html=/var/qmail2/control/disclaimer/$QMAILHOST.html || { echo Error: message rejected; exit $EX_UNAVAILABLE; }

cat $INSPECT_DIR/in.$$

rm in.$$

exit $?

* chown root:qmail /var/qmail2/bin/qmail-disclaimer
* chmod 777 /var/qmail2/bin/qmail-disclaimer

== Activation of Qmail2 ==
'''Changes on Qmail2-Send run file '''

* vi /service/qmail2-smtpd/run

( add following line at the top )

<nowiki>#!/bin/sh</nowiki>

QMAILQUEUE="/var/qmail2/bin/qmail-tail"; export QMAILQUEUE

Also Make sure the Qmail-smtpd is running on port 900 by

* vi /etc/services

<nowiki># Local services</nowiki>

second-qmail 900/tcp

'''Integrate Qmail with Qmail2 '''

vi /var/qmail/control/smtproutes

:127.0.0.1:900

'''Note: Then restart the qmail from /etc/inittab file'''

== Testing ==
* Telnet and send mail via Qmail-2 , you should get the disclaimer
* Test via offline Client like Evolution , Outlook etc . You should get the mail with

== Troubleshooting ==
* QQ error while sending mails

Check the smtp logs , if find error like

''/usr/local/bin/qmail-qfilter: error while loading shared libraries: libbg-sysdeps.so.1: cannot open shared object file: No such file or directory''

Then

you have to link libbg-sysdeps.so.1 to /usr/lib

* ln -s /usr/local/bglibs/lib/libbg-sysdeps.so.1 /usr/lib/

This should solve the issue

* 2. Some time the Qmail-1 is not able to deliver mails to Qmail-2 instance due to /var/tmp/qmail-qfilter directory is not there or vanishes. So a script to check and create the directory with cron is created for taking care of this issue.

The script is /usr/bin/check_qmail-qfilter_dir.sh

<nowiki>#!/bin/sh</nowiki>

DIRECTORY=/var/tmp/qmail-qfilter

<nowiki>if [ ! -d "$DIRECTORY" ]; then</nowiki>

mkdir -p $DIRECTORY;

chmod 777 $DIRECTORY;

chown -R root.qmail $Directory

fi

The cron entry is as follows

* crontab -e

<nowiki>*/5 * * * * /usr/bin/check_qmail-qfilter_dir.sh</nowiki>

<center>'''OPENLDAP MASTER SLAVE'''</center>

'''Openldap master (slapd.conf)'''

* Vim /etc/openldap/ldap.conf

BASE dc=groupvama,dc=com

URI ldap://127.0.0.1/

* Vim /etc/openldap/slapd.conf

<nowiki>#</nowiki>

<nowiki># See slapd.conf(5) for details on configuration options.</nowiki>

<nowiki># This file should NOT be world readable.</nowiki>

<nowiki>#</nowiki>

include /etc/openldap/schema/core.schema

include /etc/openldap/schema/cosine.schema

include /etc/openldap/schema/inetorgperson.schema

include /etc/openldap/schema/nis.schema

include /etc/openldap/schema/qmail.schema

include /etc/openldap/schema/dnszone.schema

<nowiki># Allow LDAPv2 client connections. </nowiki>This is NOT the default.

allow bind_v2

<nowiki># Do not enable referrals until AFTER you have a working directory</nowiki>

<nowiki># service AND an understanding of referrals.</nowiki>

<nowiki>#referral </nowiki>ldap://root.openldap.org

pidfile /var/run/openldap/slapd.pid

argsfile /var/run/openldap/slapd.args

<nowiki># Load dynamic backend modules:</nowiki>

<nowiki># modulepath </nowiki>/usr/lib64/openldap

<nowiki># Modules available in openldap-servers-overlays RPM package</nowiki>

<nowiki># Module syncprov.la is now statically linked with slapd and there</nowiki>

<nowiki># is no need to load it here</nowiki>

<nowiki># moduleload accesslog.la</nowiki>

<nowiki># moduleload auditlog.la</nowiki>

<nowiki># moduleload denyop.la</nowiki>

<nowiki># moduleload dyngroup.la</nowiki>

<nowiki># moduleload dynlist.la</nowiki>

<nowiki># moduleload lastmod.la</nowiki>

<nowiki># moduleload pcache.la</nowiki>

<nowiki># moduleload ppolicy.la</nowiki>

<nowiki># moduleload refint.la</nowiki>

<nowiki># moduleload retcode.la</nowiki>

<nowiki># moduleload rwm.la</nowiki>

<nowiki># moduleload smbk5pwd.la</nowiki>

<nowiki># moduleload translucent.la</nowiki>

<nowiki># moduleload unique.la</nowiki>

<nowiki># moduleload valsort.la</nowiki>

<nowiki># modules available in openldap-servers-sql RPM package:</nowiki>

<nowiki># moduleload back_sql.la</nowiki>

<nowiki># The next three lines allow use of TLS for encrypting connections using a</nowiki>

<nowiki># dummy test certificate which you can generate by changing to</nowiki>

<nowiki># /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on</nowiki>

<nowiki># slapd.pem so that the ldap user or group can read it. </nowiki>Your client software

<nowiki># may balk at self-signed certificates, however.</nowiki>

<nowiki># TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt</nowiki>

<nowiki># TLSCertificateFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># Sample security restrictions</nowiki>

<nowiki># </nowiki>Require integrity protection (prevent hijacking)

<nowiki># </nowiki>Require 112-bit (3DES or better) encryption for updates

<nowiki># </nowiki>Require 63-bit encryption for simple bind

<nowiki># security ssf=1 update_ssf=112 simple_bind=64</nowiki>

<nowiki># Sample access control policy:</nowiki>

<nowiki># </nowiki>Root DSE: allow anyone to read it

<nowiki># </nowiki>Subschema (sub)entry DSE: allow anyone to read it

<nowiki># </nowiki>Other DSEs:

<nowiki># </nowiki>Allow self write access

<nowiki># </nowiki>Allow authenticated users read access

<nowiki># </nowiki>Allow anonymous users to authenticate

<nowiki># </nowiki>Directives needed to implement policy:

<nowiki># access to dn.base="" by * read</nowiki>

<nowiki># access to dn.base="cn=Subschema" by * read</nowiki>

<nowiki># access to *</nowiki>

<nowiki># </nowiki>by self write

<nowiki># </nowiki>by users read

<nowiki># </nowiki>by anonymous auth

<nowiki>#</nowiki>

<nowiki>#access to *</nowiki>

<nowiki># </nowiki>by dn.exact="cn=Manager,dc=groupvama,dc=com" read

<nowiki># </nowiki>by * none

<nowiki># if no access controls are present, the default policy</nowiki>

<nowiki># allows anyone and everyone to read anything but restricts</nowiki>

<nowiki># updates to rootdn. </nowiki>(e.g., "access to * by * read")

<nowiki># modules available in openldap-servers-sql RPM package:</nowiki>

<nowiki># moduleload back_sql.la</nowiki>

<nowiki># The next three lines allow use of TLS for encrypting connections using a</nowiki>

<nowiki># dummy test certificate which you can generate by changing to</nowiki>

<nowiki># /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on</nowiki>

<nowiki># slapd.pem so that the ldap user or group can read it. </nowiki>Your client software

<nowiki># may balk at self-signed certificates, however.</nowiki>

<nowiki># TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt</nowiki>

<nowiki># TLSCertificateFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># Sample security restrictions</nowiki>

<nowiki># </nowiki>Require integrity protection (prevent hijacking)

<nowiki># </nowiki>Require 112-bit (3DES or better) encryption for updates

<nowiki># </nowiki>Require 63-bit encryption for simple bind

<nowiki># security ssf=1 update_ssf=112 simple_bind=64</nowiki>

<nowiki># Sample access control policy:</nowiki>

<nowiki># </nowiki>Root DSE: allow anyone to read it

<nowiki># </nowiki>Subschema (sub)entry DSE: allow anyone to read it

<nowiki># </nowiki>Other DSEs:

<nowiki># </nowiki>Allow self write access

<nowiki># </nowiki>Allow authenticated users read access

<nowiki># </nowiki>Allow anonymous users to authenticate

<nowiki># </nowiki>Directives needed to implement policy:

<nowiki># access to dn.base="" by * read</nowiki>

<nowiki># access to dn.base="cn=Subschema" by * read</nowiki>

<nowiki># access to *</nowiki>

<nowiki># </nowiki>by self write

<nowiki># </nowiki>by users read

<nowiki># </nowiki>by anonymous auth

<nowiki>#</nowiki>

<nowiki>#access to *</nowiki>

<nowiki># </nowiki>by dn.exact="cn=Manager,dc=groupvama,dc=com" read

<nowiki># </nowiki>by * none

<nowiki># if no access controls are present, the default policy</nowiki>

<nowiki># allows anyone and everyone to read anything but restricts</nowiki>

<nowiki># updates to rootdn. </nowiki>(e.g., "access to * by * read")

<nowiki>#</nowiki>

<nowiki># rootdn can always read and write EVERYTHING!</nowiki>

<nowiki>#######################################################################</nowiki>

<nowiki># ldbm and/or bdb database definitions</nowiki>

<nowiki>#######################################################################</nowiki>

serverID 001

database bdb

suffix "dc=groupvama,dc=com"

rootdn "cn=Manager,dc=groupvama,dc=com"

<nowiki># Cleartext passwords, especially for the rootdn, should</nowiki>

<nowiki># be avoided. </nowiki>See slappasswd(8) and slapd.conf(5) for details.

<nowiki># Use of strong authentication encouraged.</nowiki>

rootpw MiraE#1920

<nowiki># rootpw </nowiki>{crypt}ijFYNcSNctBYg

<nowiki># The database directory MUST exist prior to running slapd AND</nowiki>

<nowiki># should only be accessible by the slapd and slap tools.</nowiki>

<nowiki># Mode 700 recommended.</nowiki>

directory /var/lib/ldap

<nowiki># Indices to maintain for this database</nowiki>

index objectClass eq,pres

index ou,cn,mail,surname,givenname eq,pres,sub

index uidNumber,gidNumber,loginShell eq,pres

index uid,memberUid eq,pres,sub

index nisMapName,nisMapEntry eq,pres,sub

<nowiki># Replicas of this database</nowiki>

<nowiki>#replogfile /var/lib/ldap/openldap-master-replog</nowiki>

<nowiki>#replica host=ldap-1.example.com:389 starttls=critical</nowiki>

<nowiki># </nowiki>bindmethod=sasl saslmech=GSSAPI

<nowiki># </nowiki>authcId=host/ldap-master.example.com@EXAMPLE.COM

overlay syncprov

syncprov-checkpoint 100 10

syncprov-sessionlog 100

replica uri=ldap://182.71.29.139:389

binddn="cn=Manager,dc=groupvama,dc=com"

bindmethod=simple credentials=MiraE#1920

'''Openldap slave (slapd.conf)'''

* '''Vim /etc/openldap/slapd.conf'''

<nowiki>#</nowiki>

<nowiki># See slapd.conf(5) for details on configuration options.</nowiki>

<nowiki># This file should NOT be world readable.</nowiki>

<nowiki>#</nowiki>

include /etc/openldap/schema/core.schema

include /etc/openldap/schema/cosine.schema

include /etc/openldap/schema/inetorgperson.schema

include /etc/openldap/schema/nis.schema

include /etc/openldap/schema/qmail.schema

<nowiki># Allow LDAPv2 client connections. </nowiki>This is NOT the default.

allow bind_v2

<nowiki># Do not enable referrals until AFTER you have a working directory</nowiki>

<nowiki># service AND an understanding of referrals.</nowiki>

<nowiki>#referral </nowiki>ldap://root.openldap.org

pidfile /var/run/openldap/slapd.pid

argsfile /var/run/openldap/slapd.args

<nowiki># Load dynamic backend modules:</nowiki>

<nowiki># modulepath </nowiki>/usr/lib/openldap

<nowiki># Modules available in openldap-servers-overlays RPM package</nowiki>

<nowiki># Module syncprov.la is now statically linked with slapd and there</nowiki>

<nowiki># is no need to load it here</nowiki>

<nowiki># moduleload accesslog.la</nowiki>

<nowiki># moduleload auditlog.la</nowiki>

<nowiki># moduleload denyop.la</nowiki>

<nowiki># moduleload dyngroup.la</nowiki>

<nowiki># moduleload dynlist.la</nowiki>

<nowiki># moduleload lastmod.la</nowiki>

<nowiki># moduleload pcache.la</nowiki>

<nowiki># moduleload ppolicy.la</nowiki>

<nowiki># moduleload refint.la</nowiki>

<nowiki># moduleload retcode.la</nowiki>

<nowiki># moduleload rwm.la</nowiki>

<nowiki># moduleload smbk5pwd.la</nowiki>

<nowiki># moduleload translucent.la</nowiki>

<nowiki># moduleload unique.la</nowiki>

<nowiki># moduleload valsort.la</nowiki>

<nowiki># modules available in openldap-servers-sql RPM package:</nowiki>

<nowiki># moduleload back_sql.la</nowiki>

<nowiki># The next three lines allow use of TLS for encrypting connections using a</nowiki>

<nowiki># dummy test certificate which you can generate by changing to</nowiki>

<nowiki># /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on</nowiki>

<nowiki># slapd.pem so that the ldap user or group can read it. </nowiki>Your client software

<nowiki># may balk at self-signed certificates, however.</nowiki>

<nowiki># TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt</nowiki>

<nowiki># TLSCertificateFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem</nowiki>

<nowiki># Sample security restrictions</nowiki>

<nowiki># </nowiki>Require integrity protection (prevent hijacking)

<nowiki># </nowiki>Require 112-bit (3DES or better) encryption for updates

<nowiki># </nowiki>Require 63-bit encryption for simple bind

<nowiki># security ssf=1 update_ssf=112 simple_bind=64</nowiki>

<nowiki># Sample access control policy:</nowiki>

<nowiki># </nowiki>Root DSE: allow anyone to read it

<nowiki># </nowiki>Subschema (sub)entry DSE: allow anyone to read it

<nowiki># </nowiki>Other DSEs:

<nowiki># </nowiki>Allow self write access

<nowiki># </nowiki>Allow authenticated users read access

<nowiki># </nowiki>Allow anonymous users to authenticate

<nowiki># </nowiki>Directives needed to implement policy:

<nowiki># access to dn.base="" by * read</nowiki>

<nowiki># access to dn.base="cn=Subschema" by * read</nowiki>

<nowiki># access to *</nowiki>

<nowiki># </nowiki>by self write

<nowiki># </nowiki>by users read

<nowiki># </nowiki>by anonymous auth

<nowiki>#</nowiki>

<nowiki># if no access controls are present, the default policy</nowiki>

<nowiki># allows anyone and everyone to read anything but restricts</nowiki>

<nowiki># updates to rootdn. </nowiki>(e.g., "access to * by * read")

<nowiki>#</nowiki>

<nowiki># rootdn can always read and write EVERYTHING!</nowiki>

<nowiki>#access to *</nowiki>

<nowiki># </nowiki>by dn.exact="cn=Manager,dc=groupvama,dc=com" read

<nowiki># </nowiki>by * none

<nowiki>#######################################################################</nowiki>

<nowiki># ldbm and/or bdb database definitions</nowiki>

<nowiki>#######################################################################</nowiki>

serverID 002

database bdb

<nowiki>#suffix </nowiki>"dc=my-domain,dc=com"

<nowiki>#rootdn </nowiki>"cn=Manager,dc=my-domain,dc=com"

suffix "dc=groupvama,dc=com"

rootdn "cn=Manager,dc=groupvama,dc=com"

<nowiki># Cleartext passwords, especially for the rootdn, should</nowiki>

<nowiki># be avoided. </nowiki>See slappasswd(8) and slapd.conf(5) for details.

<nowiki># Use of strong authentication encouraged.</nowiki>

<nowiki># rootpw </nowiki>secret

<nowiki># rootpw </nowiki>{crypt}ijFYNcSNctBYg

rootpw MiraE#1920

<nowiki># The database directory MUST exist prior to running slapd AND</nowiki>

<nowiki># should only be accessible by the slapd and slap tools.</nowiki>

<nowiki># Mode 700 recommended.</nowiki>

directory /var/lib/ldap

<nowiki># Indices to maintain for this database</nowiki>

index objectClass eq,pres

index ou,cn,mail,surname,givenname eq,pres,sub

index uidNumber,gidNumber,loginShell eq,pres

index uid,memberUid eq,pres,sub

index nisMapName,nisMapEntry eq,pres,sub

<nowiki># Replicas of this database</nowiki>

<nowiki>#replogfile /var/lib/ldap/openldap-master-replog</nowiki>

<nowiki>#replica host=ldap-1.example.com:389 starttls=critical</nowiki>

<nowiki># </nowiki>bindmethod=sasl saslmech=GSSAPI

<nowiki># </nowiki>authcId=host/ldap-master.example.com@EXAMPLE.COM

<nowiki>#syncrepl rid=001</nowiki>

<nowiki>#provider=ldap://182.71.29.139</nowiki>

<nowiki>#type=refreshAndPersist</nowiki>

<nowiki>#searchbase="dc=groupvama,dc=com"</nowiki>

<nowiki>#filter="(objectClass=*)"</nowiki>

<nowiki>#scope=sub</nowiki>

<nowiki>#attrs="*"</nowiki>

<nowiki>#bindmethod=simple</nowiki>

<nowiki>#binddn="cn=Manager,dc=groupvama,dc=com"</nowiki>

<nowiki>#credentials=MiraE#1920</nowiki>

syncrepl rid=001

provider=ldap://182.71.29.139

type=refreshAndPersist

retry="60 +"

searchbase="dc=groupvama,dc=com"

scope=sub

schemachecking=on

bindmethod=simple

binddn="cn=Manager,dc=groupvama,dc=com"

credentials=MiraE#1920

mirrormode on

Then restart ldap on both automatically master slave synchronize.

HPC High Processing Cluster in BITS PILANI

2013-01-22T10:08:48Z

Navdeep: /* INSTALLATION OF MPI(MESSAGE PASSING INTERFACE) */

[[category:Bits pilani]]

==<center>'''HIGH PROCESSING CLUSTER USING MPICH2'''</center>==

'''FOR 2 NODES AND 9 NODES CLUSTER'''

'''NAVDEEP MATHUR'''

== <center>'''ARCHITECTURE – VLSI LAB DATA CENTER (BITS-PILANI)'''</center>==

<center>[[Image:bits_p.png]]</center>

==<center>'''ARCHITECTURE DETAILS'''</center>==

* They have two IBM servers and nine Sunfire servers.
* On two IBM servers have installed HPC 2- Node Cluster, High Availability over NFS and multimaster LDAP.
* All home directories are stored in these two ibm servers have separate HDD and they don’t have SAN , So need to rsync home directories from one to another IBM Server.
* Other nine Sunfire servers have HPC-9 Node cluster Installed.
* All sunfire servers are LDAP Client and NFS Client
* HPC 2- Node cluster uses only two home directories /staff and /projects have GID is 501 and 502 and permission is 770 because of group of members access this directory from another user as well.
* HPC 9-Node cluster uses another two home directories that is mounted in all 9 machines /ugassignmnets and /pgassignments have GID is 503 and 504 and permission is 770 because of group of members access this directory from another user as well.
* LDAP have four different OU’s for these distribution of users according GID wise.
* Members of staff and projects can’t able to use sunfire systems because GID is mismatched.
* Once if you want to run application by mpi mode then first you need to login from ldap user then switch to wolf/lam user on 2-Node IBM HPC or wolf2/lam1 user on 9-Node sunfire HPC accordingly.
* All binaries like cadence,mentor,etc. are stored in /linuxeda on all 11 servers.
* All clients are use VNC as well as Sunray.
* VNC Server are installed in all 11 servers.
* Both master node handle ganglia for hpc monitoring [http://172.20.4.25/ganglia http://172.20.4.25/ganglia] and [http://172.20.4.39/ganglia http://172.20.4.39/ganglia]
* Script is running for syncing home directories in every 4 hours located at on 172.20.4.39 “/root/script/homedir.sh”
* Ldap user add script is located at on both servers under “/root/script/”, by default password is “user123”.

='''IBM 2-Node Machines IP/HOSTNAME Details :'''=

172.20.4.39ibm-39.bits.ac

172.20.4.40ibm-40.bits.ac

'''Virtual HA IP : 172.20.4.43'''

=='''Sunfire 9-Node Machines IP/HOSTNAMES Details :'''==

172.20.4.25sunfire-25

172.20.4.26sunfire-26

172.20.4.27sunfire-27

172.20.4.28sunfire-28

172.20.4.29sunfire-29

172.20.4.30sunfire-30

172.20.4.31sunfire-31

172.20.4.32sunfire-32

172.20.4.33sunfire-33

== <center>'''INTRODUCTION OF HIGH PROCESSING CLUSTER'''</center>==

'''HPC cluster''' are used to run parallel programs for time-intensive computations and are of special interest to the scientific community. It commonly run simulations and other CPU-intensive programs that would take an inordinate amount of time to run on regular hardware.

<center>'''The basic cluster Design'''</center>

<center>[[Image:bits-1.png]]</center>

Grid computing is a broad term that typically refers to a service-oriented architecture (SOA) with collaboration among loosely coupled systems. Cluster-based HPC is a special case of grid computing in which the nodes are tightly coupled.

==<center>'''REQUIREMENT OF BITS-PILANI'''</center>==

BITS had a requirement of High Processing Cluster for there applications .For this one slave node server with one master node server and Eight Slave node server with one master node server were used. RHEL5 server where installed in two node cluster and CENTOS5 server installed in 9 node cluster.

All users authenticate via 389 ldap, IBM nodes handle Multi-master LDAP and other are LDAP Clients.

All users have home directories shared via NFS to other nodes.

Around 10 Clients they have windows machines and 35 Clients have Sunray Terminals and need to implement VNC Enterprise Server 5.03 with LDAP Authentication for Windows .All terminals handle by Sunray Server software.

High Availability over NFS is implemented on IBM Machines.

=<center>'''INSTALLATION OF 2-Node(IBM) HIGH PROCESSING CLUSTER'''</center>=

=='''Master node'''==

* NFS server running in High Availability.
* Ganglia daemon “gomnd” and “gmetad” running.
* apache running to provide web interface for ganglia
* mpd (MPI) daemon running.
* .mpd.conf file is created in wolf and lam home directory
* user wolf and group Beowulf responsible for operating cluster for all staff members, here “staff” is an OU of ldap.All “staff’ members use only wolf user for HPC.
* user lam and group prolam responsible for operating for all projects members,here “projects” is an OU of ldap. All “projects” members use only lam user for HPC

=='''Slave node'''==

* NFS server running in High Availability
* Ganglia daemon “gomnd” and “gmetad” running.
* mpd (MPI) is started by master node on each slave node.
* .mpd.conf file is created in wolf and lam home directory
* user wolf and group Beowulf responsible for operating cluster for all staff members, here “staff” is an OU of ldap.All “staff’ members use only wolf user for HPC.
* user lam and group prolam responsible for operating for all projects members,here “projects” is an OU of ldap. All “projects” members use only lam user for HPC

Note : wolf and lam are local system users in master and slave nodes.,

== Preparation of Master node(IBM-39) ==
* First the entries where made in /etc/hosts of each cluster as follows

172.20.4.39 ibm-39.bits.ac ibm-39
172.20.4.40 ibm-40.bits.ac ibm-40

* Two groups was created and a two users who will be responsible for operating cluster was added as follows.

groupadd beowulf
useradd -g beowulf wolf
groupadd prolam
useradd –g prolam lam

'''Note : This document is concern about wolf user.'''

* Following line were added in /home/wolf/.bash_profile

umask 007

* NFS server was created as follows in master node.

mkdir /linuxeda

This file have all the binaries and need to rsync with all when changes occurred.

chmod 770 /linuxeda

All home directories are in lvm mode name and location

/staff :This Home directory is for 2 node IBM HPC.

/projects:This Home directory is for 2 node IBM HPC.

/ugassignments:This Home directory is for 9 node Sunfire HPC.

/pgassignments:This Home directory is for 9 node Sunfire HPC.

'''Following entry is made in /etc/exports file '''

/staff <nowiki>* (rw,no_root_squash,sync) </nowiki>
/projects <nowiki>* (rw,no_root_squash,sync) </nowiki>
/ugassignments<nowiki>* (rw,no_root_squash,sync) </nowiki>
/pgassignments<nowiki>* (rw,no_root_squash,sync) </nowiki>

<nowiki># service nfs start ; chkconfig nfs on</nowiki>

* Communication among the nodes takes place through ssh, so ssh login for user “wolf” has to be without need of entering the password. This was acheived as follow.

Uncomment the following in /etc/sshd/sshd_config

<nowiki>#RSAAuthentication yes </nowiki>
<nowiki>#AuthorizedKeysFile .ssh/authorized_keys </nowiki>

* Reboot and login as wolf because operation of cluster will always be done by user “wolf”
* To generate your public and private SSH keys, do this:

ssh-keygen –t rsa

This will generate the two public/private key pain in .ssh directory. Copy the id_rsa.pub file into a file called "authorized_keys" right there in the .ssh directory.This key will be used later. Modify the security of file and directory

chmod 644 ~/.ssh/auth*
chmod 755 ~/.ssh

* Add these entries is /home/wolf/.bash_profile

export LAMRSH='ssh -x'

ssh-agent sh -c 'ssh-add && bash'

=<center>'''INSTALLATION OF MPI(MESSAGE PASSING INTERFACE)'''</center>=

The MPI mpich2 can be downloaded from [http://www.mpich.org/static/tarballs/1.2/mpich2-1.2.tar.gz http://www.mpich.org/static/tarballs/1.2/mpich2-1.2.tar.gz]

1. Unpack the tar ﬁle.

tar -zxvf mpich2-1.2.tar.gz

2. Choose an installation directory (the default is /usr/local/bin):

mkdir /home/wolf/mpich2-install
cd /home/wolf/mpich2-install/mpich2-install
./configure --prefix=/home/wolf/mpich2-install/ 2>&1 | tee c.txt
make 2>&1 | tee m.txt
make check
make install 2>&1 | tee mi.txt

Set the enviroment variable for user “wolf” in /home/wolf/.bash_profile

Add following lines.

MPICH2=/home/wolf/mpich2-install/bin/
PATH=$PATH:$HOME/bin:$MPICH2/bin

2.MPICH2, uses an external process manager for scalable startup of large MPI jobs. The default process manager is called MPD, which is a ring of daemons on the machines where you will run your MPI programs.

For security reasons, mpd looks in your home directory for a ﬁle named .mpd.conf containing the line in home directory. So create this file as follows

cd $HOME
touch .mpd.conf
chmod 600 .mpd.conf

add a line

<nowiki>secretword=<anysecretword> </nowiki>

we used “redhat123” as secretword in our case.

3.The ﬁrst sanity check consists of bringing up a ring of one mpd on the local machine, testing one mpd command, and bringing the “ring” down.

mpd &
mpdtrace
mpdallexit

The output of mpdtrace should be the hostname of the machine you

are running on. The mpdallexit causes the mpd daemon to exit

4.Now we will bring up a ring of mpd’s on a set of machines. Create a ﬁle consisting of a list of machine names, one per line. Name this ﬁle .mpd.hosts in home directory of user wolf. These hostnames will be used as targets for ssh so include full domain names if necessary. Check that you can reach these machines with ssh without entering a password. You can test by doing.

Ssh node1 –l wolf

# Start the daemons on (some of) the hosts in the ﬁle mpd.hosts

<nowiki>mpdboot -n <number to start> -f mpd.hosts </nowiki>

The number to start can be less than 1 + number of hosts in the ﬁle,but cannot be greater than 1 + the number of hosts in the ﬁle. One mpd is always started on the machine where mpdboot is run, and is counted in the number to start, whether or not it occurs in the ﬁle. By default, mpdboot will only start one mpd per machine even if the machine name appears in the hosts ﬁle multiple times.

mpdboot -n 5 -f mpd.hosts

This will start the cluster.

mpdtrace

This command will show you the nodes in the cluster like below

ibm-39.bits.ac

ibm-40.bits.ac

== PREPERATION OF SLAVE NODE(IBM-40) ==
a. beowulf and wolf user were created as in master node

b. Edit file /home/wolf/.bash_pofile

export LAMRSH='ssh -x'
ssh-agent
MPICH2=/home/wolf/mpich2-install/mpich2
PATH=$HOME/bin:$MPICH2/bin

Make /linuxeda directory

mkdir /linuxeda

This file have all the binaries and need to rsync with all when changes occurred.

chmod 770 /linuxeda

All home directories are in lvm mode name and location

/staff :This Home directory is for 2 node IBM HPC.

/projects:This Home directory is for 2 node IBM HPC.

/ugassignments:This Home directory is for 9 node Sunfire HPC.

/pgassignments:This Home directory is for 9 node Sunfire HPC.

Following entry is made in /etc/exports file

/staff <nowiki>* (rw,no_root_squash,sync) </nowiki>
/projects <nowiki>* (rw,no_root_squash,sync) </nowiki>
/ugassignments<nowiki>* (rw,no_root_squash,sync) </nowiki>
/pgassignments<nowiki>* (rw,no_root_squash,sync) </nowiki>
<nowiki># service nfs start ; chkconfig nfs on</nowiki>

c. Reboot all the nodes.

d. login as wolf users and install MPI as described above in MPI installation section above.

'''Note''': Firewall should be disabled in all nodes as MPI uses randoms ports each time it is started.

“mpdboot -n 2 -f mpd.hosts” ** command should be executed as wolf user from master node. This will start mpd daemon in slave nodes **

Now we will run an MPI job, using the mpiexec command as specified in the MPI-2 standard.

As part of the build process for MPICH2, a simple program to compute the value of ''pi ''by numerical integration is created in the mpich2-1.2/examples directory. If the current directory is the top level MPICH2 build directory, then you can run this program with

mpiexec -n 2 ./examples/cpi

The cpi example will tell you which hosts it is running on.

='''How to Run Cadence Application : '''=

# Firstly copy your application into /linuxeda
# Copy user database into the wolf home directory

Note : Each users have their own data

# Then Rsync /home /wolf/cadence6 to other nodes of same /home/wolf/cadence6
# Ensure keyless ssh to execute commands to other nodes.
# Command to execute application by mpi

mpiexec –np 4 /home/wulf/cadence6/spectre/linuxeda/cadence/(whatever)

Then it executes on both nodes and divide equally

Check with command

Mpdlistjobs on both nodes by wolf user

= INSTALLATION OF GANGLIA (CLUSTER MONITERING TOOL) ON EACH NODE. =
Ganglia can be downloaded from [http://ganglia.sourceforge.net/downloads.php http://ganglia.sourceforge.net/downloads.php]

Install ganglia as follows

# rpm –Uvh rrdtool-x.x.x.rpm ( this is dependency of ganglia)
# rpm –Uvh rrdtool-devel-.x.x.x.rpm
# rpm –Uvh ganglia-gmond-x.x.x.rpm
# rpm –Uvh ganglia-gmetad-x.x.x.rpm
# rpm –Uvh ganglia-web-x.x.x.rpm ( web interface for ganglia to be installed only in master node)
# create a file /etc/httpd/conf.d/ganglia.conf only in master node.

Alias /ganglia /usr/share/ganglia

open the file /etc/gmetad.conf and edit the file with following entry only in master node

data_source “unspecified” ibm-39 ibm-40

start the ganglia service in each node.

/etc/init.d/gmond start

/etc/init.d/gmetad start

gateway of all nodes should be master_node.

ganglia can be accessed in any browser with the url [http://172.20.4.39/ganglia http://172.20.4.39/ganglia]

'''Note : lam have same configuration as wolf'''

= <center>'''INSTALLATION OF 9-Node(SUNFIRE) HIGH PROCESSING CLUSTER'''</center>=

=='''Master node'''==

* NFS Client
* Ganglia daemon “gomnd” and “gmetad” running.
* apache running to provide web interface for ganglia
* mpd (MPI) daemon running.
* .mpd.conf file is created in wolf and lam home directory
* user wolf2 and group beowulf2 responsible for operating cluster for all pgassignments members, here “pgassignments” is an OU of ldap.All “pgassignments’ members use only wolf2 user for HPC.
* user lam1 and group prolam1 responsible for operating for all projects members,here “ugassignments” is an OU of ldap. All “ugassignments” members use only lam user for HPC

=='''Slave node'''==

* NFS client
* Ganglia daemon “gomnd” and “gmetad” running.
* mpd (MPI) is started by master node on each slave node.
* .mpd.conf file is created in wolf and lam home directory
* user wolf2 and group beowulf2 responsible for operating cluster for all pgassignments members, here “pgassignments” is an OU of ldap.All “pgassignments’ members use only wolf2 user for HPC.
* user lam1 and group prolam1 responsible for operating for all projects members,here “ugassignments” is an OU of ldap. All “ugassignments” members use only lam user for HPC

Note : wolf2 and lam1 are local system users in master and slave nodes.,

== Preparation of Master node(IBM-39) ==
* First the entries where made in /etc/hosts of each cluster as follows

172.20.4.25sunfire-25

172.20.4.26sunfire-26

172.20.4.27sunfire-27

172.20.4.28sunfire-28

172.20.4.29sunfire-29

172.20.4.30sunfire-30

172.20.4.31sunfire-31

172.20.4.32sunfire-32

172.20.4.33sunfire-33

* Two groups was created and a two users who will be responsible for operating cluster was added as follows.

groupadd beowulf2
useradd -g beowulf2 wolf2
groupadd prolam1
useradd –g prolam1 lam1

'''Note : This document is concern about wolf2 user.'''

* Following line were added in /home/wolf2/.bash_profile

umask 007

* '''Mount all home directories for these HPC2 Cluster i.e.'''

Mkdir /ugassignments /pgassignments

mount –t nfs 172.20.4.43: /ugassignments /ugassignments
mount –t nfs 172.20.4.43: /pgassignments /pgassignments

Then make permanent entry on fstab

* Communication among the nodes takes place through ssh, so ssh login for user “wolf” has to be without need of entering the password. This was acheived as follow.

Uncomment the following in /etc/sshd/sshd_config

<nowiki>#RSAAuthentication yes </nowiki>
<nowiki>#AuthorizedKeysFile .ssh/authorized_keys </nowiki>

* Reboot and login as wolf because operation of cluster will always be done by user “wolf”
* To generate your public and private SSH keys, do this:

ssh-keygen –t rsa

This will generate the two public/private key pain in .ssh directory. Copy the id_rsa.pub file into a file called "authorized_keys" right there in the .ssh directory.This key will be used later. Modify the security of file and directory

chmod 644 ~/.ssh/auth*
chmod 755 ~/.ssh

* Add these entries is /home/wolf/.bash_profile

export LAMRSH='ssh -x'
ssh-agent sh -c 'ssh-add && bash'

* Install MPI as above HPC1 section
* Install slave nodes as above section but home directories mount as a nfs.
* Install Ganglia as above HPC1 section

Category:Installation/MDI Qmail with disclaimer

2013-01-14T12:24:37Z

Navdeep:

[[category:Installation]]

'''
== Qmail Installation On rhel 6.3 ==

'''

'''Ensure rpmforge and epel repos are enabled.'''

Switch off SELinux.

Flush Iptables rules

'''

== Create directory for downloading required packages: ==
'''

mkdir /downloads

cd /downloads
'''

'''Download all required packages for qmail-ldap installation:''''''

wget http://www.qmailrocks.org/downloads/qmailrocks.tar.gz

wget http://cr.yp.to/software/qmail-1.03.tar.gz

wget http://cr.yp.to/ucspi-tcp/ucspi-tcp-0.88.tar.gz

wget http://www.qmailrocks.org/downloads/patches/ucspi-tcp-0.88.errno.patch

wget http://cr.yp.to/daemontools/daemontools-0.76.tar.gz

wget http://www.qmail.org/moni.csi.hu/pub/glibc-2.3.1/daemontools-0.76.errno.patch

wget http://www.nrg4u.com/qmail/qmail-ldap-1.03-20060201.patch.gz

wget http://lifewithqmail.org/inst_check

wget http://sourceforge.net/projects/courier/files/maildrop/2.5.4/maildrop-2.5.4.tar.bz2/download --no-check-certificate

wget http://prdownloads.sourceforge.net/qmail-scanner/qmail-scanner-2.08.tgz?download

wget http://www.qmailrocks.org/downloads/scripts/finalize/qmailctl

wget http://sourceforge.net/projects/phpldapadmin/files/latest/download

wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm

Extract packages:

tar -xvzf qmailrocks.tar.gz

tar -xvzf phpldapadmin-1.2.2.tgz

tar -xvzf squirrelmail-webmail-1.4.22.tar.gz

tar -xvjf maildrop-2.5.4.tar.bz2

tar -xvzf qmail-scanner-2.08.tgz

tar -xvzf qmailrocks/autorespond-2.0.5.tar.gz

==
'''Install all required packages before qmail-ldap installation:''' ==

yum install vim-enhanced httpd php* php-ldap perl gcc* gcc-c++ gcc44* openssl openssl-devel kernel-headers openssl-devel
kernel-headers patch pcre* db4* openldap* glibc* zlib* glib* gdbm* php

== '''Create initial qmail directories:''' ==

mkdir -p /var/qmail
mkdir /usr/src/qmail

== '''Creating all needed users and groups:''' ==

groupadd nofiles

useradd -g nofiles -d /var/qmail/alias -s /sbin/nologin -p'*' alias

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaild

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaill

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmailp

groupadd qmail

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailq

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailr

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmails

groupadd vmail

useradd -g vmail -s /bin/true vmail

Unpack qmail and apply the qmail-ldap patch:

cd /usr/src/qmail

tar -xvzf /downloads/qmail-1.03.tar.gz

gunzip /downloads/qmail-ldap-1.03-20060201.patch.gz

cd qmail-1.03

patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch

Make changes on "Makefile" to qmail work properly with ldap:

LDAPFLAGS=-DQLDAP_CLUSTER -DEXTERNAL_TODO -DDASH_EXT -DDATA_COMPRESS -DQMQP_COMPRESS -DSMTPEXECCHECK -DALTQUEUE -DBIGBROTHER

# ZLIB needed for -DDATA_COMPRESS and -DQMQP_COMPRESS

ZLIB=-lz

# to enable the auto-maildir-make feature

MDIRMAKE=-DAUTOMAILDIRMAKE

# to enable the auto-homedir-make feature

HDIRMAKE=-DAUTOHOMEDIRMAKE

# on most systems we need this to make auth_pop and auth_imap

SHADOWLIBS=-lcrypt

# to enable the possibility to log and debug imap and pop

DEBUG=-DDEBUG

After that, setup qmail

Changed the qmail-ldap.h in Source of qmail

from

#define LDAP_HOMEDIR "homeDirectory"

to

#define LDAP_HOMEDIR "nohomeDirectory"

Referance QLDAPNEWS ( in the source files )

Recompiled , Started and check found OK

make man

make setup check

sync control files and supervise scripts from live server

cd /usr/src/qmail

tar -xvzf /downloads/ucspi-tcp-0.88.tar.gz

cd ucspi-tcp-0.88

patch < /downloads/ucspi-tcp-0.88.errno.patch

make && make setup check

mkdir -p /package

chmod 1755 /package

cd /package

tar -xvzf /downloads/daemontools-0.76.tar.gz

cd /package/admin/daemontools-0.76/src

patch < /downloads/daemontools-0.76.errno.patch

cd /package/admin/daemontools-0.76

package/install

== '''SVSCAN Issue ,as init q will not work on RHEL 6''' ==

( http://www.kluner.net/2011/04/04/daemontools-on-redhat-enterprise-6-0/)

create /etc/init/svscan.conf

start on runlevel [345]

respawn

exec /command/svscanboot

* initctl reload-configuration

* initctl start svscan

* initctl start svscan

If Svscan is running then kill by

kill -HUP <Pid of Svscan>

kill -HUP <pid of service>

mkdir /var/qmail/supervise

cd /var/qmail/supervise

mkdir -p qmail-smtpd/log qmail-send/log qmail-pop3d/log

chmod +t qmail-smtpd qmail-send qmail-pop3d

vim qmail-smtpd/run

#!/bin/sh

#QMAILQUEUE="/var/qmail/bin/qmail-tail" ; export QMAILQUEUE

QUID=`id -u qmaild`

QGID=`id -g qmaild`

MAXD=`head -1 /var/qmail/control/concurrencyincoming`

HOST=`head -1 /var/qmail/control/me`

SOFT=`head -1 /var/qmail/control/qmail-smtpd-softlimit`

CDBF="/etc/tcp.smtp.cdb"

if [ -z "$QUID" -o -z "$QGID" -o -z "$MAXD" -o -z "$HOST" ]; then

echo QUID, QGID, MAXD, or HOST is unset in

echo /var/qmail/supervise/qmail-smtpd/run

exit 1

fi

exec /usr/local/bin/softlimit -m $SOFT \
/usr/local/bin/tcpserver -v \
-H \
-R \
-l $HOST \
-x $CDBF \
-c $MAXD \
-u $QUID \
-g $QGID \
0 \
smtp \
/var/qmail/bin/qmail-smtpd \
/var/qmail/bin/auth_smtp /usr/bin/true 2>&1

vim qmail-smtpd/log/run

#!/bin/sh

PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin

export PATH

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail/qmail-smtpd 2>&1

vim /var/qmail/rc

#!/bin/sh

QLOG="`cat /var/qmail/control/qmail-start-loglevel`"

DEFD="`cat /var/qmail/control/defaultdelivery`"

exec env - PATH="/var/qmail/bin:$PATH" LOGLEVEL="$QLOG" qmail-start "$DEFD"

Creating qmail-send run supervise script:

vim qmail-send/run

#!/bin/sh

exec /var/qmail/rc

vim qmail-send/log/run

#!/bin/sh

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail

==
'''Creating qmail-pop3d run supervise script:''' ==

vim qmail-pop3d/run

#!/bin/sh

IP=`head -1 /var/qmail/control/me`

LL=`head -1 /var/qmail/control/qmail-pop3d-loglevel`

SL=`head -1 /var/qmail/control/qmail-pop3d-softlimit`

exec \

env LOGLEVEL=$LL \

softlimit -m $SL \

/usr/local/bin/tcpserver -v -R -H -l 0 0 pop3 \

/var/qmail/bin/qmail-popup $IP \

/var/qmail/bin/tcp-env \

/var/qmail/bin/auth_pop \

/var/qmail/bin/qmail-pop3d Maildir 2>&1

'''Creating qmail-pop3d log run supervise script:
'''

vim qmail-pop3d/log/run

#!/bin/sh

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000

n20 /var/log/qmail/qmail-pop3d 2>&1

Creating auto directory maker script:

vim /var/qmail/bin/dirmaker

#!/bin/sh

echo '----------------------------------------------' >> /tmp/dirmaker

date >> /tmp/dirmaker

echo $1 >> /tmp/dirmaker

id >> /tmp/dirmaker

mkdir --parents -m 700 -p $1/Maildir

mkdir --parents -m 700 -p $1/Maildir/tmp

mkdir --parents -m 700 -p $1/Maildir/cur

mkdir --parents -m 700 -p $1/Maildir/new

chown -R vmail:vmail $1

Set permissions of all qmail supervise run scripts:

chmod 755 qmail-pop3d/run qmail-smtpd/run qmail-send/run

chmod 755 qmail-pop3d/log/run qmail-smtpd/log/run qmail-send/log/run

chmod 755 /var/qmail/rc /var/qmail/bin/dirmaker

Create tcp.smtp file to appy tcprules:

vim /etc/tcp.smtp

127.:allow,RELAYCLIENT="",SENDERCHECK="STRICT",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

192.168.30.32:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",MAXRCPTCOUNT="30",RBL="On"

192.168.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

#172.16.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On"

150.101.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

192.168.30.30:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

#192.168.100.101:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

#192.168.100.101:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

192.168.30.31:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

121.241.224.1:allow,RELAYCLIENT=""

121.241.224.2:allow,RELAYCLIENT=""

121.241.224.3:allow,RELAYCLIENT=""

121.241.224.4:allow,RELAYCLIENT=""

192.168.17.83:allow,RELAYCLIENT=""

112.110.53.:deny,RELAYCLIENT=""

#82.128.16.93:deny,RELAYCLENT""

:allow,BLOCKRELAYPROBE="",RCPTCHECK="strict",SENDERCHECK="",AUTHPREPEND="Authenticated user: ",SANITYCHECK="",SMTPAUTH="",DATABYTES="12582912",MAXRCPT="100",LOGLEVEL="3",RBL="On",TARPITCOUNT="15",TARPITDELAY="5"

==
Creating qmail logging directories and set permissions: ==
'''Bold text'''

mkdir /var/log/qmail

cd /var/log/qmail

mkdir qmail-send qmail-smtpd qmail-pop3d

chown -R qmaill:root /var/log/qmail

chmod -R 750 /var/log/qmail

== '''Creating qmail alias users, links and set permissions:'''
==

cd /var/qmail

cp -p /downloads/qmailctl /var/qmail/bin/.

chmod 755 /var/qmail/bin/qmailctl

ln -s /var/qmail/bin/qmailctl /usr/bin/

qmailctl cdb

mkdir -p /service

cd /service/

ln -s /var/qmail/supervise/qmail-* .

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-root

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-postmaster

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-mailer-daemon

ln -s /var/qmail/alias/.qmail-root /var/qmail/alias/.qmail-anonymous

chmod 644 /var/qmail/alias/.qmail*

Stop sendmail and remove all related files:

/etc/init.d/sendmail stop

chkconfig sendmail off

mv /usr/lib/sendmail /usr/lib/sendmail.org

mv /usr/sbin/sendmail /usr/sbin/sendmail.org

ln -s /var/qmail/bin/sendmail /usr/lib/sendmail

ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail

'''== Dovecot installation ==
'''

yum install tcp* -y

wget http://pkgs.fedoraproject.org/lookaside/pkgs/dovecot/dovecot-2.0.14.tar.gz/92a10a6ca341921db9e35c6753e8de0b/dovecot-2.0.14.tar.gz

cd /var/qmail/control

openssl req -newkey rsa:1024 -x509 -nodes -days 3650 -out servercert.pem -keyout servercert.pem

#Answer the prompt. The only important field is COMMON NAME. There you
have to enter the full hostname of the mail server: eg:
mailserver.mdi.ac.in

ln -s servercert.pem clientcert.pem

chmod 640 servercert.pem clientcert.pem

chown qmaild servercert.pem

mkdir -p /etc/ssl/private/

mkdir -p /etc/ssl/certs/

ln -s /var/qmail/control/servercert.pem /etc/ssl/certs/dovecot.pem

ln -s /var/qmail/control/servercert.pem /etc/ssl/private/dovecot.pem

cd /downloads/

tar xvzf dovecot-2.0.14.tar.gz

cd dovecot-2.0.14

./configure --without-shadow --without-pam --without-bsdauth --without-gssapi --without-sia --without-vpopmail --without-sql --without-pgsql --without-mysql --without-sqlite --with-ssl=openssl --with-libwrap --with-ldap --without-shadow --prefix=/usr

make && make install

useradd -d /nonexistent -s /bin/false -c 'Dovecot user' dovecot

mkdir -p /etc/ssl/private/

mkdir -p /etc/ssl/certs/

cp -pv /usr/share/doc/dovecot/example-config/dovecot.conf /usr/etc/dovecot/dovecot.conf

cp -pv /usr/share/doc/dovecot/example-config/dovecot-ldap.conf.ext /usr/etc/dovecot/dovecot-ldap.conf

ln -s /usr/etc/dovecot/dovecot-ldap.conf /usr/etc/dovecot/dovecot-ldap-userdb.conf

Make Acl's to /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}bdb.ldif

olcAccess: to *

by * write

by * read

olcAccess: to attrs=userPassword,sambaLMPassword,sambaNTPassword

by * write

by * auth

dovecot-ldap.conf file (You can copy+paste it):

hosts = localhost

dn = cn=Manager,dc=mdi,dc=ac,dc=in

dnpass = secret

auth_bind = no

ldap_version = 3

base = dc=mdi,dc=ac,dc=in

scope = subtree

user_filter = (&(objectClass=qmailUser)(uid=%u))

#user_attrs = mailMessageStore=home

user_attrs = mailMessageStore=home=/home/vmail/%$

##user_attrs = mail=home:/home/vmail/%d/%n

##user_attrs = mail=maildir:/home/vmail/%d/%n/Maildir

pass_filter = (&(objectClass=qmailUser)(uid=%u)(!(accountStatus=disabled))(!(accountStatus=noaccess)))

pass_attrs = uid=user,userPassword=password

default_pass_scheme = SSHA

dovecot.conf file (You can copy+paste it):

auth_verbose = yes

listen = *

disable_plaintext_auth = no

debug_log_path = /var/log/dovecot-debug.log

default_login_user = dovecot

first_valid_uid = 89

info_log_path = /var/log/dovecot-info.log

last_valid_uid = 2000

log_path = /var/log/dovecot

login_greeting = MDI mail server!

mail_gid = vmail

mail_location = maildir:~/Maildir

mail_uid = vmail

namespace {

inbox = yes

location = maildir:~/Maildir

prefix = INBOX.

separator = .

}

passdb {

args = /usr/etc/dovecot/dovecot-ldap.conf

driver = ldap

}

protocols = imap

ssl_cert = </etc/ssl/certs/dovecot.pem

ssl_key = </etc/ssl/private/dovecot.pem

userdb {

args = /usr/etc/dovecot/dovecot-ldap-userdb.conf

driver = ldap

}

verbose_proctitle = yes

verbose_ssl = yes

protocol lda {

postmaster_address = admin@mdi.ac.in

}

Dovecot {For start}

dovecot stop' stops it.

dovecot -n' checks config file.

Install autoresponder and maildrop:

cd /downloads/autorespond-2.0.5/

make && make install

cd /downloads/maildrop-2.5.4

./configure --prefix=/usr/local --exec-prefix=/usr/local --enable-maildrop-uid=root

make && make install-strip && make install-man

Reload tcp.smtp rules

Unpack Phpldapadmin and configure to access from Web:

mv /downloads/phpldapadmin-1.2.2 /var/www/html/phpldapadmin

cd /var/www/html/phpldapadmin

mkdir templates/creation.old templates/modification.old

mv templates/creation/* templates/creation.old/

mv templates/modification/* templates/modification.old/

Increase PHP memory limit:

vim /etc/php.ini

memory_limit = 128M

SQUIRREL MAIL INSTALLATION

mv /downloads/squirrelmail-webmail-1.4.22 /var/www/html/webmail

cd /var/www/html/webmail

mkdir attachements

chown -R apache:apache attachements

chown -R apache:apache data

cd config

./conf.pl

Type s
Type q

Vim config.php

$data_dir = '/var/www/html/webmail/data/';

$attachment_dir = '/var/www/html/webmail/attachments/';

Chmod 775 /var/www/html/webmail

Service https restart

Chkconfig httpd on

'''
==

Install all required packages for Qmail-Scanner: ==
'''

yum install perl-suidperl perl-Digest-SHA1 perl-Digest-HMAC perl-Net-DNS perl-Time-HiRes* perl-HTML-Tagset perl-HTML-Parser perl-Pod-Usage* perl-Parse-Syslog perl-Statistics-Distributions spamassassin clamav clamd

Add user "qscand" for scanning:

useradd -c "Qmail-Scanner Account" -s /bin/false -m qscand

Change user clamav to qscand:

vim /etc/logrotate.d/clamav [Change clamav to qscand]

/var/log/clamav/clamd.log {

missingok

notifempty

create 644 qscand qscand

postrotate

killall -HUP clamd 2>/dev/null || :

endscript

}

Vim /etc/logrotate.d/freshclam [Change clamav to qscand]

/var/log/clamav/freshclam.log {

missingok

notifempty

create 644 qscand qscand

}

vim /etc/clamd.conf

User qscand

vim /etc/freshclam.conf

DatabaseOwner qscand

chown qscand.qscand /var/log/clamav/ -R

chown -R qscand.qscand /var/run/clamav/

/etc/init.d/clamd restart

/etc/init.d/spamassassin restart

'''
== Install Qmail-Scanner: =='''

cd /downloads/qmail-scanner-2.08

./configure --admin admin --domain mdi.ac.in

mkdir -p /var/spool/qscan

mkdir -p /var/spool/qscan/quarantine/viruses/tmp /var/spool/qscan/quarantine/viruses/cur /var/spool/qscan/quarantine/viruses/new

mkdir -p /var/spool/qscan/quarantine/spam/tmp /var/spool/qscan/quarantine/spam/cur /var/spool/qscan/quarantine/spam/new

mkdir -p /var/spool/qscan/quarantine/policy/tmp /var/spool/qscan/quarantine/policy/cur /var/spool/qscan/quarantine/policy/new

mkdir -p /var/spool/qscan/working/tmp /var/spool/qscan/working/cur /var/spool/qscan/working/new

mkdir -p /var/spool/qscan/archive/tmp /var/spool/qscan/archive/cur /var/spool/qscan/archive/new

cp /downloads/qmail-scanner-2.08/quarantine-events.txt /var/spool/qscan/

chown -R qscand:qscand /var/spool/qscan/

cp -pv /downloads/qmail-scanner-2.08/qmail-scanner-queue.pl /var/qmail/bin/

chown qscand.qscand /var/qmail/bin/qmail-scanner-queue.pl

chmod 4755 /var/qmail/bin/qmail-scanner-queue.pl

/var/qmail/bin/qmail-scanner-queue.pl -z

/var/qmail/bin/qmail-scanner-queue.pl -g

cp -v /downloads/qmail-scanner-2.08/contrib/logrotate.qmail-scanner /etc/logrotate.d/qmail-scanner

/etc/init.d/syslog restart

'''== Integrate Qmail-scanner with qmail queue: =='''

vim /var/qmail/supervise/qmail-smtpd/run

QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" ; export QMAILQUEUE

==
'''Check Qmail-scanner Installation:
''' ==

su - tetra

/var/qmail/bin/qmail-scanner-queue.pl -g

/root/downloads/qmail-scanner-2.08/contrib/test_installation.sh -doit

###[ This step generate 2 spam mails and send to the admin e-mail account]###

'''==
Second Instance of Qmail for Disclaimer.
=='''

mkdir -p /var/qmail2

mkdir /usr/src/qmail2

cd /usr/src/qmail2

tar xvzf /downloads/qmailrocks/qmail-1.03.tar.gz

cd qmail-1.03

patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch

echo 255 > /usr/src/second-qmail/qmail-1.03/conf-spwan

echo 211 > /usr/src/second-qmail/qmail-1.03/conf-split

vi conf-qmail

( replace qmail with qmail2 )

-------------------------------------------------------------------------------------------------

/var/qmail2
-------------------------------------------------------------------------------------------------

cd /downloads/

yum install bglibs* either wget http://www6.atomicorp.com/channels/atomic/centos/6/i386/RPMS/bglibs-1.106-1.el6.art.i686.rpm

rpm -Uvh bglibs-1.106-1.el6.art.i686.rpm

wget http://www.icewalkers.com/jump.php url=e3b53d133ca7ab23eb55edf87f11c1f4&id=1910

cd altermime-0.3.6

make

make install

cd /downloads

wget http://untroubled.org/qmail-qfilter/qmail-qfilter-2.1.tar.gz

tar xvzf qmail-qfilter-2.1.tar.gz

cd qmail-qfilter-2.1

vi qmail-qfilter.c

( change qmail into qmail2 )

------------------------------------------------------------------------------------------------------

#ifndef QMAIL_QUEUE

#define QMAIL_QUEUE "/var/qmail2/bin/qmail-queue"

#endif

------------------------------------------------------------------------------------------------------

make

make install

chmod 777 /usr/local/bin/qmail-qfilter

chown root:qmail /usr/local/bin/qmail-qfilter

================================

vi /var/qmail2/bin/qmail-tail

-------------------------------------------------------------------------------------------------------

#!/bin/sh

exec /usr/local/bin/qmail-qfilter /var/qmail2/bin/qmail-disclaimer

-------------------------------------------------------------------------------------------------------

=========================================

chown root:qmail /var/qmail2/bin/qmail-tail

chmod 777 /var/qmail2/bin/qmail-tail

mkdir /var/qmail2/control/disclaimer/

cd /var/qmail2/control/disclaimer

=================================

vim mdi.ac.in.html

================================

<html>

<body>

DISCLAIMER : Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the

addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not

disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this

message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any

attachments for the presence of viruses. The Institute accepts no liability for any damage \ caused by any virus transmitted by this email.

</body>

</html>

========================================================

chown root:qmail /var/qmail2/control/disclaimer/*

chmod 777 /var/qmail2/control/disclaimer/*

mkdir /var/tmp/qmail-qfilter

chown root:qmail /var/tmp/qmail-qfilter

chmod 777 /var/tmp/qmail-qfilte

vi /var/qmail2/bin/qmail-disclaimer

====================================

#!/bin/sh

QMAILHOST=mdi.ac.in

INSPECT_DIR=/var/tmp/qmail-qfilter

if [ ! -f /var/qmail2/control/disclaimer/$QMAILHOST.txt ]

then

cat

exit 0

fi

EX_TEMPFAIL=31

EX_UNAVAILABLE=31

trap "rm -f /var/tmp/qmail-qfilter/in.$$" 0 1 2 3 15

cd $INSPECT_DIR || { echo Error: $INSPECT_DIR does not exist; exit $EX_TEMPFAIL; }

cat >$INSPECT_DIR/in.$$ || { echo Error: Cannot write to disk; exit $EX_TEMPFAIL; }

/usr/local/bin/altermime --input=$INSPECT_DIR/in.$$ \

--xheader="X-Disclaimer: $QMAILHOST" \

--disclaimer=/var/qmail2/control/disclaimer/$QMAILHOST.txt \

--disclaimer-html=/var/qmail2/control/disclaimer/$QMAILHOST.html || { echo Error: message rejected; exit $EX_UNAVAILABLE; }

cat $INSPECT_DIR/in.$$

rm in.$$

exit $?

=====================================================

chown root:qmail /var/qmail2/bin/qmail-disclaimer

chmod 777 /var/qmail2/bin/qmail-disclaimer

================================================

vi /service/qmail2-smtpd/run

( add following line at the top)

----------------------------------------------------------------------------------------------------

#!/bin/sh

QMAILQUEUE="/var/qmail2/bin/qmail-tail" export QMAILQUEUE

===========================================================

vi /etc/services

# Local services

second-qmail 910/tcp

================================

vi /var/qmail/control/smtproutes

----------------------------------------------------------------------------------------------------

:127.0.0.1:910

----------------------------------------------------------------------------------------------------

==================================

Category:Installation/MDI Qmail with disclaimer

2013-01-14T12:09:47Z

Navdeep: /* Qmail for RHEL6 (This is different from earlier versions ) */

[[category:Installation]]

'''
== Qmail Installation On rhel 6.3 ==

'''

'''Ensure rpmforge and epel repos are enabled.'''

Switch off SELinux.

Flush Iptables rules

'''Create directory for downloading required packages:'''

mkdir /downloads

cd /downloads
'''

'''Download all required packages for qmail-ldap installation:''''''

wget http://www.qmailrocks.org/downloads/qmailrocks.tar.gz

wget http://cr.yp.to/software/qmail-1.03.tar.gz

wget http://cr.yp.to/ucspi-tcp/ucspi-tcp-0.88.tar.gz

wget http://www.qmailrocks.org/downloads/patches/ucspi-tcp-0.88.errno.patch

wget http://cr.yp.to/daemontools/daemontools-0.76.tar.gz

wget http://www.qmail.org/moni.csi.hu/pub/glibc-2.3.1/daemontools-0.76.errno.patch

wget http://www.nrg4u.com/qmail/qmail-ldap-1.03-20060201.patch.gz

wget http://lifewithqmail.org/inst_check

wget http://sourceforge.net/projects/courier/files/maildrop/2.5.4/maildrop-2.5.4.tar.bz2/download --no-check-certificate

wget http://prdownloads.sourceforge.net/qmail-scanner/qmail-scanner-2.08.tgz?download

wget http://www.qmailrocks.org/downloads/scripts/finalize/qmailctl

wget http://sourceforge.net/projects/phpldapadmin/files/latest/download

wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.i386.rpm

Extract packages:

tar -xvzf qmailrocks.tar.gz

tar -xvzf phpldapadmin-1.2.2.tgz

tar -xvzf squirrelmail-webmail-1.4.22.tar.gz

tar -xvjf maildrop-2.5.4.tar.bz2

tar -xvzf qmail-scanner-2.08.tgz

tar -xvzf qmailrocks/autorespond-2.0.5.tar.gz

==
'''Install all required packages before qmail-ldap installation:''' ==

yum install vim-enhanced httpd php* php-ldap perl gcc* gcc-c++ gcc44* openssl openssl-devel kernel-headers openssl-devel
kernel-headers patch pcre* db4* openldap* glibc* zlib* glib* gdbm* php

'''Create initial qmail directories:'''
== Headline text ==

mkdir -p /var/qmail
mkdir /usr/src/qmail

Creating all needed users and groups:

groupadd nofiles

useradd -g nofiles -d /var/qmail/alias -s /sbin/nologin -p'*' alias

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaild

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmaill

useradd -g nofiles -d /var/qmail -s /sbin/nologin -p'*' qmailp

groupadd qmail

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailq

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmailr

useradd -g qmail -d /var/qmail -s /sbin/nologin -p'*' qmails

groupadd vmail

useradd -g vmail -s /bin/true vmail

Unpack qmail and apply the qmail-ldap patch:

cd /usr/src/qmail

tar -xvzf /downloads/qmail-1.03.tar.gz

gunzip /downloads/qmail-ldap-1.03-20060201.patch.gz

cd qmail-1.03

patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch

Make changes on "Makefile" to qmail work properly with ldap:

LDAPFLAGS=-DQLDAP_CLUSTER -DEXTERNAL_TODO -DDASH_EXT -DDATA_COMPRESS -DQMQP_COMPRESS -DSMTPEXECCHECK -DALTQUEUE -DBIGBROTHER

# ZLIB needed for -DDATA_COMPRESS and -DQMQP_COMPRESS

ZLIB=-lz

# to enable the auto-maildir-make feature

MDIRMAKE=-DAUTOMAILDIRMAKE

# to enable the auto-homedir-make feature

HDIRMAKE=-DAUTOHOMEDIRMAKE

# on most systems we need this to make auth_pop and auth_imap

SHADOWLIBS=-lcrypt

# to enable the possibility to log and debug imap and pop

DEBUG=-DDEBUG

After that, setup qmail

Changed the qmail-ldap.h in Source of qmail

from

#define LDAP_HOMEDIR "homeDirectory"

to

#define LDAP_HOMEDIR "nohomeDirectory"

Referance QLDAPNEWS ( in the source files )

Recompiled , Started and check found OK

make man

make setup check

sync control files and supervise scripts from live server

cd /usr/src/qmail

tar -xvzf /downloads/ucspi-tcp-0.88.tar.gz

cd ucspi-tcp-0.88

patch < /downloads/ucspi-tcp-0.88.errno.patch

make && make setup check

mkdir -p /package

chmod 1755 /package

cd /package

tar -xvzf /downloads/daemontools-0.76.tar.gz

cd /package/admin/daemontools-0.76/src

patch < /downloads/daemontools-0.76.errno.patch

cd /package/admin/daemontools-0.76

package/install

==

SVSCAN Issue ,as init q will not work on RHEL 6 ==
'''Bold text'''

( http://www.kluner.net/2011/04/04/daemontools-on-redhat-enterprise-6-0/)

create /etc/init/svscan.conf

start on runlevel [345]

respawn

exec /command/svscanboot

* initctl reload-configuration

* initctl start svscan

* initctl start svscan

If Svscan is running then kill by by

kill -HUP <Pid of Svscan>

kill -HUP <pid of service>

mkdir /var/qmail/supervise

cd /var/qmail/supervise

mkdir -p qmail-smtpd/log qmail-send/log qmail-pop3d/log

chmod +t qmail-smtpd qmail-send qmail-pop3d

vim qmail-smtpd/run

#!/bin/sh

#QMAILQUEUE="/var/qmail/bin/qmail-tail" ; export QMAILQUEUE

QUID=`id -u qmaild`

QGID=`id -g qmaild`

MAXD=`head -1 /var/qmail/control/concurrencyincoming`

HOST=`head -1 /var/qmail/control/me`

SOFT=`head -1 /var/qmail/control/qmail-smtpd-softlimit`

CDBF="/etc/tcp.smtp.cdb"

if [ -z "$QUID" -o -z "$QGID" -o -z "$MAXD" -o -z "$HOST" ]; then

echo QUID, QGID, MAXD, or HOST is unset in

echo /var/qmail/supervise/qmail-smtpd/run

exit 1

fi

exec /usr/local/bin/softlimit -m $SOFT \

/usr/local/bin/tcpserver -v \
-H \

-R \

-l $HOST \

-x $CDBF \

-c $MAXD \

-u $QUID \

-g $QGID \

0 \

smtp \

/var/qmail/bin/qmail-smtpd \

/var/qmail/bin/auth_smtp /usr/bin/true 2>&1

vim qmail-smtpd/log/run

#!/bin/sh

PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin

export PATH

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail/qmail-smtpd 2>&1

vim /var/qmail/rc

#!/bin/sh

QLOG="`cat /var/qmail/control/qmail-start-loglevel`"

DEFD="`cat /var/qmail/control/defaultdelivery`"

exec env - PATH="/var/qmail/bin:$PATH" LOGLEVEL="$QLOG" qmail-start "$DEFD"

Creating qmail-send run supervise script:

vim qmail-send/run

#!/bin/sh

exec /var/qmail/rc

vim qmail-send/log/run

#!/bin/sh

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000 n20 /var/log/qmail

== Creating qmail-pop3d run supervise script: ==
'''Bold text'''

vim qmail-pop3d/run

#!/bin/sh

IP=`head -1 /var/qmail/control/me`

LL=`head -1 /var/qmail/control/qmail-pop3d-loglevel`

SL=`head -1 /var/qmail/control/qmail-pop3d-softlimit`

exec \

env LOGLEVEL=$LL \

softlimit -m $SL \

/usr/local/bin/tcpserver -v -R -H -l 0 0 pop3 \

/var/qmail/bin/qmail-popup $IP \

/var/qmail/bin/tcp-env \

/var/qmail/bin/auth_pop \

/var/qmail/bin/qmail-pop3d Maildir 2>&1

'''Creating qmail-pop3d log run supervise script:
'''

vim qmail-pop3d/log/run

#!/bin/sh

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s10000000

n20 /var/log/qmail/qmail-pop3d 2>&1

Creating auto directory maker script:

vim /var/qmail/bin/dirmaker

#!/bin/sh

echo '----------------------------------------------' >> /tmp/dirmaker

date >> /tmp/dirmaker

echo $1 >> /tmp/dirmaker

id >> /tmp/dirmaker

mkdir --parents -m 700 -p $1/Maildir

mkdir --parents -m 700 -p $1/Maildir/tmp

mkdir --parents -m 700 -p $1/Maildir/cur

mkdir --parents -m 700 -p $1/Maildir/new

chown -R vmail:vmail $1

Set permissions of all qmail supervise run scripts:

chmod 755 qmail-pop3d/run qmail-smtpd/run qmail-send/run

chmod 755 qmail-pop3d/log/run qmail-smtpd/log/run qmail-send/log/run

chmod 755 /var/qmail/rc /var/qmail/bin/dirmaker

Create tcp.smtp file to appy tcprules:

vim /etc/tcp.smtp

127.:allow,RELAYCLIENT="",SENDERCHECK="STRICT",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

192.168.30.32:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",MAXRCPTCOUNT="30",RBL="On"

192.168.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

#172.16.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On"

150.101.:allow,SMTPAUTH="",AUTHREQUIRED="",SENDERCHECK="",LOGLEVEL="3",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",MAXRCPTCOUNT="30",RBL="On",LOGLEVEL="3"

192.168.30.30:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

#192.168.100.101:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

#192.168.100.101:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

192.168.30.31:allow,RCPTCHECK="",NOPBS="",SANITYCHECK="",BLCKRELAYPRBE="",LOGLEVEL="3",RBL="On"

121.241.224.1:allow,RELAYCLIENT=""

121.241.224.2:allow,RELAYCLIENT=""

121.241.224.3:allow,RELAYCLIENT=""

121.241.224.4:allow,RELAYCLIENT=""

192.168.17.83:allow,RELAYCLIENT=""

112.110.53.:deny,RELAYCLIENT=""

#82.128.16.93:deny,RELAYCLENT""

:allow,BLOCKRELAYPROBE="",RCPTCHECK="strict",SENDERCHECK="",AUTHPREPEND="Authenticated user: ",SANITYCHECK="",SMTPAUTH="",DATABYTES="12582912",MAXRCPT="100",LOGLEVEL="3",RBL="On",TARPITCOUNT="15",TARPITDELAY="5"

==
Creating qmail logging directories and set permissions: ==
'''Bold text'''

mkdir /var/log/qmail

cd /var/log/qmail

mkdir qmail-send qmail-smtpd qmail-pop3d

chown -R qmaill:root /var/log/qmail

chmod -R 750 /var/log/qmail

== '''Creating qmail alias users, links and set permissions:'''
==

cd /var/qmail

cp -p /downloads/qmailctl /var/qmail/bin/.

chmod 755 /var/qmail/bin/qmailctl

ln -s /var/qmail/bin/qmailctl /usr/bin/

qmailctl cdb

mkdir -p /service

cd /service/

ln -s /var/qmail/supervise/qmail-* .

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-root

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-postmaster

echo admin@mdi.ac.in > /var/qmail/alias/.qmail-mailer-daemon

ln -s /var/qmail/alias/.qmail-root /var/qmail/alias/.qmail-anonymous

chmod 644 /var/qmail/alias/.qmail*

Stop sendmail and remove all related files:

/etc/init.d/sendmail stop

chkconfig sendmail off

mv /usr/lib/sendmail /usr/lib/sendmail.org

mv /usr/sbin/sendmail /usr/sbin/sendmail.org

ln -s /var/qmail/bin/sendmail /usr/lib/sendmail

ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail

'''== Dovecot installation ==
'''

yum install tcp* -y

wget http://pkgs.fedoraproject.org/lookaside/pkgs/dovecot/dovecot-2.0.14.tar.gz/92a10a6ca341921db9e35c6753e8de0b/dovecot-2.0.14.tar.gz

cd /var/qmail/control

openssl req -newkey rsa:1024 -x509 -nodes -days 3650 -out servercert.pem -keyout servercert.pem

#Answer the prompt. The only important field is COMMON NAME. There you
have to enter the full hostname of the mail server: eg:
mailserver.mdi.ac.in

ln -s servercert.pem clientcert.pem

chmod 640 servercert.pem clientcert.pem

chown qmaild servercert.pem

mkdir -p /etc/ssl/private/

mkdir -p /etc/ssl/certs/

ln -s /var/qmail/control/servercert.pem /etc/ssl/certs/dovecot.pem

ln -s /var/qmail/control/servercert.pem /etc/ssl/private/dovecot.pem

cd /downloads/

tar xvzf dovecot-2.0.14.tar.gz

cd dovecot-2.0.14

./configure --without-shadow --without-pam --without-bsdauth --without-gssapi --without-sia --without-vpopmail --without-sql --without-pgsql --without-mysql --without-sqlite --with-ssl=openssl --with-libwrap --with-ldap --without-shadow --prefix=/usr

make && make install

useradd -d /nonexistent -s /bin/false -c 'Dovecot user' dovecot

mkdir -p /etc/ssl/private/

mkdir -p /etc/ssl/certs/

cp -pv /usr/share/doc/dovecot/example-config/dovecot.conf /usr/etc/dovecot/dovecot.conf

cp -pv /usr/share/doc/dovecot/example-config/dovecot-ldap.conf.ext /usr/etc/dovecot/dovecot-ldap.conf

ln -s /usr/etc/dovecot/dovecot-ldap.conf /usr/etc/dovecot/dovecot-ldap-userdb.conf

Make Acl's to /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}bdb.ldif

olcAccess: to *

by * write

by * read

olcAccess: to attrs=userPassword,sambaLMPassword,sambaNTPassword

by * write

by * auth

dovecot-ldap.conf file (You can copy+paste it):

hosts = localhost

dn = cn=Manager,dc=mdi,dc=ac,dc=in

dnpass = secret

auth_bind = no

ldap_version = 3

base = dc=mdi,dc=ac,dc=in

scope = subtree

user_filter = (&(objectClass=qmailUser)(uid=%u))

#user_attrs = mailMessageStore=home

user_attrs = mailMessageStore=home=/home/vmail/%$

##user_attrs = mail=home:/home/vmail/%d/%n

##user_attrs = mail=maildir:/home/vmail/%d/%n/Maildir

pass_filter = (&(objectClass=qmailUser)(uid=%u)(!(accountStatus=disabled))(!(accountStatus=noaccess)))

pass_attrs = uid=user,userPassword=password

default_pass_scheme = SSHA

dovecot.conf file (You can copy+paste it):

auth_verbose = yes

listen = *

disable_plaintext_auth = no

debug_log_path = /var/log/dovecot-debug.log

default_login_user = dovecot

first_valid_uid = 89

info_log_path = /var/log/dovecot-info.log

last_valid_uid = 2000

log_path = /var/log/dovecot

login_greeting = MDI mail server!

mail_gid = vmail

mail_location = maildir:~/Maildir

mail_uid = vmail

namespace {

inbox = yes

location = maildir:~/Maildir

prefix = INBOX.

separator = .

}

passdb {

args = /usr/etc/dovecot/dovecot-ldap.conf

driver = ldap

}

protocols = imap

ssl_cert = </etc/ssl/certs/dovecot.pem

ssl_key = </etc/ssl/private/dovecot.pem

userdb {

args = /usr/etc/dovecot/dovecot-ldap-userdb.conf

driver = ldap

}

verbose_proctitle = yes

verbose_ssl = yes

protocol lda {

postmaster_address = admin@mdi.ac.in

}

Dovecot {For start}

dovecot stop' stops it.

dovecot -n' checks config file.

Install autoresponder and maildrop:

cd /downloads/autorespond-2.0.5/

make && make install

cd /downloads/maildrop-2.5.4

./configure --prefix=/usr/local --exec-prefix=/usr/local --enable-maildrop-uid=root

make && make install-strip && make install-man

Reload tcp.smtp rules

Unpack Phpldapadmin and configure to access from Web:

mv /downloads/phpldapadmin-1.2.2 /var/www/html/phpldapadmin

cd /var/www/html/phpldapadmin

mkdir templates/creation.old templates/modification.old

mv templates/creation/* templates/creation.old/

mv templates/modification/* templates/modification.old/

Increase PHP memory limit:

vim /etc/php.ini

memory_limit = 128M

SQUIRREL MAIL INSTALLATION

mv /downloads/squirrelmail-webmail-1.4.22 /var/www/html/webmail

cd /var/www/html/webmail

mkdir attachements

chown -R apache:apache attachements

chown -R apache:apache data

cd config

./conf.pl

Type s
Type q

Vim config.php

$data_dir = '/var/www/html/webmail/data/';

$attachment_dir = '/var/www/html/webmail/attachments/';

Chmod 775 /var/www/html/webmail

Service https restart

Chkconfig httpd on

'''
==

Install all required packages for Qmail-Scanner: ==
'''

yum install perl-suidperl perl-Digest-SHA1 perl-Digest-HMAC perl-Net-DNS perl-Time-HiRes* perl-HTML-Tagset perl-HTML-Parser perl-Pod-Usage* perl-Parse-Syslog perl-Statistics-Distributions spamassassin clamav clamd

Add user "qscand" for scanning:

useradd -c "Qmail-Scanner Account" -s /bin/false -m qscand

Change user clamav to qscand:

vim /etc/logrotate.d/clamav [Change clamav to qscand]

/var/log/clamav/clamd.log {

missingok

notifempty

create 644 qscand qscand

postrotate

killall -HUP clamd 2>/dev/null || :

endscript

}

Vim /etc/logrotate.d/freshclam [Change clamav to qscand]

/var/log/clamav/freshclam.log {

missingok

notifempty

create 644 qscand qscand

}

vim /etc/clamd.conf

User qscand

vim /etc/freshclam.conf

DatabaseOwner qscand

chown qscand.qscand /var/log/clamav/ -R

chown -R qscand.qscand /var/run/clamav/

/etc/init.d/clamd restart

/etc/init.d/spamassassin restart

'''
== Install Qmail-Scanner: =='''

cd /downloads/qmail-scanner-2.08

./configure --admin admin --domain mdi.ac.in

mkdir -p /var/spool/qscan

mkdir -p /var/spool/qscan/quarantine/viruses/tmp /var/spool/qscan/quarantine/viruses/cur /var/spool/qscan/quarantine/viruses/new

mkdir -p /var/spool/qscan/quarantine/spam/tmp /var/spool/qscan/quarantine/spam/cur /var/spool/qscan/quarantine/spam/new

mkdir -p /var/spool/qscan/quarantine/policy/tmp /var/spool/qscan/quarantine/policy/cur /var/spool/qscan/quarantine/policy/new

mkdir -p /var/spool/qscan/working/tmp /var/spool/qscan/working/cur /var/spool/qscan/working/new

mkdir -p /var/spool/qscan/archive/tmp /var/spool/qscan/archive/cur /var/spool/qscan/archive/new

cp /downloads/qmail-scanner-2.08/quarantine-events.txt /var/spool/qscan/

chown -R qscand:qscand /var/spool/qscan/

cp -pv /downloads/qmail-scanner-2.08/qmail-scanner-queue.pl /var/qmail/bin/

chown qscand.qscand /var/qmail/bin/qmail-scanner-queue.pl

chmod 4755 /var/qmail/bin/qmail-scanner-queue.pl

/var/qmail/bin/qmail-scanner-queue.pl -z

/var/qmail/bin/qmail-scanner-queue.pl -g

cp -v /downloads/qmail-scanner-2.08/contrib/logrotate.qmail-scanner /etc/logrotate.d/qmail-scanner

/etc/init.d/syslog restart

'''== Integrate Qmail-scanner with qmail queue: =='''

vim /var/qmail/supervise/qmail-smtpd/run

QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" ; export QMAILQUEUE

==
'''Check Qmail-scanner Installation:
''' ==

su - tetra

/var/qmail/bin/qmail-scanner-queue.pl -g

/root/downloads/qmail-scanner-2.08/contrib/test_installation.sh -doit

###[ This step generate 2 spam mails and send to the admin e-mail account]###

'''==
Second Instance of Qmail for Disclaimer.
=='''

mkdir -p /var/qmail2

mkdir /usr/src/qmail2

cd /usr/src/qmail2

tar xvzf /downloads/qmailrocks/qmail-1.03.tar.gz

cd qmail-1.03

patch -p1 < /downloads/qmail-ldap-1.03-20060201.patch

echo 255 > /usr/src/second-qmail/qmail-1.03/conf-spwan

echo 211 > /usr/src/second-qmail/qmail-1.03/conf-split

vi conf-qmail

( replace qmail with qmail2 )

-------------------------------------------------------------------------------------------------

/var/qmail2
-------------------------------------------------------------------------------------------------

cd /downloads/

yum install bglibs* either wget http://www6.atomicorp.com/channels/atomic/centos/6/i386/RPMS/bglibs-1.106-1.el6.art.i686.rpm

rpm -Uvh bglibs-1.106-1.el6.art.i686.rpm

wget http://www.icewalkers.com/jump.php url=e3b53d133ca7ab23eb55edf87f11c1f4&id=1910

cd altermime-0.3.6

make

make install

cd /downloads

wget http://untroubled.org/qmail-qfilter/qmail-qfilter-2.1.tar.gz

tar xvzf qmail-qfilter-2.1.tar.gz

cd qmail-qfilter-2.1

vi qmail-qfilter.c

( change qmail into qmail2 )

------------------------------------------------------------------------------------------------------

#ifndef QMAIL_QUEUE

#define QMAIL_QUEUE "/var/qmail2/bin/qmail-queue"

#endif

------------------------------------------------------------------------------------------------------

make

make install

chmod 777 /usr/local/bin/qmail-qfilter

chown root:qmail /usr/local/bin/qmail-qfilter

================================

vi /var/qmail2/bin/qmail-tail

-------------------------------------------------------------------------------------------------------

#!/bin/sh

exec /usr/local/bin/qmail-qfilter /var/qmail2/bin/qmail-disclaimer

-------------------------------------------------------------------------------------------------------

=========================================

chown root:qmail /var/qmail2/bin/qmail-tail

chmod 777 /var/qmail2/bin/qmail-tail

mkdir /var/qmail2/control/disclaimer/

cd /var/qmail2/control/disclaimer

=================================

vim mdi.ac.in.html

================================

<html>

<body>

DISCLAIMER : Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the

addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not

disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this

message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any

attachments for the presence of viruses. The Institute accepts no liability for any damage \ caused by any virus transmitted by this email.

</body>

</html>

========================================================

chown root:qmail /var/qmail2/control/disclaimer/*

chmod 777 /var/qmail2/control/disclaimer/*

mkdir /var/tmp/qmail-qfilter

chown root:qmail /var/tmp/qmail-qfilter

chmod 777 /var/tmp/qmail-qfilte

vi /var/qmail2/bin/qmail-disclaimer

====================================

#!/bin/sh

QMAILHOST=mdi.ac.in

INSPECT_DIR=/var/tmp/qmail-qfilter

if [ ! -f /var/qmail2/control/disclaimer/$QMAILHOST.txt ]

then

cat

exit 0

fi

EX_TEMPFAIL=31

EX_UNAVAILABLE=31

trap "rm -f /var/tmp/qmail-qfilter/in.$$" 0 1 2 3 15

cd $INSPECT_DIR || { echo Error: $INSPECT_DIR does not exist; exit $EX_TEMPFAIL; }

cat >$INSPECT_DIR/in.$$ || { echo Error: Cannot write to disk; exit $EX_TEMPFAIL; }

/usr/local/bin/altermime --input=$INSPECT_DIR/in.$$ \

--xheader="X-Disclaimer: $QMAILHOST" \

--disclaimer=/var/qmail2/control/disclaimer/$QMAILHOST.txt \

--disclaimer-html=/var/qmail2/control/disclaimer/$QMAILHOST.html || { echo Error: message rejected; exit $EX_UNAVAILABLE; }

cat $INSPECT_DIR/in.$$

rm in.$$

exit $?

=====================================================

chown root:qmail /var/qmail2/bin/qmail-disclaimer

chmod 777 /var/qmail2/bin/qmail-disclaimer

================================================

vi /service/qmail2-smtpd/run

( add following line at the top)

----------------------------------------------------------------------------------------------------

#!/bin/sh

QMAILQUEUE="/var/qmail2/bin/qmail-tail" export QMAILQUEUE

===========================================================

vi /etc/services

# Local services

second-qmail 910/tcp

================================

vi /var/qmail/control/smtproutes

----------------------------------------------------------------------------------------------------

:127.0.0.1:910

----------------------------------------------------------------------------------------------------

==================================

Test Process In Bank Of Tokyo

2012-12-22T05:18:01Z

Navdeep: /* NDL Mail Server: */

[[category:Tetra Clients]]

=='''Test Process In Bank Of Tokyo'''==

'''There are in total 4 servers for Bank Of Tokyo'''
For Bank Of Tokyo To send a mail to Customer, it involve 4 servers

1.Augment Server

2.Mail Server (New Delhi Server)

3.Mail Kiban (Japan Server)

4.Client mailbox

=='''Augment Server:'''==
Augment is application server and it used java application only.

Augment server is used to generate mails.

Mails generated from augment servers are sent to NDL server for relay and which are send to Mail Kiban (Japan Server) which will then send them to customer's mailbox.

Mail Kiban (Japan Server) is running on Lotus Notes.

=='''NDL Mail Server:'''==
There are 2 servers

1.Live server with IP 150.25.2.40 with hostname in.bk.mufg.jp

2.Testing Server with IP 150.25.2.41 with t.in.bk.mufg.jp

First testing is to be done on testing servers and then successfull tests are implemented on live server.

On Test server '''Qmail + vpopmail''' services are running.

'''The two accounts used for test in NDL Mail Server are'''

1.india_e-cms@t.in.bk.mufg.jp

2.testmail@t.in.bk.mufg.jp

=='''Tests Performed On NDL Test Server:'''==

1.Telnet is done from NDL Mail Server to Mail Kiban (Japan Server) to check connectivity.

2.Telnet is done from Mail Kiban Server to NDL Mail Server to check connectivity.

3.Mail is send from NDL Mail server to a valid account with attachment to check whether mails are relaying from NDL Mail Server to Mail Kiban Server or not.

4.Mails are sent from NDL Mail Server to some annonymous unexisted customers with unexisted domain to check whether NDR(Non Delivery Report) is generated or not.

=='''Test Done from Augment Server (Application Server) to NDL Mail Server:'''==

1.Mails (2000 mails in a slot) are bombarded from Augment server with generated attachments regarding customer's account details to check feasibility of server.

2.While sending these test mails a anonymous unexisted email id was put in “TO” to check whether NDR is being generated or not.

3.Mails per second count was generated with stats that in 182 seconds 2000 mails were send and receive from NDL Mail server as 10.989 mails per second.

4.NDR for bounced mails was generated within 5 minutes.

=='''Mail Kiban Server:'''==

Mail Kiban Server is Japan Server placed in Japan with IP 172.27.160.227

Test Process In Bank Of Tokyo

2012-12-22T05:17:19Z

Navdeep: /* NDL Mail Server: */

[[category:Tetra Clients]]

=='''Test Process In Bank Of Tokyo'''==

'''There are in total 4 servers for Bank Of Tokyo'''
For Bank Of Tokyo To send a mail to Customer, it involve 4 servers

1.Augment Server

2.Mail Server (New Delhi Server)

3.Mail Kiban (Japan Server)

4.Client mailbox

=='''Augment Server:'''==
Augment is application server and it used java application only.

Augment server is used to generate mails.

Mails generated from augment servers are sent to NDL server for relay and which are send to Mail Kiban (Japan Server) which will then send them to customer's mailbox.

Mail Kiban (Japan Server) is running on Lotus Notes.

=='''NDL Mail Server:'''==
There are 2 servers

1.Live server with IP 150.25.2.40 with hostname in.bk.mufg.jp

2.Testing Server with IP 150.25.2.41 with t.in.bk.mufg.jp

First testing is to be done on testing servers and then successfull tests are implemented on live server.

On Test server '''Qmail + vpopmail''' services are running.

'''The two accounts used for test in NDL Mail Server are'''

1.india_e-cms@t.in.bk.mufg.in

2.testmail@t.in.bk.mufg.jp

=='''Tests Performed On NDL Test Server:'''==

1.Telnet is done from NDL Mail Server to Mail Kiban (Japan Server) to check connectivity.

2.Telnet is done from Mail Kiban Server to NDL Mail Server to check connectivity.

3.Mail is send from NDL Mail server to a valid account with attachment to check whether mails are relaying from NDL Mail Server to Mail Kiban Server or not.

4.Mails are sent from NDL Mail Server to some annonymous unexisted customers with unexisted domain to check whether NDR(Non Delivery Report) is generated or not.

=='''Test Done from Augment Server (Application Server) to NDL Mail Server:'''==

1.Mails (2000 mails in a slot) are bombarded from Augment server with generated attachments regarding customer's account details to check feasibility of server.

2.While sending these test mails a anonymous unexisted email id was put in “TO” to check whether NDR is being generated or not.

3.Mails per second count was generated with stats that in 182 seconds 2000 mails were send and receive from NDL Mail server as 10.989 mails per second.

4.NDR for bounced mails was generated within 5 minutes.

=='''Mail Kiban Server:'''==

Mail Kiban Server is Japan Server placed in Japan with IP 172.27.160.227

Category:Installation/Postfix Restriction

2012-12-11T08:09:22Z

Navdeep:

[[category:Installation]]

== '''''Protecting internal email distribution lists on Postfix ( Done at BLKHOSPITAL )''''' ==

'''Implementation Done at BLK Hospital'''

We want to implement an internal email distribution list. Something like teamblk@blkhospital.com.

Postfix can implement per-address access controls. What follows is based on the SMTP client IP address, and therefore is subject to IP spoofing.

==Installation==

==main.cf modifications==

'''vim /etc/postfix/main.cf'''

smtpd_recipient_restrictions = check_recipient_access '''hash:/etc/postfix/conf/protected_recipients'''
check_recipient_access = hash:/etc/postfix/conf/protected_recipients
permitted_senders_list = check_sender_access '''hash:/etc/postfix/conf/permitted_senders''', reject
smtpd_restriction_classes = '''permitted_senders_list'''

Save this file

==Protected Recipients (Groups)==

'''vim /etc/postfix/conf/protected_recipients'''

tetragroup@blkhospital.com permitted_senders_list
teamblk@blkhospital.com permitted_senders_list

Save this file

==Permitted Senders ==

'''vim /etc/postfix/conf/permitted_senders'''

tetra_test@blkhospital.com OK
sanjay.mehta@blkhospital.com OK
bhoovanpawar@blkhospital.com OK
ritu.verma@blkhospital.com OK
mybuddyhr@blkhospital.com OK
ceo@blkhospital.com OK
praneetkumar@blkhospital.com OK
nareshkapoor@blkhospital.com OK
blk@blkhospital.com OK
mradul.kaushik@blkhospital.com OK
ritachoudhrie@blkhospital.com OK
dhruvchoudhrie@blkhospital.com OK
prashantsingh@blkhospital.com OK
keshav.gupta@blkhospital.com OK

Save this file

==Final Steps ==

postmap /etc/postfix/conf/protected_recipients
postmap /etc/postfix/conf/protected_recipients
postfix reload

Getting past this scheme is relatively easy, because all one has to do is to spoof the SMTP sender address.

If the internal list is a low-volume one, perhaps it makes more sense to make it moderated.

Category:Installation/Postfix Restriction

2012-12-11T08:01:12Z

Navdeep:

[[category:Installation]]

== ''''''Protecting internal email distribution lists'''''' ==

We want to implement an internal email distribution list. Something like teamblk@blkhospital.com.

Postfix can implement per-address access controls. What follows is based on the SMTP client IP address, and therefore is subject to IP spoofing.

'''vim /etc/postfix/main.cf'''

smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/conf/protected_recipients

check_recipient_access hash:/etc/postfix/conf/protected_recipients

permitted_senders_list = check_sender_access hash:/etc/postfix/conf/permitted_senders, reject

smtpd_restriction_classes = permitted_senders_list

Save this file

'''vim /etc/postfix/conf/protected_recipients'''

tetragroup@blkhospital.com permitted_senders_list

teamblk@blkhospital.com permitted_senders_list

Save this file

'''vim /etc/postfix/conf/permitted_senders'''

tetra_test@blkhospital.com OK

sanjay.mehta@blkhospital.com OK

bhoovanpawar@blkhospital.com OK

ritu.verma@blkhospital.com OK

mybuddyhr@blkhospital.com OK

ceo@blkhospital.com OK

praneetkumar@blkhospital.com OK

nareshkapoor@blkhospital.com OK

blk@blkhospital.com OK

mradul.kaushik@blkhospital.com OK

ritachoudhrie@blkhospital.com OK

dhruvchoudhrie@blkhospital.com OK

prashantsingh@blkhospital.com OK

keshav.gupta@blkhospital.com OK

Save this file

postmap /etc/postfix/conf/protected_recipients

postmap /etc/postfix/conf/permitted_recipients

postfix reload

Getting past this scheme is relatively easy, because all one has to do is to spoof the SMTP sender address.

If the internal list is a low-volume one, perhaps it makes more sense to make it moderated.

Category:Installation/Postfix Restriction

2012-12-11T07:56:23Z

Navdeep: Created page with "category:Installation == ''''''Protecting internal email distribution lists'''''' == We want to implement an internal email distribution list. Something like teamblk@bl..."

[[category:Installation]]

== ''''''Protecting internal email distribution lists'''''' ==

We want to implement an internal email distribution list. Something like teamblk@blkhospital.com.

Postfix can implement per-address access controls. What follows is based on the SMTP client IP address, and therefore is subject to IP spoofing.

'''vim /etc/postfix/main.cf'''

smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/conf/protected_recipients

check_recipient_access hash:/etc/postfix/conf/protected_recipients

permitted_senders_list = check_sender_access hash:/etc/postfix/conf/permitted_senders, reject

smtpd_restriction_classes = permitted_senders_list

Save this file

'''vim /etc/postfix/conf/protected_recipients'''

tetragroup@blkhospital.com permitted_senders_list

teamblk@blkhospital.com permitted_senders_list

Save this file

'''vim /etc/postfix/conf/permitted_senders'''

tetra_test@blkhospital.com OK

sanjay.mehta@blkhospital.com OK

bhoovanpawar@blkhospital.com OK

ritu.verma@blkhospital.com OK

mybuddyhr@blkhospital.com OK

ceo@blkhospital.com OK

praneetkumar@blkhospital.com OK

nareshkapoor@blkhospital.com OK

blk@blkhospital.com OK

mradul.kaushik@blkhospital.com OK

ritachoudhrie@blkhospital.com OK

dhruvchoudhrie@blkhospital.com OK

prashantsingh@blkhospital.com OK

keshav.gupta@blkhospital.com OK

Save this file

postmap /etc/postfix/conf/protected_recipients

postmap /etc/postfix/conf/protected_recipients

postfix reload

Getting past this scheme is relatively easy, because all one has to do is to spoof the SMTP sender address.

If the internal list is a low-volume one, perhaps it makes more sense to make it moderated.

Category:Installation/Openldap server Installation RHEL6

2012-12-06T18:28:09Z

Navdeep:

[[category:Installation]]

=== Openldap 2.4 for RHEL6 (This is different from earlier versions of OPENLDAP )===

This Document was prepared while migrating the MDI Qmail Server to RHEL 6 Platform

=Basic Installation=

==Step 1- Yum install==

first we need to install the required packages

yum install openldap-servers

==Step 2 - Basic Configuration==
As the configuration for LDAP is stored inside the LDAP server itself the configuration has to be done by editing LDIF files under the /etc/openldap/slapd.d/ directory.

==Step 3 - Create LDAP Password==

Create the ldap password:

slappasswd some_password_text

you’ll get something like this ”{SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U” as a result. This is the string we will have to add to the bdb.ldif config file.

vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif
substitute my-domain.com with yourdomain.com
:%s/dc=my-domain,dc=com/dc=mdi,dc=ac,dc=in/g

==Step 4 -Setup Admin Password and Certificates==

We now set the admin password and specify the location of our encryption certificate and key.

Add these 3 lines at the end of the file bdb.ldif file:

olcRootPW: {SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U
olcTLSCertificateFile: /etc/pki/tls/certs/slapdcert.pem
olcTLSCertificateKeyFile: /etc/pki/tls/certs/slapdkey.pem

==Step 5- Admin Privileges==

Now we have to specify the Admin privileges

vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}monitor.ldif

Again, we have to replace the default domain name with our domain name

:%s/cn=manager,dc=my-domain,dc=com/cn=Manager,dc=mdi,dc=ac,dc=in/g

==Step 6 - Further Configuration==

Now copy data base configuration file

cp /usr/share/doc/openldap-servers-2.4.19/DB_CONFIG.example /var/lib/ldap/DB_CONFIG
chown -Rf ldap:ldap /var/lib/ldap/

==Step 7 - Certificate creation ==

Now we will need to set up a certificate for TLS. First we need to edit /etc/sysconfig/ldap and change SLAPD_LDAPS from no to yes.

vi /etc/sysconfig/ldap
SLAPD_LDAPS=yes

Now we can create the Self Sign certificate 10 years

openssl req -new -x509 -nodes -out /etc/pki/tls/certs/slapdcert.pem -keyout /etc/pki/tls/certs/slapdkey.pem -days 3650

This will create the two required keys in the /etc/pki/tls/certs/ directory. We need to make them readable for the ldap user.

chown -Rf root:ldap /etc/pki/tls/certs/$cert.pem
chmod -Rf 750 /etc/pki/tls/certs/$key.pem

==Step 8 - Importing .schema Files ==

Copy qmail.schema (ldif) files to /etc/openldap/slapd.d/cn\=config/cn\=schema/

All ldif files are sequential wise so copy with sequence

Edit ldif file according to the sequence number

dn: cn={12}qmail
objectClass: olcSchemaConfig
cn: {12}qmail

Now restart ldap

/etc/init.d/slapd start

(Error : inconsistent duplicate attribute type "mailHost")

'''Resolution :'''

Edit file : /etc/openldap/slapd.d/cn=config/cn=schema/cn={*}misc.ldif

Remove this line

olcAttributeTypes: {1}( 2.16.840.1.113730.3.1.18 NAME 'mailHost' DESC 'FQDN of
the SMTP/MTA of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} SINGLE-VALUE )

and remove “mailHost” entry from olcObjectClasses.

Again restart ldap

==Step 8 - Assigning Admin rights ==

Copy all Acl's to /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif

olcAccess: to *
by * write
by * read
olcAccess: to attrs=userPassword,sambaLMPassword,sambaNTPassword
by * write
by * auth
olcAccess: to *
by dn="uid=admin,ou=mdi.ac.in,dc=mdi,dc=ac,dc=in" write
by * read
olcAccess: to dn="cn=(.*),ou=(.*),dc=mdi,dc=ac,dc=in" attrs=mailforwardingaddress attrs=deliveryMode
by self write
by * read
by anonymous auth
olcAccess: to * by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write
by * read
olcAccess: to attrs=userPassword
by dn="uid=dovecot,ou=mail,dc=mdi,dc=ac,dc=in,dc=com" read
by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write
by anonymous auth

Again restart ldap

==Step 9 - LDAP Population of Users==

Add all users from existing ldif file from Live server

ldapadd -x -D"cn=Manager,dc=mdi,dc=ac,dc=in" -w secret -f newmdi.ldif

where newmdi.ldif is sample ldif file having users , In our case we have used the imported files from the old server (openldap-2.3.x)

=How to take backup of ldap users =

ldapsearch -x -D”cn=Managerdc=mdi,dc=ac,dc=in” -w secret -LLL > newmdi.ldif

edit ldap.conf

vim /etc/openldap/ldap.conf

HOST 127.0.0.1
BASE dc=mdi,dc=ac,dc=in

=Testing ldap server =

1.ldapsearch -x |less

2.ldapsearch -x -D”cn=Manager,dc=mdi,dc=ac,dc=in” -w secret |less

3.Test with change password using ldapmodify

4.Also login on phpldapadmin with admin user and check password will change or not

5.Check on squirrelmail , user's are able to change own password or not

Category:Installation/Openldap server Installation RHEL6

2012-12-05T09:39:47Z

Navdeep:

[[category:Installation]]

=== Openldap 2.4 for RHEL6 (This is different from earlier versions of OPENLDAP )===

This Document was prepared while migrating the MDI Qmail Server to RHEL 6 Platform

=Basic Installation=

==Step 1- Yum install==

first we need to install the required packages

yum install openldap-servers

==Step 2 - Basic Configuration==
As the configuration for LDAP is stored inside the LDAP server itself the configuration has to be done by editing LDIF files under the /etc/openldap/slapd.d/ directory.

==Step 3 - Create LDAP Password==

Create the ldap password:

slappasswd some_password_text

you’ll get something like this ”{SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U” as a result. This is the string we will have to add to the bdb.ldif config file.

vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif
substitute my-domain.com with yourdomain.com
:%s/dc=my-domain,dc=com/dc=mdi,dc=ac,dc=in/g

==Step 4 -Setup Admin Password and Certificates==

We now set the admin password and specify the location of our encryption certificate and key.

Add these 3 lines at the end of the file bdb.ldif file:

olcRootPW: {SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U
olcTLSCertificateFile: /etc/pki/tls/certs/slapdcert.pem
olcTLSCertificateKeyFile: /etc/pki/tls/certs/slapdkey.pem

==Step 5- Admin Privileges==

Now we have to specify the Admin privileges

vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}monitor.ldif

Again, we have to replace the default domain name with our domain name

:%s/cn=manager,dc=my-domain,dc=com/cn=Manager,dc=mdi,dc=ac,dc=in/g

==Step 6 - Further Configuration==

Now copy data base configuration file

cp /usr/share/doc/openldap-servers-2.4.19/ DB_CONFIG.example /var/lib/ldap/DB_CONFIG
chown -Rf ldap:ldap /var/lib/ldap/

==Step 7 - Certificate creation ==

Now we will need to set up a certificate for TLS. First we need to edit /etc/sysconfig/ldap and change SLAPD_LDAPS from no to yes.

vi /etc/sysconfig/ldap
SLAPD_LDAPS=yes

Now we can create the Self Sign certificate 10 years

openssl req -new -x509 -nodes -out /etc/pki/tls/certs/slapdcert.pem -keyout /etc/pki/tls/certs/slapdkey.pem -days 3650

This will create the two required keys in the /etc/pki/tls/certs/ directory. We need to make them readable for the ldap user.

chown -Rf root:ldap /etc/pki/tls/certs/$cert.pem
chmod -Rf 750 /etc/pki/tls/certs/$key.pem

==Step 8 - Importing .schema Files ==

Copy qmail.schema (ldif) files to /etc/openldap/slapd.d/cn\=config/cn\=schema/

All ldif files are sequential wise so copy with sequence

Edit ldif file according to the sequence number

dn: cn={12}qmail
objectClass: olcSchemaConfig
cn: {12}qmail

Now restart ldap

/etc/init.d/slapd start

(Error : inconsistent duplicate attribute type "mailHost")

'''Resolution :'''

Edit file : /etc/openldap/slapd.d/cn=config/cn=schema/cn={*}misc.ldif

Remove this line

olcAttributeTypes: {1}( 2.16.840.1.113730.3.1.18 NAME 'mailHost' DESC 'FQDN of
the SMTP/MTA of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} SINGLE-VALUE )

and remove “mailHost” entry from olcObjectClasses.

Again restart ldap

==Step 8 - Assigning Admin rights ==

Copy all Acl's to /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif

olcAccess: to *
by * write
by * read
olcAccess: to attrs=userPassword,sambaLMPassword,sambaNTPassword
by * write
by * auth
olcAccess: to *
by dn="uid=admin,ou=mdi.ac.in,dc=mdi,dc=ac,dc=in" write
by * read
olcAccess: to dn="cn=(.*),ou=(.*),dc=mdi,dc=ac,dc=in" attrs=mailforwardingaddress attrs=deliveryMode
by self write
by * read
by anonymous auth
olcAccess: to * by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write
by * read
olcAccess: to attrs=userPassword
by dn="uid=dovecot,ou=mail,dc=mdi,dc=ac,dc=in,dc=com" read
by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write
by anonymous auth

Again restart ldap

==Step 9 - LDAP Population of Users==

Add all users from existing ldif file from Live server

ldapadd -x -D"cn=Manager,dc=mdi,dc=ac,dc=in" -w secret -f newmdi.ldif

where newmdi.ldif is sample ldif file having users , In our case we have used the imported files from the old server (openldap-2.3.x)

=How to take backup of ldap users =

ldapsearch -x -D”cn=Managerdc=mdi,dc=ac,dc=in” -w secret -LLL > newmdi.ldif

edit ldap.conf

vim /etc/openldap/ldap.conf

HOST 127.0.0.1
BASE dc=mdi,dc=ac,dc=in

=Testing ldap server =

1.ldapsearch -x |less

2.ldapsearch -x -D”cn=Manager,dc=mdi,dc=ac,dc=in” -w secret |less

3.Test with change password using ldapmodify

4.Also login on phpldapadmin with admin user and check password will change or not

5.Check on squirrelmail , user's are able to change own password or not

Category:Troubleshooting/Punjabgovt Project

2012-12-05T08:49:32Z

Navdeep:

[[category:Troubleshooting]]

'''Zimbra Server 8'''

Architecture :

1. MTA : 192.168.70.54

Cluster IP : 192.168.70.53

2. MTA : 192.168.70.55

Mailbox server (Failover)

1. Mailbox : 192.168.70.56

2. Mailbox : 192.168.70.57

Archive Server : 192.168.70.60 (virtual machine)

That is situated in 192.168.70.55

1. Zimbra server cluster Ip is not working but zimbra serices are running:

Command :

1. clustat status

2. On both the server's simultaneously :

service rgmanager stop

service cman stop

then

service cman start

service rgmanager start

3. Where Archive server located , at 192.168.70.55 that is MTA2

== == '''Punjab Government Servers - Startup and shut-off Commands''' == ==

'''SAMBA SERVER SHUTDOWN PROCESS'''

This server running Samba PDC,DNS,DHCP,LAM,ntp.

SERVER MASTER ADDRESS : 192.168.10.81

SERVER SLAVE ADDRESS : 192.168.10.82

//Run these command on both master and slave simultaneously as root

# service ctdb stop

# service clvmd stop

# service cman stop

'''SAMBA SERVER STARTUP PROCESS'''

#service cman start

#service clvmd start

<check partitions are mounted or not ,If not mounted then (mount –a)

#mount -a

# service ctdb start

For testing run

# ping 192.168.10.93 //cluster ip

# ctdb status

'''
ZIMBRA MAIL SERVER SHUTDOWN PROCESS'''

There are five servers of Zimbra :

1.192.168.70.54 – MailBox1

2.192.168.70.55 – MailBox2

3.192.168.70.56 – MTA1

4.192.168.70.57 – MTA2

5.192.168.70.60 – ZIMBRA ARCHIVING

Cluster IP : 192.168.70.53(mail.punjabgovt.gov.in)

'''STEPS:'''

1.Firstly shutdown properly 192.168.70.60 that is virtual machine inside the 192.168.70.55

Command run as a root user

# init 0

2.Then shutdown MTA servers properly 192.168.70.56 and 192.168.70.57

Command run as a root user

# init 0

3.Then properly shutdown MAILBOX servers 192.168.70.54 and 192.168.70.55

Command run as a root user

# init 0

'''
ZIMBRA MAIL SERVER STARTUP PROCESS'''

1.Start automatically both MTA servers

2.Mail Box 2 server : 192.168.10.55

Run command as a root user,

Command : ifup bridge0

3.Then on both the machine(mailbox1 and mailbox2 run simultaneously )

Command run as a root user,

#service cman start

#service rgmanager start

4.Check if cluster is in mailbox1

# clustat

5.If cluster is not in mailbox1

Then run on machine (mailbox1 )

# clusvcadm –d mailCluster

#clusvcadm –e mailCluster –m `hostname`

==
'''DOMAIN SERVER SHUTDOWN PROCESS''' ==

There are two domain servers that contain 4 virtual machines each so firstly properly shut down these virtual machines on both the servers then after shutdown the base machines of domain1 and domain2

Virtual Machines Domain1

Domain1 : 192.168.10.57

Virtual Machine 1 :

1.AAA 1: 192.168.10.92

2.SQUID1: 192.168.10.94

3.LDAP1: 192.168.10.96

4.NITROBIT1: 192.168.10.95

Domain2: 192.168.10.58

Virtual Machine 2 :

1.AAA 2 : 192.168.10.97

2.SQUID2 : 192.168.10.99

3.LDAP2 : 192.168.10.96

4.NITROBIT2 : 192.168.10.100

CLUSTERS IP:

1.LDAP : 192.168.10.98

2.SQUID : 192.168.10.105

3.AAA : 192.168.10.104

4.NITROBIT ARE IN FAIL OVER ENVIRONMENT

How to Shutdown these servers properly

'''Steps:'''

1.Properly shutdown ldap,squid,aaa (run below commands simultaneously)

Command run as a root user

# service rgmanager stop

# service cman stop

# init 0

2.On domain 1 and domain 2 machine (run simultaneously on both the machines)

Run command as a root user

#service rgmanager stop

#service cman stop

'''DOMAIN SERVER STARTUP PROCESS'''

1.Firstly on Domain1 machine then after 2-3 minutes Domain 2 machine.

2.On Domain 2 machine run

# ifup bridge0

3.Then on both Domain1 and Domain2 machines run command simultaneously)

#service cman start

#service rgmanager start

4.Now all the base machines are up

5.Then Check virtual machine (ldap,aaa,squid,nitrobit)

6.On LDAP1 machine run command to check cluster is in LDAP1 or LDAP2.

# clustat

If machine is in LDAP2 then run command on LDAP1 machine

# clusvcadm –d dummy_httpd

#clusvcadm –e dummy_httpd –m `hostname`

Check by ping 192.168.10.98

7.On SQUID1 machine run command to check cluster is in SQUID1 or SQUID2.

# clustat

If machine is in SQUID2 then run command on SQUID1 machine

# clusvcadm –d Squid

#clusvcadm –e Squid –m `hostname`

Check by ping 192.168.10.105

8.On AAA1 machine run command to check cluster is in AAA1 or AAA2.

# clustat

If cluster is in AA2 then run command on AAA1 machine

# clusvcadm –d Radius

#clusvcadm –e Radius –m `hostname`

Check by ping 192.168.10.104

9.Nitrobit 1 and Nitrobit 2 machine automatically started properly and not required to run any.

TROUBLESHOOTING WITH SERVERS

Note : If network fails then server restart automatically when machine is in cluster (HP-ILO restart server then they fence services to another server)
If network fails long time then it can’t able to fence services to another but then retry up to 10 minutes after still network is down then both the machines are shut-off automatically(HP-ILO has an capability to shutdown the machine).
After network is UP then machines are properly start according to above documentation.

DOMAIN SERVER :

1.If Domain server is shutoff then read the documentation above to start the domain servers.

2.If in case domain 1 machine is off and domain2 is in cluster and wanted to change the state of cluster

Run these command on Domain 2 firstly

# service rgmanager stop

# service cman stop

3.After on the Domain1 machine :

Run these command on Domain2

#ifup bridge0

4.After both the machine are in network and ON, then run command simultaneously on both the machine

#service cman start

#service rgmanager start

LDAP SERVER:

1.If LDAP server is not starting , when u restart the ldap service then error comes then run this command on both the server.

On LDAP1

# cp /etc/dirsrv/slapd-ldap1/dse.ldif.bak /etc/dirsrv/slapd-ldap1/dse.ldif

On LDAP2

#cp /etc/dirsrv/slapd-ldap2/dse.ldif.bak /etc/dirsrv/slapd-ldap2/dse.ldif

2.This command is run because dse.ldif file is corrupted when server unproperly shutoff/ fencing is not done.

3.If cluster is in Node2(LDAP2) and wanted to change the state then check Node1 server is ON or OFF.

4.If Node1 is OFF then ON the machine or ON then run these commands on Node1(LDAP1)

# clusvcadm –d dummy_httpd

# clusvcadm –e dummy_httpd –m `hostname`

Same process for Squid and AAA Server to change the state of cluster.

Category:Troubleshooting/Punjabgovt Project

2012-12-05T08:47:39Z

Navdeep:

[[category:Troubleshooting]]

'''Zimbra Server 8'''

Architecture :

1. MTA : 192.168.70.54

Cluster IP : 192.168.70.53

2. MTA : 192.168.70.55

Mailbox server (Failover)

1. Mailbox : 192.168.70.56

2. Mailbox : 192.168.70.57

Archive Server : 192.168.70.60 (virtual machine)

That is situated in 192.168.70.55

1. Zimbra server cluster Ip is not working but zimbra serices are running:

Command :

1. clustat status

2. On both the server's simultaneously :

service rgmanager stop

service cman stop

then

service cman start

service rgmanager start

3. Where Archive server located , at 192.168.70.55 that is MTA2
''''''

Punjab Government Servers - Startup and shut-off Commands''''''
== Headline text ==

'''SAMBA SERVER SHUTDOWN PROCESS'''

This server running Samba PDC,DNS,DHCP,LAM,ntp.

SERVER MASTER ADDRESS : 192.168.10.81

SERVER SLAVE ADDRESS : 192.168.10.82

//Run these command on both master and slave simultaneously as root

# service ctdb stop

# service clvmd stop

# service cman stop

'''SAMBA SERVER STARTUP PROCESS'''

#service cman start

#service clvmd start

<check partitions are mounted or not ,If not mounted then (mount –a)

#mount -a

# service ctdb start

For testing run

# ping 192.168.10.93 //cluster ip

# ctdb status

'''
ZIMBRA MAIL SERVER SHUTDOWN PROCESS'''

There are five servers of Zimbra :

1.192.168.70.54 – MailBox1

2.192.168.70.55 – MailBox2

3.192.168.70.56 – MTA1

4.192.168.70.57 – MTA2

5.192.168.70.60 – ZIMBRA ARCHIVING

Cluster IP : 192.168.70.53(mail.punjabgovt.gov.in)

'''STEPS:'''

1.Firstly shutdown properly 192.168.70.60 that is virtual machine inside the 192.168.70.55

Command run as a root user

# init 0

2.Then shutdown MTA servers properly 192.168.70.56 and 192.168.70.57

Command run as a root user

# init 0

3.Then properly shutdown MAILBOX servers 192.168.70.54 and 192.168.70.55

Command run as a root user

# init 0

'''
ZIMBRA MAIL SERVER STARTUP PROCESS'''

1.Start automatically both MTA servers

2.Mail Box 2 server : 192.168.10.55

Run command as a root user,

Command : ifup bridge0

3.Then on both the machine(mailbox1 and mailbox2 run simultaneously )

Command run as a root user,

#service cman start

#service rgmanager start

4.Check if cluster is in mailbox1

# clustat

5.If cluster is not in mailbox1

Then run on machine (mailbox1 )

# clusvcadm –d mailCluster

#clusvcadm –e mailCluster –m `hostname`

==
'''DOMAIN SERVER SHUTDOWN PROCESS''' ==

There are two domain servers that contain 4 virtual machines each so firstly properly shut down these virtual machines on both the servers then after shutdown the base machines of domain1 and domain2

Virtual Machines Domain1

Domain1 : 192.168.10.57

Virtual Machine 1 :

1.AAA 1: 192.168.10.92

2.SQUID1: 192.168.10.94

3.LDAP1: 192.168.10.96

4.NITROBIT1: 192.168.10.95

Domain2: 192.168.10.58

Virtual Machine 2 :

1.AAA 2 : 192.168.10.97

2.SQUID2 : 192.168.10.99

3.LDAP2 : 192.168.10.96

4.NITROBIT2 : 192.168.10.100

CLUSTERS IP:

1.LDAP : 192.168.10.98

2.SQUID : 192.168.10.105

3.AAA : 192.168.10.104

4.NITROBIT ARE IN FAIL OVER ENVIRONMENT

How to Shutdown these servers properly

'''Steps:'''

1.Properly shutdown ldap,squid,aaa (run below commands simultaneously)

Command run as a root user

# service rgmanager stop

# service cman stop

# init 0

2.On domain 1 and domain 2 machine (run simultaneously on both the machines)

Run command as a root user

#service rgmanager stop

#service cman stop

'''DOMAIN SERVER STARTUP PROCESS'''

1.Firstly on Domain1 machine then after 2-3 minutes Domain 2 machine.

2.On Domain 2 machine run

# ifup bridge0

3.Then on both Domain1 and Domain2 machines run command simultaneously)

#service cman start

#service rgmanager start

4.Now all the base machines are up

5.Then Check virtual machine (ldap,aaa,squid,nitrobit)

6.On LDAP1 machine run command to check cluster is in LDAP1 or LDAP2.

# clustat

If machine is in LDAP2 then run command on LDAP1 machine

# clusvcadm –d dummy_httpd

#clusvcadm –e dummy_httpd –m `hostname`

Check by ping 192.168.10.98

7.On SQUID1 machine run command to check cluster is in SQUID1 or SQUID2.

# clustat

If machine is in SQUID2 then run command on SQUID1 machine

# clusvcadm –d Squid

#clusvcadm –e Squid –m `hostname`

Check by ping 192.168.10.105

8.On AAA1 machine run command to check cluster is in AAA1 or AAA2.

# clustat

If cluster is in AA2 then run command on AAA1 machine

# clusvcadm –d Radius

#clusvcadm –e Radius –m `hostname`

Check by ping 192.168.10.104

9.Nitrobit 1 and Nitrobit 2 machine automatically started properly and not required to run any.

TROUBLESHOOTING WITH SERVERS

Note : If network fails then server restart automatically when machine is in cluster (HP-ILO restart server then they fence services to another server)
If network fails long time then it can’t able to fence services to another but then retry up to 10 minutes after still network is down then both the machines are shut-off automatically(HP-ILO has an capability to shutdown the machine).
After network is UP then machines are properly start according to above documentation.

DOMAIN SERVER :

1.If Domain server is shutoff then read the documentation above to start the domain servers.

2.If in case domain 1 machine is off and domain2 is in cluster and wanted to change the state of cluster

Run these command on Domain 2 firstly

# service rgmanager stop

# service cman stop

3.After on the Domain1 machine :

Run these command on Domain2

#ifup bridge0

4.After both the machine are in network and ON, then run command simultaneously on both the machine

#service cman start

#service rgmanager start

LDAP SERVER:

1.If LDAP server is not starting , when u restart the ldap service then error comes then run this command on both the server.

On LDAP1

# cp /etc/dirsrv/slapd-ldap1/dse.ldif.bak /etc/dirsrv/slapd-ldap1/dse.ldif

On LDAP2

#cp /etc/dirsrv/slapd-ldap2/dse.ldif.bak /etc/dirsrv/slapd-ldap2/dse.ldif

2.This command is run because dse.ldif file is corrupted when server unproperly shutoff/ fencing is not done.

3.If cluster is in Node2(LDAP2) and wanted to change the state then check Node1 server is ON or OFF.

4.If Node1 is OFF then ON the machine or ON then run these commands on Node1(LDAP1)

# clusvcadm –d dummy_httpd

# clusvcadm –e dummy_httpd –m `hostname`

Same process for Squid and AAA Server to change the state of cluster.

Category:Installation/Openldap server Installation RHEL6

2012-12-04T13:17:17Z

Navdeep: Created page with "category:Installation == == == '''Openldap 2.4 for RHEL6''' == == == '''Step 1''': first we need to install the required packages: #yum install openldap-servers..."

[[category:Installation]]

== == == '''Openldap 2.4 for RHEL6''' == == ==

'''Step 1''': first we need to install the required packages:

#yum install openldap-servers migrationtools

'''Step2:''' As the configuration for LDAP is stored inside the LDAP server itself the configuration has to be done by editing LDIF files under the /etc/openldap/slapd.d/ directory.

Now create the ldap password:

#slappasswd

you’ll get something like this ”{SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U” as a result. This is the string we will have to add to the bdb.ldif config file.

vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif

substitute my-domain.com with yourdomain.com

:%s/dc=my-domain,dc=com/dc=mdi,dc=ac,dc=in/g

'''
Step 3:''' We now set the admin password and specify the location of our encryption certificate and key.

add these 3 lines at the end of the file bdb.ldif file:

olcRootPW: {SSHA}4+B3B1p3LlDAApcill87VXFD80jbgX8U

olcTLSCertificateFile: /etc/pki/tls/certs/slapdcert.pem

olcTLSCertificateKeyFile: /etc/pki/tls/certs/slapdkey.pem

'''Step 4:''' Now we have to specify the monitoring privileges

#vim /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}monitor.ldif

again, we have to replace the default domain name with our domain name

:%s/cn=manager,dc=my-domain,dc=com/cn=Manager,dc=mdi,dc=ac,dc=in/g

'''Step 5:''' Now copy data base configuration file

#cp /usr/share/doc/openldap-servers-2.4.19/ DB_CONFIG.example /var/lib/ldap/DB_CONFIG

#chown -Rf ldap:ldap /var/lib/ldap/

'''Step 6:''' Now we will need to set up a certificate for TLS. First we need to edit /etc/sysconfig/ldap and change SLAPD_LDAPS from no to yes.

#vi /etc/sysconfig/ldap

SLAPD_LDAPS=yes

Now we can create the certificate

#openssl req -new -x509 -nodes -out /etc/pki/tls/certs/slapdcert.pem -keyout /etc/pki/tls/certs/slapdkey.pem -days 3650

This will create the two required keys in the /etc/pki/tls/certs/ directory. We need to make them readable for the ldap user.

# chown -Rf root:ldap /etc/pki/tls/certs/$cert.pem

# chmod -Rf 750 /etc/pki/tls/certs/$key.pem

Copy schema (ldif) files to /etc/openldap/slapd.d/cn\=config/cn\=schema/

* All ldif files are sequential wise so copy with sequence

Edit ldif file according to the sequence number

dn: cn={12}qmail

objectClass: olcSchemaConfig

cn: {12}qmail

Now restart ldap

#/etc/init.d/slapd start

(Error : inconsistent duplicate attribute type "mailHost")
'''
Resolution :'''

Edit file : /etc/openldap/slapd.d/cn=config/cn=schema/cn={*}misc.ldif

Remove this line

olcAttributeTypes: {1}( 2.16.840.1.113730.3.1.18 NAME 'mailHost' DESC 'FQDN of

the SMTP/MTA of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} SINGLE-VALUE )

and remove “mailHost” entry from olcObjectClasses.

Again restart ldap

'''Step7:'''

Copy all Acl's to /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif

olcAccess: to *

by * write

by * read

olcAccess: to attrs=userPassword,sambaLMPassword,sambaNTPassword

by * write

by * auth

olcAccess: to *

by dn="uid=admin,ou=mdi.ac.in,dc=mdi,dc=ac,dc=in" write

by * read

olcAccess: to dn="cn=(.*),ou=(.*),dc=mdi,dc=ac,dc=in" attrs=mailforwardingaddress attrs=deliveryMode

by self write

by * read

by anonymous auth

olcAccess: to * by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write

by * read

olcAccess: to attrs=userPassword

by dn="uid=dovecot,ou=mail,dc=mdi,dc=ac,dc=in,dc=com" read

by dn="uid=admin,ou=mail,dc=mdi,dc=ac,dc=in" write

by anonymous auth

Again restart ldap

'''Step8:''' Add all users from existing ldif file from Live server

ldapadd -x -D"cn=Manager,dc=mdi,dc=ac,dc=in" -w secret -f newmdi.ldif

How to take backup of ldapusers :

ldapsearch -x -D”cn=Managerdc=mdi,dc=ac,dc=in” -w secret -LLL > newmdi.ldif

edit ldap.conf

vim /etc/openldap/ldap.conf

HOST 127.0.0.1

BASE dc=mdi,dc=ac,dc=in

'''Test ldap server :'''

1.ldapsearch -x |less

2.ldapsearch -x -D”cn=Manager,dc=mdi,dc=ac,dc=in” -w secret |less

3.Test with change password using ldapmodify

4.Also login on phpldapadmin with admin user and check password will change or not

5.Check on squirrelmail , user's are able to change own password or not

Category:Troubleshooting/Punjabgovt Project

2012-12-03T12:50:03Z

Navdeep: Created page with "'''Zimbra Server 8''' Architecture : 1. MTA : 192.168.70.54 Cluster IP : 192.168.70.53 2. MTA : 192.168.70.55 Mailbox server (Failover) 1. Ma..."

'''Zimbra Server 8'''

Architecture :

1. MTA : 192.168.70.54

Cluster IP : 192.168.70.53

2. MTA : 192.168.70.55

Mailbox server (Failover)

1. Mailbox : 192.168.70.56

2. Mailbox : 192.168.70.57

Archive Server : 192.168.70.60 (virtual machine)

That is situated in 192.168.70.55

1. Zimbra server cluster Ip is not working but zimbra serices are running:

Command :

1. clustat status

2. On both the server's simultaneously :

service rgmanager stop

service cman stop

then

service cman start

service rgmanager start

3. Where Archive server located , at 192.168.70.55 that is MTA2

TetraWiki:General disclaimer

2012-11-28T12:59:04Z

Navdeep: Created page with "Powered by Tetra Information Services"

File:Capital11.png

2012-11-28T07:42:20Z

Navdeep:

Main Page

2012-11-28T07:41:30Z

Navdeep:

=== WELCOME TO TetraWiki ===

This is a place to learn and contribute. Enjoy your stay...!!!

----

If your answer is not found here, please try the following:

* RTFM

* Google

{{Special:Categories}}

File:Zimbra 7 HA DRBD+Heartbeat1.doc

2012-11-28T07:31:20Z

Navdeep: uploaded a new version of "File:Zimbra 7 HA DRBD+Heartbeat1.doc": Zimbra on HA with DRBD and Heartbeat on ALPHA

Alpha ZImbra on HA with DRBD and HeartbeatV1 Implementation

File:Zimbra 7 HA DRBD+Heartbeat1.doc

2012-11-28T07:28:18Z

Navdeep: Alpha ZImbra on HA with DRBD and HeartbeatV1 Implementation

Alpha ZImbra on HA with DRBD and HeartbeatV1 Implementation