[sniffer] Re: Error Code 69

[Pete McNeil]

On 12/15/2016 07:04 AM, Don Winsauer wrote:

I have had 419 occurrences of this error since the 1st of the month.  I don't 
even run a virus scanner on this Windows mail server.  We are running IMail, 
Declude with Sniffer.


This could be an indication of a file system problem?

The only reason that occurs is when the file system / OS prevents SNF 
from removing the original file.


Are the files still there?

What changed since the 1st? (did the problem begin then precisely?)

_M


--
Pete McNeil
Chief Scientist
ARM Research Labs, LLC
www.armresearch.com
866-770-1044 x7010
twitter/codedweller


#
This message is sent to you because you are subscribed to
 the mailing list .
This list is for discussing Message Sniffer,
Anti-spam, Anti-Malware, and related email topics.
For More information see http://www.armresearch.com
To unsubscribe, E-mail to: 
To switch to the DIGEST mode, E-mail to 
To switch to the INDEX mode, E-mail to 
Send administrative queries to  

[sniffer] Re: Error Code 69

[Don Winsauer]

Hi Pete,

I have had 419 occurrences of this error since the 1st of the month.  I don't 
even run a virus scanner on this Windows mail server.  We are running IMail, 
Declude with Sniffer.

Don

-- Original Message --
From: Pete McNeil 
Reply-To: "Message Sniffer Community" 
Date:  Wed, 14 Dec 2016 18:48:59 -0500

>On 12/14/2016 06:12 PM, John Tolmachoff wrote:
>> > m='c:\SmarterMail\Spool\proc\work\1743661413.eml' code='69' 
>> text='ERROR_MSG_XHDRi: Drop Msg XHDR injector can't remove original!'/>
>
>When SNF is configured to inject headers it does so safely---
>First, it reads the entire original message into a buffer, then scans it,...
>Then it writes a new copy of the message to a .tmp file with the headers 
>injected.
>When that completes without errors, it deletes the original and renames 
>the .tmp file in it's place.
>That way, if anything goes wrong, the original is always there as a 
>backup until the last moment.
>
>The error above indicates that SNF was trying to delete the original 
>message file so that it could move the new version over. Something went 
>wrong and it wasn't able to do that.
>
>On windows systems this is most likely because something removed the 
>file first -- perhaps a virus scanner or some other process.
>
>On linux systems it's usually a permissions issue (but this does 
>sometimes happen on windows in rare cases).
>
>So, if you can figure out what is preventing SNF from deleting the 
>original file you will solve the problem.
>
>Hope this helps,
>
>_M
>
>
>-- 
>Pete McNeil
>Chief Scientist
>ARM Research Labs, LLC
>www.armresearch.com
>866-770-1044 x7010
>twitter/codedweller
>
>
>#
>This message is sent to you because you are subscribed to
>  the mailing list .
>This list is for discussing Message Sniffer,
>Anti-spam, Anti-Malware, and related email topics.
>For More information see http://www.armresearch.com
>To unsubscribe, E-mail to: 
>To switch to the DIGEST mode, E-mail to 
>To switch to the INDEX mode, E-mail to 
>Send administrative queries to  
>
>
 





Sent via the WebMail system at net1media.com


 
   

#
This message is sent to you because you are subscribed to
  the mailing list .
This list is for discussing Message Sniffer,
Anti-spam, Anti-Malware, and related email topics.
For More information see http://www.armresearch.com
To unsubscribe, E-mail to: 
To switch to the DIGEST mode, E-mail to 
To switch to the INDEX mode, E-mail to 
Send administrative queries to  

[sniffer] Re: Error Code 69

[Pete McNeil]

On 12/14/2016 06:12 PM, John Tolmachoff wrote:




When SNF is configured to inject headers it does so safely---
First, it reads the entire original message into a buffer, then scans it,...
Then it writes a new copy of the message to a .tmp file with the headers 
injected.
When that completes without errors, it deletes the original and renames 
the .tmp file in it's place.
That way, if anything goes wrong, the original is always there as a 
backup until the last moment.


The error above indicates that SNF was trying to delete the original 
message file so that it could move the new version over. Something went 
wrong and it wasn't able to do that.


On windows systems this is most likely because something removed the 
file first -- perhaps a virus scanner or some other process.


On linux systems it's usually a permissions issue (but this does 
sometimes happen on windows in rare cases).


So, if you can figure out what is preventing SNF from deleting the 
original file you will solve the problem.


Hope this helps,

_M


--
Pete McNeil
Chief Scientist
ARM Research Labs, LLC
www.armresearch.com
866-770-1044 x7010
twitter/codedweller


#
This message is sent to you because you are subscribed to
 the mailing list .
This list is for discussing Message Sniffer,
Anti-spam, Anti-Malware, and related email topics.
For More information see http://www.armresearch.com
To unsubscribe, E-mail to: 
To switch to the DIGEST mode, E-mail to 
To switch to the INDEX mode, E-mail to 
Send administrative queries to