Port 25 blocked

Well....the reason the port is blocked is it is the smtp port for outbound email. Organizations that block it prevent email viruses (that have their own smtp server built into the virus) from mass emailing outside their company. A better way to prevent viruses is to require everyone to have and maintain some type of virus control program, but some companies are too cheap for that (this is a cheap way to block outbound viruses) or they may want to block 35 to make doubly sure no email viruses are getting out.With that said, there isn't much you can do about the port 25 block. But in any case, you probably shouldn't be doing the email thing anyway because it requires the user to have email configured in the browser (or at least able to bring up an email client) and have access to an smtp server. What if, for example, someone was sitting at a machine that had no email client on it and took your test? Unless you can guarantee that won't happen, you are actually creating problems doing tests this way.Instead,I would have it post to a CGI script on a server and have the server email the responses to the appropriate person. (Or the cgi script can place the responses into a database such as Access or SQL2K). This approach would get around the port 25 problem but, you will need access to a server that can either store the data in a db or email it out from there.I have an asp file that will email the data out from the server. (You would just have to get the company to unblock 25 for that one server, assuming the server is inside their network, and that unblocking is easy to do.) The ASP file works in IIS5/Win2K. I can send it to you if you want.Jeff