Replace your fully qualified pop3 server name with your pop3 server's IP address in the BrowserExpress.ini file. For example, replace
POP3server = pop3.yourdomain.com
with
POP3server = 192.192.192.2

You must select Binary mode. If you do not select Binary mode, BrowserExpress will not run on your Webserver.

When executed, BrowserExpress creates a temporary file in directory that BrowserExpress is located. This error will ocurr if you have the directory where BrowserExpress executable resides set as "Read Only" from the NTFS or unix file system perspective. Additionally, in an NT environment, a temporary file is also created in directory defined by "TEMP". In a W2000 environment, a temporary file is created in the Winnt\Temp directory. When execution is completed, temporary files are deleted. Consequently whoever "owns" the BrowserExpress application needs write access to its corresponding directory. In an NT/2000 environment this user is usually IUSR_System_Name. In a 2000 environment, one must explicitly add this write access to the Winnt\Temp directory. In the NT/2000 enviroment: Right click on the directory, select Properties, Security, Permissions to add write access to the owner of BrowserExpress process. [In an IIS environment one does NOT need to enable write access from the IIS admin GUI. Script/Execute access is the only box that should be checked!]

This error will ocurr if you have the directory where BrowserExpress executable resides set as "Read Only" from the NTFS or unix file system perspective. Additionally, in an NT environment, a temporary file is also created in directory defined by "TEMP". In a W2000 environment, a temporary file is created in the Winnt\Temp directory. When execution is completed, temporary files are deleted. Consequently whoever "owns" the BrowserExpress application needs write access to its corresponding directory. In an NT/2000 environment this user is usually IUSR_System_Name. In a 2000 environment, one must explicitly add this write access to the Winnt\Temp directory. In the NT/2000 enviroment: Right click on the directory, select Properties, Security, Permissions to add write access to the owner of BrowserExpress process. [In an IIS environment one does NOT need to enable write access from the IIS admin GUI. Script/Execute access is the only box that should be checked!]

The attachment was probably greater than the MaxAttachment size specified in the BrowserExpress.ini file. You should be able to send attachments without problems up to the size limit specified by MaxAttachment.

If you experience the POP3 box $lockfile problem, you need to increase the value for Delay or DelayList in your BrowserExpress.ini file.

From a command prompt, run the three commands listed below on the Webserver on which you intend to run BrowserExpress. Mail the output to support@progressivesoft.com. PSS will send you a compiled version of BrowserExpress that will work on your platform. Please note that the last command is not in single quotes--the command itself includes the back ticks (the key left of the "1" key on many keyboards). The three commands follow: strings BrowserExpress.cgi | grep lib ls -l /lib /usr/lib ldd `which perl`

We are a small company located in Alexandria, VA. Yes, BrowserExpress was made in America! But, our reach is global with satisfied customers on six continents. Customer support for BrowserExpress is free via e-mail - we want you to be satisfied with BrowserExpress.

Yes BrowserExpress is readily customized. For samples with source code to customize your BrowserExpress interface, please goto http://www.progressivesoft.com/BE-Custom/BE-Customize.shtml

Our next version of BrowserExpress is expected to be out by the end of August, 2000. It will include this feature. Remember, those who purchase BrowserExpress are entitled to free upgrades for one year from the purchase date.

From a command prompt, run the command listed below on the Webserver on which you intend to run BrowserExpress.
Mail the output to support@progressivesoft.com.
PSS will determine if we can send you a compiled version of BrowserExpress that will work on your platform.
Please note that the command is not in single quotes--the command itself includes the back ticks (the key left of the "1" key on many keyboards). The command follows: ldd `which perl`

For redhat Linux: libnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.6 => /lib/libc.so.6 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Slackware Linux: libnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.5 => /lib/libc.so.5 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Caldera Linux: libnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.5 => /lib/libc.so.5 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Cobalt Linux: libnsl.so.1 => /lib/libnsl.so.1 (0xcaacd000) libdb.so.2 => /lib/libdb.so.2 (0xcab14000) libdl.so.2 => /lib/libdl.so.2 (0xcab67000) libm.so.6 => /lib/libm.so.6 (0xcaba9000) libc.so.6 => /lib/libc.so.6 (0xcac0d000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xcad22000) /lib/ld.so.1 => /lib/ld.so.1 (0x00000000) For FreeBSD: libperl.so.3 => /usr/lib/libperl.so.3 (0x28063000) libm.so.2 => /usr/lib/libm.so.2 (0x280f4000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2810f000) libc.so.3 => /usr/lib/libc.so.3 (0x28112000) For other operating systems: Please send the output to support at progressivesoft.com

BrowserExpress provides a capability for address book support via LDAP databases.
If you go to our demo at http://www.progressivesoft.com/cgi-bin/BrowserExpress1.exe you will see that there is a place for the name of your LDAP server. The demo is currently set for ldap.bigfoot.com as the default. For the version you are evaluating, put your own LDAP server. The following describes how you can update your .ini file to accommodate your own LDAP server:
LDAPserver = ldap.bigfoot.com
Replace ldap.bigfoot.com with the IP address of your LDAP server--or the fully qualified name of your LDAP server, e.g., ldap.your_domain.com.
The default port used is 389.
If your organization uses another port for LDAP use: port. For example
LDAPserver = ldap.bigfoot.com: 123
If you do not desire to include support for directory services, replace ldap.bigfoot.com with "NULL".
LDAPserver = NULL

You can use the Domain license to Web-enable a single mail server for a single domain.
Purchase the Enterprise license to Web-enable multiple domains.
With the Domain License, only a single mail domain is supported. The user interface for the Domain License is featured at http://www.progressivesoft.com/cgi-bin/BrowserExpressD.exe. Since it Web-enables a single mail domain, the user is only required to provide a valid POP3 username/password. Prompting the user for an e-mail address is optionally enabled to support environments where the pop3 account is different from e-mail address. Multiple copies of BrowserExpress with a Domain License can run on the same webserver, each configured and customized to support a unique mail domain.
The Enterprise License supports unlimited users and unlimited mail domains from one web server. If you support multiple mail domains from one web server and/or you wish to provide Webmail services to visitors to your Website with a single BrowserExpress application, the Enterprise License is appropriate. The user interface for the Enterprise License is featured at http://www.progressivesoft.com/cgi-bin/BrowserExpressE.exe. Since the Enterprise License supports any mail domain, the user is required to provide a valid POP3 Server, a POP3 username/password, and an e-mail address.

The X11 lib is missing in the cgi environment on BSDOS Virtual Servers. Consequently, compiled executables do not have proper path identified in your Virtual Server environment. To correct this Virtual Server bug, you must:
1. telnet to your webserver
2. log in as the user that the webserver runs as
3. issue following commands:
a) mkdir ~/usr/X11R6
b) mkdir ~/usr/X11R6/lib
c) ln /usr/X11R6/lib/*_s.3* ~/usr/X11R6/lib