Web-based POP3 Domains Admin Utility Setup Help

[System Requirements]  [Synchronization]  [Security]  [Admin Usage]
  • System Requirements -- this web-based component is designed for use with DAWKCo POP3 Server Hosting Version and requires the following system configuration(s).


    • Pentium class processor(s) (I / II / III / IV), or compatible
    • Windows® 2000 Server operating system
    • Network interface card (or equivalent) and TCP/IP protocol
    • Fixed disk with NTFS file system format
    • IIS (Internet Information Server) v5.0 with a World Wide Web Publishing Service default website
    • DAWKCoTM POP3 Server Hosting Version 5.0 (or later)


    The web pages output from the utility should work well with any Internet Standards based web browser, regardless of operating system, that conforms to the following W3C (World-Wide Web Consortium) standards:

    • HTML 4 (Hyper-Text Markup Language)
    • CSS 2 (Cascading Style Sheets)
    • ECMA 2.62 Scripting (European Computer Manufacturers Association), a.k.a. JavaScript, or JScript

    That includes current web browser versions from Microsoft®, Netscape® and Qualcomm®, and online services such as AOL®, CompuServe®, MSN®, Prodigy® and others.

    Password Inputs Note: with some web browsers, including Netscape Navigator v6, you must not "copy & paste" values into web form Password inputs. If you do, invalid input will be generated. Therefore, if you are using such a browser, you must type your password entries.

    ^Top^     [Close Help]
  • POP3 Synchronization -- full synchronization between the POP3 Server Service, the MailDaemon e-Mail Routing Service, the WebMAIL Extension for IIS, the stand-alone executable POP3 Admin Utility, and the web-based POP3 Domains Admin and POP3 Password Changer Utilities is provided by the software.
    Specifically, simultaneous configuration updates being performed by different parties that might cause conflicts or collisions are blocked in a FIFO (First-In-First-Out) queue fashion by using system global named Mutex (Mutual Exclusion) and Event synchronization objects and Interlocked Variables. While this method should prevent crashes and/or data corruption due to collisions during configuration write operations, it presents the possibility of time delays and/or time-outs during a wait for ownership of an object.
    All of the DAWKCo mail services and utilities (including web-based) will use a default synchronization wait time-out value of 60 seconds, unless you override that value by setting Windows System Registry key values. Although there are necessarily two storage locations for the "Sync Wait Timeout" values (one location for the POP3 Server, MailDaemon and the stand-alone executable POP3 Admin Utility, and another for WebMAIL and the web-based POP3 Domains Admin/Password Changer Utilities) they should always be set to the same value in the range between 20 and 300 seconds, at the following registry key locations--
    WebMAIL and Web-based Utilities:
     Sync Wait Timeout
     20 - 300 (0x14 - 0x12c)
    POP3 Server, MailDaemon and stand-alone POP3 Admin Utility:
     Sync Wait Timeout
     20 - 300 (0x14 - 0x12c)

    Note: changing this setting is usually not necessary, but if you do, make sure that you enter the same value in both locations. Failure to do so could possibly cause one mail service or utility to block another long enough to cause mail routing failure (Badmail). As mentioned above, a "default" Sync Wait Timeout value of 60 seconds is set at the time of installation. If you set the value outside the range between 20 and 300 seconds, either the minimum or maximum value will be used depending on whether your setting was less than the minimum or greater than the maximum.
    Since configuration updates made with the web-based utilities are discreet in nature, in other words they affect only a mailbox or mailboxes within a domain, they do NOT require the server mail services to be restarted. This includes adding, updating and removing domains and mailboxes. Updates made using the stand-alone executable POP3 Admin Utility, on the other hand, are global in nature and can affect all of the domains and mailboxes within the site; therefore, updates using the POP3 Admin utility require automatic mail services restart during updates. The impact is lessened by the fact that the utility stores up all the configuration data and applies all the changes in a quick batch between services stop and restart.
    Note: if a web-based admin operation times out, it's most likely that Mutex ownership for an object could not be obtained due to a sharing conflict. If you get a "cannot find server, or DNS error" message from the web browser, then it's likely that the web-based admin context initialization failed because the default website was being restarted during a global update by the stand-alone executable POP3 Admin Utility. In either case, just try again.
    ^Top^     [Close Help]
  • Security Considerations -- in order for the DAWKCo WebMAIL process to properly authenticate and impersonate users, using the same techniques used by the DAWKCo POP3 Server for Windows Logon authentication and impersonation, the IWAM_machine "Launch IIS Process Account" User account must be granted the TCB (Trusted Computer Base) privilege. The privilege is required by the operating system for any process that performs Windows Logon functions. (According to Microsoft, that requirement will be eliminated in the next version of Windows server operating system ("Whistler").
    To minimize any potential security risk, the DAWKCo WebMAIL process is isolated from the IIS process, and the process security context is immediately switched from that of the IWAM_machine account to the account controlling access to the logged on POP3 client's mailbox. Additional security measures have also been introduced, for example, stronger encryption of Windows Usernames and Passwords in a form that is different from that used by the POP3 Server, as well as other data obscuring techniques. In any event, even if a hacker were to hack a POP3 Alias/Password combination, a client's mailbox is as far as they would get.
    See also, the "Web-based Mailbox Creation Notes" below.
    ^Top^     [Close Help]
  • Admin Usage -- only mailbox owners designated as a POP3 Domain Administrator in their mailbox properties may administer the mailboxes within their domain using this web-based utility. Additionally, IF the Site Postmaster e-mail address is a locally defined mailbox AND the user type is set to Administrator in that mailbox, then Site Administrators may gain access to administer all of the POP3 domains within the site by using the Site Postmaster e-mail address and password to login to this web-based utility. The locally defined Administrator type Site Postmaster also has access to the WebMAIL Color Scheme Settings through this utility.
    Note: mailbox owner type settings have nothing to do with Windows user account types or privileges. POP3 Domain Administrators are merely given access to configure the mailboxes within their domain (or domains for Site Admins) using this web-based utility.
    Complete Help documentation on all features and use of the utility is provided via help links on the utility's web pages. POP3 Site/Domain Administrators access the web-based POP3 Domains Admin Utility at the following location:
    Where <default_website_domain> is replaced with the domain name, or virtual domain name, for your IIS web server default website.
    • Logon Procedure -- logon to the web-based POP3 Domains Admin Utility by entering your POP3 mailbox email address and POP3 password into the appropriate input fields on the "Logon" web page, and then click the Logon button. For additional details, see the Help link on the "Logon" web page.
    • Session Expiration -- for security purposes, this web-based utility's admin sessions expire after a period of inactivity that exceeds a preset time delay--the Session Timeout value. If no actions are performed during a time period greater than or equal to the session timeout value, the session expires and the administrator must login to the web-based utility again before any new tasks can be accomplished.
      The default session timeout period is 10 minutes, but may be adjusted between the values of 10 minutes minimum and 60 minutes maximum in the WebMAIL Session Timeout text edit/spinner control of the WebMAIL Setup dialog, which is accessible from the Network Settings dialog of the stand-alone executable POP3 Admin Utility.
    Web-based Mailbox Creation Notes: in order to facilitate web-based creation of new POP3 mailboxes without having to send Windows User Account information over the network, two (2) default mailbox creation template Windows User Accounts are created when you install the POP3 Server software. One account (named "P3Box.GenUser0") is for normal User type mailboxes, and the other (named "P3Box.GenAdmin0") is for Administrator type mailboxes. The default mailbox creation template Windows Accounts must not be renamed, and their passwords must not be changed.
    However, you can override the use of the default mailbox creation template Windows Accounts by defining specifically named mailbox creation template POP3 Mailboxes in the default local domain, in which you are allowed to change the controlling Windows Accounts/Passwords using the stand-alone executable POP3Admin Utility, and thereby increasing your system and network security. This also facilitates preconfiguring new mailboxes with commonly used properties.
    If you define these mailbox creation template Mailboxes, then a new mailbox created using the web-based "POP3 Domains Admin Utility" will inherit the properties of the template mailbox in a manner similar to mailbox cloning.
    The specific "Override" mailbox creation template POP3 Mailboxes must be created in the Default Local Domain and must have the following Primary Aliases:
    User type: 
    Administrator type: 
    Also, in order to function properly, a override template mailbox must use the installed POP3 Server software Serial Number as the POP3 Password for the mailbox.
    The template mailbox primary aliases were so chosen because it is highly unlikely that anyone would use such a name for a real mailbox. However, after you create the override template mailboxes they will appear in the list of mailboxes. Even though they are not actually intended for receiving e-mail, they could do so.

[System Requirements]  [Synchronization]  [Security]  [Admin Usage]

Copyright ©2000-2015 DAWKCoTM Software. All rights reserved.

^Top^     [Close Help]