[SOLVED] Relaying Disaster...please HELP!

[timothyalangorman]

I tried to run
./zmprov to allow relayin from another IP set...

now all incoming mail is held in defered.
How do I figure out wha the issue is>?

I restored relaying to the original ip set only with

./zmprov modifyServer cpe.cortpump.com zimbraMtaMyNetworks '127.0.0.0/8 208.243.90.0/24'

Please Help

[jholder]

try to flush the queue
postconf -f

Also, did you follow these instructions?
Outgoing Mail Problems - ZimbraWiki

[timothyalangorman]

I reviewed the link at it seems that I've done the correct thing....

./postconf -f


returns


/opt/zimbra/postfix-2.2.9/sbin/postconf: invalid option -- f
/opt/zimbra/postfix-2.2.9/sbin/postconf: fatal: usage: /opt/zimbra/postfix-2.2.9/sbin/postconf [-c config_dir] [-d (defaults)] [-e (edit)] [-h (no names)] [-l (lock types)] [-m (map types)] [-n (non-defaults)] [-v] [name...]


Any other ideas?


heres the error I get when I hover the deferred messages...

[timothyalangorman]

It looks like theres something to do with the clamav scanner?

[timothyalangorman]

root@cpe:/opt/zimbra/postfix-2.2.9/sbin# ./postconf mynetworks


returns this


mynetworks = 127.0.0.0/8 208.243.90.0/24

[jholder]

Yeah, looks like you an is down. We've seen this and its a pretty big bug in clamav.

To fix, you can
su - zimbra
mkdir /tmp/clamdb
mv /opt/zimbra/clamav/db/* /tmp/clamdb
zmprov ms `zmhostname` +zimbraServiceEnabled antivirus
/opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf
zmamavisctl stop
zmamavisctl start

[timothyalangorman]

Got through the backup and when command below was issued I got an error...




zimbra@cpe:~/bin$ /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf

ERROR: Problem with internal logger (UpdateLogFile = /opt/zimbra/log/freshclam.log).

reading that freshclam.log now....

[timothyalangorman]

ily.cvd updated (version: 4107, sigs: 16433, f-level: 21, builder: ccordes)
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Current functionality level = 15, recommended = 21
DON'T PANIC! Read Clam AntiVirus
Database updated (149596 signatures) from db.us.clamav.net (IP: 129.64.99.170)
WARNING: Clamd was NOT notified: Can't connect to clamd on 127.0.0.1:3310


Looks like I still have an issue...can I go on without clamav?

[jholder]

I'd stop zimbra altogether, and wipe the clamav dir /opt/zimbra/clamav.xxx (newest ver)
then rerun the installer with the -s option.
./install.sh -s

You can also turn off clam in the admin console, but you will be vulnerable to viruses.

[timothyalangorman]

This post below Resolved the issue....

[SOLVED] Clamav problem ? What's happening ?


+++++++++++++++++++++++++++++++++++++++++++++
Originally Posted by aNt1X View Post
Ok, i solved modifying the watchdog interval in /opt/zimbra/libexec/zmmtaconfig

[code]
my %config = (
progname => "zmmtaconfig",
hostname => $ENV{zimbra_server_hostname},
loglevel => 3,
watchdog => 1,
wd_all => 0,
debug => 0,
interval => 180,
baseDir => "/opt/zimbra",
logStatus => ( 4 => "Debug", 3 => "Info", 2 => "Warning", 1 => "Error", 0 =$
);[code]

(i extended the interval value from 60 to 180).

I was going crazy looking at crontabs, but this watchdog process wasn't in the crontab, but in this perl script

I hope it will not break something else ...

Thank you anyway.

aNt1X
++++++++++++++++++++++++++++++++++++++++