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 "Noel J. Bergman (JIRA)" <se...@james.apache.org> on 2006/06/04 04:31:29 UTC
[jira] Created: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Noel J. Bergman (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Commented: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Noel J. Bergman (JIRA)" <se...@james.apache.org>.
[ 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.
--
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
[jira] Resolved: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-522?page=all ]
Norman Maurer resolved JAMES-522:
---------------------------------
Fix Version: 2.3.0
Resolution: Fixed
> 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
> Fix For: 2.3.0
>
> 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
[jira] Commented: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Vincenzo Gianferrari Pini (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Updated: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-522?page=all ]
Stefano Bagnara updated JAMES-522:
----------------------------------
Fix Version: 2.3.0b1
2.4.0
(was: 2.3.0)
> 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
> Fix For: 2.4.0, 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
[jira] Assigned: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-522?page=all ]
Norman Maurer reassigned JAMES-522:
-----------------------------------
Assign To: Norman Maurer
> 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
[jira] Updated: (JAMES-522) Having the ClamAVScan mailet
configured, but clamd unavailable when JAMES starts, keeps JAMES from
starting.
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ 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