Here is a list of differences between the POP3 servers provided by PMDF and MultiNet.

  • PMDF has the new Popstore technology for a more efficient pop message store.

  • PMDF's POP servers is a multithreaded daemon process which runs under the Dispatcher starting in PMDF 5.1. Each process is capable of handling up to 31 concurrent connections. (but not too likely in real life because most POP clients disconnect right after downloading the mail). Since it is a daemon, you do not incur the process creation overhead for every POP client connection coming in. The startup time in the MultiNet's POP server includes process creation for every connection which can be significant.
  • PMDF does not run the system-wide LOGIN or user's LOGIN.COM, nor does it create any .log files in the user's directory.
  • PMDF's POP3 server always reads the NEWMAIL folder. Messages read but not deleted are either filed into MAIL folder like VMSMAIL (when POP3_MOVE_READMAIL is set to 1 in pop3d.cnf) or left in NEWMAIL (the default behavior in PMDF 5.0 or later).
  • When new mail is deleted after reading by the POP3 client then it goes into the WASTEBASKET folder and is purged if you have AUTO_PURGE on and kept there if you don't have AUTO_PURGE on. PMDF's POP3/IMAP server never compresses your mail file.

    MultiNet provides logicals names which can be defined in system table or in the user's LOGIN.COM to change the from/to folder names.

      MULTINET_POPx_SOURCE_FOLDER    (which folder to read 
                                     instead of NEWMAIL)
      MULTINET_POPx_DEST_FOLDER      (where msg is moved 
                                     after it is read)
      MULTINET_POPx_FLAGS            (read only NEW msg, 
                                     move to MAIL after 
                                     reading, quick close, 
                                     compress mailfile)
            
  • PMDF's POP3 server uses PMDF's logic for processing addresses. MultiNet's does not. Normally the two are close enough that there aren't any problems, but if you use any of the more advanced address mapping facilities in PMDF (e.g. VMSMAIL-TO-PMDF mapping, headertop/headerbottom control, etc.) Multinet's server won't understand what going on and you'll end up with trashed addresses.
  • PMDF supports MultiNet, TCPware, and DEC's TCP/IP services for VMS(UCX).
  • PMDF provides a better IMAP server than TCPware or MultiNet. IMAP is a much better and richer protocol, more useful than POP. IMAP will probably be overtaking POP in popularity as people outgrow POP3.



Search: