Hello

Keep in mind that the SYSTEM account is very special ... (can't access
shares , ...)
And the default directory used can be ... %SYSTEMROOT%/SYSTEM32 ...?

Allways specify full files paths or make sure your program cd to its =
working
directory at start (or with a .cmd file)

On my windows installation i also use a user account for running the =
xmail
service (security purpose, can access shares, ...)
and for example, the temp dir used by xmail to put temp files for =
filters is
the one specified in the user profile temp var, not the system temp dir =
(so
isolate xmail and filters work from system work)
(in case this info help ...)

Francis


> -----Message d'origine-----
> De : Sergio Casagrande [mailto:[EMAIL PROTECTED]
> Envoy=E9 : mercredi 18 f=E9vrier 2004 18:14
> =C0 : [EMAIL PROTECTED]
> Objet : [xmail] R: Re: mailproc external Windows 2K Server
>=20
>=20
> I had a problem like this.
> I solved it calling program with:
> "c:\winnt\system32\cmd.exe /c C:\Progra~1\batch\XMail\command.cmd"
> I hope this can help.
> Ciao.
> Sergio C.
>=20
>=20
> -----Messaggio originale-----
> Da: Terry L Fritts [mailto:[EMAIL PROTECTED]
> Inviato: mercoled=3DEC 18 febbraio 2004 16.33
> A: Terry L Fritts
> Oggetto: [xmail] Re: mailproc external Windows 2K Server
>=20
>=20
>=20
> I posted about my problem executing an exe from a command alias or
> from mailproc and wanted to report the issue.
>=20
> I had set up a mailroot\scripts directory and had my programs in that
> folder to run.  The programs each opened a log file extended,=20
> wrote a =3D
> line
> with the arguments passed, closed, and exited.  The log file name was
> of the form "program.log" - no path information.
>=20
> So just to review the issues:
>=20
>    Perl script worked called thusly:
>      "c:\perl\bin\perl.exe c:\mailroot\scripts\test1.pl"
>=20
>    Wsh vb script worked:
>      "C:\winnt\system32\cscript.exe //T:120 =3D
> c:\mailroot\scripts\test2.vbs"
>=20
>    Direct exe did not (seem to) work:
>      "c:\mailroot\scripts\test3.exe"
>=20
>    And I thought this because I could not find test3.log.
>=20
> So in the course of searching for this I moved the test3.exe program
> to the C:\winnt\system32\ folder and changed my cmdalias line
> accordingly.  Sent and e-mail and then looked for the log file in the
> c:\winnt\system32\ folder.
>=20
> And sure enough it was there which left me very puzzled since the
> permissions were exactly the same.  But, suddenly, I noticed there
> were other entries in the log file.  So I switched back to the
> original and sent another e-mail and sure enough the log file in
> c:\winnt\system32\ folder was updated.
>=20
> I am certainly no Windows expert but I assume that the context of the
> system user must somehow default to the C:\winnt\system32 directory
> (not that that seems strange really) and so the log file was written
> there since I didn't give it a better path.
>=20
> I suppose the lesson must be that you have to really define the file
> paths used in the executables.
>=20
>=20
> Thought I'd report in case anyone else was having trouble.
>=20
>=20
> Terry Fritts
>=20
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe xmail" in
> the body of a message to [EMAIL PROTECTED]
> For general help: send the line "help" in the body of a message to
> [EMAIL PROTECTED]
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe xmail" in
> the body of a message to [EMAIL PROTECTED]
> For general help: send the line "help" in the body of a message to
> [EMAIL PROTECTED]
>=20
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]

Reply via email to