[jira] Commented: (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=comments#action_12414751 ]
Vincenzo Gianferrari Pini commented on JAMES-522:
-
I would keep things as now, because this was the intended behaviour. If
maxPingsn/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 maxPings0/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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (JAMES-522) Having the ClamAVScan mailet configured, but clamd unavailable when JAMES starts, keeps JAMES from starting.
So what you consider ? Only changge the Exception text or also the
default config ?
bye
Norman
Am Sonntag, den 04.06.2006, 02:37 + 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 maxPings0/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.
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
[jira] Commented: (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=comments#action_12414615 ]
Noel J. Bergman commented on JAMES-522:
---
In the mailet config, adding maxPings0/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]
