Always start with a dump from sac -D. If "SacServer not responding." is displayed, start up sacserver: "start /min sacserver". Verify all the paths look correct for your installation.

Be sure to adjust registry and disk letter as necessary.

Start/Run/Cmd
cd \mail*
spamassassin < c:\Mail-SpamAssassin-3.2.5\sample-spam.txt

RESULT: marked up email should scroll by.




start "spamd" spamd -x -D

RESULT: Spamd should open in another cmd window, pause a few seconds, and then dump bunches of stuff to the console. I like to set the properties wide and long and save settings for windows of this title. Keep it so you can see it when you do the other tests.




cd \temp (or wherever)
drag a copy of a matched set of D and Q files from c:\imail\spool (or c:\imail\spool\spamtested if any are in there - they hold still better!)

spamc < De5096fe2001cc36d.SMD > test1.smd

RESULT: You should see bunches of stuff go by on the Spamd window, and c:\temp\test1.smd should now exist, and be just like the input file except with SpamAssassin headers near the beginning of the Data.




Test it again using spamccall. Your cmd window will close, but the output file will exist with SpamAssassin headers. Clipboard your command because you will use it again in the next step.

spamccall De5096fe2001cc36d.SMD test2.smd 783 10000 c:\IMail

RESULT: c:\temp\test2.smd should now exist, and be just like the input file except with SpamAssassin headers near the beginning of the Data.




If you've gotten this far, let's see if spamccall can start spamd for us. It won't have the -D switch (unless you clip the "Start" line in the module) but you'll still see it launch, and log something.

Kill the spamd that's running (The X will bring up the unresponsive dialog - Say "End Now").

spamccall c:\temp\De5096fe2001cc36d.SMD test.smd 783 10000 c:\IMail

RESULT: you should see 3 "connection failed" messages
a 10 second pause
and then spamd should start. You won't see the messages. Messages go to c:\imail\spool\sdYYMMDD.log.
Success is the final line being rc=0. The Spamd window will show nothing and the original input file will now have the Spamassassin headers in it.




If you get all these things to run, the only thing left to test is SAC itself. To test SAC, you need to point it at temp and not IMail. The last step We did overwrote the input file, so get another matched "Q" and "D" file for the final test. Change the registry temporarily so SAC can find your test file. 

NOTE: DO NOT change the registry settings for SAC if Imail is using SAC for delivery. Only do these steps if Imail is delivering via smtp32.exe.

MailProgram c:\perl\site\bin\smtp32DUMMY.exe
MailSpool   c:\temp

And be sure smtp32DUMMY.exe is in C:\perl\site\bin.

NOTE: The call to sac uses the "Q" file, not the "D" file as in all previous examples.

\imail\sac c:\temp\Qe4e56fe1001cc36b.SMD

RESULT: This time, the "updated" D file uses the same name as the original, not test.SMD, but the result should be the same.

NOTE: Be sure to change the registry settings back to:
MailProgram c:\imail\smtp32.exe
MailSpool   c:\imail\spool




Any problems not uncovered above must be related to the permissions of SYSTEM (or whomever is the userid on you Queuemanager service).