fatal: Queue report unavailable – mail system is down

[root@webmail ~]# tail -f /var/log/maillog
Oct 13 16:24:57 webmail amavis-services[14204]: amavis-services-2.9.0 (20140506) task ‘msg-forwarder’ [14204] started. ZMQ::LibZMQ3 1.13, lib 3.2.3
Oct 13 16:24:57 webmail amavis-services[14205]: amavis-services-2.9.0 (20140506) task ‘childproc-minder’ [14205] started. ZMQ::LibZMQ3 1.13, lib 3.2.3
Oct 13 16:24:57 webmail amavis-services[14206]: amavis-services-2.9.0 (20140506) task ‘snmp-responder’ [14206] started. ZMQ::LibZMQ3 1.13, lib 3.2.3
Oct 13 16:24:58 webmail amavis-services[14205]: childproc_minder: FLUSH process states
Oct 13 16:25:00 webmail postfix/postqueue[14314]: fatal: Queue report unavailable – mail system is down
Oct 13 16:25:05 webmail amavis-services[14206]: snmp_responder: FLUSH snmp data
Oct 13 16:25:05 webmail amavis-services[14205]: childproc_minder: FLUSH process states
Oct 13 16:25:30 webmail postfix/postqueue[15496]: fatal: Queue report unavailable – mail system is down
Oct 13 16:26:00 webmail postfix/postqueue[15622]: fatal: Queue report unavailable – mail system is down
Oct 13 16:26:30 webmail postfix/postqueue[17160]: fatal: Queue report unavailable – mail system is down
Oct 13 16:27:00 webmail postfix/postqueue[17226]: fatal: Queue report unavailable – mail system is down

SOLUSI

[root@webmail /]# locate master.pid
/opt/zimbra/data/postfix/spool/pid/master.pid
[root@webmail /]# cd /opt/zimbra/data/postfix/spool/pid/

[root@webmail pid]# cp master.pid master.pid.bak

[root@webmail pid]# rm -Rf master.pid

[root@webmail pid]# su – zimbra
Last login: Thu Oct 13 16:24:45 WIB 2016 on pts/0
[zimbra@webmail ~]$ zmmtactl start
Rewriting configuration files…done.
Starting saslauthd…already running.
/postfix-script: starting the Postfix mail system
[zimbra@webmail ~]$

 

Specific Whitelist/Blacklist per IP

https://wiki.zimbra.com/wiki/Specific_Whitelist/Blacklist_per_IP

 

Purpose

With ZCS 8.5 and later, it is possible to maintain an IP blacklist for connections to Postfix. This is useful in DoS and targeted spam attack scenarios.

Many clients use RBLs to block spammers from flooding their MTAs with spam. Unfortunately, perfectly valid sites occasionally end up on these lists. With ZCS 8.5 and later, it is possible to create an on-disk database map that allows the client to whitelist specific blacklisted IPs so that emails from those IPs still get delivered.

Resolution

Whitelist Edit /opt/zimbra/conf/postfix_rbl_override. Add IP address(es) SPACE OK to the file, one IP address per line:

1.2.3.4 OK

Run the postmap to save and apply the changes in Postfix:

postmap /opt/zimbra/conf/postfix_rbl_override

Run the zmprov to apply the changes to the Zimbra Collaboration Server:

zmprov mcf +zimbraMtaRestriction 'check_client_access lmdb:/opt/zimbra/conf/postfix_rbl_override'

postmap will need to be rerun on the file any time an IP address is added or removed.

Blacklist Edit /opt/zimbra/conf/postfix_blacklist. Add IP address SPACE REJECT to the file, one IP address per line:

1.2.3.4 REJECT

Run the postmap to save and apply the changes in Postfix:

postmap /opt/zimbra/conf/postfix_blacklist

Run the zmprov to apply the changes to the Zimbra Collaboration Server:

zmprov mcf +zimbraMtaRestriction 'check_client_access lmdb:/opt/zimbra/conf/postfix_blacklist'

postmap will need to be rerun on the file anytime an IP address is added or removed.

Whitelists and Blacklists on Zimbra

  1. Buka file [root@webmail /]# vim /opt/zimbra/conf/amavisd.conf.in
  2. Cari bagian seperti berikut ini “soft-blacklisting” :
    yang tampak seperti dibawah ini
    # soft-blacklisting (positive score)
    ‘sender@example.net’ => 3.0,
    ‘.example.net’ => 1.0,
    ‘admin@buzzup.net’ => 15.0,

    berikan score 15, jika masih tembus juga score naik menjadi 20, save dan keluar dan editor

  3. Restart service anti virus dan anti spam dengan perintah :
    su – zimbra
    zmamavisdctl stop && zmamavisdctl start

VIRUS (Heuristics.Encrypted.PDF) Di Zimbra

Error pada email akan seperti ini
VIRUS (Heuristics.Encrypted.PDF) in mail TO YOU from

supaya ga di blok ikutin step di bawah : ( saya pake zimbra Release 8.6.0_GA_1153.RHEL7_64_20141215151110 RHEL7_64 FOSS edition, Patch 8.6.0_P4. yah )

1. buka zimbra admin https://mailserver:7071/zimbraAdmin/

2. Open Menu | Configure| Global Setting | AS/AV |

3. Uncek Block encrypted archives

4. jangan lupa settingan nya di save

sekarang coba anda mengirim pdf yang di password

semoga membantu

*source : zimbra forum & google.

Backup Database MYSQL

backup database mysql

Mengecek dulu isi database yang sudah terdaftar

# mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 782 to server version: 5.0.22

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.

mysql> show database;
+——————–+
| Database |
+——————–+
| information_schema |
| mysql |
| postfix |
| test |
+——————–+
4 rows in set (0.00 sec)
mysql>
mysql> exit
Bye

Selanjutnya keluar dari mysql dan lakukan command dibawah ini untuk melakukan backup database

#mysqldump -u root -p postfix > /home/backupdb-27082015/db-27082015.sql
Enter password:
#

selesai sudah, maka db-27082015.sql disimpan dalam folder /home/backupdb-27082015/

@fedora 20

menambahkan static routing

vim /etc/sysconfig/network-scripts/route-p6p1

10.10.0.0/16 via 10.10.1.253 dev p6p1

 

saat reboot maka lakukan perintah ini, dimasukan di crontab.

crontab -e

@reboot /usr/sbin/iptables -F

 

Can not chdir(/var/spool/clientmqueue/)

squid Error :
NOQUEUE: SYSERR(root): can not chdir(/var/spool/clientmqueue/): No such file or directory

when you debug
[root@localhost ~]# tail -f /var/log/maillog
May 29 10:09:01 proxy sendmail[13664]: NOQUEUE: SYSERR(root): can not chdir(/var/spool/clientmqueue/): No such file or directory
May 29 10:10:01 proxy sendmail[13688]: NOQUEUE: SYSERR(root): can not chdir(/var/spool/clientmqueue/): No such file or directory
May 29 10:11:05 proxy sendmail[13700]: NOQUEUE: SYSERR(root): can not chdir(/var/spool/clientmqueue/): No such file or directory

try this :

#pwd
/var/spool/squid
#ls -ltr
-rw-r—– 1 root squid 127790832 May 28 18:30 swap.state

#chmod 770 swap.state
#ls -ltr
-rwxrwx— 1 root squid 127790832 May 28 18:30 swap.state

# service squid restart
# tail -f /var/log/squid/access.log
10.10.7.119 – yusuf [29/May/2013:11:39:53 +0700] “CONNECT idesouvenir.com:443 HTTP/1.1” 200 6680 TCP_MISS:DIRECT

problem solved.