Re: [NoXMail] error #2 Access violation at address 75740054
A very large number of my log lines have this error.
I have coppied large excerpts from both nox and declude logs to view.
refer to ;
http://www.cfhosting.net/declude.txt
http://www.cfhosting.net/noxmail.txt
These are VERY large chuncks of my logs
So a fast connection would be a good idea.
Let me know what you can find out.
I need to delete these after you have seen them
to avoid spambots from finding them, please let me know.
Greg Hedgepath
[EMAIL PROTECTED]
http://www.CFHosting.net/
ICQ#: 290276 | AIM: colFu
Yahoo: cfhosting
msn: [EMAIL PROTECTED]
- Original Message -
From: Brian Milburn [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 04, 2003 3:05 PM
Subject: Re: [NoXMail] error #2 Access violation at address 75740054
Hi Greg,
Does this happen very often? It is a handled error condition and not
critical, but I am curious how often you see it and under what
circumstances
it may occur. I have never actually seen this error before, although I
have
designed the program to recognize and report that it may occur.
Brian
On 01/04/03 2:32pm you wrote...
Please explain;
What is Could not unlock .. Error #2 ??
What is Access violation at address 75740054 ??
Are these due to the fact the email is being deleted?
Just want some clarification on these log entries.
Thanx.
Excerpt from Declude log below.
01/04/2003 14:24:47 Q34fe07c7011ad907 WARNING: Could not unlock
C:\IMail\spool\_34fe07c7011ad907.~MD due to error #2.
Excerpt from NoXMail log below
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD (IN) [FAILED SPAM] Scores -
Adult: 0 (Req: 18) Spam: 37 (Req: 22) ExitCode: 37 (Req: 26)
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - MSG TO: [EMAIL PROTECTED]
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - ENV TO: [EMAIL PROTECTED]
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - MBX TO: [EMAIL PROTECTED]
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - MSG FROM:
[EMAIL PROTECTED]
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - MSG SUBJECT: After
Christmas
Sale - Save 75% off Everything in Stock
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - Subject consistent with
SPAM:
3 penalty points added.
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - Found 11 embedded image
links:
6 penalty points added.
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - Matched: (#Spam)STOCK(1*2)
(Spam)BEREMOVED(2*2) (Spam){UNSUBSCRIBESUBJECT}(1*6)
(Spam)MAILMARKETING(2*8)
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - Msg processed in: 52ms -
Msg
Size: 7234 bytes
1/4/2003 2:24:47 PM - D34fe07c7011ad907.SMD - Access violation at address
75740054. Read of address 75740054 message deleted.
Running latest NoX beta and version 165i declude.
Greg Hedgepath
[EMAIL PROTECTED]
http://www.CFHosting.net/
ICQ#: 290276 | AIM: colFu
Yahoo: cfhosting
msn: [EMAIL PROTECTED]
-
[This E-mail scanned for viruses by declude AntiVirus Software]
ware]
---
[This E-mail scanned for viruses by Solid Oak Software]
Archives: http://www.mail-archive.com/nox-list%40mail.noxmail.com/
Removal address: [EMAIL PROTECTED]
---
[This E-mail scanned for viruses by Solid Oak Software]
Archives: http://www.mail-archive.com/nox-list%40mail.noxmail.com/
Removal address: [EMAIL PROTECTED]
-
[This E-mail scanned for viruses by declude AntiVirus Software]
-
[This E-mail scanned for viruses by declude AntiVirus Software]
ware]
---
[This E-mail scanned for viruses by Solid Oak Software]
Archives: http://www.mail-archive.com/nox-list%40mail.noxmail.com/
Removal address: [EMAIL PROTECTED]
RE: [NoXMail] error #2 Access violation at address 75740054
Actually, a couple of interim versions back, and I think in the last official update, he suppressed the message if the D file was deleted. Maybe he also did that for the real Q file, but we delete the _ temporary file which is what the Q file is renamed to when the message is in process. On 01/04/03 3:28pm you wrote... The Declude file errors are due to No-X-Mail deleting the in-process, temporary Q file when the message is held. I probably need to clue Scott into the fact we are doing this so he can suppress the error if necessary. It should not do any harm other than add a line to the Declude log file. It happens here as well. If I remember correctly, Scott has said this can be ignored if it is your intended action. I do know he was going to make a change at some point so that if that error is incurred, Declude stops all processing of that message. I am not sure if that has been implemented. John Tolmachoff MCSE, CSSA IT Manager, Network Engineer RelianceSoft, Inc. Fullerton, CA 92835 www.reliancesoft.com ft.com --- [This E-mail scanned for viruses by Solid Oak Software] Archives: http://www.mail-archive.com/nox-list%40mail.noxmail.com/ Removal address: [EMAIL PROTECTED] --- [This E-mail scanned for viruses by Solid Oak Software] Archives: http://www.mail-archive.com/nox-list%40mail.noxmail.com/ Removal address: [EMAIL PROTECTED]
