#!/usr/bin/perl
#!c:/perl/bin/perl.exe
# The above line may need to be changed to reflect the location of
# the perl interpreter on your system. Use "which perl" on a Unix system
# to make a noble attempt to locate your perl interpreter. If you are
# installing this on an NT IIS server then you probably do not need to
# modify this line because it will most likely be ignored. Apache under
# NT generally DOES require the top line to be configured. We have provided
# two common paths above as examples, only the top line will be used, the
# second line is just there to provide an example.
############################################################################
# POP3Mail, Standard Edition, version 2.3
#
# Copyright (c) 2000, Indian Magic. All rights reserved.
############################################################################
package mailman;
# Enable these while you are working on modifications. Make absolutely
# certain that 'use strict' is NOT enabled in production installations.
# CGI.pm and 'use strict' are not compatible, if you have 'use strict'
# enabled then your users will not be able to upload files because CGI.pm
# provides uploaded files using a bizarre on-the-fly file handle that will
# cause an error if you have 'use strict' enabled. We think that this is
# ugly too, but there is no way around it at the moment.
#use strict;
#$^W = 1; # Warnings.
# Version information that might find its way into output.
$mailman::strPOP3MailVersion = 'v2.3';
$mailman::strPOP3MailEdition = 'Standard Edition';
# Variable initialization. Clean and neat and all, but very necessary
# for mod_perl.
InitializeVars();
############################################################################
# This section contains a few variables that you might need to set in order
# to get POP3Mail functioning properly. If your installation is working,
# then you don't need to worry about any of these.
############################################################################
# Location Attachments
# When a user selects an attachment from a message for downloading,
# POP3Mail generates that attachment on-the-fly and sends it through the
# HTTP server to the user's browser. POP3Mail includes the necessary
# HTTP header information for the user's browser to determine the
# file name, but many broswers, most notably Microsoft's Internet
# Explorer, either ignore these headers or just don't handle them
# very well. The result is that when a user downloads an attachment,
# your browser may present the user with a "Save As" box with the
# file name filled in as the name of this script, a string or random
# characters, or any number of other un-graceful things. We think that
# the best solution to this problem would be for browser makers to
# pay attention to HTTP headers, but until then we provide a mechanism
# for working around the problem. If you set up a directory that is
# writable by POP3Mail and readable by your web server, then POP3Mail
# will write out the attachment file to that directory temporarily,
# and redirect the user's browser to that file. When the user logs
# in or out POP3Mail will ensure that the user's files in this
# temporary directory are removed. A user that exits POP3Mail without
# logging out and never logs back in could potentially leave stale
# attachment files on the server, so occasional monitoring of the
# temporary directory for stale files would be appropriate. Also note
# that this mechanism could be considered a privacy problem since a
# user's attachments are deposited temporarily into a world-readable
# directory rather than generated on-the-fly the way POP3Mail normally
# would do. We have left the decision up to each individual
# administrator as to whether or not to use this feature. Most people
# seem to prefer allowing POP3Mail to generate attachments on-the-fly
# for simplicity, ease of administration, and security/privacy, but
# some people think that the attachment file name thing is a critical
# issue. The decision is yours.
# To use this feature, create a directory that is readable by your
# web server and writable by the user that POP3Mail runs as. Set
# $mailman::strLocalLocationAttachments to the local path name of
# this directory, for instance
# $mailman::strLocalLocationAttachments = '/public_html/attachtmp/';
# Then set $mailman::strURLLocationAttachments to the URL location
# of this directory, for instance
# $mailman::strURLLocationAttachments = '/attachtmp/';
# Note the terminal slashes at the end, those are necessary. Just
# set and uncomment the following lines to use this feature:
#$mailman::strLocalLocationAttachments = 'c:/www/public_html/pop3mail/tmp/';
#$mailman::strURLLocationAttachments = '/pop3mail/tmp/';
# Local File Permissions
# Use this if you want to modify the permissions that files and
# directories created by POP3Mail use. This will only make much sense
# to Unix and Unix-like operating systems. If this value is not set,
# nothing will happen. This should be an octal integer as in the
# example below, not a string.
# This value will only matter if you set
# $mailman::strLocalLocationAttachments and
# $mailman::strURLLocationAttachments, of course.
$mailman::iLocalFilePermissions = 0666;
# Local Directory Permissions
# Same as above, used for directories created by POP3Mail.
# This value will only matter if you set
# $mailman::strLocalLocationAttachments and
# $mailman::strURLLocationAttachments, of course.
$mailman::iLocalDirectoryPermissions = 0777;
# Outgoing Banner Text
# This is the banner that is appended to the end of any message that
# this POP3Mail installation sends. One reason why this is one of the
# first configuration options is because we want to make it very
# obvious that you can remove or modify this banner. Indian Magic places
# no restrictions at all on this banner, so don't worry about leaving
# credit to us in here or anything like that. Please feel free to
# change this to whatever you like, or completely remove it. If this
# value is not defined then it will simply append no banner.
$mailman::strOutgoingBannerText = "Check any POP3 Mail at http://mail.indian-magic.net" ;
# Incoming Mail Server:
# The way that we originally intended to allow people to 'rig' the server
# names for an installation was through simple template modifications, as
# mentioned in the FAQ. A lot of people have asked about ways to rig the
# server names in the script itself though, so we added this. We aim to
# please... If you want to rig your incoming server name so that it makes
# no difference at all what an incoming form specifies, just un-comment
# this line and specify it.
#$mailman::strIncomingServer = 'mail.indian-magic.net';
# Outgoing Mail Server:
# Same deal, different server.
#$mailman::strOutgoingServer = 'mail.indian-magic.net';
# From Domain Name:
# Set this variable to override the domain name that is assumed when a
# user logs in. For instance, when the user "abcd" logs into the POP3
# server "mail.indian-magic.net", POP3Mail will assume that his address
# is "abcd@mail5.indian-magic.net". If you set this variable to
# "indian-magic.net", then it will assume that his address is
# "abcd@indian-magic.net" instead. If the mapping between POP3 user names
# and email addresses is more complicated then you will need to actually
# build your own routines to do the mapping.
#$mailman::strFromDomainName = "indian-magic.net";
# From Domain Trim:
# If the above option doesn't work for you, you can set this value to
# instruct POP3Mail to trim the machine name when it derives the 'from'
# email address. The number that you set this to represents the total
# number of names to shear off of the left-hand side of the machine
# name. For instance, if the user's POP3 server name is
# "mail.abcd.indian-magic.net", and you set this value to 0, the default,
# then when the user composes a message POP3Mail will guess
# "username@mail.abcd.indian-magic.net" as the 'from' address. If you set
# this value to 1 then it will guess "username@abcd.indian-magic.net", if
# you set it to 2 then it will guess "username@indian-magic.net", etc. This
# can be helpful if you have a number of different virtual domains
# and you want the email address to be inferred dynamically, rather
# than by hard-coding it with the "From Domain Name" configuration value.
#$mailman::iFromDomainTrim = 1;
# Outgoing Domain Name:
# When a user specifies a recipient name without full domain qualification
# ("abcd" instead of "abcd@indian-magic.net", for example) then the SMTP server
# should provide configuration rules for determining how to deal with this
# mail. It should not be the responsibility of the mail client to fill in
# a complete address. We have had many requests for a feature to allow
# an administrator to specify a default domain name, however, and we aim
# to please. This configuration variable is the result. If you want
# POP3Mail to assume a default domain name when it is given an incomplete
# address, uncomment this line and set it to your domain name. We strongly
# recommend against this, however, you should be looking into your SMTP
# server's configuration options and not using this feature.
#$mailman::strOutgoingDomainName = indian-magic.net';
# Messages Per Page:
# This value controls the number of messages returned per page in a
# message list. Adjust it if you like.
$mailman::iMessagesPerPage = 20;
# Local Template Location:
# If you have a web server that sets the current directory to something
# strange, you can set this to an absolute path to make it easier to
# allow POP3Mail to find the templates. Just set this variable to an
# absolute path like "C\:\\inetpub\\wwwroot\\pop3mail\\templates\\"
# or '/usr/home/indian-magic/pop3mail/' or whatever. Note the final slash, that's
# important. If you leave it out then things won't work. If you need
# to set this value, then un-comment the following line:
#$mailman::strLocalTemplateLocation = "D:/inetpub/wwwroot/indian-magic/products/pop3mail/";
$mailman::strLocalTemplateLocation = "/home/sites/site6/web/pop3mail/";
# Local Script Location:
# If your server is one of the ones that causes problems that require the
# above value to be set, then you might also need to set this value. In
# most cases your script location and your template location will be
# identical, but if you move your templates to a different directory than
# your script for whatever reason, then you will need to set this. If you
# have no idea what I'm talking about, you should probably just leave this.
#$mailman::strLocalScriptLocation = $mailman::strLocalTemplateLocation;
$mailman::strLocalScriptLocation = "/home/sites/site6/web/";
# URL Image Location:
# Use this to rig the URLs that will be used to access the images that
# the templates point to. This value will be prepended to any value in
# the templates of the form ""i_*.gif"" (including the inner quotes).
# If you have customized your templates and your own custom images are
# not showing up in POP3Mail's output, it is probably because the custom
# images that you are using are not named "i_*.gif".
# To use this variable, set it to the exact value that you want prepended
# to image names in order to make them into URLs that will point to your
# image directory. For instance, if you bury your images in an "images"
# directory under the directory where POP3Mail is installed, set this to
# 'images/' (with the slash). If you put your images in a completely
# different directory, something that is rooted, like '/pop3mail/images/'
# might be what you are looking for. In the most extreme cases you can
# do away with relative URLs entirely and provide a complete absolute URL
# like the one below
#$mailman::strURLImageLocation = 'http://www.indian-magic.net/pop3mail/';
# Use Perl 'alarm()' function:
# Set this to true if your Perl interpreter supports "alarm". As of this
# Writing, NT Perl does not. If this is not set, POP3Mail will not be able
# to timeout when a server hangs. The OSSettings() routine will attempt
# to set this variable, but you can override it here if you want.
# The point of the "alarm" feature as used in POP3Mail is to allow POP3Mail
# to detect when a mail server has not responded within a reasonable
# amount of time. If your server's Perl interpreter does not support
# "alarm", then POP3Mail will still work, but if a mail server ever does
# not respond then the user will get no feedback to that effect.
#$mailman::bUseAlarm = 1;
# Timeout Duration:
# The aforementioned timeout delay. Set this to something else to modify
# how long POP3Mail will sit around waiting for a mail server to respond.
# Only works if $mailman::bUseAlarm is set to something.
$mailman::iTimeoutDurationInSeconds = 180;
# Use Perl 'crypt()' function:
# Some Perl impelentations apparently do not support the crypt() function.
# We have never seen one, and there are plenty of implementations out there
# that you should be able to find a good one, but we try to accomodate
# anyway. Comment out this line if your Perl implementation is breaking
# on the crypt() function. Be warned that if you do this your users'
# usernames and passwords will be less obfuscated than they were before,
# which admittedly wasn't much. This is a good place to repeat the
# suggestion that POP3Mail is an excellent candidate for SSL and other
# fancy HTTP security mechanisms.
#$mailman::bUseCrypt = 1;
# Use Hijack Test:
# POP3Mail performs a test to determine if the current session has been
# hijacked by a different user from a different address. On a few
# systems this will not work because of the configuration. If your
# POP3Mail installation sits behind a cluster of caching proxy servers
# for load balancing, for instance. If you want to disable the hijack
# checking functionality, just comment out this line.
#$mailman::bUseHijackTest = 1;
# Kiosk Mode:
# If you are using POP3Mail in a kiosk environment, it will generally
# be possible for a user to use a combination of "BACK" and "RELOAD" in
# the kiosk web browser to intrude backwards into the mail sessions of
# previous users. If you set this value then POP3Mail will operate in
# kiosk mode, which means that when a user logs in, POP3Mail will create
# a new browser window with that user's session. If the user logs out
# then that window will close, and the user's history information will
# go with the window so that intrusions with "BACK" and "RELOAD" aren't
# possible. We recommend against using this feature for installations
# that are not kiosk-based because it relies on Javascript and cookies,
# which does not leave users with older browsers with a way in. If you
# are in a kiosk environment then you have control over the browser an
# that's not a problem. We strongly recommend against using the
# Microsoft Internet Explorer for kiosk environments because it does not
# properly respect the "Expires:" and "Cache-control:" HTTP headers, so
# IE will cache user mail to the hard drive whether you want it to or
# not. Microsoft appears to have no interest in fixing this problem.
# IE 4 SP1 pretty consistently crashed during our tests of the
# full-screen popup window kiosk mode, too, which is likely not exactly
# the behavior that you are looking for in your kiosk browser.
# The kiosk mode feature primarily activates and deactivates sections
# of outbound templates, so if you have customized your templates before
# you decided to use kiosk mode then it is entirely possible that you
# broke this mode by removing vital Javascript. Consult the
# out-of-the-box template set for examples of the Javascript snippets
# necessary for this mode.
#$mailman::bKioskMode = 1;
############################################################################
# You should not have to configure any values after this line.
############################################################################
use Socket; use FileHandle; my($mma) = new FileHandle(); use CGI;
my($mmb) = new CGI; { my(@mmc) = $mmb->param; my($mmd) = 0;
for($mmd=0;$mmd<$#mmc+1;$mmd++) { my($mme) = $mmc[$mmd];;
if($mme =~ /^(.+)\.[xy]$/) { my($mmf) = $1; if($mme =~ /^([^\#]+)\#(.*)\.[xy]$/) {
$mmf = $1; $mmb->param($mmf,mmmd($2)); } else {
$mmb->param($mmf,'MAILMANSPECIALTRUE'); } $mmb->delete("${mmf}.x");
$mmb->delete("${mmf}.y"); } else { if($mme =~ /^([^\#]+)\#(.*)$/) {
$mmb->param($1,mmmd($2)); } } } } if($mmb->param('INTERFACE')) {
my(@mmg) = split(/\&/,$mmb->param('INTERFACE')); my($mmh) = '';
foreach $mmh (@mmg) { if($mmh =~ /^([^\=]+)\=(.*)$/) {
$mmb->param($1,mmmd($2)); } }
unless($mmb->param('INTERFACE') =~ /ALTERNATE_TEMPLATES/) {
$mmb->param('ALTERNATE_TEMPLATES',''); } } {
@mailman::mmi = split(/\;/,$ENV{'HTTP_COOKIE'}); my($mmj) = '';
foreach $mailman::mmj (@mailman::mmi) { $mailman::mmk = 1;
if($mailman::mmj =~ /POP3MailAuth\=(\S+)/) { my(@mml) = split(/\&/,$1);
my($mmm) = ''; foreach $mmm (@mml) { $mmm =~ /^(.+)\#(.+)$/; unless($mmb->param($1))
{ $mmb->param($1,$2); } } } } } $mailman::mmn = mmmh($mmb->param('USERNAME'));
$mailman::mmn =~ s/^\s*([^\s]+)\s*$/$1/;
$mailman::mmo = mmmg($mailman::mmn);
$mailman::mmp = mmmh($mmb->param('PASSWORD'));
$mailman::mmp =~ s/^\s*([^\s]+)\s*$/$1/;
$mailman::mmq = mmmg($mailman::mmp); unless($mailman::strIncomingServer) {
$mailman::strIncomingServer = mmmh($mmb->param('SERVER'));
$mailman::strIncomingServer =~ s/^\s*([^\s]+)\s*$/$1/; }
$mailman::mmr = mmmg($mailman::strIncomingServer);
unless($mailman::strOutgoingServer) {
$mailman::strOutgoingServer = $mmb->param('OUTGOING');
$mailman::strOutgoingServer =~ s/^\s*([^\s]+)\s*$/$1/; } $mailman::mms = '';
if(defined($mailman::strLocalLocationAttachments) &&
defined($mailman::strURLLocationAttachments)) {
unless($mailman::strLocalLocationAttachments =~ /[\/\\]$/) {
$mailman::strLocalLocationAttachments .= '/'; }
unless($mailman::strURLLocationAttachments =~ /[\/\\]$/) {
$mailman::strURLLocationAttachments .= '/'; } $mailman::mmt =
$mailman::strLocalLocationAttachments . mmmc($mailman::mmn .
'@' . $mailman::strIncomingServer); $mailman::mmu =
$mailman::strURLLocationAttachments . mmmc(
mmmc($mailman::mmn . '@' . $mailman::strIncomingServer));
$mailman::mmv = 1; } $mailman::mmw = mmmb($ENV{SERVER_NAME},42);
$mailman::mmw .= mmmb($ENV{REMOTE_HOST} . $ENV{REMOTE_ADDR},69);
$mailman::mmx = mmmg($mailman::mmw); mmma();
$mailman::mmy = $ENV{SCRIPT_NAME}; unless($mailman::mmy =~ /^\//) {
$mailman::mmy = "/$mailman::mmy"; } $mailman::mmz = $mailman::mmy;
$mailman::mmz =~ s/^(.*[\\\/])[^\\\/]+$/$1/; if($mailman::mmz eq '/') {
$mailman::mmaa = ''; } else { $mailman::mmaa = "path=$mailman::mmz; "; }
sub mmkl { if($mmb->param('NOFRAMES')) { $mailman::mmab = 1; }
if($mmb->param('NOCACHE')) { $mailman::mmac = 1; }
if(defined($mmb->param('ALTERNATE_TEMPLATES'))) { $mailman::mmad =
$mmb->param('ALTERNATE_TEMPLATES'); } } sub mmkm { my($mmae) = shift;
my(@mmc) = $mmb->param; my($mmd) = 0; for($mmd=0;$mmd<$#mmc+1;$mmd++) {
my($mme) = $mmc[$mmd];; if($mme =~ /^$mmae\:(.*)$/) { return $1; } } return; }
mmkl(); mmkn(); { my($mmj) = '';
@mailman::mmi = split(/\;/,$ENV{'HTTP_COOKIE'});
foreach $mailman::mmj (@mailman::mmi) { if($mailman::mmj =~ /POP3MailCmds\=(\S+)/) {
my($mmaf) = ''; @mailman::mmag = split(/\&/,$1); foreach $mmaf (@mailman::mmag) {
$mmaf =~ /^(.+)\#(.+)$/; unless($mmb->param($1)) { $mmb->param($1,$2); } } } } }
mmkl(); mmkn(); mmkq();
sub mmkn { my($mmah) = ''; if($mmb->param('BLANK')) {
mmlz('t_blank.htm'); } if($mmb->param('MENU')) {
mmlz('t_f_menu.htm'); } if($mmb->param('LOGOUT')) { if($mailman::mmv) {
mmmo(); } if($mailman::bKioskMode) {
print "Set-cookie: POP3MailAuth=;$mailman::mmaa" .
"expires=Sun, 03-May-1998 16:00:00 GMT\n";
print "Set-cookie: POP3MailCmds=;$mailman::mmaa" .
"expires=Sun, 03-May-1998 16:00:00 GMT\n";
print "Set-cookie: POP3MailDir=;$mailman::mmaa" .
"expires=Sun, 03-May-1998 16:00:00 GMT\n"; $mailman::mmn = '';
mmlz('t_closewindow.htm'); } else { mmkq(); } }
if($mmb->param('START')) { mmkq(); } if($mmb->param('LOGIN')) {
my($mmai) = ''; if($mmai = mmks()) { if(defined($mmai)) {
$mmai =~ s/^\-ERR(.*)$/$1/; } $mailman::bKioskMode = 0;
$mailman::mmaj{'GREETING'} =
"
The output template "$mmfc" exists and was found by the POP3Mail\n| .
qq|script, but the script does not have permission to read it.
\n| .
qq|
On most Unix systems, you can go to the directory where POP3Mail is\n| .
qq|installed and type "chmod 644 $mmfc" to solve this problem. If\n| .
qq|your HTTP server is running in a different operating in a different\n| .
qq|operating system, consult your HTTP server and operating system \n| .
qq|documentation for more information.
The output template "$mmfc" could not be found by the POP3Mail \n| .
qq|script.
Make sure that this template is located where POP3Mail can \n| .
qq|find it (in the same directory as the script itself on most web servers,\n| .
qq|but not necessarily) and make sure that the web server process has\n| .
qq|permission to read the file. Consult your HTTP server and operating\n| .
qq|system documentation for more information.