Back to Community Threads
2
SmarterMail v15.1.6005 - Error in Maintenance Log
Problem reported by Nathan Harrington - 7/14/2016 at 8:27 AM
Submitted
I'm seeing the following error in the Maintenance Log:
 
[2016.07.14] 00:09:30 The following error occurred while cleaning message retrieval folders: Could not find a part of the path 'c:\SmarterMail\ImapRetrieval'.
 
The error message is legitimate...there is no "C:\SmarterMail\ImapRetrieval" path on the server.
 
I have searched through mailconfig.xml looking for "path", ":\", and "C:".  None of the references to "path" or ":\" refer to "c:\SmarterMail\ImapRetrieval" as referenced in the error message.  There are no references to "C:" at all.  Further, there is an entry for "imapRetrievalDownloadPath" set to d:\SmarterMail\ImapRetrieval", which does exist.
 
My question is where is the reference to this path (as used by the "cleaning message retrieval folders" process) stored, and how can I change it?

10 Replies

Reply to Thread
0
Employee Replied
7/14/2016 at 9:52 AM
Employee Post
Hi Nathan.  This setting is located at Settings >> Protocol Settings >> IMAP tab.
0
Nathan Harrington Replied
7/14/2016 at 10:38 AM
Rod,
 
Thanks for the quick reply.  I have checked that setting via the UI (Settings > Protocol Settings > IMAP > IMAP Retrieval Download Path), and it is set to d:\SmarterMail\ImapRetrieval\ (i.e. not C: as indicated in the log file).  Note that d:\ as indicated in the UI matches what I'm seeing in the mailconfig.xml file as well.
 
Is there some other location where this could be stored, or is it possible that it got hard-coded somewhere in the code to look for C: rather than D:?  Seems odd that it's even looking in the root of C: given that SmarterMail is typically installed a couple layers deep under Program Files.
 
Nathan
 
0
Employee Replied
7/14/2016 at 3:17 PM
Employee Post
Nathan, I just tried this locally and everything was as expected. You'd probably need to open a ticket so we can look at this deeper.
0
Ed Welch Replied
7/14/2016 at 9:12 PM
I have seen the same thing for a year or more.  It started after a previous version upgrade - not sure which one.   Here's the  IMAP Retrieval path: "d:\SmarterMail\PopRetrieval".  SmarterMail has never been on C on this server, it was installed on D originally.  This is on Windows 2008 R2.  I once searched all the xml files for the string "c:\SmarterMail" and did not find it.
 
Logs:
[2016.07.14] 00:12:39 The following error occurred while cleaning message retrieval folders: Could not find a part of the path 'c:\SmarterMail\ImapRetrieval'.
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-activation.log
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-delivery.log
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-imapRetrieval.log
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-maintenance.log
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-popLog.log
[2016.07.14] 00:12:39 Compressed d:\SmarterMail\Logs\2016.07.11-smtpLog.log
0
Nathan Harrington Replied
7/14/2016 at 9:27 PM
Ed...agreed.  I just checked the logs from before my upgrade to v15.1.6005, and it was occurring prior to the upgrade, which would have been on v12.0.5178, so the issue goes back at least a couple of years.
0
Nathan Harrington Replied
7/14/2016 at 9:43 PM
As a follow-up, I just completed a non-case-sensitive search for "ImapRetrieval" in all files located under C:\Program Files (X86)\SmarterTools.
 
I found a bunch of occurrences of "ImapRetrieval", including "<imapRetrievalDownloadPath>d:\SmarterMail\ImapRetrieval\</imapRetrievalDownloadPath>".
 
I did not find any reference to "C:\SmarterMail\ImapRetrieval".  This makes me think it might be encoded within an EXE, DLL, or some other type of file.
0
Ed Welch Replied
7/15/2016 at 9:46 PM
c:\SmarterMail may be the default path coded in the one of the maintenance EXE's or DLL's and is not being replaced by the real path in the config files for this one function. It's possible also that the real path is supposed to be also listed elsewhere, and setup did not do that. Since Imap Retrieval works, and there is no folder on C, the effect only applies to maintenance.
0
Ed Welch Replied
9/6/2016 at 6:18 PM
I just noticed that the error has not been logged since upgrading our server to version 15.3.6081 on 8/30.  It had continued through many previous upgrades.  No settings were changed, just the latest version installation, as before.
0
Nathan Harrington Replied
9/7/2016 at 6:52 AM
I've been working with SmarterTools on a fix for this. The custom build they created for me resolved the issue, but I wasn't sure which public release the fix was going to be in. Sounds like it may have been in 15.3.6081.
0
Ed Welch Replied
9/7/2016 at 7:22 AM
It appears so. After upgrading to 15.2.6039, the error continued to be logged, and was gone in the next maintenance run after upgrading to 15.3.6081.
Back to Community Threads

Reply to Thread