|exit /b 0 |exit /b 19 | |Is that right ? It does not matter. Command "exit x" would exit batch and command interpreter with errorlevel x. Command "exit / x" would not exit command interpreter but only the batch file. Because in this case the only thing = to be run is this batch, it works with "/b" as well as withount it.
|Then, your solution rejects spam. Maybe you could consider=20 |adding a second parameter to allow marking without=20 |rejecting. Leaving the reject decision to the end user's MUA=20 |filtering system ? The main problem is that SpamAssassin does not produce XMail-compatible message, the "pseudo-headers" on top are not present. So this is over = the possibility of simple batch file. I am now working on modification of my XMail-WAI, which would work the following way: filter would move (unmodified) spam messages to separate folder and you would be able to read them via web interface. They would = be kept there for defined time (about a week). -- Michal Altair Val=E1=B9ek, Microsoft MVP - ASP.NET=20 ASP Network - v=B9e o Microsoft technologi=EDch pro Internet _________________________________________________________________________= __ http://www.aspnetwork.cz/ | [EMAIL PROTECTED] There is no place like 127.0.0.1=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]
