[spambayes-bugs] [ spambayes-Bugs-988095 ] Athlon64, SP2, NX (no execute)=no workee

[SourceForge.net]

Bugs item #988095, was opened at 2004-07-10 05:00
Message generated for change (Settings changed) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=988095&group_id=61702

Category: Outlook
Group: Binary 1.0rc2
Status: Open
Resolution: None
Priority: 5
Submitted By: mlarma (mlarma)
>Assigned to: Mark Hammond (mhammond)
Summary: Athlon64, SP2, NX (no execute)=no workee

Initial Comment:
When enabling the NX function underneath WinXP with 
SP2 RC2 (32 bit edition, not 64 bit windows), I was 
unable to start Outlook with the SpamBayes plug-in.  
After disabling and only disabling NX (remove /noexecute 
from boot.ini), it worked.  

Funny thing is that the owner of the company I work for 
developed a Bayesian spam filter as well and it had the 
same issue with the NX.  Not sure what the problem is, 
but the NX feature would be nice to turn on.  Does 
anyone know if NX can be disabled at the application 
level so that the other processes were protected with 
NX?

Mark

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2004-07-10 05:35

Message:
Logged In: YES 
user_id=31435

You'll really have to ask about NX gimmicks on an Athlon list.

SpamBayes is written entirely in the Python programming 
language, and that never, ever tries to execute code from a 
data region (I'm very familiar with Python's implementation)   
My only guess is that Outlook itself, or MAPI, try to do this 
when interfacing with extensions.  Or Mark Hammond is 
playing disgusting games (the only kind he knows, really 
<wink>) in the win32all Python extensions.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=988095&group_id=61702