FYI, I had an issue last week where I couldn't get an IMail program alias to run a command within a VB script that called another script.  Clearly this was an issue with IMail not calling things in the proper context and others have reported similar issues.  It's possible that if everything else checks out fine, that IMail isn't calling Declude under the context necessary to log on a network share.

Disclaimer: I'm stabbing in the dark and 9 times out of 10, things like this turn out to be the result of "user error," affectionately referred to an "ID ten T" error :)

Matt



Gerald V. Livingston II wrote:
On Sun, 1 Feb 2004 14:11:23 -0500 
Sanford Whiteman said something about Re[2]: [Declude.JunkMail] LOGFILE action:

  
No  other LOGFILE entries. The drive is there (it's a network mapped
drive actually). I can copy files back and forth on it.
      
This  is  the  same  issue  I  referred you to on the IMail Forum. The
service  accounts need rights to the share (and you should use the UNC
path).

--Sandy
    

I hadn't quite reached that point while doing the IMail logs. Went off on a
tangent and decided to run Kiwi on another workstation as a syslog daemon.
Since I decided not to try to fiddle with the registry to make IMail's
syslogd point to the shared drive and I have Kiwi running ON the log box I
never bumped into the permissions problems. 

Now I just need to figure out HOW to get WinXP to actually give full
permissions on that drive to ANYONE who accesses the share.

You said I should use the UNC -- will 'LOGFILE \\machine\sharename' work in
declude also?

  

-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================

Reply via email to