[Bug 991233] New: amavisd.service fails to start because required default folders are missing

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=991233

Bug ID: 991233
           Summary: amavisd.service fails to start because required
                    default folders are missing
           Product: Fedora
           Version: 19
         Component: amavisd-new
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail], [e-mail]

+++ This bug was initially created as a clone of Bug #863069 +++

Description of problem:
There are some default folder locations specified in the config file that don't
get created when amavisd-new is installed.  The program fails to start because
of it, at least until the host is rebooted.

For example, this message gets printed to the log file when trying to start the
service:
amavis[5461]: (!)Net::Server: 2012/10/04-04:35:06 Couldn't open pid file
"/var/run/amavisd/amavisd.pid" [No such file or directory].\n\n  at line 318 in
fil...Net/Server.pm

In order to make amavisd.service start correctly, I had to do the following:
mkdir /var/spool/amavisd/var
mkdir /var/run/amavisd/
chown -R amavis:amavis /var/spool/amavisd/var /var/run/amavisd/
chmod 700 /var/spool/amavisd/var

After that, everything worked as expected.  The other option is to reboot
before attempting to start the service.

Version-Release number of selected component (if applicable):
amavisd-new-2.8.0-5.fc19

How reproducible:
Always

Steps to Reproduce:
1. yum install amavisd-new
2. systemctl start amavisd.service
3.

Actual results:
Fails to start

Expected results:
Starts using default config file

Additional info:
I noticed that /var/run/amavisd is not present immediately after installing the
package.  Once I rebooted the host, the directory became available.  To me this
suggests that the entry /etc/tmpfiles.d/amavisd-new.conf is doing its job, but
the spec file for this package needs to also make the same temporary
directories as part of package installation, or somehow rerun the tmpfiles.d
jobs.  Without doing this, those directories won't be available right after
package installation.