Scott, Thanks for the technical insight - yes, I understand the challenges and remember this from your earlier feedback.
However, with the new "suits" in charge, I though it was worth mentioning again for two reasons: 1. If it was easy, we would all do it ourselves :-) 2. With a bigger company now, the investment in time/people/money might be feasible to solve it a "better way" than just slaving off the Imail limitations. 3. If your new business goal is to be more general-purpose, then NOT trying to use IMail web server is a good thing. Gen-up an end-user GUI using IIS or your own embedded server and give us the option to use a dedicated IP address and port 80, or any host header combo (ip, header, port) for maximum flexibility in the firewall issue. A common trend is for network apps to have web-based GUI configuration/control. Most include their own "run-time" web server or else they put a stake in the ground and require IIS or Apache. For example, Lyris Mailing List Server (embedded TCLweb), LiveStats Log Analysis (requires IIS), and of course IMail (Embedded Apache?) Not trying to design it, but personally I would prefer a solution that is not dependent much on Imail itself and either has it's own embedded server or runs under IIS/ASP.NET -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry Sent: Monday, July 12, 2004 12:51 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] GUI - End-User is the priority! >Something getting lost here in the discussion of the installation GUI is >the request from time-to-time for an end-user GUI. This is something that we would love to do -- and would have been done *years* ago if Ipswitch allowed third-party access to web messaging (with about 20 lines of code, they could). The problem is that it requires packets going to and from your mailserver and your clients. If we don't use IMail's web messaging, we have to either write our own webserver, or come up with our own protocol for transferring the data. Worse, firewalls become a huge issue -- not only do you have to make sure that *your* firewall can handle packets on oddball ports (since the standard WWW port 80 is usually taken on an IMail server), your users do too. Some of your users will have firewalls preventing them from sending to non-standard ports. That's not to say that we won't come up with an end-user GUI -- it's just that it becomes very complicated (much more so than a GUI for our customers). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
