upgrading - see below
Except for the data files that have to be deleted and recreated by the program, ALL files have been renamed so the older program can remain until installation is proved.

ListMerge has always created its own safe copies of E-Mail lists.

Two new list formats have been added to v2.+
List "formats" are an E-Lists and ennyForms subscriber thing where original lists can be created with extra subscriber/program input for personalising merged mail-outs via PC or ListMerge. See the new formats "4" and "5" below (blue E-Lists info box).

The lack of HTML code in the texts saving HTML box in the "sending" window will cause the program to send only plain text e-mails OR all can be overridden to send only HTML e-mails.

It is expected that a site is tidy with all mail list saving programs saving to the one directory (preferably secure as a sub of the true cgi-bin). ListMerge is pointed to this directory and attempts to detect the format of the lists it finds with file name extensions matching those in the new $elst_exten variable. ListMerge then looks for any delimiters in those lists matching the new @seps array.

A list with a delimiter matching the default $sep variable between fields in the original list will be treated as an E-Lists or ennyForms saved list with possible "name" and "date" and "htm" fields saved with the "address". Lists with other delimiters from other porgrams will be recorded as "address only" lists with the new format marker of "5'.

Plain address only lists will be recorded with the original (earlier versions of ListMerge) format marker of "3". These marker values can be changed - but only IF really necessary.

A marked list of "3" can be changed to "5" even if the original list contains possible user "htm" fields (E-Lists v2+ and ennyForms) to slightly speed up the mailing process BUT only do this if the first fields of each record in the original list are addresses!

ListMerge v2+ allows the sending of test mails to the default site address of one plain text letter and one HTML page formatted letter - if the latter has been saved via the texts saving form.

All relevant files are supplied in one compressed .zip file that includes the recommended directory structure. It is assumed that the Zip file has been uncompressed to the root directory creating the default directory structure included in the Zip file, and described below. A utility to create the default recommended cgi-bin subdirectories, file names, plus chmod permissions is included.

For each original e-mail list found on your site, three files are created. One is the above mentioned copy of the original, and another is the data and texts associated with each list. Therefore the body text, a header or introduction text, signature text, the 'from' address, the 'Subject' line, and an HTML page can be created differently for each list. ie one might be in reference to price list upgrades with a 'from' address for sales@yourdomain.name and another for a monthly newsletter 'from' editor@yourdomain.name.... blah blah.

Once the mailing of all addresses for any list is completed and another later mail-out is ready, ie once a month or when a new upgrade is to be announced, the ListMerge copy of addresses can be recreated (over written) with the latest version of the original list (with new additions or deletions).

NOTE: Very large mass mail-outs should only be performed by a dedicated mail server. If your lists become so successful, consider leasing one for your business. The basic cgi methods of sending mail are inefficient for very large mail-outs on shared servers, and some programs including ListMerge offer an option to send mail in blocks to reduce the load on the Mail Server of your Hosting service.

You control the mail-out quantity by 'batch' sending
This simply means that once a nominated number of addresses have been mailed to, the "Send" page reappears ready for the next batch to be sent thus allowing the Mail Server CPU to perform other tasks in between. This will help prevent you from being banned by the host service (reports have confirmed this happens and people welcome the ListMerge batch option, but all it takes is contact with your host and they will mostly respond positively with perhaps a suggested "batch' figure).

Because ListMerge records addresses sent and those not sent (ready) per session, if the server is very slow you can return anytime later and continue where you left off with the next 'batch' without having to remain logged on while the full list is exhausted. If the program is "time terminated" by the server - the most common reason for mailing crashes - the last successful mailed address is recorded allowing you to continue again with possibly only one address sent twice.

Your Domain.Name
You MUST alter all reference to "yourdomain.name" in the "lmrgeset.pl" 'require' file and supplied webmasters page (see below), and change the configuration variables in "lmrgeset.pl", also described in this Readme text.

With or Without E-lists
There is a sample Admin page and Sending/Editing page supplied. Familiarise yourself with these before starting and you will soon understand how easy the program is to use. To add another list, all you have to do is create a form on one of your pages that saves the list via your subscriber program (ie E-Lists) with a common file name extension to the directory ListMerge will search. The matching list directory and file name extension is set-up in the ListMerge config file - "lmrgeset.pl".

SAFE "Batch" Mail-List MAILING

Wherever your lists are situated ListMerge creates safe copies of the originals and works the mailing from them. ListMerge has the very rare but immensely popular facility of allowing you to send only the number e-mails you think/know your mail server can handle at one time. Then the program is ready to send the next batch and so forth until the current mail out is complete.

Because ListMerge keeps track of which addresses have been sent and which are ready to send, during a mail out the list copy can be refreshed with new arrivals without upsetting the "sent" tracking. With the "batch" method employed, addresses canot receive extra copies because the program knows where it left off. You have to reset the list when later ready to perform another mail out!

Each mail list Listmerge copies is acompanied by a data file that holds the letter information and texts and/or HTM page sent to each address in the list. The "sending and editing" admin page includes areas for entry of the From Address, Subject wording, Organisation name if desired, Header portion of the letter, Main body portion of the letter, Signature portion of the letter, AND a complete HTML page. An unsubscribe URL should now be included by you

NOTE: LnkinLite is ideal for creating permanent or temporary "named" hyperlinks that can be quickly created, generated and copied into your mail letter. This way not only subscribers can be given a special hidden html page to view, but responses can be judged by LnkinLite's link-click counting feature.

Already described above, if ListMerge detects the E-Lists file format when mail lists are saved with the subscribers name and subscription date then ListMerge can add that extra info to each letter by a simple process of you including field markers in the head/body/signature/HTML areas of the letter.

And as already mentioned each list accessed by Listmerge retains its own letter data file, so at the next mail out the new body text can be edited from the previous and perhaps the head and signature sections left as is.... designed with the user in mind.

Resetting or refreshing of each list is perfomed on the first admin page. Each list name is dsiplayed and from there the individual letter data and "batch mailing" form is accessed.

The program has an in built password administration page for changing your desired GMTime zone, admin page access password, and a further encrypted password authorising editing changes and mail-outs. Therefore, even if another person discovers your 'access' password in the browsers cache (all generated pages use the no-cache meta-tag), they cannot change or send any data, and if remote from your server loft, the prefered remote time is reflected in all output AND now displays your local time in the visible e-mail header in standard email time format!!

The cgi-bin directory and any subdirectories of it should be protected from user access by system default, so they are an ideal place for maximum security (nothing can be done if your server is hacked into). the programs can access info files, but files cannot be accessed from outside.

Upgrades
YOU MUST DELETE ALL PREVIOUS DATA FILES FROM THE MRGLISTS DIRECTORY so they can be rebuilt with important file detection data - which is only created once.... read next praragraph

ALL FILES have now been renamed EXCEPT for the data files. So by first backing them up and then later "copy and pasting" the previous texts in to the new text windows the new data files can be (MUST BE) recreated with little fuss.

The rest of the program has been completely renamed except for the password file, so the old version can remain until confident with v2.0 - list data files are incompatible.

For INTERMEDIATE installation experience - Help / Advice information is available.
CONFIGURATION VARIABLES in DETAIL

GMT TIME ZONE reference - set via ListMerge pages.
As with www.dtp-aus.com, Hosting services are used now "remote" from ones local ISP service. Normally this means that all of our scripts etc report dates and times are different to that of our local access points, ie our home locality from where we view our sites. To overcome this I use a Perl facility that allows us to use (G)reenwich (M)ean (T)ime with an offset reference reporting in my local time and date. One of the perl "require" files, 'gmtset.pl', contains a variable name - $gmtPlusMinus - whose value MUST be set for your local GMT offset. I live in a world time zone 15 hours ahead of that of my Host Servers. Therefore, when I set the variable to 36000 (+10hrs = Melbourne Australia GMTime), the lists record, and I view, all dates and times relevant to my locality irrespective of where my Hosting service is. With this method I can move my Domain and the results would not change.

ListMerge now takes advantage of the GMT method for all visible e-mail headers too.

Most home / business computer systems have the GMT value listed in the system clock control panel... simple.

The calculation is also simple. Your local GMT time, multiplied by 60, and multiplied by 60 again. ie 10X60X60. Therefore my variable entry is "$gmtPlusMinus = 36000". If your GMT zone is a negative value, simply include a negative value ie "$gmtPlusMinus = -36000". If you want the dates/times to be the same as the servers, simply enter the value for the servers GMT zone.

US AND BRITISH DATE reporting
ListMerge can save the e-mail address submission time using either the US mm/dd/yyyy format, or the BRITISH dd/mm/yyyy format. In the configuration file, 'lmrgeset.pl', you will find a variable named $dtUS. Leaving this variable value as null, ie '$dtUS = ""' will cause the scripts to use "dd/mm/yyyy". Setting this variable to '$dtUS = "1"' will force 'mm/dd/yyyy'.

CHECKING FOR CORRECT REFERRERS - this can block even YOU... "Bad Referrer"
This option in the 'lmrgeset.pl' file allows you create an "array" of Domain names and IP numbers that lstmrge.cgi will respond positively to. By including the acceptable calls to your pages and/or your IP#, ie 'www.yourdomain.com' and yourdomain.com' you effectively stop improper additions to your lists from distant sites (entries are only accepted from pages on your site, not remote copies of your pages elsewhere – they try all the time). The array is named "@referers" and you simply (MUST) enter your preferences in place of the examples. NOTE: The brackets, quotes and commas enclosing each item must be included else an error will occur, ie:

('www.yourdomain.com','yourdomain.com','000.000.000.000',). Leave out the IP# if you do not have a true domain name with a static IP#. "www.ahost.net/mysite/" etc will also work for second level site calls etc, but not the IP#. If your scripts are called from the cgi-bin of a domain that is housing your site and your specific scripts are in that domains cgi-bin, you may have to include the cgi-bin also in relevant urls ie: "ahost.net/cgi-bin/".

At this point I will bring your attention to the semi colons ( ; ) appearing at the end of each line in the config files. These MUST remain else an error will occur.

PATHS TO FILES ACCESSED BY SCRIPTS
The defaults used in the ' lmrgeset.pl ' file assume you will place these files in your cgi-bin and add directories to it called "sets" and "mrglists". If you have to use other directory names, or your "cgi-bin" has a different name, then you will have to change the paths accordingly; "cgi-yourdomain" is not uncommon. There are three path types that can be used at various times with in a program or script. A full URL is the same as the path you enter in your browsers address box when typing in a site path that you wish to go to: ie 'http://www.wooz.com/harry.htm'. A relative path is a path description to a source, relative to the directory of the program, file or web page that is calling it: ie "jimbo.htm" means that the file being called should be in the same directory. "inone/jimbo.htm" refers to a file that should be in a directory named 'inone' which is a subdirectory within the current directory, and "../jimbo.htm" means that the file should be in a directory one above the current directory, and "../../jimbo.htm" is in a directory two above etc.

For some servers, a simple relative path called by a script is unacceptable, so an absolute path relative to the sites root directory must be called. There are also variations to this description but "web/yourdomain/yourdirectory/jimbo.htm" (example only) is a relative root path description that works on many servers. Another root path is "/home/yourdomain/www/yourdirectory/jimbo.htm". If you have trouble with accessing the default simple relative paths included in the 'lmrgeset.pl' file, try the root reference ie "web/yourdomain/cgi-bin/mrglists/mrgml.pw" etc. If this is still a problem, look in any installed scripts on your server for a reference, or contact your hosting support staff.

NOTE: If you have problems, double check ALL permission's (below) before changing the default paths, unless you know in advance what the paths should be, and reload files to double check that you used ASCII transfer mode for all text files.

"SENDMAIL" MAIL PROGRAM server path $mailprog
Similar to the Perl program path, this path has to be known for ListMerge to send submitted mail. If you do not know what it is or cannot find reference to in other installed scripts, ask your Host service support staff - the utility "testbin.cgi" may report this path for you.
The default is $mailprog = "/usr/sbin/sendmail";

ADMIN Password $adminword_pth
The file path relative to the script that will be created when you create an Admin Password. DO NOT edit this file – the new password will be encrypted. When you first start the script successfully from a form using the Access Password, create a new Admin password immediately via the 'passwords' page link to secure your data from visitors. The current password will be nothing (null) and you enter the new word twice to be sure. Once accepted you have to enter the admin password in the editing forms next to the submit buttons whenever you try to edit any options.

GMT Path $gmt_pth
When you edit the GMT zone value from the passwords admin page, the script needs to know the path to the gmtset.pl file. The default is the "sets" sub directory and file name relative to the scripts directory.

CONFIGURATION Path $cnfg_pth
When you edit any configuration values or data files from the admin pages, the script needs to know the path to the 'lmrgeset.pl' file. The default is the "sets" sub directory and file name relative to the scripts directory. The "sets" directory is used by almost ALL dtp-aus.com programs and will have even more significance in the future.

The DATA FILES DIRECTORY $mrgdatdir_pth
This is the directory path (not file) for the files created when copies of the lists are created or updated, and data files are created or amended. The default is "mrglists".

DEFAULT MAIL ADDRESS $deflt_mail
NEW v2. This is the default mail address used by the new "Mail Test" option.

ORIGINAL LIST-FILES File Name Extension $elst_exten
CHANGED v2. If you want to use lists other than / as well as E-Lists list files, add their file name extension (including the dot) to this variable. The ".elf" extension is the dfault for E-List and ennyForms subscriber lists. If changes are made the format and "|" divider MUST remain as is.

ADDRESS,NAME,DATE SEPARATOR $sep
This is the default delimiter ListMerge uses to divide record filelds when merge list data is detected. It would be wise to keep this the same as E-Lists and ennyForms if those programs are used to create subscriber lists.

INSTALLING

THE PATH TO PERL
At the top of each perl script (and must remain as the first line) is a default path to the Perl program on your host server. This can vary slightly between UNIX servers. If you have problems running the scripts, check with your host support staff about the correct path described in this line. The default entry is "#!/usr/bin/perl" and another common variation is "#!/usr/local/bin/perl". In Perl scripts the hash sign "#" character comments out the code on a line starting with this character. Here it has a special meaning to Perl and MUST remain. Check with other installed scripts also if you do not know what this line should look like.

UP LOADING FILES (Posting)
The script must be given chmod 755 read and execute permissions (r+x).

CGI-BIN permissions are set by the server and no attempt should be made to change them. Should you have to use another directory, AND your server allows the execution of Perl CGI scripts in other directories, then that directory should be set with read and execute permissions - chmod 755 (r+x).

By far the biggest problems faced when installing scripts are firstly the file transport encoding used and secondly the permissions settings set for both files and new directories. Bitmap images must be sent to the server using the "Binary" protocol. Text files, ie html pages, CGI SCRIPTS and require files, MUST be sent in "ASCII" format. Failure to do this will result in a server failing to recognise and execute the scripts. Although often referred to as programs, scripts must be compiled before they do anything. As an example, files with the .EXE extension on programs that are installed on Wintel machines are pre-compiled binary executable programs. Perl scripts on the other hand are compiled in memory by Perl each time before they can be executed. The script (text) must be in ASCII text format for the interpreter to be able to read it.

CALLING THE SCRIPT from a hyperlink
<a href="http://www.yourdomain.path/cgi-bin/lstmrge.cgi?accwrd=***"> ListMerge </a> where *** = your access password (NOT your admin password),
OR from a simple form as viewed in the webmstr.html code.

I REPEAT: Up load scripts and other text files as "ASCII" files, images as "Binary".

So, assuming the default directory structure is used, you will up load into:
• CHANGED v2.0+

Directory:

cgi-bin (server)

lstmrge.cgi (chmod 755)

cgi-bin/sets (chmod 766 or 777)

lmrgeset.pl, gmtset.pl (chmod 766 or 777)

cgi-bin/mrglists (chmod 766 or 777)

mrgml.pw, admn1.pl, admn21.pl, admn3.pl, admn4.pl, admn5.pl
plus [list / data files created by program], (chmod 766 or 777)

If you must use another directory for the ??.set files, you must also change the path to those files at the top of the code in lstmrge.cgi. ie::

#--- Alter these two paths (TWICE EACH) only, if needed! -----#
      if (-s "sets/lmrgeset.pl") {require "sets/lmrgeset.pl" ..etc etc
      if (-s "sets/gmtset.pl") {require "sets/gmtset.pl" ..etc etc
#--- Do Not make any changes below this line. ----------------#

To help keep the program free, we need your support on link and resource listing sites!