Reporting

Imap App Error Possible typo

bckq
Path Finder

Hi,
I got an error while making btool check which is attached below. Is this normal? Should I change something?

enter code heresplunk btool check --debug

Checking: /opt/splunk/etc/apps/imap/default/indexes.conf
Possible typo in stanza [mail] in 
/opt/splunk/etc/apps/imap/default/indexes.conf, line 6: maxQueryIds = 10000000
     Did you mean 'maxBloomBackfillBucketAge'?
     Did you mean 'maxConcurrentOptimizes'?
     Did you mean 'maxDataSize'?
     Did you mean 'maxHotBuckets'?
     Did you mean 'maxHotIdleSecs'?
     Did you mean 'maxHotSpanSecs'?
     Did you mean 'maxMemMB'?
     Did you mean 'maxMetaEntries'?
     Did you mean 'maxRunningProcessGroups'?
     Did you mean 'maxRunningProcessGroupsLowPriority'?
     Did you mean 'maxTotalDataSizeMB'?
     Did you mean 'maxVolumeDataSizeMB'?
     Did you mean 'maxWarmDBCount'?
     Did you mean 'memPoolMB'?
     Did you mean 'minRawFileSyncSecs'?
0 Karma
1 Solution

rturk
Builder

The "Splunk for IMAP" app is quite old, with the last update in August 2009 (by Erik Swan no less).

The maxQueryIds configuration option was deprecated in 3.3.3 & retired in version 3.4.4 (See HERE).

I'm pretty sure Splunk just ignores this line, but if you no longer wish to see it just remove it from the "Splunk for IMAP" indexes.conf file.

View solution in original post

rturk
Builder

The "Splunk for IMAP" app is quite old, with the last update in August 2009 (by Erik Swan no less).

The maxQueryIds configuration option was deprecated in 3.3.3 & retired in version 3.4.4 (See HERE).

I'm pretty sure Splunk just ignores this line, but if you no longer wish to see it just remove it from the "Splunk for IMAP" indexes.conf file.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...