Incoming email stuck in the Spool
Problem reported by Chew Man Fai - January 18 at 7:53 PM
Submitted
Hello,
 
We having an issue where our client email stuck in the spool as some of the status Pending, Waiting to Deliver.
As per our checking in the log, it shows the error as follow:-
 
13:03:01 [94329] Exception: An attempt was made to move the file pointer before the beginning of the file.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.SeekCore(Int64 offset, SeekOrigin origin)
   at System.IO.FileStream.Seek(Int64 offset, SeekOrigin origin)
   at MailStore.GroupFileAccess.GroupFile.AddHeaderItemAlreadyLocked(UInt32 uid, BinaryWriter bw)
   at MailStore.GroupFileAccess.GroupFile.AddMessage(String #Lrb, UInt32 #q9, Boolean #Psb, String& #Qsb, Int32& #9r)
   at MailStore.GroupFileAccess.GroupFile.Add(String emailFilePath, UInt32 uid, Boolean wait, String& headerText, Int32& size)
   at MailStore.Mailboxes.Mailbox.AddMessage(String messagePath, MessageFlags flags, Int32 size, String& headerText, String& failureReason)
   at MailStore.Mailboxes.MailboxManager.#eEb(String #c1i, String #90i, MessageFlags #Yu, Int32 #9r, Boolean #T9, String& #Qsb, String& #Jwi, String #WL, Boolean #Ibl)
   at MailStore.Mailboxes.MailboxManager.AddMessage(String messagePath, String subFolderName, MessageFlags flags, Int32 size, Boolean createMailbox, String& headerText, String& failureReason, String source, Boolean isNew)
   at RelayServer.DeliveryManager.#DEb(LocalRecipient #w5i, MimeReader #ABb, String #Qsb, String #4Db, String #3n, Boolean #x5i, Boolean #y5i)
   at RelayServer.DeliveryManager.#xEb(SpoolMessage #Nrb, LocalRecipient #w5i, String #4Db, Boolean #x5i, Boolean #y5i)
   at RelayServer.DeliveryManager.#SBb(SpoolMessage #Nrb)
 
May we know what is the reason for this issue? Or should we open a ticket to the support?
 
 

4 Replies

Reply to Thread
0
Derek Curtis Replied
Employee Post
First, make sure you're on the most recent minor or whatever major version of SmarterMail you're running. Then see if the emails clear out. Next, how often is this occurring? 
Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278
0
Kyle Kerst Replied
Another thing you may want to check/do:
 
- Make sure your .net framework is fully up to date, and appropriate Windows updates have been installed. 
- Do a file system check on this server (pointer errors are concerning)
- Add exclusions to your third party antivirus so that it doesn't scan SmarterMail spool directories. Locking of the EML or GRP files will cause SM to get hung up trying to read/write data to user directories. 
 
You may need to do a full server restart as well, maybe the antivirus is hung up on something? Let us know how it goes :-)
Kyle Kerst Cameron Solutions LLC www.cameron-solutions.com
1
Linda Pagillo Replied
Another thing you can try... right click on the message and view the reason why they are still in the spool. If you see that a lot of them have 601 errors, that usually points to a DNS issue and you should check your DNS servers assigned in SmarterMail to see if they are working properly. If not, you can change them to Google's DNS servers which are 8.8.8.8 and 8.8.4.4. Once you do that, try to force out a few messages to see if they leave the spool.
Linda Pagillo
Mail's Best Friend
Email: linda.pagillo@mailsbestfriend.com
Web: www.mailsbestfriend.com
Authorized SmarterTools Reseller
Authorized Message Sniffer Reseller
 
0
Kyle Kerst Replied
I forgot to mention that last time around, thats a big one! DNS issues are one of the most common causes of backed up spools. Thanks!
Kyle Kerst Cameron Solutions LLC www.cameron-solutions.com

Reply to Thread