Bug 732289

Summary: cyrus-imap maillog and imap fetching user_deny.db
Product: [Fedora] Fedora Reporter: Eli Wapniarski <eli>
Component: cyrus-imapdAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 15CC: mhlavink, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cyrus-imapd-2.4.12-2.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-12 15:00:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eli Wapniarski 2011-08-21 16:45:22 UTC
With Fedora 15 and cyrus-imapd-2.4.10-1 I get the following message in maillog over and over again:

imap fetching user_deny.db maillog

Thanks for looking into this

Comment 1 Eli Wapniarski 2011-09-16 05:34:50 UTC
Anybody looking at this???

Comment 2 Michal Hlavinka 2011-09-19 11:13:33 UTC
(In reply to comment #1)
> Anybody looking at this???

yes, but this has low priority

some background:
- cyrus-imapd sends all levels of messages to syslog, (debug,info,warn,error,...)
- there's no option to enable/disable debug messages in cyrus-imapd
- syslog accepts mail.* (including debug) messages by default, but because mail.* is not used only by cyrus-imapd, it won't be the correct fix to change that (as default)

so we need to implement new options for enabling/disabling debug messages in cyrus-imapd, but it's low priority task, especially because there is simple workaround available. In /etc/rsyslog.conf change:

mail.* .....
to
mail.info ......

and restart rsyslog:
service rsyslog restart

Comment 3 Michal Hlavinka 2011-12-12 15:00:51 UTC
syslog(LOG_DEBUG, "fetching user_deny.db entry for '%s'", user);

has LOG_DEBUG priority, so this should be fixed with the fix for bug #754940