You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2006/07/21 17:35:16 UTC

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

     [ http://issues.apache.org/jira/browse/JAMES-522?page=all ]

Stefano Bagnara updated JAMES-522:
----------------------------------

        Fix Version/s:     (was: 3.0)
    Affects Version/s: 2.3.0a3

> 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
>          Issue Type: Bug
>          Components: Matchers/Mailets (bundled)
>    Affects Versions: 2.3.0a3
>            Reporter: Noel J. Bergman
>         Assigned To: Norman Maurer
>            Priority: Trivial
>             Fix For: 2.3.0b1
>
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org