james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincenzo Gianferrari Pini (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-522) Having the ClamAVScan mailet configured, but clamd unavailable when JAMES starts, keeps JAMES from starting.
Date Mon, 05 Jun 2006 12:43:30 GMT
    [ http://issues.apache.org/jira/browse/JAMES-522?page=comments#action_12414751 ] 

Vincenzo Gianferrari Pini commented on JAMES-522:
-------------------------------------------------

I would keep things as now, because this was the intended behaviour. If <maxPings>n</maxPings>,
with n > 0, the desired behaviour is to delay the startup of James until clamd is up and
running, *without allowing any message to flow without an anti-virus check*. Such situation
could arise with a server startup, where clamd could take longer than james to start. If after
some time clamd has not yet started, James must fail and the administrator shall intervene
to fix clamd.
If I don't want such "safe" behaviour, I can set <maxPings>0</maxPings> as you
did.
BTW, I'm changing config.xml to have a commented invocation of ClamAVScan (plus some other
enhancements).

> 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
>     Assignee: Norman Maurer
>     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