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

[Norman Maurer <nm...@byteaction.de>]

So what you consider ? Only changge the Exception text or also the
default config ?

bye
Norman

Am Sonntag, den 04.06.2006, 02:37 +0000 schrieb Noel J. Bergman (JIRA):
>     [ 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.
>