Mail Server problems with Mountain Lion Server

Thanks for this. I ran you command and it didn't accept it.

sudo -u _amavisd -H amavisd -d -c /Library/Server/Mail/Config/amavisd/amavisd.conf

amavisd-new-2.7.0 (20110701):

Unknown command line parameter: /library/server/mail/config/amavisd/amavisd.conf

Usage:

/Applications/Server.app/Contents/ServerRoot/usr/bin/amavisd

[-u user] [-g group]

[-i instance_name] {-c config_file}

[-d log_level,area,...]

[-m max_servers] {-p listen_port_or_socket}

[-L lock_file] [-P pid_file] [-H home_dir]

[-D db_home_dir | -D ''] [-Q quarantine_dir | -Q '']

[-R chroot_dir | -R ''] [-S helpers_home_dir] [-T tempbase_dir]

( [start] | stop | reload | restart | debug | debug-sa | foreground |

showkeys {domains} | testkeys {domains} | genrsa file_name [nbits]

convert_keysfile file_name )

where area is a SpamAssassin debug area, e.g. all,util,rules,plugin,dkim,dcc

or:

Sorry, pasted your parameters without thinking. Omit -d

Taking a step back, what are you trying to achieve? amavisd should be launched through launchd

It was the fact that amavisd wouldn't start and was killing mail. It turned out to be as epikouze said with his \example.

Is this going to stick in the next update or was it an apple bug to begin with?

My client updated their server and I noticed server was 2.10 and not 2.11. I updated that but not sure at what point things failed. I'm sure it was before I did that update and some time after they did their update since it ran for about a week with no problems. Probably wasn't restarted in that time.

Anyway, contemplating either going back to Lion or moving to Kerio. Don't really want to customise 10.8 to get it where 10.7 once was.

Great thread. Very usefull.

My server was working well, and i don't know why it turned out of working one day.

Since I change the file, everything run well.

pterobyte wrote:

There is no reason to launch amavisd manually. That said, if you must, use:

sudo -u _amavisd -H amavisd -d -c /Library/Server/Mail/Config/amavisd/amavisd.conf

This will make sure amavisd runs under the correct user with the correct configuration file. Modifying amavisd itself is not a good idea as it will be overwritten at each update.

I understand what you mean, but i already tried this and there was a problem with the file amavisd.conf

So i will wait for the next update and see if something change.

I ran into one problem mentioned in this thread: Dubious ownership on file. This was the rresult of how I got my Server.app. I downloaded it on another system and copied it over. As a result, the owner was changed to the administrator user instead of root:wheel.

Now I worry: how much more went wrong because of this? Should I redo my entire upgrade?

This solved my problem as well. Thanks, previoulsy i had commented out the line in main.cf that called this process in order to get mail to flow.

I'm currently missing my imap log, ive got all the others, you dont happen to have a fix do you?

Cheers

Cowan

its ok i solved it by recreating mailaccess.log in the correct folder.

Cheers