[SOLVED] Not able to receive or send mail

[mmorse]

The 'possibilities' so far about the utility file:
-missing
-not covered in path
-invalid permissions

echo $PATH
which file
ls -la /usr/bin/file

[joeleo]

Hi All, thanks for the input... I will try some of the suggestions mentioned. But, question: Say that this file is missing or does not have the right permissions, would this prevent the emails both from being sent/received?
-Joe

[mmorse]

well you get the exact same error both ways-so clearly something is up with amavisd

[joeleo]

Hi All, Here's the output for what was asked for from past thread...

root@mx1:/# find / -name file
/usr/lib/apt/methods/file
/opt/zimbra/zimbramon/lib/URI/file
root@mx1:/home/user1#

Based on the output it looks like the file "file" exist. Below are the permissions for that file.

root@mx1:/opt/zimbra/libexec# ls -la /usr/lib/apt/methods/file
-rwxr-xr-x 1 root root 8992 Apr 18  2006 /usr/lib/apt/methods/file
root@mx1:/opt/zimbra/libexec#

Not sure if this output will help.

root@mx1:/opt/zimbra/zimbramon/lib/URI# ls -la
total 200
drwxr-xr-x  4 root root 4096 Oct  8 08:03 .
drwxr-xr-x 32 root root 4096 Oct  8 08:03 ..
-r--r--r--  1 root root 6604 Nov  5  2004 Escape.pm
-r--r--r--  1 root root 5707 Jan 14  2004 Heuristic.pm
-r--r--r--  1 root root 4647 Jan 14  2004 QueryParam.pm
-r--r--r--  1 root root 2332 Jan 14  2004 Split.pm
-r--r--r--  1 root root 5530 Jan 14  2004 URL.pm
-r--r--r--  1 root root 3826 Jan 14  2004 WithBase.pm
-r--r--r--  1 root root   75 Sep 14  1998 _foreign.pm
-r--r--r--  1 root root 5659 Jul 23  2003 _generic.pm
-r--r--r--  1 root root 3241 Jan  1  2004 _ldap.pm
-r--r--r--  1 root root  222 Sep 11  1998 _login.pm
-r--r--r--  1 root root 2052 Apr  6  2004 _query.pm
-r--r--r--  1 root root  377 Sep 11  1998 _segment.pm
-r--r--r--  1 root root 2239 Aug 18  2003 _server.pm
-r--r--r--  1 root root  977 Sep 11  1998 _userpass.pm
-r--r--r--  1 root root 3343 Jan 14  2004 data.pm
drwxr-xr-x  2 root root 4096 Oct  8 08:03 file
-r--r--r--  1 root root 9862 Sep  7  2004 file.pm
-r--r--r--  1 root root 1058 Dec 30  2001 ftp.pm
-r--r--r--  1 root root 2399 Oct  4  2003 gopher.pm
-r--r--r--  1 root root  405 Oct  5  2004 http.pm
-r--r--r--  1 root root   89 Sep 11  1998 https.pm
-r--r--r--  1 root root 2997 Jan 14  2004 ldap.pm
-r--r--r--  1 root root  460 Jan  1  2004 ldapi.pm
-r--r--r--  1 root root   89 Jan  1  2004 ldaps.pm
-r--r--r--  1 root root 1254 Sep 11  1998 mailto.pm
-r--r--r--  1 root root   89 Dec 31  2003 mms.pm
-r--r--r--  1 root root 1427 Sep 11  1998 news.pm
-r--r--r--  1 root root   91 Sep 11  1998 nntp.pm
-r--r--r--  1 root root 1174 Sep 11  1998 pop.pm
-r--r--r--  1 root root   96 Sep 11  1998 rlogin.pm
-r--r--r--  1 root root  197 Feb 14  2000 rsync.pm
-r--r--r--  1 root root   89 Jul 16  2002 rtsp.pm
-r--r--r--  1 root root   90 Jul 16  2002 rtspu.pm
-r--r--r--  1 root root 1753 Jun  3  2004 sip.pm
-r--r--r--  1 root root   87 Aug 20  2002 sips.pm
-r--r--r--  1 root root  118 Sep 11  1998 snews.pm
-r--r--r--  1 root root  122 Nov  1  2001 ssh.pm
-r--r--r--  1 root root   95 Sep 11  1998 telnet.pm
-r--r--r--  1 root root   95 Jan  2  2003 tn3270.pm
drwxr-xr-x  2 root root 4096 Oct  8 08:03 urn
-r--r--r--  1 root root 1954 Aug  4  2002 urn.pm
root@mx1:/opt/zimbra/zimbramon/lib/URI#

And, also:

root@mx1:/opt/zimbra/zimbramon/lib/URI/file# ls -la
total 36
drwxr-xr-x 2 root root 4096 Oct  8 08:03 .
drwxr-xr-x 4 root root 4096 Oct  8 08:03 ..
-r--r--r-- 1 root root 1426 Sep  7  2004 Base.pm
-r--r--r-- 1 root root  468 Sep  7  2004 FAT.pm
-r--r--r-- 1 root root 2464 Sep  7  2004 Mac.pm
-r--r--r-- 1 root root  532 Sep  7  2004 OS2.pm
-r--r--r-- 1 root root  320 Sep  7  2004 QNX.pm
-r--r--r-- 1 root root 1004 Sep  7  2004 Unix.pm
-r--r--r-- 1 root root 1739 Sep  7  2004 Win32.pm
root@mx1:/opt/zimbra/zimbramon/lib/URI/file#

Also, I did the command ./zmfixperms as suggested in the previous thread. I stopped and restarted Zimbra services and posted the output on pastebin - collaborative debugging tool

I've highlighted some lines that I thought could be potential problems.

-Joe

[soxfan]

The file "file" may exist on your system, but it's not the one that amavisd needs. The one you mentioned in the /opt/zimbra directory is actually a directory, so that's not it. Not sure about the other one, as I don't have this on my system. The "file" in question is a UNIX command that, when executed against some file, will try to determine what type of file it is. From the man page:

NAME
file - determine file type

SYNOPSIS
file [ -bcikLnNprsvz ] [ -f namefile ] [ -F separator ] [ -m magic-
files ] file ...
file -C [ -m magicfile ]

DESCRIPTION
This manual page documents version 4.10 of the file command.

File tests each argument in an attempt to classify it. There are
three sets of tests, performed in this order: filesystem tests, magic
number tests, and language tests. The first test that succeeds causes
the file type to be printed.

This command should exist somewhere in the zimbra user's PATH; ie /bin, /usr/bin, /usr/local/bin. Not sure what flavor of Linux (or Mac OS X) you are running, but you should be able to find a the "file" package fairly easily. Once you get it installed I'm guessing you should be OK.
I guess the other option may be to totally disable virus and spam checking; that may totally bypass amavisd.

[joeleo]

soxfan, thanks for your comments and assistance... I am a bit confused with the info you provided. You refer to some command should exist some where in the system. What exactly is this command you are referring to?

Also, any idea why this command would be missing from doing an install? Has there been any other user reported issues regarding this that you are aware of?
Should I do a new install?

Also, I posted a output of my Zimbra log when starting Zimbra. I posted that file here: pastebin - collaborative debugging tool
I've highlighted that file with some potential problems. But, for me I am not sure. Would appreciate if you or anyone can take a look and comment on any spotted issues with the lines I've marked.

Joe

[soxfan]

I know it might be a bit confusing, but the command is actually called 'file'. It would not be a file/command that you would get from the Zimbra install, but rather from your OS install. I don't ever remember seeing it not installed on any Linux systems that I've worked on, but that doesn't really mean much. I've pretty much stuck to RedHat/Fedora/CentOS systems, and perhaps it is just something that is installed by default with these flavors, and not with others. You don't specify which distro you are working with.

I don't see anything that jumps out at me with the logs you posted at pastebin. The only thing that is a bit confusing to me is that the logs clearly show that amavis did not find the 'file' command, and it says "not using it". Yet, the error message that you posted seems to indicate that the 'file' command is required. Not sure why it didn't complain louder, so to speak, when it started.

Anyway, I really think you need to find the package that includes the 'file' command for your distro and get it installed. Not saying this will absolutely fix your problem, but it would certainly get you past this one issue.

Hope this helps, and please post back if you are still not clear on this.

[jholder]

Lots of stuff in this thread, but I think it all comes down to a botched uninstall which didn't clean things up.

Rather than treating his symptoms, I think that his issue comes down to that.
Also, it would be helpful to know why your installs failed so many times. Perhaps it's related?

My advice would be to totally remove zimbra. Then scan the dpkg database to see if anything is left over from zimbra. Then kill /opt/zimbra

If this is ubuntu, I'd run synaptic to see if any packages are broken before installing zimbra again.

Then once it's all done, reinstall zimbra.

But, that's just my thought

[joeleo]

Soxfan, the Linux I am running is Ubuntu6... Thank Jholder for your comments. I have had some bad installs but not entirelly all Zimbra related. I had to learn to setup OpenVZ and setup things right there. Also, had to figure out DNS as well.
But now, I've got all these layers understood it should not be to difficult to do a clean install. I will try a clean install. Though, I have this question:

Once Zimbra is installed, Is there anything that must be done in the Zimbra Admin for the domain in order for mail to be sent/receive properly. What I had done before is just created an account for myself and that's it. Should I create a Vhost? Is there anything else beside creating an email account as I did to get things working?

Another thing that I spotted is that when I go to Zimbra Admin I can't seem to see any info shown for "Server Status"... It tells me:
"Server Status is not available. To see sever status, logger service must be installed. But, I did have logger service installed and confirmed that with zmcontrol status command. Same issue for "Server Statistic" No data is available there either - Any toughts?

Joe

[joeleo]

Jholder, per your comments about running synaptic to check for broken packagees... What is the exact command to do this? I am kind of new to linux.

Joe