Try
this
cmd.exe /c yourbat.bat
This
will cause the command interperter to process the bat file.
Type
cmd.exe /? to get all of the paremeters for cmd.exe
Kevin
Bilbee
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] Custom SMTP delivery application
I'm stumped. Here what has/hasn't worked for getting a different delivery application to work.
1. I created a perl script and put "c:\perl\bin\perl.exe c:\mailUtility\xlate.pl" as the delivery application and got an error 123 (volume, path, or filename error)
2. I added the PATHEXT for .pl and made sure that the .pl association was present, and put "c:\mailUtility\xlate.pl" as the delivery app and got error 193 (not an executable)
3. I created a xlate.bat, which calls xlate.pl and put c:\mailUtility\xlate.bat as the delivery app and got no error, but no action
4. I (re)created Terry's mytest.bat and mytest.pl, same result as 3.
5. I wrote a vbscript program and replicated 1-2 above with the same results (except using c:\winnt\system32\cscript.exe instead of perl)
5. I simplyfied mytest.bat to just do a "copy %1 c:\imail\spool\yeah.msg", same result as 3.
6. Changed mytest.bat to "C:\Imail\smtp32.exe %1", same result as 3.
All the Imail services are running as default (SYSTEM) and all the directories have Everyone/Full Control. I've even explicitly added the SYSTEM account to have Full Control with no change in behaviour.
Ideas? I've done this before with a compiled VB6 program, so I know that it can work, at least with .EXEs...
[EMAIL PROTECTED] wrote on 10/16/2003 12:25:05 PM:
> scott,
>
> Thursday, October 16, 2003 you wrote:
> > Ok, I've tried all of these and still no joy. It seems like my
> > .bat file is not being called. I added calls to Net::Syslog to
> > it, too, and nothing. When I run it at the command prompt, though
> > it works fine.
>
> This might indicate a permissions issue. Normally IMAIL will run
> under system context. So make certain that your perl bin directory
> and perl program can be accessed by System. Frequently these have
> "everyone - all" permissions but I've seen servers where System had
> to be added explicitly.
>
> Of course if you've changed the context for IMAIL then you have to
> add that user to the perl and program permissions.
>
> Usually registry permissions are okay.
>
> It also could be that you need to include a CD to the directory your
> script is in. I've had to do this sometimes and I'm not really
> certain why. (like cd "c:\wsh\")
>
> The way to know if your alias is working or not is to look in your
> spool file for a .tmp file. You can view it in a text editor.
>
> Yes, I suspect almost all of us went through this when we made our
> first program alias. The way I did it was that I started with the
> example in the Knowledge Base. I copied it exactly and got it to
> work.
>
> http://support.ipswitch.com/kb/IM-19980116-DD11.htm
>
> You can make almost anything up for the alias though and the .tmp
> file will be created in the spool. I don't think there is much
> error reporting in the logs - maybe in debug - but I haven't tried
> it in a long time.
>
> Then I changed the bat file and kept messing with it until I got it
> to work with my perl script.
>
> But I recall this being very frustrating when I started.
>
>
> HTH
>
> Terry Fritts
>
>
>
>
>
>
> To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
> List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
> Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
