Hi Seun, The strange thing is, the previous versions work correctly ( for all but a certain few foreign chars) After updating to the *dev version, It starts throwing this error on mails that it was properly indexing before and almost nothing makes it into the index anymore. Using 1.3.5 (which seems to not be available anymore) it seems to work properly, however 1.3.5dev, 1.3.6dev, and 1.3.7dev all throw the same errors for mail that 1.3.5 indexes without issues. This one really has me scratching my head, as I am sure there is something simple/small that I/we are missing. In any case I really appreciate your efforts, let me know if you have any ideas on where to look to solve this issue. Regards. ... View more

Hi Seun, Unfortunately I am not able to get the *.dev versions to work properly for me, I get this error: Mail found with unexpected codec - Only the headers get indexed and none of the content, this is happening for ALL mail, even the ones that were working properly before. Do you have an idea where I should start looking to resolve this issue? Thank you, Regards. ... View more

Hi Seun, Will test it out and let you know how it goes. Thanks for your efforts. Regards. ... View more

Hi Seun, I tested 1.3.6dev and 1.3.5dev quickly but I noticed that right away I started seeing the error 'Mail found with unexpected codec - '. This is happening for mails that were previously being indexed properly also, so I have reverted to 1.3.5 for now which is working properly. I would like to thank you again for all your efforts, these improvements make life easier for us as admins. I was busy for a bit during the holidays but tomorrow we are back in the office and I can help you test future builds as they become ready. Best Regards! ... View more

Hi Seun, For our particular use case we are indexing thousands of emails daily that are generated by WHM servers so read only isn't really ideal as they would build up really fast. We have some alerting in place for certain email events so the previous behavior of stalling indexing when it came across something it couldn't index was a much bigger problem for us as we then needed something to alert us that indexing had stalled, and then still required manual intervention to delete the email it had failed to index. Losing the odd email containing un-supported characters is a much smaller issue as we would generally just delete them anyways (it's usually just things like failed SSH logins with unsupported chars, or failed IMAP logins, etc that stops the processing for us) That being said, maybe a great option would be to to either: A, leave them in place but continue to process the others deleting only what was successfully indexed or B, and perhaps an even better option - Move them to a different IMAP folder ( for example, dump them in a folder named processing_failed ). In any case, we are very happy already with the improvements you have made they have made a big difference for us so thank you very much for that. On a side note, we had the option to include headers disabled on every account it's indexing but it was still including headers for most of the accounts, not sure why it would do that but I was able to resolve it by setting DEFAULT_INCLUDE_HEADERS = False in mail_constants.py Funny thing is, it was working at first and I think when we upgraded to Splunk Enterprise 7.0.1 it started including headers ( It could be a coincidence I am not certain of this being related but it was definitely around the same time ) Anyways, thanks again for your efforts I am sure there are others out there who really appreciate it too! Regards. ... View more

Hi Seun, if it’s set to delete the emails upon indexing what would be the expected behaviour when it comes across something it can’t index? Will it discard the email and continue to index the others or will it leave it behind and continue processing the rest and deleting only after being indexed?? ... View more

Hi Seun, We will try it out too and let you know how it goes. Thank you for your efforts. ... View more

Hi seunomosowon, We are having a very similar issue relating to the indexing of emails generated by WHM/cPanel servers, thank you for addressing this and we are looking forward to the update! ... View more