Dave, Wednesday, October 23, 2002 you wrote: DK> Yes the server admin in question SHOULD have setup their firewall DK> to address the problem, but clearly if IMail crashes at that low a DK> level of scans, it has some problems that need fixin'.
This is certainly not accurate in my experience. However it is certainly easy enough to test if you have doubts about it. Ipswitch uses some sort of modified Apache code. It was never vulnerable to code red. Moreover unless you were running web mail directly on port 80 the chances of code red finding web mail was not even very high. There have been buffer overflow exploits reported and all have been promptly patched by Ipswitch. Imail has a number of faults but this just isn't one of them. A number of folks set up IIS servers to provide images for the web messaging server and also to allow redirect webs from standard port 80 to whatever imail's server is running. And this is done for various reasons. Imail's web server does not handle images particularly well but using an IIS or some other web server helps solve that issue. So that may be where some of the code red issues arose. The general complaints regarding web messaging as I recall: 1) non-port 80 defaults 2) images 3) AOL (and other changing IP) login problems 4) the indexing of messages especially under high volume 5) fixed session timeout at 12 minutes 6) issue with saving messages sent messages 7) then the people who insist on keeping mega-size mailboxes That's about all I remember. 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/
