TetraWiki - User contributions [en]

System requirement by a Java Trainee

2013-03-01T09:48:13Z

Deepak:

'''System Requirement by a Java Trainee'''

----

'''For Jboss Trainee'''

1. Jdk 1.6 java

2. Linux Operating System

3. RAM 2GB

4. Google Chrome

5. Mozilla Firefox

6. Teamviewer7

7. Jboss final

8. Eclipse

9. Copy some files related to ireport

----

----

'''For Tomcat Trainee'''

1. Jdk 1.6 java

2. Linux Operating System

3. RAM 2GB

4. Google Chrome

5. Mozilla Firefox

6. Teamviewer7

7. Tomcat

8. Eclipse

9. Copy some files related to ireport

10. Dbvisualiser

System requirement by a Java Trainee

2013-03-01T09:47:29Z

Deepak: Created page with "'''System Requirement by a Java Trainee''' ---- '''For Jboss Trainee''' 1. Jdk 1.6 java 2. Linux Operating System 3. RAM 2GB 4. Google Chrome 5. Mozilla Firefox 6. Te..."

'''System Requirement by a Java Trainee'''

----

'''For Jboss Trainee'''

1. Jdk 1.6 java

2. Linux Operating System

3. RAM 2GB

4. Google Chrome

5. Mozilla Firefox

6. Teamviewer7

7. Jboss final

8. Eclipse

9. Copy some files related to ireport

----

----

'''For Jboss Trainee'''

1. Jdk 1.6 java

2. Linux Operating System

3. RAM 2GB

4. Google Chrome

5. Mozilla Firefox

6. Teamviewer7

7. Tomcat

8. Eclipse

9. Copy some files related to ireport

10. Dbvisualiser

How to change logo on Zimbra

2013-02-16T06:04:41Z

Deepak: Created page with "'''Steps to change logo on zimbra server''' ---- ---- 1. Make your own logo to the size 300 x 48 pixel, and save with format .png and give its name LoginBanner.png 2. Cop..."

'''Steps to change logo on zimbra server'''

----

----

1. Make your own logo to the size 300 x 48 pixel, and save with format .png and give its name LoginBanner.png

2. Copy (upload) to Zimbra Server (/tmp/LoginBanner.png)

3. Login as root user and type the following commands:

cd /opt/zimbra/jetty/webapps/zimbra/skins/carbon/logos/

cp LoginBanner.png LoginBanner.bak

cp /tmp/LoginBanner.png .

4. Refresh the login page. NOTE: You might need to press CTRL+F5 to force a re-download of the image file in the browser.

'''Here is how to change or hide the little vmware logo on the login page:'''

1. Make your own logo (or empty image) to the size 71 x 11 pixel, and save with format .png and give its name AltBanner.png

2. Copy (upload) to Zimbra Server (/tmp/AltBanner.png)

3. Login as root user and type the following commands:

cd /opt/zimbra/jetty/webapps/zimbra/skins/carbon/logos/

cp AltBanner.png AltBanner.bak

cp /tmp/AltBanner.png .

4. Refresh the login page. NOTE: You might need to press CTRL+F5 to force a re-download of the image file in the browser.

'''Here is how to change the Zimbra logo that sits at the top-left of the app window:'''

1. Make your own logo to the size 250 x 35 pixel, and save with format .png and give its name AppBanner.png

2. Copy (upload) to Zimbra Server (/tmp/AppBanner.png )

3. Login as root user and type the following commands:

cd /opt/zimbra/jetty/webapps/zimbra/skins/carbon/logos/

cp AppBanner.png AppBanner.bak

cp /tmp/AppBanner.png .

4. Refresh the web page. NOTE: You might need to press CTRL+F5 to force a re-download of the image file in the browser.

'''Finally restart Zimbra'''

Category:Tetra Clients/Bank Of Tokyo Configuration

2013-02-12T06:03:01Z

Deepak: Created page with "'''Production Server Configuration''' ---- ---- IP : 150.25.2.40 Server Name : indiamail.in.bk.mufg.jp Service Running : qmail with vpopmail '''Operating system''' D..."

'''Production Server Configuration'''

----

----

IP : 150.25.2.40

Server Name : indiamail.in.bk.mufg.jp

Service Running : qmail with vpopmail

'''Operating system'''

Distributer ID : RedHatEnterpriseServer

Description : Red Hat Enterprise Linux Server release 5.8 (64 bit)

Release : 5.8

Kernel Name : Linux

Processor : X86_64

Kernel-release : 2.6.18-308.el5

'''/etc/tcp.smtp'''

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

172.27.69.1:allow,RELAYCLIENT=""

'''qmail Configuration:'''

helohost : indiamail.in.bk.mufg.jp

locals : indiamail.in.bk.mufg.jp

me : IndiaPost

queuelifetime : 300

smtproutes : 172.27.65.3

timeoutremote : 90

timeoutconnect : 110

concurrencyremote : 10

concurrencyincoming : 120

'''Hardware Configuration'''

RAM : 16015 MB

Harddisk : 3600 GB ( 6 harddisk each of 600 GB)

Vendor_ID : GenuineIntel

cpu MHZ : 1200.00

address sizes : 46 bits physical, 48 bits virtual

----

----

'''Backup Server Configuration'''

IP : 150.25.2.42

Server Name : indiamail.in.bk.mufg.jp

Service Running : qmail with vpopmail

'''Operating system'''

Distributer ID : RedHatEnterpriseServer

Description : Red Hat Enterprise Linux Server release 5.8 (64 bit)

Release : 5.8

Kernel Name : Linux

Processor : X86_64

Kernel-release : 2.6.18-308.el5

'''/etc/tcp.smtp'''

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

172.27.69.1:allow,RELAYCLIENT=""

'''qmail Configuration:'''

helohost : indiamail.in.bk.mufg.jp

locals : indiamail.in.bk.mufg.jp

me : IndiaPost

queuelifetime : 300

smtproutes : 172.27.65.3

timeoutremote : 90

timeoutconnect : 110

concurrencyremote : 10

concurrencyincoming : 120

'''Hardware Configuration'''

RAM : 16015 MB

Harddisk : 3600 GB ( 6 harddisk each of 600 GB)

Vendor_ID : GenuineIntel

cpu MHZ : 1200.00

address sizes : 46 bits physical, 48 bits virtual

----

----

'''Test Server Configuration'''

IP : 150.25.2.41

Server Name : indiamailt.t.in.bk.mufg.jp

Service Running : qmail with vpopmail

Operating system

Distributer ID : RedHatEnterpriseServer

Description : Red Hat Enterprise Linux Server release 5.8 (64 bit)

Release : 5.8

Kernel Name : Linux

Processor : X86_64

Kernel-release : 2.6.18-308.el5

'''/etc/tcp.smtp'''

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

172.27.160.5:allow,RELAYCLIENT=""

'''qmail Configuration:'''

helohost : indiamailt.t.in.bk.mufg.jp

locals : indiamailt.t.in.bk.mufg.jp

me : IndiaPost

queuelifetime : 300

smtproutes : 172.27.160.227

timeoutremote : 90

timeoutconnect : 110

concurrencyremote : 10

concurrencyincoming : 120

'''Hardware Configuration'''

RAM : 16015 MB

Harddisk : 3600 GB ( 6 harddisk each of 600 GB)

Vendor_ID : GenuineIntel

cpu MHZ : 1200.00

address sizes : 46 bits physical, 48 bits virtual

----

Category:Tetra Clients/Orient Bell

2013-01-05T11:32:11Z

Deepak: Created page with "'''OrientBell''' ---- '''Global IP:''' 182.18.187.40 eth0 '''Local IP :''' 182.18.187.41 eth0:1 ---- '''Services Running:''' 1.Zimbra ---- '''General Tickets with Orie..."

'''OrientBell'''

----

'''Global IP:''' 182.18.187.40 eth0

'''Local IP :''' 182.18.187.41 eth0:1

----

'''Services Running:'''

1.Zimbra

----

'''General Tickets with Orientbell:'''

----

'''To check what is the date of the oldest mail of a user'''

zmprov ga user@orientbell.com | grep zimbraPrefPop3DownloadSince

zimbraPrefPop3DownloadSince: YYYYMNDDHHMMSSZ

(it is showing that year YYYY month MN date DD hour HH minute MM second SS)

'''To download mails for a user'''

zmprov ma user@orientbell.com zimbraPrefPop3DownloadSince YYYYMNDDHHMMSSZ

To check whether mails are downloaded upto specific daet or not use

zmprov ga user@orientbell.com | grep zimbraPrefPop3DownloadSince

zimbraPrefPop3DownloadSince: YYYYMNDDHHMMSSZ

'''To check all accounts:'''

zmaccts

It will show each and every account in the domain with it's status whether active or closed , last logon, account creation date.

'''To get all distribution lists in domain'''

zmprov gadl orientbell.com

'''To get details of a distribution list:'''

zmprov gdl list@orientbell.com

Category:Tetra Clients/Jacob Ballas Architecture

2013-01-05T11:00:26Z

Deepak: Created page with " == Architecture of Jacob India == There are 3 server for Jacob India in total. Two are physical and one is virtual. '''Kloxo Link:''' http://208.109.176.99:7778/ '''Ope..."

== Architecture of Jacob India ==

There are 3 server for Jacob India in total.

Two are physical and one is virtual.

'''Kloxo Link:''' http://208.109.176.99:7778/

'''Operating System:''' CentOS release 5.5

'''Global IP:''' 208.109.176.99

----

'''Device Name:''' eth0

'''Ipaddress:''' 208.109.176.99

'''Netmask:''' 255.255.255.0

'''Device Name:''' eth0-1

'''Ipaddress:''' 208.109.176.32

'''Netmask:''' 255.255.255.0

'''Device Name:''' eth0-0

'''Ipaddress:''' 208.109.176.6

'''Netmask:''' 255.255.255.0

'''Mail Server:''' mail.jbindia.co.in

'''Services Running'''

1.courier-imap

2.httpd

3.iptables

4.DNS

5.qmail

6.Spamassassin

'''Various clients on jbindia'''

1.Arihant

2.Babaramsaapeer

3.Bbfgroup

4.Eltek

5.Holostik

6.Jbindia

7.Jvintl

8.Kortekelectronics

9.Krishnamaruti

10.Lgalumni

11.Pria

12.Rtdc_sahara

13.Ssbf

14.Support-tetra

15.Supportcareindia

----

'''Global IP:''' 122.160.38.106

'''Operating System:''' Fedora Core-3

'''Services Running:'''

1.Proxy

2.Squid

3.Shorewall

----

'''Global IP:''' 192.168.0.227

'''Operating System:''' Fedora Core-3

'''Services Running:'''

1.Qmail+3 Instance

2.Transparent Proxy

3.Webmin

4.Squid

5.Trend

6.DNS

File:Email Configuration on iPhone 4.doc

2013-01-05T10:45:39Z

Deepak: The file consist steps for Email Configuration on i-Phone 4 for heromotocorp.biz

The file consist steps for Email Configuration on i-Phone 4 for heromotocorp.biz

Category:Zimbra/Restricting users to send mails to certain domains

2013-01-03T11:49:07Z

Deepak:

'''Restricting users to send mails to certain domains'''
== Headline text ==

1. Enter following in the file “/opt/zimbra/conf/postfix_recipient_restrictions.cf”. Make sure it is entered at the top of the file.

vi /opt/zimbra/conf/postfix_recipient_restrictions.cf

check_sender_access hash:/opt/zimbra/postfix/conf/restricted_senders

2. Enter following in "/opt/zimbra/conf/zmmta.cf"

vi /opt/zimbra/conf/zmmta.cf

###Find the section labeled SECTION mta and enter the following two lines directly below####

POSTCONF smtpd_restriction_classes local_only

POSTCONF local_only FILE postfix_check_recipient_access.cf

3. Create a file "/opt/zimbra/conf/postfix_check_recipient_access.cf"

vi /opt/zimbra/conf/postfix_check_recipient_access.cf

check_recipient_access hash:/opt/zimbra/postfix/conf/local_domains, reject

4. Create a file "/opt/zimbra/postfix/conf/restricted_senders" and list all the users, whom you want to restrict. Follow this syntax:

vi /opt/zimbra/postfix/conf/restricted_senders

(all users in tipl domain) local_only

5. Create a file "/opt/zimbra/postfix/conf/local_domains" and list all the domains where "restricted users" allowed to sent mails. Please follow this syntax:

vi /opt/zimbra/postfix/conf/local_domains

domain.com OK

6. Run following commands:

postmap /opt/zimbra/postfix/conf/restricted_senders

postmap /opt/zimbra/postfix/conf/local_domains

zmmtactl stop

zmmtactl start

After these settings, all the users listed in "/opt/zimbra/postfix/conf/restricted_senders" are restricted to send mails only to domain which are defined in "/opt/zimbra/postfix/conf/local_domains".

Category:Tetra Clients/Care India Architecture

2013-01-01T08:23:52Z

Deepak:

'''CARE INDIA'''
----

'''Weblink:'''careindia.org

'''DNS:''' 204.232.209.139

----

'''Services supported by Tetra:'''

1.Website

2.Send mail

----

'''Sendmail-''' when somebody donates money than a mail get generated from their server through send mail and this mail is relayed from our mail.tetrain.com

Webmail account for Care India is at http://208.109.176.99:7778/login/ with name supportcareindia.

'''Global IP :''' 204.232.209.139

Category:Tetra Clients/Care India Architecture

2013-01-01T08:20:52Z

Deepak: Created page with "'''CARE INDIA''' ---- '''Weblink:'''careindia.org '''DNS:''' 204.232.209.139 ---- '''Services supported by Tetra:''' 1.Website 2.Send mail ---- '''Sendmail-''' when ..."

Category:Tetra Clients/Muthoot Architecture

2012-12-22T10:22:52Z

Deepak: Created page with "'''Muthoot Finance''' '''Global IP:''' 182.71.162.134 (Global) '''Local IP accesible to us and on which we have installed services:''' 192.168.1.129 eth0 192.168.1.130 1..."

'''Muthoot Finance'''

'''Global IP:''' 182.71.162.134 (Global)

'''Local IP accesible to us and on which we have installed services:'''

192.168.1.129 eth0

192.168.1.130

192.168.1.131

192.168.1.132

192.168.1.133

192.168.1.136

'''Hostname:'''
backup.muthoot2.com

'''Services Running:'''

1.Postgres

2.Jboss (Used for Application)

We have to provide them support regarding Database and J-Boss.

'''Number Of Processors:''' 4

Category:Tetra Clients/RL Khanna Architecture

2012-12-22T09:00:49Z

Deepak: RL Khanna Architecture

'''Architecture for RL Khanna'''
----

'''Services Running On:'''

1.Shorewall

2.Squid

3.Qmail+2instances

4.vpopmail

5.Spamassassin

----

'''Location:'''

R.L.Khanna & Co. (Overseas) 289 Udyog Vihar Phase-2, Gurgaon

----

'''This is a single Physically Dedicated server.'''

'''Server Details:'''

'''Global IP :''' 122.160.87.129 (active), eth0 port

'''Local IP :''' 192.9.200.250 , eth0 port

'''DNS : ''' 202.56.215.6 and 202.56.230.6

Category:Tetra Clients/Arihant Electricals Arhitecture

2012-12-21T11:01:12Z

Deepak: Created page with "'''Arihant Electricals Architecture''' '''Mail Transfer Agent = qmail''' '''Services Running on server:''' 1.qmail 2.vpopmail 3.fetchmail '''Server Details''' '''Glo..."

'''Arihant Electricals Architecture'''

'''Mail Transfer Agent = qmail'''

'''Services Running on server:'''

1.qmail

2.vpopmail

3.fetchmail

'''Server Details'''

'''Global IP''' : 182.73.42.26, eth1 port

'''Gateway''' : 182.73.42.25

'''Webmail''' : arihant.arihantelectricals.com

'''There are two catchual acconts:'''

1.ajain@arihantelectricals.com

2.catch_arihant@arihantelectricals.com

Mails are being received by catchual account and then distributed locally.

Category:Tetra Clients/Arihant Arhitecture

2012-12-21T10:53:34Z

Deepak: Blanked the page

Category:Tetra Clients/Arihant Arhitecture

2012-12-21T10:52:40Z

Deepak: Arihant Electricals Architecture

Category:Tetra Local/How to up 192.168.1.11

2012-12-21T04:45:28Z

Deepak: Steps to up the server 192.168.1.11

'''Steps to up the server 192.168.1.11'''

----

1.First make sure that power for 192.168.1.10 is on.

2.If power is off then start 192.168.1.10.

3.ping 192.168.1.10 - to ensure that 192.168.1.10 is up.

4.Login to 192.168.1.10 with “ssh root@192.168.1.10 -v”

5.xm list - it will show the list of servers which are up

6.xm create tetra - it will create tetra(192.168.1.11) in xm list which will up the server tetra(192.168.1.11)

7.xm restore tetra - it will refresh the xm list

8.xm list - it will show the list of servers which are up and now we will see 192.168.1.11(tetra)

9.ping 192.168.1.11 - to confirm that 192.168.1.11 is up

Test Process In Bank Of Tokyo

2012-12-20T11:53:26Z

Deepak: Testing process done in Bank Of Tokyo

'''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.in
2.Testing Server with IP 150.25.2.41 with t .bk.mufg.in

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

Test Process In Bank Of Tokyo

2012-12-20T11:47:32Z

Deepak: Testing process done in Bank Of Tokyo

'''Test Process In Bank Of Tokyo

There are in total 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.in
2.Testing Server with IP 150.25.2.41 with t .bk.mufg.in

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

Test Process In Bank Of Tokyo

2012-12-20T11:46:52Z

Deepak: Testing process done in Bank Of Tokyo

'''Test Process In Bank Of Tokyo

There are in total 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.in
2.Testing Server with IP 150.25.2.41 with t .bk.mufg.in

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