Home > Articles > Programming > Perl

www4mail Technicalities — A Road Map, Statistics, and Future Developments

  • Print
  • + Share This
Even though www4mail is quite young, the software is evolving rapidly due largely to extensive user feedback. The resulting software product available today is quite reliable, even though it is still undergoing continual development and improvement. Read this article for a discussion of Version 3.0, some typical usage statistics, and a look toward www4mail's future.

The www4mail software is written in modular Perl because it has good string processing, pattern matching, and pattern replacement functions. The www4mail Perl code has undergone three major public releases, each of which are described in general.

Version 2.0: The first public release dated December 1998, and depended greatly on the Lynx text mode browser. In fact, it required patching Lynx 2.8.1 in order to support cookies when working in dump mode. The www4mail Perl script was run via sendmail or some other Mail Transport Agent (MTA) and was quite large. Because it was not very memory efficient, it quickly faced problems as soon as the user base grew. In addition, the string processing functions were not very strong. Sometimes, for example, unusual characters such as regrex meta characters and patterns appear, break the software, and generate an error report to the user.

Versions 2.2 - 2.4.x: Released in May of 1999. The 2.2 series marked the appearance of an internal browser function. www4mail depended less on Lynx for http requests but still used Lynx for ftp and other non-http requests. This version also introduced a private spooling system for www4mail processes along with an AUTOLOAD routine for loading sub-routines on demand. This autoloader was simple and based on the Perl generic autoloader routines. This basically improved memory usage, but was not optimal. There were issues with mail loops in the earlier versions, which were resolved in later releases. A key signpost included the introduction of multi-lingual user interfaces.

Version 3.0: Release Candidates for Version 3.0 were made available in May of 2001. This series marked a rewrite of the www4mail code, which is cleaner and more portable. This version presents a completely new architecture with emphasis on easily adding new functionality to the www4mail server.

Version 3.0

The new Version 3.0 architecture is an integration of dynamic module (subroutine) loading and unloading on demand and the ability to register one or more module(s) as plug-in(s) to another module. In order to archive this new architecture, a novel, more robust autoloader was developed with the following three characteristics:

  • The ability to automatically load Perl sub-routines (modules) from external files.

  • The ability to evaluate certain test conditions (as required by modules) before loading modules.

  • The ability to run other modules and plug-ins immediately before or after a module. Essentially this means that before running a subroutine, www4mail can evaluate certain test conditions that are required for the correct functioning of the module. If the tests fail, the module is never loaded. This procedure has drastically improved the memory usage of the server process, as only the necessary modules required to fulfill a request will ever get loaded into memory.

The third characteristic mentioned here, allows the server to natively know just a few modules and all other modules and routines are called based on their association with the native modules. The core and native modules are a reflection of the various processing stages required for each Email received. These modules are named as follows:

  • load_modules_list: Loads and defines a meta information block for all available modules. Each meta block has information about the source file on disk, the various tests required by the module, the list of plug-ins attached before and after a module, any alternative routines to this module, and any flags (indicating whether the module is to be reloaded from file each time it is called or if the module should only be run once during program runtime).

  • init: Performs the initial initialization, which usually means defining suitable default values for most variables.

  • cmdline: Processes the command line arguments.

  • lireadmail: Collects the user's email from STDIN or from a local spooled file.

  • maincfg: Loads the server configuration files.

  • userauth: Authenticates the user's email address along with a preliminary quota check.

  • daemon: Breaks the connection with the parent sendmail process, if so configured.

  • parsemail: Checks the user's email and applies (if necessary) MIME or other suitable decoders.

  • globalcmd: Checks for and processes the global commands.

  • process: Performs a loop that processes the user's requested URLs one at a time.

  • endrun: Performs actions before closing, such as updating the error log file, cleaning up temporary files, and exiting.

It takes an average of one to two seconds to go from the init stage to the process stage during runtime; all modules and plug-ins here are only run once during the lifetime of each run. The process stage basically loops around the following items:

  • urlauth: Checks the local ACL files to see if this URL is permitted.

  • urlduplicate: Checks if the URL was previously processed within the session. Some users send their requests in a MIME multipart with both a text section and an HTML section.

  • urlspool: Checks to see if the computer is currently busy or if the configuration demands that the request be queued.

  • browser: Responsible for downloading the HTML page or binary file from a remote server. For HTML pages, additional tasks include removing line breaks from within tags and also including external scripts, style sheets, frames, and layers. This module and its plug-ins may take anything from two seconds to several minutes — as dictated by factors such as network speed and the number of external scripts, style sheets, frames, and so on.

  • fileauth: Checks the resulting file based on local ACL configurations. At this stage, it can deny the request based on the file extensions, MIME type of file, appearance of one or more keywords or phrases, and even the pics rating system. When www4mail encounters a binary file, as a result of an http request, it will run the ACL check on the main page of the site. This generally involves one or more calls to the browser module.

  • filter: Applies the necessary HTML code transformations and generates the user's desired output.

  • reply: Codes the data (file) and mails it to the end user.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020