james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-522) Having the ClamAVScan mailet configured, but clamd unavailable when JAMES starts, keeps JAMES from starting.
Date Sun, 04 Jun 2006 02:37:31 GMT
     [ http://issues.apache.org/jira/browse/JAMES-522?page=all ]

Noel J. Bergman updated JAMES-522:
----------------------------------

    Priority: Trivial  (was: Minor)

> 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: Trivial

>
> 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


Mime
View raw message