[ http://issues.apache.org/jira/browse/JAMES-574?page=all ]
Stefano Bagnara updated JAMES-574:
----------------------------------
Fix Version/s: 2.3.0rc2
(was: 2.3.0rc1)
(was: 3.0)
Affects Version/s: (was: 3.0)
> Annoying logging of whitelist/blacklist nomatching as "unknown host exception
> thrown: listname" if INFO is enabled
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JAMES-574
> URL: http://issues.apache.org/jira/browse/JAMES-574
> Project: James
> Issue Type: Bug
> Components: SMTPServer
> Affects Versions: 2.3.0a1, 2.3.0a2, 2.3.0a3, 2.3.0b1, 2.3.0b2, 2.3.0b3
> Reporter: Vincenzo Gianferrari Pini
> Assigned To: Vincenzo Gianferrari Pini
> Priority: Trivial
> Fix For: 2.3.0rc2
>
>
> When a checkDNSRBL is done, in case getLogger().isInfoEnabled() is true, both
> successfull and unsuccessfull matches are being logged.
> While successfull matches are useful to log as INFO, the much more frequent
> unsuccessfull matches are logged as "unknown host exception thrown:
> listname", heavily increasing the size of the log file. Such log message is
> useful only in DEBUG mode.
--
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]
