Track messages sent and received by a user zimbra

Mencari email history di zimba adalah sebagai berikut.

Penerima (-r = Recipient address)
#/opt/zimbra/libexec/zmmsgtrace -r penerima@email.com /var/log/maillog-20161226

Pengirim (-s = Sender address)
#/opt/zimbra/libexec/zmmsgtrace -s pegirim@email.com /var/log/maillog-20161226

menggunakan file gz

/opt/zimbra/libexec/zmmsgtrace -s pegirim@email.com zimbra.log-20170113.gz

-h (help)

regards

file new failed nt_status_unsuccessful status unsuccessful samba

file_new failed: NT_STATUS_UNSUCCESSFUL
file new failed nt_status_unsuccessful status unsuccessful samba

salah-satu error di samba FC 24,  jika di cek menggunakan maka terlihat spt dibawah ini bahwa yg di cetak tebal sudah 100%

[root@pdc2 ~]# df -i

Filesystem                 Inodes  IUsed     IFree IUse% Mounted on

devtmpfs                  1003748    494   1003254    1% /dev

tmpfs                     1006507     13   1006494    1% /dev/shm

tmpfs                     1006507    736   1005771    1% /run

tmpfs                     1006507     16   1006491    1% /sys/fs/cgroup

/dev/mapper/fedora-root    655360 215569    439791   100% /

tmpfs                     1006507     30   1006477    1% /tmp

/dev/sda1                  128016    430    127586    1% /boot

/dev/mapper/fedora-home 120905728  41359 120864369    1% /home

tmpfs                     1006507     19   1006488    1% /run/user/42

tmpfs                     1006507     20   1006487    1% /run/user/1000

dan yang harus dilakukan adalah menghilangkan agar bisa berkurang di folder /var/log/journal , menghapus isi dari folder tersebut.

/dev/mapper/fedora-root    655360 215569    439791   33% /

Zimbra reports “ Error: Queue report unavailable – mail system is down ”

zcs @ zimbra: ~ $ zmcontrol status
Host zcs.ilba.cat
        antispam                Running
        antivirus               Running
        convertd                Running
        ldap                    Running
        LOGGER Running
        mailbox                 Running
        mta                     Running
        opendkim                Running
        proxy                   Running
        snmp                    Running
        spell                   Running
        stats                   Running
        zmconfigd               Running
zimbra@zcs:~$ tail -f /var/log/mail.log
Jan 22 11:08:00 zcs postfix/postqueue[19195]: fatal: Queue report unavailable - mail system is down
root@zcs:~# locate master.pid
/opt/zimbra/data/postfix/spool/pid/master.pid

zcs root @: ~ # mv master.pid master.pid.bak.21des2016

root@zcs:~# su - zimbra
Zimbra ZCS @: ~ $ / opt / Zimbra / bin / zmmtactl start
Rewriting configuration files...done.
Starting saslauthd...already running.
/postfix-script: starting the Postfix mail system

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.