TetraWiki - User contributions [en]

Tuning Kloxo space Issue

2017-06-19T09:15:07Z

Prashantkumar:

[[category:KLOXO]]
[[category:Jacob Ballas]]

==objective==

== '''Tuning Kloxo space Issue'''==

SCENARIO:
On kloxo server, disk space was reach to 95% due to which critical client hosted on this server could be hampered from recieving mails any point of time.

RESOLUTION:
On analyzing kloxo server through df -h and command ‘du -sh /home/lxadmin/mail/domains’ found “rtdc.in” directory to be consuming most space and hece below steps were performed.
Steps:
# cd /home/lxadmin/mail/domains/rtdc.in/

[ensure that below file is made of current date else all mails will fail to work for this domain ]
# touch .qmail-default

[ensure only to remove files older than 1 year ]
# find . -mtime +365 -exec rm {} \;

Tuning Kloxo space Issue

2017-06-19T09:10:39Z

Prashantkumar: Created page with "category:KLOXO category:Jacob Ballas ==objective== Tuning Kloxo space Issue SCENARIO: On kloxo server, disk space was reach to 95% due to which critical client host..."

[[category:KLOXO]]
[[category:Jacob Ballas]]

==objective==
Tuning Kloxo space Issue

SCENARIO:
On kloxo server, disk space was reach to 95% due to which critical client hosted on this server could be hampered from recieving mails any point of time.

RESOLUTION:
On analyzing kloxo server through df -h and command ‘du -sh /home/lxadmin/mail/domains’ found “rtdc.in” directory to be consuming most space and hece below steps were performed.
Steps:
# cd /home/lxadmin/mail/domains/rtdc.in/

[ensure that below file is made of current date else all mails will fail to work for this domain ]
# touch .qmail-default

[ensure only to remove files older than 1 year ]
# find . -mtime +365 -exec rm {} \;

Qmail restore at NIIT

2017-06-17T13:30:50Z

Prashantkumar:

[[category:NIIT- CCTNS LUCKNOW‏‎]]

= Objective =

Qmail and Ldap beckup restore on NIIT

1 Stop Qmail serive.
qmailctl stop

2. Copy backup of qmail and ldap to the server where we want to restore.

3. move the current vmail file to new org_17062017. And put backup vmail file to /home.

4. Give vmail permission to vmail.
chown -r vmail:vmail /home/vmail

5. start qmail servie.
qmailctl Start

6. Stop Ldap servie
/etc/init.d/ldap stop

7. delete old ldap file.
rm -rf /var/lib/ldap/*

8. Put ldap backup to /var/lib/ldap/

9. Give Ldap permission to /var/lib/ldap.
chown -r Ldap:Ldap /var/lib/Ldap

10. change memory size in /etc/php.ini from 125 to 256MB
vi /etc/php.ini

memory_limit = 256M ; Maximum amount of memory a script may consume

11. start ldap service
/etc/init.d/ldap start

12. Restart httpd service.
/etc/ini.d/httpd restart

Qmail restore at NIIT

2017-06-17T13:28:34Z

Prashantkumar:

[[category:NIIT- CCTNS LUCKNOW‏‎]]

= Objective =

Qmail and Ldap beckup restore on NIIT

1 Stop Qmail serive.
Qmailctl stop

2. Copy backup of qmail and ldap to the server where we want to restore.

3. move the current vmail file to new org_17062017. And put backup vmail file to /home.

4. Give vmail permission to vmail.
Chown -r vmail:vmail /home/vmail

5. start qmail servie.

qmailctl Start

6. Stop Ldap servie
/etc/init.d/ldap stop

7. delete old ldap file.
rm -rf /var/lib/ldap/*

8. Put ldap backup to /var/lib/ldap/

9. Give Ldap permission to /var/lib/ldap.
chown -r Ldap:Ldap /var/lib/Ldap

10. change memory size in /etc/php.ini from 125 to 256MB
vi /etc/php.ini

memory_limit = 256M ; Maximum amount of memory a script may consume

11. start ldap service
/etc/init.d/ldap start

12. Restart httpd service.
/etc/ini.d/httpd restart

Qmail restore at NIIT

2017-06-17T13:16:39Z

Prashantkumar: Created page with "category:NIIT-Tobacco Board Project‏‎ = Objective = Qmail and Ldap beckup restore on NIIT 1 Stop Qmail serive. Qmailctl stop 2. Copy backup of qmai..."

[[category:NIIT-Tobacco Board Project‏‎]]

= Objective =

Qmail and Ldap beckup restore on NIIT

1 Stop Qmail serive.
Qmailctl stop

2. Copy backup of qmail and ldap to the server where we want to restore.

3. move the current vmail file to new org_17062017. And put backup vmail file to /home.

4. Give vmail permission to vmail.
Chown -r vmail:vmail /home/vmail

5. start qmail servie.

qmailctl Start

6. Stop Ldap servie
/etc/init.d/ldap stop

7. delete old ldap file.
rm -rf /var/lib/ldap/*

8. Put ldap backup to /var/lib/ldap/

9. Give Ldap permission to /var/lib/ldap.
chown -r Ldap:Ldap /var/lib/Ldap

10. change memory size in /etc/php.ini from 125 to 256MB
vi /etc/php.ini

memory_limit = 256M ; Maximum amount of memory a script may consume

11. start ldap service
/etc/init.d/ldap start

12. Restart httpd service.
/etc/ini.d/httpd restart

File:Pic2.jpg

2017-06-14T12:19:18Z

Prashantkumar:

File:Pic1.jpg

2017-06-14T12:17:11Z

Prashantkumar:

Jbindia mail fetching

2017-06-13T11:19:30Z

Prashantkumar:

[[category:KLOXO]]
[[category:Jacob Ballas‏‎]]

==objective==
JBINDIA mail feching

Solution to restart the pop service/ Courier service
SCENARIO:
Client = jbindia is unable to fetch mails from kloxo server.

RESOLUTION:

1. Log-in to :
http://mail.jbindia.co.in:7778/

2. select Services in "Server:Linux" table. As highlighted below:

[[File:pic1.jpg|300px]]

click 3rd blue button to restart the courier pop3/imap service. As highlighted below:

[[File:pic2.jpg|300px]]

Jbindia mail fetching

2017-06-13T07:57:42Z

Prashantkumar: Created page with " category:KLOXO category:Jacob Ballas‏‎ ==objective== JBINDIA mail feching Solution to restart the pop service/ Courier service SCENARIO: Client = jbindia is un..."

[[category:KLOXO]]
[[category:Jacob Ballas‏‎]]

==objective==
JBINDIA mail feching

Solution to restart the pop service/ Courier service
SCENARIO:
Client = jbindia is unable to fetch mails from kloxo server.

RESOLUTION:

1. Log-in to :
http://mail.jbindia.co.in:7778/

2. select Services in "Server:Linux" table. As highlighted below:

[[File:pic1.jpg]]

click 3rd blue button to restart the courier pop3/imap service. As highlighted below:

[[File:pic2.jpg]]

Jbindia mail fatching

2017-06-13T07:46:29Z

Prashantkumar:

[[category:Jacob Ballas‏‎]]

==objective==
jbindia mail fatching from kloxo

Solution to restart the pop service/ Courier service
SCENARIO:
Client = jbindia is unable to fetch mails from kloxo server.

RESOLUTION:

1. Log-in to :
http://mail.jbindia.co.in:7778/

2. select Services in "Server:Linux" table. As highlighted below:

[[File:pic1.jpg]]

click 3rd blue button to restart the courier pop3/imap service. As highlighted below:

[[File:pic2.jpg]]

Jbindia mail fatching

2017-06-13T07:42:49Z

Prashantkumar:

[[category:Jacob Ballas‏‎]]

==objective==
jbindia mail fatching from kloxo

Solution to restart the pop service/ Courier service
SCENARIO:
Client = jbindia is unable to fetch mails from kloxo server.

RESOLUTION:

1. Log-in to :
http://mail.jbindia.co.in:7778/

2. select Services in "Server:Linux" table. As highlighted below:

/home/tetra/Desktop/pic1.jpg

click 3rd blue button to restart the courier pop3/imap service. As highlighted below:
/home/tetra/Desktop/pic2.jpg

Jbindia mail fatching

2017-06-13T07:33:06Z

Prashantkumar: Created page with "category:Jacob Ballas‏‎ ==objective== jbindia mail fatching from kloxo Solution to restart the pop service/ Courier service SCENARIO: Client = jbindia is unable to ..."

[[category:Jacob Ballas‏‎]]

==objective==
jbindia mail fatching from kloxo

Solution to restart the pop service/ Courier service
SCENARIO:
Client = jbindia is unable to fetch mails from kloxo server.

RESOLUTION:

1. Log-in to :
http://mail.jbindia.co.in:7778/

2. select Services in "Server:Linux" table. As highlighted below:

[[File:Example.jpg]]

click 3rd blue button to restart the courier pop3/imap service. As highlighted below:

[[File:Example.jpg]]

Allow blocked compressed format extensions for all users in zimbra

2017-05-15T10:02:08Z

Prashantkumar: Created page with "category:NEWSNATIONS ==Objective== Allow blocked compressed format extensions for all users in zimbra for Newsnation 1. First log in to the zimbra admin penal and go to..."

[[category:NEWSNATIONS]]

==Objective==
Allow blocked compressed format extensions for all users in zimbra for Newsnation

1. First log in to the zimbra admin penal and go to the globel setting then in Attachments option And check in the right side Box which Show “urrently blocked extensions by MTA”.

2. If there is showing extesion list then select zip, rar, 7zip and remove them. And then save the changes.

3. If the “Currently blocked extensions by MTA” is empty then login to the IP 115.112.117.163 and then login to zimbra server.

4. now open the given file
vi /opt/zimbra/postfix/conf/main.cf

in this file go to the last line in which you will find the following line
mime_header_checks = regexp:/opt/zimbra/conf/mime_header_checks

5. Now copy the file and open it.
Vim /opt/zimbra/conf/mime_header_checks

6. Now delete the extensions name like zip, rar, 7zip. And arrange the remaining with the same format as before.

7. After saving this file restart postfix service.

File:Allow blocked compressed format extensions for all users in zimbra

2017-05-15T09:36:42Z

Prashantkumar: Created page with "category:NEWSNATION ==Objective== Allow blocked compressed format extensions for all users in zimbra for Newsnation 1. First log in to the zimbra admin penal and go to..."

[[category:NEWSNATION]]

==Objective==
Allow blocked compressed format extensions for all users in zimbra for Newsnation

1. First log in to the zimbra admin penal and go to the globel setting then in Attachments option And check in the right side Box which Show “urrently blocked extensions by MTA”.

2. If there is showing extesion list then select zip, rar, 7zip and remove them. And then save the changes.

3. If the “Currently blocked extensions by MTA” is empty then login to the IP 115.112.117.163 and then login to zimbra server.

4. now open the given file
vi /opt/zimbra/postfix/conf/main.cf

in this file go to the last line in which you will find the following line
mime_header_checks = regexp:/opt/zimbra/conf/mime_header_checks

5. Now copy the file and open it.
Vim /opt/zimbra/conf/mime_header_checks

6. Now delete the extensions name like zip, rar, 7zip. And arrange the remaining with the same format as before.

7. After saving this file restart postfix service.

Reduce mail disk space in supportwwfindia

2017-04-19T05:39:32Z

Prashantkumar: Created page with "category:SUPPORTWWFINDIA category:KLOXO ==Objective== The Account supportwwfindia is using 101% of quota for maildisk_usage. 1) First login to the kloxo server usin..."

[[category:SUPPORTWWFINDIA]]
[[category:KLOXO]]

==Objective==
The Account supportwwfindia is using 101% of quota for maildisk_usage.

1) First login to the kloxo server using login sheet

2) switch to root user

3) Go to the domail list using bilow command:-

cd /home/lxadmin/mail/domain/

4) Change timestamp of .qmail-default file using touch command below:-

touch .qmail-default ( so that it should not get deleted )

5) just keep 6 months mail and delete old mails using below command:-

find . -mtime +180 -exec rm {} \;

File:Applying global IP to tetra local IP.odt

2017-03-23T06:26:10Z

Prashantkumar:

How to Implement Sender or Moderator Restricted Groups on Qmail-LDAP environment

2017-03-15T13:17:47Z

Prashantkumar:

[[category:Qmail]]

'''How to Implement Sender or Moderator Restricted Groups on Qmail-LDAP environment'''

==Contents==

= Sender Restricted Groups =
When a Sender send a mail to the group , the Qmail see whether the sender is allowed to send the mail or not . Also Sends back a mail to the sender , for him to reply and release the mail to the group members .

Please have following example of Sender Restricted group implemented in LDAP

<nowiki># testgroup@krishnamaruti.com, groups, krishnamaruti.com </nowiki>
dn: uid=testgroup@krishnamaruti.com,ou=groups,dc=krishnamaruti,dc=com
mailMessageStore: krishnamaruti.com/testgroup
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: qmailUser
'''objectClass: qmailGroup '''
'''senderconfirm: TRUE'''
'''membersonly: TRUE'''
sn: GROUP-K
uid: testgroup@krishnamaruti.com
userPassword:: e01ENX1YMDNNTzFxblpkWWRneWZldUlMUG1RPT0=
cn: GROUP-K
deliveryMode: noLocal
givenName: KMLGRPOUP
'''mailAlternateAddress: testgroup-catchall@krishnamaruti.com '''
mail: testgroup@krishnamaruti.com
'''rfc822sender: '''biswajit@tetrain.com
'''rfc822member: '''[mailto:biswajit@tetrain.com biswajit@tetrain.com]

Please note

* '''objectClass: qmailGroup''' is mandatory
* '''mailAlternateAddress''' – A catch all type of address needs to be created as shown in example
* The Restricted Sender is defined a email address by '''rfc822sender . '''The sender can belong to any domain . You can also define '''dnsender'''
* Group Members are defined by 2 ways
** '''rfc822member , '''where any email address can come''' .'''
** '''dnmember , '''where you can define any distinquish names (dn) of this LDAP . For ex . dn: [mailto:uid%3Dtetra@krishnamaruti.com uid=tetra@krishnamaruti.com],dc=krishnamaruti,dc=com
* To Ensure that the mails generated by the sender are authentic in nature , '''senderconfirm: TRUE '''is specified . An return mail to the same ID will be generated by Qmail ( Qmail-secetary ) and the sender has to reply this mail to release the sent mail to Group .

= Moderator Restricted Groups =

When a Sender send a mail to the group , the Qmail sends a mail to the defined moderators for approval . When Moderator replies , then Qmail releases the mail to the group members .

Please have following example of Modrator Restricted group implemented in LDAP

<nowiki># group_1, tetrain.com, tetrain.com </nowiki>
dn: uid=group_1,ou=tetrain.com,dc=tetrain,dc=com
objectClass: top
objectClass: qmailUser
'''objectClass: qmailGroup'''
objectClass: inetOrgPerson
sn: group_1
cn: group_1
uid: group_1
mailMessageStore: tetrain.com/group_1
mail: group_1@tetrain.com
'''mailAlternateAddress: group_1-catchall@tetrain.com'''
'''dnmoderator:''' uid=biswajit,ou=tetrain.com,dc=tetrain,dc=com
'''confirmtext: '''Do you really want to post to this group,R U Sure ?
'''moderatortext:''' Hello, hello!? Shall we proceed and send this out?
dnmember: uid=biswajit,ou=tetrain.com,dc=tetrain,dc=com
rfc822member: [mailto:biswajit_gmail@gmail.com biswajit_gmail@gmail.com]

Please note

* '''objectClass: qmailGroup''' is mandatory
* '''mailAlternateAddress''' – A catch all type of address needs to be created as shown in example
* The Modrator is defined by '''dnmoderator '''for ex.''' '''uid=biswajit,ou=tetrain.com,dc=tetrain,dc=com ( The distinguish name in LDAP)''' . '''You can also define '''rfc822moderator''' , which can be any email address belonging to any domain .
* To Ensure that the mails generated by the sender are moderated , '''confirmtext: '''and''' moderatortext '''is specified . An mail to the moderator's ID will be generated by Qmail ( Qmail-secetary ) and the any of the moderator has to reply this mail to release the sent mail to Group .

== Allow full domain to send mail other restricted ==
Add an attribute like
filtersender: (mail=*@sceh.net)

This will allow all the populated address in the ldap having <anyuser>@sceh.net to send the mail to this list and will not allow any other domain to send mail to this list .

= Referance =
* QLDAPGROUP file in Qmail Source after Qmail-LDAP patch Applied [[File:QLDAPGROUP.txt]]

I Hope it is clear . Please get back @ [mailto:biswajit@tetrain.com biswajit@tetrain.com] for clarification

File:Reports was not displaying on Beetal.odt

2017-02-12T09:27:39Z

Prashantkumar: /* objective */

==Objective==
Reports was not displaying on Beetal

For this we had restarted the tomcat server.

1.login to tetraadmin user.

2.Switch to tomocat user “rep6545”
su -rep6545

3.Execute the command
cd tomcat4/bin/

4.Command to stop tomcat server
./shutdown.sh

5.Command to start the tomcat server
./startup.sh

Note:report server log path is-

/home/rep6545/tomcat4/log/CCreport.log

6.Execute the command
cd tomcat4/bin/*

7.Execute the command
cd tomcat4/bin/

File:Reports was not displaying on Beetal.odt

2017-02-12T09:13:10Z

Prashantkumar:

File:Allow blocked compressed format extensions for all users in zimbra 1.odt

2017-02-12T08:52:45Z

Prashantkumar: /* objective */

==Objective==
Allow blocked compressed format extensions for all users in zimbra for Newsnation

1. First log in to the zimbra admin penal and go to the globel setting then in Attachments option And check in the right side Box which Show “urrently blocked extensions by MTA”.

2. If there is showing extesion list then select zip, rar, 7zip and remove them. And then save the changes.

3. If the “Currently blocked extensions by MTA” is empty then login to the IP 115.112.117.163 and then login to zimbra server.

4. now open the given file
vi /opt/zimbra/postfix/conf/main.cf

in this file go to the last line in which you will find the following line
mime_header_checks = regexp:/opt/zimbra/conf/mime_header_checks

5. Now copy the file and open it.
Vim /opt/zimbra/conf/mime_header_checks

6. Now delete the extensions name like zip, rar, 7zip. And arrange the remaining with the same format as before.

7. After saving this file restart postfix service.

File:Allow blocked compressed format extensions for all users in zimbra 1.odt

2017-02-12T08:45:25Z

Prashantkumar:

File:Manual-process-triburg-archive-population.odt

2017-02-12T08:07:35Z

Prashantkumar: /* objective */

==Objective==
Process for manually activating the archive users on Triburg Zimbra mail archive server

As the automated script is failing due to the fact , Triburg’s Admin people ( Ramesh ) delete some accounts from the archiving Server , we have to adopt following Manual process .

Prerequisite from Triburg’s Team
Accounts created recently and not able to get mails on the said accounts

Process to follow

1. Main Mail Server – mail.triburg.co.in , 124.30.5.188 (Local IP 172.16.1.6).

2. Archive Server – archive2.triburg.co.in ( 172.16.1.19 ).

3. Login to archive server after login via mail.triburg.co.in ( key based , password less authentication).

4. confirm the existence of given users via
zmprov -l gaa | grep -i <said_user>
(as zimbra users and use only the name and not the full address as full address will be said_user@archive2@triburg.co.in).

5. if all users exists then Proceed to next step , else create user on archive server by zimbra cli as
user@archive2.triburg.co.in .

6. Once confirmed that all given users are created on then add the users in the given file as same as other users are added-
vim /opt/zimbra/postfix/conf/archivelist

7. after adding the user postmap the file
postmap /opt/zimbra/postfix/conf/archivelist

File:Manual-process-triburg-archive-population.odt

2017-02-12T07:51:33Z

Prashantkumar:

File:Bypassed the user from mail sending quota.odt

2017-02-11T11:41:59Z

Prashantkumar: /* objective */

==objective==
Bypass the user from mail sending quota in sheelaform

1.- Open the web page using the given url-

http://mail.sheelafoam.com:7780/webui/policy-main.php

2.- Now click on the main option given in left side in the policies.

3.- Select the 5th option "Rate limit sending message" then select action to members

4.- Now select both option one bye one and select action to change.

5. Now copy paste Source to the left side line to right side and add user name in the last in the same format and also copy paste the destination and select no to disabled.

File:Bypassed the user from mail sending quota.odt

2017-02-11T11:31:04Z

Prashantkumar: Bypassed the user from mail sending quota

Bypass the user from mail sending quota in sheelaform

1.- Open the web page using the given url-

http://mail.sheelafoam.com:7780/webui/policy-main.php

2.- Now click on the main option given in left side in the policies.

3.- Select the 5th option "Rate limit sending message" then select action to members

4.- Now select both option one bye one and select action to change.

5. Now copy paste Source to the left side line to right side and add user name in the last in the same format and also copy paste the destination and select no to disabled.

File:Bypassed the user from mail sending quota.odt

2017-02-11T08:07:04Z

Prashantkumar: Bypasse the user from mail sending quota in sheelaform

Bypasse the user from mail sending quota in sheelaform

1.- Open the web page using the given url-

http://mail.sheelafoam.com:7780/webui/policy-main.php

2.- Now click on the main option given in left side in the policies.

3.- Select the 5th option "Rate limit sending message" then select action to members

4.- Now select both option one bye one and select action to change.

5. Now copy paste Source to the left side line to right side and add user name in the last in the same formate. and also copy paste the destination and select no to disabled.

File:Bypassed the user from mail sending quota.odt

2017-02-11T07:59:28Z

Prashantkumar:

Rejecting false "mail from" addresses

2017-02-10T10:11:17Z

Prashantkumar: Editing Rejecting false "mail from" addresses

Rejecting false "mail from" addresses
1.-Zimbra Collaboration 8.5 and above
Please use the next commands to increase the security and reject the logins for users that doesn't exist in the LDAP:
zmprov mcf zimbraMtaSmtpdRejectUnlistedRecipient yes
zmprov mcf zimbraMtaSmtpdRejectUnlistedSender yes
zmmtactl restart
zmconfigdctl restart

2.- For Zimbra Collaboration 8.0.x and previous
Open the file /opt/zimbra/conf/zmconfigd/smtpd_sender_restrictions.cf and add this line into the middle of the file, prior to the tag_as_foreign.re lines: Add this:
check_sender_access hash:/opt/zimbra/conf/domainrestrict

It should look like this..
check_sender_access hash:/opt/zimbra/conf/domainrestrict
%%contains VAR:zimbraServiceEnabled antivirus^ check_sender_access regexp:/opt/zimbra/postfix/conf/tag_as_foreign.re%%

3. Zimbra Collaboration 7.x
You should follow the next steps:
su - zimbra
zmlocalconfig -e postfix_smtpd_sender_restrictions="reject_unknown_sender_domain, permit_mynetworks, permit_sasl_authenticated, check_sender_access hash:/opt/zimbra/conf/domainrestrict, permit"

4.-Remaining steps are same for ZCS 8.0.x and previous versions
i.-Create the file "/opt/zimbra/conf/domainrestrict" and add your domain(s) to it.

localdomain.com REJECT
anotherlocaldomain.com REJECT
ii.- Create the hash database of "/opt/zimbra/conf/domainrestrict". Run as 'zimbra' user.
postmap /opt/zimbra/conf/domainrestrict
iii.- Restart zmmtactl.
zmmtactl stop
zmmtactl start

5.- Testing

i.- Make following connection from a non-local host which is not part of mynetworks.
telnet ZCS_server_address 25
mail from: user@localdomain.com
rcpt to: user2@localdomain.com

ii.- You should get following error at the rcpt command if you used the Zimbra Collaboration 8.6 steps:
550 5.1.0 <hi@example.com>: Sender address rejected: example.com
iii.- You should get following error at the rcpt command
554 5.7.1 <user@localdomain.com>: Sender address rejected: You're not me!

File:Rejecting false "mail from" addresses.odt

2017-02-09T14:45:32Z

Prashantkumar: