Considering I used this almost a year ago, it is possible your results are much different than what I had. I ran this for over a month and the scripts I had created worked great. Of course the constant faulting and restarting made this unusable the SMTP scripts did appear to be executing correctly. At one point I even added database logging to a mySQL server in the script text and it also worked fine but that was the first thing I removed when I noticed the faulting and restarting.
The cause of the fault/lockup has been identified and patched. The fix is only available for the 3.5 release and can be downloaded here: http://www.mailenable.com/beta/SMTPSCR_35.zip
It can be run on versions prior to 3.5, but you would need to ensure that you have installed the VC 9 runtime.
The issue in question related to the fact that the SMTP Connectors main thread not coinitializing - which was leading to com environment initializers and destructors firing as scripts were being processed.
MailEnable wrote:The cause of the fault/lockup has been identified and patched. The fix is only available for the 3.5 release and can be downloaded here: http://www.mailenable.com/beta/SMTPSCR_35.zip
It can be run on versions prior to 3.5, but you would need to ensure that you have installed the VC 9 runtime.
The issue in question related to the fact that the SMTP Connectors main thread not coinitializing - which was leading to com environment initializers and destructors firing as scripts were being processed.
Ben:
Will this functionality be offcially supported in the 3.5 release? From a developers view point the functionality would be very useful. Being able to drop during the SMTP session would improve the overall performance of filtering agents
MXSCAN :: AntiSpam & AntiVirus for MailEnable (now with Spamtrap/Honeypot!)
Built-in SpamAssassin, Clam, MessageSniffer, DNSBL, URLBL, DCC, Senderbase, SpamTrap, ShortCircuit, Content Filters, Disclamers, Archiving and more.
Visit www.mxuptime.com
i have been testing the new beta release and so far it works quite well. However, with the default script provided you have to disable the DATA Script Status=0 in the registry or it will throw an error 503
However, both the "RCPT Script Status" and "MAIL Script Status" appears to work.
Ben: My question here is there a way to specify an alternate script to call instead of SMTP-Inbound.VBS. Can we call something else instead?
Thanks
MXSCAN :: AntiSpam & AntiVirus for MailEnable (now with Spamtrap/Honeypot!)
Built-in SpamAssassin, Clam, MessageSniffer, DNSBL, URLBL, DCC, Senderbase, SpamTrap, ShortCircuit, Content Filters, Disclamers, Archiving and more.
Visit www.mxuptime.com
I tried this with the 3.63 Enterprise eval and it does NOT work with it either. I have put the script in several places and can not get any event to fire, not RCPT, MAIL, or DATA!
At this point I would be happy if I could get "RCPT Script Status" and/or "MAIL Script Status" to work like polarisie mentioned.
Is this not supported in eval mode? Anyone have any thoughts?
I know that the scripts will not run on 64 bit windows in current version 3 releases (Version 4 beta has the fixes).
Perhaps run filemon and monitor the smtp connector and see where it is looking for thr script and whether it is finding it. This should also allow you to see whether there is a permissions problem accessing the script.
MailEnable wrote:I know that the scripts will not run on 64 bit windows in current version 3 releases (Version 4 beta has the fixes).
Perhaps run filemon and monitor the smtp connector and see where it is looking for thr script and whether it is finding it. This should also allow you to see whether there is a permissions problem accessing the script.
I found the location with Procmon.exe filtered on MESMTPC.EXE. Once I had that and moved the VBS file, "RCPT Script Status" and "MAIL Script Status" started working as expected.
The "DATA Script Status" still does not work, but two outta three ain't bad...