I don't see anything unusual in the clamd.log or freshclam.log.

in the system.log I see the following:

Feb 26 14:45:01 clearos servicewatch: sanity checking amavisd
Feb 26 14:46:02 clearos servicewatch: restarting amavisd

Is that normal?

In my maillog I have these which look suspicious:

Feb 26 18:05:06 clearos amavis[30281]: (!!)TROUBLE in pre_loop_hook: db_init: BDB no dbC: __fop_file_setup: Retry limit (100) exceeded, File exists. at (eval 82) line 302.
Feb 26 18:05:06 clearos amavis[30281]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: db_init: BDB no dbC: __fop_file_setup: Retry limit (100) exceeded, File exists. at (eval 82) line 302.

You can now view your log files in /var/log. Start the apps then try viewing the messages log and possibly the system and maillogs for any obvious messages. Also the logs in /var/log/clamav.

I'm setup with both. What's next?

There should be a log file viewer under Webconfig > Reports > Log Viewer, but I prefer the WinSCP method. If you don't have the Log Viewer app, it is available free from the marketplace

Also get hold of a copy of WinSCP and PuTTy. WinSCP is a graphical file manager and text editor. The logs are found in /var/log. PuTTy is a remote ssh console which integrates with WinSCP. You can copy from it by selecting text and paste to it by right-clicking. That way you don't need to take screenshots to post to the forum.

Sorry, I'm a bit of a novice. How do I look at the logs? Also, I forgot to original post that mail is delivered as expected.

I assumed you were on ClearOS 7.x. journalctl does not exist on 6.x nor does the -l switch on the"service" command.

What about the logs?

It does start an in about 30 seconds stops with a status of "amavisd dead but pid file exists" and journalctl returns command not found.

Is the SMTP server running? Are you getting any messages in the messages or system log when they die?

Can you try starting amavis from the command line with a:

service amavisd start

Watch for any messages as it starts. If there are any messages, you can expand the lines with a:

service amavisd status -l

Also, if it fails, check the output of:

journalctl -xe