I am having problems with the message screener. I followed the instructions that I obtained from this site. When I turn it on the IIS server queue starts building. It will send a few messages through but I'm not even sure how it decides what to let through. When I turn it off and resart the SMTP service (which takes much longer than I have ever seen) the messages are then sent on to their intended recepients. I have not modified any of the rules in the SMTP Filter yet. Please assist as this is driving me nuts.
I set up a standalone IIS machine that the message screener is installed on. Everything works fine until I install the message screener. When I install it (and reboot) the messages start getting hung in the Queue. I have configured the ISA server as directed and ran SMTPCred on the IIS server. The ISA server has been up and running for some time with all of the necessary DCOM mods. One thing I have not tried is at the very end of the process. Restarting the ISA server and then restarting the IIS server. Essentially to test I am Changing the SMTP pointer to the Message Screener Computer, Enabling the filter, and restarting the Firewall service. I tried testing the functionality of the IIS server before I add it into the mix. Is this not possible to do? Well Im not sure where to go from here. I've been going through the process of installing and uninstalling SP's in hopes that that was an issue. As it stands the IIS server is SP3, with all of the critical fixes. The ISA server is SP2 (because when the server was set up adding some of the hotfixes that were avail., caused the server to not have internet access and I have been afraid to upgrade it ever since :-) Thank you for your help
Sorry I forgot to answer whether or not is was a relay for outgoing. It is a relay for outgoing mail. If any of our out of office users connect via SMTP and send a message then the server sends the mail directly.
Not sure how things are configured *exactly*, but you may be having a problem with your relay configuration. Remember that requirements for incoming relay and outgoing relay are different.
However, no matter how you have your relay configured, it would not have any effect on the SMTP Message Screener. I *always* restart both the ISA Server and the SMTP server, although you may not need to. Its something I do so that I don't have to mess around with things for 6 hours, at which point I'll end up restarting the servers anyway
The relay was working fine until I setup the Message Screener. Then (when I look at the logs) messages that are submitted are not sent for One minute. Then it sends 3 messages. Waits till that same minute marker (which is 30 seconds after the minute) and sends 3 more. If in uninstall the message screener it sends them all immediately. Am I missing something? This is so perplexing.
P.s. I tried restarting it properly with no success.
I am comparing the Metabase for Both the SmtpSvc and "1" for a server that has the Message screener installed and one that does not. These are the differences that I've noticed that may be relevant.
SMTPSvc: Not on Message Screener Machine Id: SmtpAdvQueueDll 36987 Data Type: String Data: C:\WINNT\System32\inetsrv\aqueue.dll
"1" Not on Message Screener Machine Id: Blank 1012 Dword Data:1
Interesting. Not sure what it means, but there may be some performance issues with the Message Screener. I suspect you might see some fixes in the near future.
I agree that its odd, because I've installed dozens of SMTP Message Screening machines without problems. Its got to be a subtle configuration problem or network design issue. But what it is?
SP3 hasn't been a problem that I'm aware of. I don't install hotfixes unless I see a compelling reason to do so I always have to test them before installing them, to make sure they don't break something important (which they often do). When doing my testing, I have to install them one at a time, test, install another one, test, install the next one, test. Its very time consuming but makes it a lot easier to troubleshoot what HF broke the computer
All right. I think Im finally getting somewhere. The problem is with the ISA server not the Screener. I can successfully set up the Screener in Stand alone mode but not in enterprise mode. Exact same server. Uninstall and reinstall and set up in Stand Alone works fine. Uninstall and reinstall and set up in Enterprise mode then I get the problem I described.
Interesting! I haven't heard of a similar report, but you could be the first one. I haven't tested this configuration, as most of the enterprise policy customers use a 3rd SMTP screener like MailEssentials or MailSecurity