[JAMES-522] Having the ClamAVScan mailet configured, but clamd unavailable when JAMES starts, keeps JAMES from starting.

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.3.0
• Component/s: Matchers/Mailets (bundled)
• Assignee: Norman Maurer
• Reporter: Noel J. Bergman
• Created: 04/Jun/06 09:30
• Updated: 21/Nov/07 08:31
• Resolved: 06/Jun/06 14:36

Description

If JAMES attempts to start, ClamAVScan is configured, and clamd is not running, ClamAVScan.init() will throw an exception, terminating JAMES entirely. This can be seen in ${james}/logs/phoenix.log where the maxPings error will appear, and the spoolmanager component will be shown as failing.

I'm marking this as minor since there is a work around, biut actually, I consider it a more major error.