[ http://issues.apache.org/jira/browse/JAMES-522?page=comments#action_12414615 ]
Noel J. Bergman commented on JAMES-522: --------------------------------------- In the mailet config, adding <maxPings>0</maxPings> will disable the check, and the error, so this is arguably a "trivial" error. Still, it presents a good example of where we can improve retry with queuing. And we really should provide a better error message to help admins, since the default is to fail. > Having the ClamAVScan mailet configured, but clamd unavailable when JAMES > starts, keeps JAMES from starting. > ------------------------------------------------------------------------------------------------------------ > > Key: JAMES-522 > URL: http://issues.apache.org/jira/browse/JAMES-522 > Project: James > Type: Bug > Components: Matchers/Mailets (bundled) > Reporter: Noel J. Bergman > Priority: Minor > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
