Hello, I am using FC15 and following the tutorial for setting up Postfix. I have run into a bit of a dilemma and I have been searching all over the place to try to find an answer. Sorry for the lengthy post, but I figured I'd tell my tale so that everyone can see where I've been; this way I won't be told to go there again. I installed amavisd-new and clamav as per Page 4 of the tutorial. I changed the settings in amavisd.conf as instructed (entering my correct server information, of course). When I entered the command to start amavisd, I was presented with the following error: Code: Starting amavisd (via systemctl): Job failed. See system logs and 'systemctl status' for details. [FAILED] I noticed it did not give me a log to check. So I went to /var/log and looked at the messages log, where I got this Code: Oct 2 00:35:14 server systemd: amavisd.service: control process exited, code=exited status=255 Oct 2 00:35:14 server systemd: Unit amavisd.service entered failed state. I searched for the above error string, only to be sent to articles about what status 255 means and not answering my question. The Force guided me to run Code: # cd /etc/init.d # amavisd (note the absence of 'start') At first it told me that the file /etc/amavisd.conf did not exist and that the script was failing at line 1795 in /usr/bin/amavisd. So, I went to edit said script file, only to find that the variable was set by another file (or at least it appeared to be. Searching for $config_file only sent me on an endless circle with nowhere to set the file path to the conf file). So, I created a symbolic link to point to /etc/amavisd/amavisd.conf; I then ran the amavisd command above again. Apparently $myhostname needed to be a FQDN and did not like my machine's name, which was simply 'server.' Funny, I don't remember that being in the tutorial. I should probably add that I've followed similar tutorials for the previous versions of Fedora and never had amavisd give me this problem. Anyway, I did as requested by amavis: I uncommented the line and entered a FQDN in $myhostname and commanded Fedora to start the flippin' program: Code: # /etc/rc.d/init.d/amavisd start I about threw the screen out the window when the error message about it failing came up again, but this time the code was 102. However, I remembered my Jedi training and did not give in to the Dark Side. So, I went and looked in the messages log... No new error entry there... I looked in maillog, and behold! Amavis created the BDB in /var/spool/amavisd, and all other kinds of activities (PERL modules loading)... But wait, Fedora told me the process failed, so how is this happening? Code: # service amavisd status amavisd.service - SYSV: amavisd is an interface between MTA and content checkers Loaded: loaded (/etc/rc.d/init.d/amavisd) Active: failed since Sun, 02 Oct 2011 00:44:00 -0400; 8min ago Process: 32438 ExecStart=/etc/rc.d/init.d/amavisd start (code=exited, status=102) CGroup: name=systemd:/system/amavisd.service # cd /etc/init.d # amavisd The amavisd daemon is already running, PID:  So now I am really confused! How can I have a PID (in essence, it's running) yet the process failed? To make sure SELinux wasn't giving me any issues, I set it to permissive mode, stopped amavis and started it again. I was given the same failed messages in the beginning and amavis wouldn't start... At this point, if I again process Code: # cd /etc/init.d # amavisd I get: Code: The amavisd daemon is already running, PID:  So, here is where I am now... can anyone please shed some light on this. Did I miss a setting somewhere?