[SOLVED] Upgrade breaks destination for zmdailyreport

[dwmtractor]

I have had some headaches ever since an upgrade from 4.5.6 to 4.5.7 (now on .9) that have recently been fixed. At the same time as they started, I stopped getting my daily mail reports. I assumed--erroneously it now appears--that they were related. Now with a LOT of help I have my stats, logger and graphs working again, but I still am not getting the Daily Mail Report that goes to admin.

I went to the cli and checked my crontab; zmdailyreport is scheduled to run nightly at 1:10 am. However if I try to run it from the command line I get the following error:

zimbra@mail:~/libexec$ . zmdailyreport -m
-su: use: command not found
-su: no: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: use: command not found
-su: zmdailyreport: line 30: syntax error near unexpected token `('
-su: zmdailyreport: line 30: `my %options = ();'

Not being a perl expert (heck, having no clue at all in perl ) I don't know what that syntax error might be. Can anyone help me?

Thanks

Dan

[jholder]

try running /opt/zimbra/libexec/zmdailyreport -m
instead.

[dwmtractor]

Originally Posted by jholder

try running /opt/zimbra/libexec/zmdailyreport -m
instead.

OK, when I put in the whole path it runs (well, it at least gives no errors). Confusing to me, because when I just cd to /opt/zimbra/libexec and then run zmdailyreport -m it doesn't. I thought those were equivalent??

But more importantly, though it must run (as in there is no error) I'm not getting a message. What log files should I be looking in to see what is/isn't happening?

[jholder]

because if you run it via ./ it uses the bash as the interpreter. Are there any errors in your logs

[dwmtractor]

Originally Posted by jholder

Are there any errors in your logs

Of course I should have thought of this myself; yes, there are. In /var/log/zimbra.log is the answer, though I am not sure what the solution is (domain obfuscated):

Oct 25 11:02:11 mail postfix/qmgr[12228]: 40CFC3D0BF2: removed
Oct 25 11:02:11 mail postfix/smtp[28889]: 101093D0BF3: to=<admin@mail.mydomain.n
et>, relay=none, delay=0, status=bounced (mail for mail.mydomain.net loops back
to myself)
Oct 25 11:02:11 mail postfix/cleanup[28884]: 37ABC3D0BF4: message-id=<20071025180211.
37ABC3D0BF4@mail.mydomain.net>
Oct 25 11:02:11 mail postfix/qmgr[12228]: 37ABC3D0BF4: from=<>, size=6461, nrcpt=1 (q
ueue active)
Oct 25 11:02:11 mail postfix/qmgr[12228]: 101093D0BF3: removed
Oct 25 11:02:11 mail postfix/smtp[28889]: 37ABC3D0BF4: to=<zimbra@mail.mydomain.
net>, relay=none, delay=0, status=bounced (mail for mail.mydomain.net loops back
 to myself)
Oct 25 11:02:11 mail postfix/qmgr[12228]: 37ABC3D0BF4: removed

[jholder]

k, let's change that

zmlocalconfig -e smtp_destination=you@domain.com

[dwmtractor]

John,

It occurs to me that this may have started about the time you discovered I had not set up the FQDN properly (along with my bad syntax in the hosts file that was required to get .6 to install). Is there any chance that in changing the FQDN within Zimbra a setting got missed, that would lead to this issue?

[dwmtractor]

Originally Posted by jholder

k, let's change that

zmlocalconfig -e smtp_destination=you@domain.com

Yep. That did it. Thanks, and mark solved.

[NoN]

Hello,

I can confirm this bug. I had exactly the same problem after upgrading my zimbra installation 4.5.8 to 4.5.9_GA_1454.UBUNTU6. For some reason the upgrade process changed all my default users from:

smtp_destination=admin@domain.com
smtp_source=admin@domain.com
av_notify_user=admin@domain.com

to

smtp_destination=admin@FQDN-hostname
smtp_source=admin@FQDN-hostname
av_notify_user=admin@FQDN-hostname

Which ofcourse resulted in the same mailloop as mentioned above.

After changing these three parameters with zmlocalconfig -e PARAMETER it works again as intended.

Best regards,
Pontus

[dwmtractor]

Originally Posted by NoN

Hello,

I can confirm this bug. I had exactly the same problem after upgrading my zimbra installation 4.5.8 to 4.5.9_GA_1454.UBUNTU6. For some reason the upgrade process changed all my default users from:

smtp_destination=admin@domain.com
smtp_source=admin@domain.com
av_notify_user=admin@domain.com

to

smtp_destination=admin@FQDN-hostname
smtp_source=admin@FQDN-hostname
av_notify_user=admin@FQDN-hostname

Which ofcourse resulted in the same mailloop as mentioned above.

After changing these three parameters with zmlocalconfig -e PARAMETER it works again as intended.

Best regards,
Pontus

I just realized that this happened again when I upgraded from 4.5.9 to 4.5.10. Is this by design, that the system overwrites admin addresses? Is there a reason, for example, that I should maybe just create an alias admin@mail.mydomain.com (my fqdn) and point it to admin@mydomain.com which is what the address actually is? Or is this a legitimate cause to file a bug? Whatever it is, it's a pain!