Copyright 2000-2024 by Frank Bauer
Add2it.com - All Rights Reserved.

Contents :

1. Description & Features
2. Add2it Affiliate Program
3. Script Info
4. Copyright Notice
5. Disclaimer
6. htmlArea License
7. Installation Instructions
8. Script History
9. Manual
10. Support Forum
11. Add2it Scripts Update + Announcement List

1. Description & Features :

Click here for the most current description and list of features.

Click here for all details about the Add2it.com Affiliate / Reseller Program and how you can earn up to 70% commissions.

Click here for the Add2it.com Affiliate Program Sign-Up form.

Affiliates can click here to log-in.

Platform:

Unix / Linux & Windows server

Requirements:

1. Perl 5.0 or higher. 2. MySQL 4.0.20 or higher (use script version 3.02 if no MySQL is available). 3. You must have FULL cgi-bin access. 4. You need to be able to set permissions (only UNIX / Linux). 5. Various Perl modules (CGI, DBI, Fcntl, Socket, Time::Local, IO::Socket - A good host will have them all) 6. Ability to forward (pipe) emails to a script (only for subscribe / unsubscribe by email feature as well as the "Bounce Manager" feature) OR 7. Ability to setup a cron job (Unix / Linux) or scheduled tasks (Windows) one time (OR have your hosting service volunteer to perform this service for you; for schedule function and for subscribe / unsubscribe by email feature as well as the "Bounce Manager" feature if you don't forward emails).

Click here to take a look at the interactive online demo.

This scripts is for your use only and you may NOT distribute them to other parties.

You can install this script per license ONE TIME on ONE server and it is not allowed to make modifications in any way, shape or form to the scripts.

Add2it.com has spent 100's of man hours to create a software to help you - please respect OUR RIGHTS in selling you this software for your unlimited usage, by NOT violating our rights as the sole copyright owners and creators of this scripts.

You may not in any way, shape or form adjust, reprogram or change this scripts.

All coding is copyright Frank Bauer, Add2it.com and is licensed to you for your usage only. This scripts and all it's components are whole created, owned, and copyrighted Add2it.com.

In other words you are only allowed to install and use this scripts ONLY - you may NOT change it, or use any part of it in whole or in part in any other program or any other way, shape or form without permission of Add2it.com.

By installing and/or using this scripts you agree to these terms and shall be binding in a court of law - in all countries worldwide - forever. All people that violate these terms will be dealt with by legal means - any person that informs Add2it.com of a copyright violation, will be rewarded.

Please click here if you require special services.

This software is provided as is - Add2it.com will not be held responsible for any loss or damage indirectly or directly caused by your installing and using this scripts in any way, shape or form. By installing this scripts you agree, completely and absolutely with all terms in this manual and release Add2it.com from any and all responsibility by you using this scripts.

htmlArea License (based on BSD license)
Copyright (c) 2002, interactivetools.com, inc.
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3) Neither the name of interactivetools.com, inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

7. Installation Instructions :

1. To unpack the MRP###.ZIP file (### is the version number), go to the folder where you saved it to and unzip the file into a directory of your choice.

2. If you do not have ZIP decompression software installed on your computer, get it for free at:

http://www.shareware.com

3. The installation of this script is simple, no variables or setting need to be adjusted prior to upload. All settings are accessible online, via the Admin Control Center.

4. The path to Perl within the scripts is set to the typical standard value of /usr/bin/perl. This path works on 90% of the servers.

If you know that the path to Perl is different on your server, please consult the "Troubleshooting" section below to see in which files the path to Perl has to be changed.

5. This program must be uploaded to your server where your website files are located.

This program is tested on UNIX / Linux and WINDOWS server systems.

6. To upload, you will need an FTP program. Either WS-FTP or CUTE-FTP, free at:

http://www.shareware.com

For Macs, you will need a copy of FETCH.

Upload using FRONTPAGE is NOT recommended AND will NOT WORK.

All you are doing is moving all files from your local computer to the server where your website files are located, and setting the permissions of install.pl to allow the script to be treated like a program.

8. Login into your website account using your FTP username and FTP password.

9. Create a new a new directory for the scripts in your CGI / CGI-BIN folder or somewhere else*. The recommended name for this new directory is "mrp". Set the file upload to ASCII only [ASCII mode].

CGI-BIN permissions are set by the server and no attempt should be made to change them.

On some servers you will have to CREATE a CGI-BIN - to do this:

MKDIR cgi-bin

And set the permissions on UNIX / Linux systems to 755.
[CHMOD 755 - see below for example.]

* NOTE: If you attempt to install this in a directory other than a CGI/CGI-BIN, even with the proper permissions set on both the FILE and DIRECTORY the files are located in it MAY NOT WORK as some web servers restrict where CGI programs can operate and run.

10. On UNIX / Linux systems set permissions on this new folder.

Once created, CHMOD [right click - this will be under settings in other programs, other than WS-FTP] this directory to 755**.

Visually, Setting are as follows [WS-FTP]:

	Owner	USER	Other
READ	[YES]	[YES]	[YES]
WRITE	[YES]	[NO]	[NO]
EXECUTE	[YES]	[YES]	[YES]

Some servers MAY require CHMOD 777 or visually, setting are as follows [WS-FTP]:

	Owner	USER	Other
READ	[YES]	[YES]	[YES]
WRITE	[YES]	[YES]	[YES]
EXECUTE	[YES]	[YES]	[YES]

** "CHMOD" means change permissions to allow this program to be treated as a program [vs a webpage] and allow it to do certain things. This is only necessary on UNIX / Linux systems.

On some servers, you may have to use a program called TELNET to go and change the settings...
[CHMOD] - consult with your server company for instructions on this - generally speaking most hosting companies have this info in an online instructions manual.

You can also view the online manuals at:
http://www.best-host.com/

For instructions on TELNET, general uploading of files and setting permissions.

11. Open this folder.

12. Select the folder/directory in your computer where you unzipped the MRP###.ZIP file (### is the version number).

13. Upload the following files to the new folder on your server:

Important: All files, exept those ending in .gif, have to be uploaded in ASCII mode. Only the files end in .gif have to be uploaded in Binary mode. Please make sure your FTP software DOESN'T automatically convert all file names into lower case.

- .htaccess (upload ONLY if .pl files can't be executed)
- add.pl
- addlist.pl
- add2it-optin.js
- admin.cgi
- admin.pl
- auto.pl
- bounce.pl
- bounceman.pl
- CGI-Carp.pm
- confirm.pl
- data-auto-index.htm
- data-bouncetype.dat
- data-foot.dat
- data-head.dat
- data-html-index.htm
- data-images-arrow.gif (Binary)
- data-images-ed_align_center.gif (Binary)
- data-images-ed_align_left.gif (Binary)
- data-images-ed_align_right.gif (Binary)
- data-images-ed_blank.gif (Binary)
- data-images-ed_color_bg.gif (Binary)
- data-images-ed_color_fg.gif (Binary)
- data-images-ed_format_bold.gif (Binary)
- data-images-ed_format_italic.gif (Binary)
- data-images-ed_format_strike.gif (Binary)
- data-images-ed_format_sub.gif (Binary)
- data-images-ed_format_sup.gif (Binary)
- data-images-ed_format_underline.gif (Binary)
- data-images-ed_hr.gif (Binary)
- data-images-ed_html.gif (Binary)
- data-images-ed_image.gif (Binary)
- data-images-ed_indent_less.gif (Binary)
- data-images-ed_indent_more.gif (Binary)
- data-images-ed_link.gif (Binary)
- data-images-ed_list_bullet.gif (Binary)
- data-images-ed_list_num.gif (Binary)
- data-images-fullscreen_maximize.gif (Binary)
- data-images-fullscreen_minimize.gif (Binary)
- data-images-insert_table.gif (Binary)
- data-index.htm
- data-lang-afr-language.kit
- data-lang-afr-language2.kit
- data-lang-afr-language3.kit
- data-lang-chi-language.kit
- data-lang-chi-language2.kit
- data-lang-chi-language3.kit
- data-lang-dutch-language.kit
- data-lang-dutch-language2.kit
- data-lang-dutch-language3.kit
- data-lang-eng-language.kit
- data-lang-eng-language2.kit
- data-lang-eng-language3.kit
- data-lang-espa-language.kit
- data-lang-espa-language2.kit
- data-lang-espa-language3.kit
- data-lang-ger-language.kit
- data-lang-ger-language2.kit
- data-lang-ger-language3.kit
- data-lang-gre-language.kit
- data-lang-gre-language2.kit
- data-lang-gre-language3.kit
- data-lang-index.htm
- data-lang-por-language.kit
- data-lang-por-language2.kit
- data-lang-por-language3.kit
- data-lang-sch-language.kit
- data-lang-sch-language.kit
- data-lang-sch-language2.kit
- data-lang-spa-language3.kit
- data-lang-spa-language2.kit
- data-lang-spa-language3.kit
- data-lang-swe-language.kit
- data-lang-swe-language2.kit
- data-lang-swe-language3.kit
- data-language.dat
- data-messages-index.htm
- data-popups-fullscreen.html
- data-popups-insert_image.html
- data-popups-insert_table.html
- data-popups-select_color.html
- data-variables.pl
- display.pl
- ed.cgi
- ed.pl
- edlist.pl
- editor.js
- editschedule.pl
- editsub.pl
- fieldman.pl
- filter.pl
- get.pl
- index.htm
- index.pl
- install.cgi
- install.pl
- liesmich.htm
- manager.pl
- mrp-sublib.pl
- Net-Cmd.pm
- Net-Config.pm
- Net-POP3.pm
- readme.htm
- remove.pl
- schedule.pl
- scriptsub.pl
- scriptunsub.pl
- send.pl
- sub.cgi
- sub.pl
- subfilter.pl
- unsub.cgi
- unsub.pl
- unsubfilter.pl
- update.pl

There are two installation options (modes) available:

1. Standard: All files are uploaded in one location on one server (as just described).

2. External: All files are uploaded in one location on one server. PLUS: A copy of all files is uploaded in another location on another server. 

14. Now create a MySQL database and assign a MySQL user with all rights to it. The process to do this might vary from web host to web host. If you are not sure how to do this, please contact your web hosts technical support staff. If your web hosts doesn't offer you to use MySQL, you can switch to a more advanced web host. To see a list of recommendable web hosts, click here.

When you have setup your MySQL database, please write down your MySQL database name, the MySQL username assigned to that database and the password. You will need this information in step 17.

15. On UNIX / Linux systems, set the permissions of the install.pl file. CHMOD mode it [right click over the install.pl script] and also set it to 755 as above.

16. You are now ready to let the install.pl script do the rest of the installation process.

Open your browser and call to install the rest of the script.

All sub-directories will be created automatically, all files will be moved into the proper sub-directories and on UNIX / Linux systems all file and directory permissions will be adjusted automatically.

If there is any problem, the script will let you know what it is.

17. Then call in your browser to setup the script. All necessary variables will be set. Please enter the URL to the directory where the scripts are located, choose if you want all outgoing emails to be send with Sendmail (UNIX / Linux) or with your SMTP server (UNIX / Linux or Windows), enter the MySQL database name, username and password as well as the administrators name, email and admin area access password. Modify all other settings as you like.

Instead of forwarding (pipe) emails that arrive at the Subscribe / Unsubscribe addresses to the filter.pl, subfilter.pl or unsubfilter.pl scripts, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, you need to enter the Address of your POP3 email server as well as the POP3 account username and password for that POP3 email box.

Also, instead of forwarding (pipe) emails that arrive at the Return-Path / Errors-To: address to the bounce.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, you need to enter the Address of your POP3 email server as well as the POP3 account username and password for that POP3 email box.

Important: In the External mode the passwords of both installations need to be the same.

18. Now you need to enter your order number as well as your order password for this script. Please enter them to finish the registration.

19. Next the setting for your first list need to be entered.

20. Now you just need to setup the cron job (Unix / Linux) or scheduled tasks (Windows) for the schedule function (see 9.7), the subscribe / unsubscribe by email function (see 9.6, 9.12 & 9.14) and the "Bounce Manager" function (see 9.2) if you like to use these functions.

...All done!

Note: You can update from any Add2it Mailman Free, Standard or Pro version as well as from any earlier version of Add2it MailResponder Pro to the most current version at any time without losing any of your settings, lists or subscribers. Just upload the Add2it MailResponder Pro version files as mentioned above and leave all other files on your server as they are.

If you are updating, please follow these two steps:

1. Upload all file except the .htaccess file into the same directory on your web server that your old installation is in. E.g. If your old files are located in http://www.yourdomain.com/cgi-bin/mrp/, then you would upload the new files into that directory as well.

Important: All files, except those ending in .gif, have to be uploaded in ASCII mode. Only the files end in .gif have to be uploaded in Binary mode.

2. Call the install.pl file in your browser. E.g. If the install.pl script is located in http://www.yourdomain.com/cgi-bin/mrp/ then you would type into your browser... http://www.yourdomain.com/cgi-bin/mrp/install.pl

3. You are finished because there are only two steps to upgrading. :)

Important: If you upgrade from Add2it Mailman Free, Standard or a non-MySQL version of Add2it Mailman Pro (up to 3.02) the field name for the 4th field (misc1) needs to be changed in the HTML forms used on your site. Please refer to the "HTML Code / Links" section of the admin area for the new name.

BTW: If you need to move the the script to another server or if you want to make a backup of all important files, please make sure you download all files in the data directory as well as in all sub-directories. Plus make a backup copy of your MySQL database.

Troubleshooting :

1. First, if you get an error - make sure you uploaded all files (except graphics) in ASCII format only. Uploading in BINARY will corrupt the files.

2. If you attempt to run the script, and get a server error double check you set the permissions as shown above on both the DIRECTORY the script is uploaded to AND the FILE install.pl - if you still get an error try CHMODing the DIRECTORY ONLY to 777 [visually, all permissions are "YES"], then re-try the script initialization.

If necessary, adjust the path to Perl within these files:

- admin.cgi
- admin.pl
- auto.pl
- bounce.pl
- confirm.pl
- display.pl
- ed.cgi
- ed.pl
- filter.pl
- get.pl
- index.pl
- install.cgi
- install.pl
- manager.pl
- schedule.pl
- send.pl
- sub.cgi
- sub.pl
- subfilter.pl
- unsub.cgi
- unsub.pl
- unsubfilter.pl

At the top of each script (and it must remain as the first line) is a default path to the Perl program on your host server. This can vary slightly between UNIX / Linux 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.

NOTE: If you attempt to install this in a directory other than a CGI/CGI-BIN, even with the proper permissions set on both the FILE and DIRECTORY the files are located in it MAY NOT WORK as some web servers restrict where CGI programs can operate and run.

3. Upon initialization "I can't create this file" - This means the permissions are wrong on the DIRECTORY only - the one you created to upload the files to. Check as noted above in number 2.

4. I try to send a message and get a server error.

This means the SENDMAIL or SMTP server settings are incorrect for your script. Click on "Script Settings" in the Add2it MailResponder Pro admin area, and check the SENDMAIL or SMTP server settings. Consult with your web hosting company for the CORRECT SENDMAIL or SMTP server settings for your server.

http://add2it.com/cgi-bin/discus/show.cgi?11/11

http://add2it.com/services/order.php

You can find the Script History online at:
http://add2it.com/scripts/mailresponder-pro-history.shtml

9. Manual of Add2it MailResponder Pro :

9.1 The administrator needs the script to:

SEND/SAVE MESSAGE

- Send a personalized message to a list
  - Choose a list
  - Enter the senders email address, the senders name and the subject of the message.
  - Choose if you like to send this message as a plain text email, a HTML email or simultaneously as plain text and HTML email.
  - Enter the text of the message as plain text and / or HTML text. The top field is for plain text and the bottom field is the WYSIWYG HTML editor. Note the <> toggle to switch from preview to coding.
    Note:  The advanced WYSIWYG HTML message editor (htmlArea) for the HTML message field is only available if you use IE 5.5+ on a Windows system (IE 5.5+ and Windows are copyright by Microsoft)
  - Within the subject, plain text and HTML text of the message you can use the following tags:
    ^fname^ - first name of the receiver
    ^lname^ - last name of the receiver
    ^name^ - full name of the receiver
    ^email^ - email address of the receiver
    ^misc1^ etc. - any other field data of the receiver that you defined for this list
    ^ipreid^ - opt-in, double opt-in request or confirmation IP address or email address when they subscribed by email
    ^timestamp^ - opt-in, double opt-in request or confirmation timestamp
    ^list^ - ID of the list
    ^listtitle^ - title of the list
    ^number^ - number of subscribers of the list
    ^date+x^ - date in x days (x can be any number, e.g. 0=today, 1=tomorrow, -1=yesterday)
    ^month+x^ - month in x months (x can be any number, e.g. 0=this month, 1=next month, -1=last month)
    ^year+x^ - year in x years (x can be any number, e.g. 0=this year, 1=next year, -1=last year)
    ^SSI:URL or path to file^ - Will be replaced with the content of that file (which may contain other tags), e.g. ^SSI:http://www.yourdomain.com/file.htm^ or ^SSI:/home/username/username-www/file.htm^
  - Within the subject, plain text and HTML text of the message for the scheduled sending you can additionally use the following tags:
    ^s_senddate^ - sending date
    ^s_date^ - another date
    ^s_name^ - a name
    ^s_title^ - a title
    ^s_place^ - a place
    ^s_begintime^ - a start time
    ^s_endtime^ - an end time
    ^s_offer^ - an offer text
    ^s_text^ - another text
    ^s_year^ - the year
  - If you want to attach files to your message choose them (up to four files)
  - Choose if you want to send, schedule and or save the message
    - If you want to save or schedule it, enter an ID
- Load a saved message to edit and / or send it
- Delete a saved message

EDIT SCHEDULE (Requires cron job to be setup... see 9.7)

- Save a schedule on which a personalized message should be send to a list
  - Enter the sending date in the format DD.MM.YY or MM/DD/YY
  - Choose a list
  - Choose a saved message
  - Enter data in all other fields as you like
- Save several schedules from a list of schedules
  - Choose if the first line of the list contains field names and should be skipped
  - Choose the symbol that delimits the fields
  - Enter your list of schedules in the format sending date, list ID, other date, name, title, place, start time, end time, offer text, message ID, other text, year
- Load a saved schedule to edit it
- Erase a saved schedule

ADD SUBSCRIBERS

- Add subscribers manually to one or more lists (Press and hold 'CTRL' to select several lists)
  - one subscriber at the time
    - You have to enter the email address. The first name, last name and the fourth field are, depending on how you chose the settings of the list, eventually optional.
    - Choose if you want to send subscribe autoresponse to new subscriber. Yes or No
    - Choose if you want to overwrite existing subscriber entries. Yes or No
    - Choose if you want to add without double opt-in. Yes or No (only with double opt-in lists)
  - several subscriber at once (import lists)
    - Choose a format and which symbol delimits each field of a list of subscribers
    - Choose if you want to send subscribe autoresponse to new subscriber. Yes or No
    - Choose if you want to overwrite existing subscriber entries. Yes or No
    - Choose if you want to add without double opt-in. Yes or No (only with douple opt-in lists)
    - Enter a list of subscribers
      Note: One subscriber per line and each field has to be delimited with the provided symbol.
    - or choose a list file on your computer
      Note: One subscriber per line and each field has to be delimited with the provided symbol.
  - Import leads of a specific format (If a list doesn't have the additional fields with the tags shown in italic, this part of the data will not be imported)
    - Choose the leads format that you want to import
    - Choose if you want to send subscribe autoresponse to new subscriber. Yes or No
    - Choose if you want to overwrite existing subscriber entries. Yes or No
    - Choose if you want to add without double opt-in. Yes or No (only with douple opt-in lists)
    - choose a list file on your computer
      Note: One subscriber per line.

SUBSCRIBER COUNTER

- Count how many subscribers, unconfirmed double opt-in and double opt-out requests each list has
- Count the total number of subscribers and unique subscribers in all three categories

SUBSCRIBER EDITOR

- Search for subscribers and edit, copy, move or delete them or view their log file entries
  - Choose the list and the field in which you want to search.
  - Choose the order you want the results to be displayed
  - Select if you want the search to be case sensitive
  - Choose if you want to seach only the log file of a list (sorted by date)
  - Enter the string you want to search for
    - You can change and save the data of every subscriber that has been found the way you like it
    - If you change the list or the email address, choose if you want this subscriber to be moved or copied.
    - You can take a look at the log file entries
    - The subscriber can be deleted, choose if you want to send an "Unsubscribe Message" to the subscriber or if you want to remove them without asking them to double opt-out (only with double opt-out lists)

REMOVE SUBSCRIBERS

- Remove subscribers manually from one or more lists (Press and hold 'CTRL' to select several lists)
  - One or more subscriber at the time (remove whole lists)
    - Choose if you want to send subscribe autoresponse to new subscriber. Yes or No
    - Choose if you want to overwrite existing subscriber entries. Yes or No
    - Choose if you want to remove without double opt-out. Yes or No (only with double opt-out lists)
    - Enter a list of subscribers
      Note: One email address per line.
    - or choose a list file on your computer
      Note: One email address per line.

ADD LIST

- Add new lists
  - Choose a title for your list (e.g. More4you Newsletter)
  - Choose an ID for your list (e.g. m4u)
    Note: Each list must have a unique ID and all spaces will be converted to dashes. It is recommended to keep the ID as short as possible.
  - Choose if you want any of the following options:
    Send copy of subscribe request to admin? Yes or No
    Send copy of unsubscribe request to admin? Yes or No
    Send copy of edit request to admin? Yes or No
    Is the first name required? Yes or No
    Is the last name required? Yes or No
    Is the subscriber allowed to edit his/her email address? Yes or No
    Is the subscriber allowed to edit his/her first name? Yes or No
    Is the subscriber allowed to edit his/her last name? Yes or No
  - Choose a subject for the subscribe messages (e.g. Thank you ^fname^ ^lname^ for subscribing to the '^listtitle^' list...)
  - Choose a subject for the unsubscribe messages (e.g. As requested ^email^ has been unsubscribed from the '^listtitle^' list...)
  - Does this list require double opt-in from subscribers? Yes or No
  - Does this list require double opt-out from subscribers? Yes or No
  - Choose a subject for the double opt-in confirmation email messages (e.g. ^fname^ ^lname^, important message regarding your '^listtitle^' list subscription...)
  - Choose a subject for the double opt-out confirmation email messages (e.g. ^fname^ ^lname^, do you really want to unsubscribe from the '^listtitle^' list?)
  - If you like, choose a list to remove subscriber from when added to this list
  - If you have Add2it AutoRespond Pro installed on the same server:  Choose if at the time a subscriber subscribes, the subscriber should be also added to an Add2it AutoRespond Pro autoresponder list (choose which Add2it AutoRespond Pro autoresponder list)
  - Enter/edit the "Subscribe Autoresponse Email", "HTML Subscribe Autoresponse Email", "Unsubscribe Autoresponse Email", "HTML Unsubscribe Autoresponse Email", "Double Opt-in Autoresponse Email", "HTML Double Opt-in Autoresponse Email", "Double Opt-out Autoresponse Email" and "HTML Double Opt-out Autoresponse Email" messages. If you want the autoresponses to be plain text messages, simply leave the HTML autoresponse fields blank.
    Note:  The advanced WYSIWYG HTML message editor (htmlArea) for the HTML message field is only available if you use IE 5.5+ on a Windows system (IE 5.5+ and Windows are copyright by Microsoft)
  - Within the subject and the text of the messages you can use the following tags:
    ^fname^ - first name of the receiver
    ^lname^ - last name of the receiver
    ^name^ - full name of the receiver
    ^email^ - email address of the receiver
    ^misc1^ etc. - any other field data of the receiver that you defined for this list
    ^ipreid^ - opt-in, double opt-in request or confirmation IP address or email address when they subscribed by email
    ^timestamp^ - opt-in, double opt-in request or confirmation timestamp
    ^list^ - ID of the list
    ^listtitle^ - title of the list
    ^number^ - for the number of subscribers of the list
    ^date+x^ - for the date in x days (x can be any number, e.g. 0=today, 1=tomorrow, -1=yesterday)
    ^month+x^ - for the month in x months (x can be any number, e.g. 0=this month, 1=next month, -1=last month)
    ^year+x^ - for the year in x years (x can be any number, e.g. 0=this year, 1=next year, -1=last year)
    ^confirmurl^ - for the confirmation URL in the double Opt-in / Opt-out Autoresponse Email boxes only
    ^SSI:URL or path to file^ - Will be replaced with the content of that file (which may contain other tags), e.g. ^SSI:http://www.yourdomain.com/file.htm^ or ^SSI:/home/username/username-www/file.htm^
  - Enter/edit the "HTML Code for Subscribe page", "HTML Code for Unsubscribe page", "HTML Code for double Opt-in page" and "HTML Code for double Opt-out page" codes
  - Within the "HTML Code for Subscribe page", "HTML Code for Unsubscribe page", "HTML Code for double Opt-in page" and "HTML Code for double Opt-out page" codes you can use the following tags:
    ^fname^ - first name of the receiver
    ^lname^ - last name of the receiver
    ^name^ - full name of the receiver
    ^email^ - email address of the receiver
    ^misc1^ - fourth field of the receiver
    ^ipreid^ - opt-in, double opt-in request or confirmation IP address or email address when they subscribed by email
    ^timestamp^ - opt-in, double opt-in request or confirmation timestamp
    ^list^ - ID of the list
    ^listtitle^ - title of the list
    ^number^ for the number of subscribers of the list
    ^date+x^ for the date in x days (x can be any number, e.g. 0=today, 1=tomorrow, -1=yesterday)
    ^month+x^ - for the month in x months (x can be any number, e.g. 0=this month, 1=next month, -1=last month)
    ^year+x^ - for the year in x years (x can be any number, e.g. 0=this year, 1=next year, -1=last year)
    ^SSI:URL or path to file^ - Will be replaced with the content of that file (which may contain other tags), e.g. ^SSI:http://www.yourdomain.com/file.htm^ or ^SSI:/home/username/username-www/file.htm^
    Note:  If the code starts with "http", the subscriber will be redirected to the specified URL instead.

FIELD MANAGER

- Manage the additional fields a list uses
  - Add a new field type to a list
    - Choose a field ID which will be used as the tag in your messages and on script generated HTML pages in this format: ^fieldID^ (only letters and numbers allowed)
    - Enter a field description that will be used by ed.pl
    - Is this field required? Yes or No
    - Is this field editable by the subscriber? Yes or No
  - See a list of fields currently assigned to a list and edit or remove them
  - See a list of existing field types and add them to a list or edit them

LIST LOGS

- View the logs of a list

DELETE LIST

- Delete a list including all subscribers and logs

ACCESS BANNING

- Ban email addresses or domains from your lists
  - Enter the email addresses or domains
    e.g. spam@sender.com or @competition.com
    Note: One email address or domain per line. Be careful what you ban!  All email addresses that contain the string you entered will be banned.
  - Choose the type of the ban (admin or requested)

HTML CODE / LINKS

- Get the HTML code and links of a list in three ways:
  1. See how it could look like on a web site. This version is fully functional.
  2. The HTML code ready to copy & paste.
  3. The HTML code in the advanced WYSIWYG HTML code editor. You can adjust it, before you copy & paste it.
     Note:  The advanced WYSIWYG HTML message editor (htmlArea) for the HTML message field is only available if you use IE 5.5+ on a Windows system (IE 5.5+ and Windows are copyright by Microsoft)

SOURCE OF LIST

- View and download the complete source of a list

LIST SETTINGS

- Edit the options of a list
  - When should the administrator get email copies of what is happening?
  - Are subscribers allowed to edit their own data (First name, last name, email address and miscellaneous field)?
  - Which fields are required for new subscribers?
  - How should the autoresponce email subjects look like?
  - Should the list require double opt-in and / or double opt-out?
  - How should the autoresponce emails look like?
    Note:  The advanced WYSIWYG HTML message editor (htmlArea) for the HTML message field is only available if you use IE 5.5+ on a Windows system (IE 5.5+ and Windows are copyright by Microsoft)
  - How should the HTML pages look like?
  - If you like, change the list to remove subscriber from when added to this list
  - If you have Add2it AutoRespond Pro installed on the same server:  Change if at the time a subscriber subscribes, the subscriber should be also added to an Add2it AutoRespond Pro autoresponder list (choose which Add2it AutoRespond Pro autoresponder list)

BOUNCE MANAGER (Requires email pipe or cron job to be setup... see 9.2 or 9.7)

- Add phrases to filter bounced messages for and choose how many bounce points an email address gets if a bounced message contains this phrase
  Note:  The phrase is NOT case sensitive. You can use the usual Perl meta characters like "." for any kind of character, "*" for zero or more of the last characters in a row and even ".*" for zero or more characters of any kind. To find e.g. "550 <anykindofemailaddress@anykindofdomain.com> User unknown" the search phrase could look like this:  550 .* user unknown
- See a list of saved phrases and their number of bounce points
  - Choose which of those saved phrases you want to delete or edit
- See a list of subjects of all unrecognized bounced messages
  - Choose which one you want to delete or edit (load message text)

SEND LOGS / STATS

- Displays the following statistic data (every one: this month, last month and total):
  - Number of messages that the admin has send
  - Number of emails that the admin has send in form of messages
  - Number of emails send after a subscription through the sub.pl file
  - Number of emails send after a double opt-in request through the sub.pl file
  - Number of emails send after a double opt-in confirmation through the confirm.pl file
  - Number of emails send after a subscription through the subfiler.pl file
  - Number of emails send after a double opt-in request through the subfiler.pl file
  - Number of emails send after a subscription through the filter.pl file
  - Number of emails send after a double opt-in request through the filter.pl file
  - Number of emails send after a subscription through the scriptsub.pl file
  - Number of emails send after a double opt-in request through the scriptsub.pl file
  - Number of emails send after a subscription through the subscript.pl file
  - Number of emails send after an unsubscription through the unsub.pl file
  - Number of emails send after a double opt-out request through the unsub.pl file
  - Number of emails send after a double opt-out confirmation through the confirm.pl file
  - Number of emails send after an unsubscription through the unsubfiler.pl file
  - Number of emails send after a double opt-out request through the unsubfiler.pl file
  - Number of emails send after an unsubscription through the filter.pl file
  - Number of emails send after a double opt-out request through the filter.pl file
  - Number of emails send after an unsubscription through the scriptunsub.pl file
  - Number of emails send after a double opt-out request through the scriptunsub.pl file
  - Number of emails send after the admin has manually added a subscriber
  - Number of emails send after the admin has manually requested double opt-in
  - Number of emails send after the admin has manually removed a subscriber
  - Number of emails send after the admin has manually requested double opt-out
- Displays the sending logs

SCRIPT SETTINGS

- Change the settings of Add2it MailResponder Pro

  Standard installation (all files are uploaded in one location on one server):
  - URL of directory in which the script files are located
  - Path to sendmail (UNIX / Linux) or
  - SMTP server and port address (UNIX / Linux and Windows)
    Note: Enter only one of the above, either the path to sendmail OR the SMTP server and port address.

  External installation (all files are uploaded in one location on one server PLUS a copy of all files are uploaded in another location on another server):
  - URL of directory in which the script files are located
  - Path to sendmail (UNIX / Linux) or
  - SMTP server and port address (UNIX / Linux and Windows)
    Note: Enter only one of the above, either the path to sendmail OR the SMTP server and port address.

  - MySQL host (usually localhost)
  - MySQL database name you setup (e.g. yourdomain_databasename)
  - MySQL username assigned to the MySQL database
  - MySQL password you chose for the MySQL user
   - Address of your POP3 email server. Only needed if you also enter POP3 account data. In that case or if you want to use the Schedule function, you need to setup this cron-job (UNIX / Linux):
    0,5,10,15,20,25,30,35,40,45,50,55 * * * * schedule.pl
    On a Windows system you need to execute the schedule.pl file once every 5 minutes.
  - Subscribe / Unsubscribe messages POP3 account username. Instead of forwarding (pipe) emails that arrive at the Subscribe / Unsubscribe addresses to the filter.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose.
  - Subscribe / Unsubscribe messages POP3 account password.
  - If this script is located inside the cgi-bin please change this path to the location of your web pages (usually located inside the public_html or www directory, has to end with /).
  - If this script is located inside the cgi-bin please change this URL to the location of your web pages (has to end with /) otherwise leave blank.
  - Choose your preferred language (English, German, Spanish - Argentina, Spanish - Continental, Dutch or Chinese - Cantonese).
  - At "New Message Line" type you should choose "RFC 822 compatible" only if you get an error message like "Message not accepted for delivery: 451 See http://pobox.com/~djb/docs/smtplf.html" or "Bare LF detected" when the script tries to send an email.
  - Maximum time for each manual subscription, unsubscriptions or messages send process at each run (1 to 30). Decrease value if your server stops early.
  - Choose how many messages the script will send per second at a maximum (0.5 to 10 or as many as possible). This is especially important, if your web hosts allows only a certain amount of email to be send within a certain time period.
  - Choose how many seconds the script should wait at least before it starts the next sending process (0 to 30).
  - Choose what to use in messages if no first name is given.
  - Standard subject of subscribe and unsubscribe messages
  - Standard double opt-in / opt-out confirmation email subjects
  - Name and email address of administrator
  - Enter a Reply-To address. This is the email address that the receiver of the message will be able to reply to you at. This is sent on all outgoing emails. If you prefer that the receiver of the message replies to the senders email address leave this field blank.
  - Enter a Return-Path / Errors-To address. This is the email address that will receive undeliverable message notices and possibly some messages from autoresponders. This is sent on all outgoing emails. If you prefer that these kind of messages should be delivered to the senders email address leave this field blank, but it is required if you want to use the "Bounce Manager".
    Note: If you notice that your server overwrites the content of the Return-path: (Bounces are not handled automatically), then you need to do the following. You or somebody with root access to your server (your web hosts technical support staff) needs to add the following line to the "MAIN CONFIGURATION SETTINGS" of the /etc/exim.conf file:
trusted_users = your_account_username
Only trusted users are permitted to specify senders when mail is passed to Exim via the command line.
To add several users you can use:
trusted_users = username1:username2:username3
  - Bounced messages POP3 account username. Instead of forwarding (pipe) emails that arrive at the Return-Path / Errors-To: address to the bounce.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose.
  - Bounced messages POP3 account password
  - Enter the number of bounce points an email address has to collect before it gets deleted.
  - Enter the number of days after which a new bounce will first reset the bounce points of an email address.
  - If you are a member of the Add2it Affiliate Program, enter your ID here to show all links with your id
  - Change password of admin center
  - Path to your Add2it AutoRespond Pro installation (optional, otherwise has to end with /).
  - Edit the header and footer area of all pages that can be seen by the admin or the subscribers. The header has to contain a ^title^ tag and the footer has to contain ^add2it^ tag. Optionally the footer can contain ^language^, ^admin^ and ^back^ tags.

  Here is an example for the header area:

<html>
<head>
<title>Add2it MailResponder Pro - ^title^</title>
<style>
<!--A:link { COLOR: #cc0000; TEXT-DECORATION: underline }
A:visited { COLOR: #990000; TEXT-DECORATION: underline }
A:hover { COLOR: #009900; CURSOR: hand; TEXT-DECORATION: underline }
-->
</style>
</head>
<body bgColor=#FFFF99 vLink=#990000 link="#CC0000">
<div align="center">
<center>
<table border="0" width="90%" cellspacing="0" cellpadding="2">
<tr>
<td width="100%" bgcolor=#003399><font face="Arial, Helvetica, sans-serif" size=2 color=#FFFF99><b>Add2it MailResponder Pro - ^title^</b></font></td>
</tr>
</table>

  Here is an example for the footer area:

<br>
<table width="90%" border="2" cellpadding="2" cellspacing="0" bordercolor="#003399">
<tr>
<td width="30%" align="center"><b><font face="Arial, Helvetica, sans-serif" size=1 color="#003399">
^add2it^
</font></b></td>
<td width="40%" align="center" bgcolor=#003399>
^language^
^admin^
</td>
<td width="30%" align="center"><b><font face="Arial, Helvetica, sans-serif" size=2>
^back^
</font></b></td>
</tr>
</table>
</center>
</div>
</body>
</html>

Please call index.pl with:
(preferred language)

(any other language)
e.g.

- Handle bounced messages automatically

Subscribers can automatically be unsubscribed, if messages to them bounced to often. The script checks each bounced message for phrases that the admin can add in the "Bounce Manager". If it recognizes the type of bounced message, it adds bounce points to that subscribers email address.

If the number of bounce points reaches a limit, which the admin can adjust in the "Script Settings", the email address will be deleted from that list.

If a certain number of days passed by beween the last bounced message and this bounced message, then the bounce points of that subscribers email address will first reset to zero before the new bounce points get added. The admin can also adjust the number of days in the "Script Settings".

The Return-Path / Errors-To address needs to be entered in the "Script Settings" section for this function to work properly. You can use e.g. returnto@yourdomain.com as your Return-Path / Errors-To address.

Note: Instead of forwarding (pipe) emails that arrive at the Return-Path / Errors-To: address to the bounce.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, please follow the instructions at 9.7.

Instructions for server using cPanel:

To redirect email to this script, all you need to do is to use cPanel's "Forwarders" within the "Mails" section. There add a forwarder from:
returnto@yourdomain.com
to:
bounce.pl

Instructions for using .qmail-returnto (servers running qmail):

To redirect email to this script, create new .qmail-returnto file and upload them in ASCII mode into that directory on your server which contains all the .qmail-.... files.

This file is the new file that replaced the rc.local.init file on the old Host4Profit servers. In other words, if your with Host4Profit, use this file and not the other three that will be mentioned later. If you are on the new Host4Profit servers, the other three files (.forward, .rc.local.init or procmailrc) will do nothing. Also, only ONE of these files should be on any system: .qmail-returnto, .forward, .rc.local.init or procmailrc. If you're not on a Kiosk or Host4Profit server, you'll need to contact your web hosts technical support staff and ask them which file is the right choice for your server (this is usually the hardest part of the install for non Kiosk or Host4Profit servers).

The content of the file has to be:
1st line:  |/usr/bin/perl bounce.pl
2nd line:  <empty line>

username = Your hosting service username. On Host4Profit this is 8 digits.

The file needs to be saved in UNIX / Linux format!

When uploading this file, upload it to the 'username-mail' directory on your server, where username is your hosting service username.

Please note that the above example is Host4Profit specific. If you're on another server, please contact your web hosts technical support staff and ask them for the proper path.

Instructions for using .rc.local.init (servers running procmail):

This file is used on the old Host4Profit servers or on Alabanza based hosting only (Alabanza is the company Host4Profit buys from... you can tell their hosting by the control panel).

The following lines need to be adjusted:
1st line:  DOMAIN=(yourdomain.com)
2nd line:  | bounce.pl

Just substitute yourdomain.com for your actual domain name. For example, if your domain was http://add2it.com, change yourdomain.com to add2it.com.

Instructions for using .procmailrc (servers running procmail):

This file is preferred over the .forward file. Ask your web hosts technical support staff if they will allow you to use this if possible. If you're on a Kiosk or Host4Profit server, please disregard this file, as it doesn't need to be installed.

In this line: * ^TOreturnto@yourdomain.com

You would replace "yourdomain" with your actual domain name.

The other line in this file is modified just like the .rc.local.init file, the line with the path in it:

| bounce.pl

Nothing else on this file needs to be modified.

Instructions for using .forward (servers running sendmail):

This file is to only be used as a last resort, and is not for use on Kiosk or Host4Profit or Alabanza based servers. You'll need to contact your web hosts technical support staff and ask them what file they prefer you use.

The following line need to be adjusted:
\catchalluser,"|/usr/bin/perl bounce.pl"

There are 3 parts to editing this line. If you're with Kiosk or Host4Profit, don't even worry about this file.

On the left hand side, you'll see the name catchalluser. The Catchalluser name really depends on what you setup as the Catchalluser name and really on the system configuration. In some cases you have control over it, in some cases you don't. For example, if you're using the name default@yourdomain.com as a funnel to forward all misdirected mail that goes to usernames that don't exist on your mail server, then all this email would be redirected to the email address of your choice.

In the case above, 'default' would be your Catchalluser name. Log into the place where you edit and add email addresses. If you have any doubt, contact your web hosts technical support staff and ask them.

In the middle, you'll see /usr/bin/perl. That's simply the path to Perl and you'll need to modify that to your unique path to Perl which can vary slightly depending on which hosting service you're with.

This has been tested on the servers of Kiosk and Host4Profit.

Add2it.com uses Kiosk.

If you know how to forward emails at arrive at a certain email address to a script on other servers, please share your knowledge and post it in the Add2it MailResponder Pro Support Forum at:
http://add2it.com/cgi-bin/discus/show.cgi?11/11

- Confirm that the subscriber wanted to opt-in / opt-out (Double Opt-in / Double Opt-out)

Note: The subscriber has 30 days time to confirm the double opt-in / opt-out request before it will expire.

They call confirm.pl with this links:
(preferred language)
e.g.

(any other language)
e.g.

- Display the number of subscribers of a list on a web page

Simply call display.pl with the following HTML tag (JavaScript):
<script language="JavaScript1.1" src="display.pl?list=^list^"></script>

or with this HTML tag (SSI):
<!--#exec cgi="cgi-bin/mrp/display.pl"-->

If you call per SSI you need to adjust the following line within the variables.pl file:

$list = "list ID";

Replace "list ID" with the actual list ID e.g. with "news".

- Change the data somebody submitted when somebody subscribed

They call ed.pl with this links:
(preferred language)
e.g.

(any other language)
e.g.

Or use the following HTML code on a web page to allow subscribers to enter their email address and then edit their subscriber data:

<form method="POST" action="ed.pl">
<p>Email address:*<br>
<input type="text" name="data" size="20"><br>
* required field</p>
<input type="hidden" name="task" value="edit">
<input type="hidden" name="list" value="list">
<input type="hidden" name="language" value="language-sub-dir">
<p><input type=submit style="BACKGROUND: #003399; COLOR: #FFFF99; FONT-WEIGHT: bold" value="Edit Subscriber Data"></p>
</form>

- add or remove subscribers automatically to or from a list

Subscribers can subscribe and unsubscribe by sending a simple email to one email address. All they need to do is to write the words "subscribe ID" or "unsubscribe ID" in the subject of that email message (where ID is replaced with the exact id of the list being subscribed or unsubscribed). For example the subject line to subscribe to a list with the id list1 would be:

subscribe list1

Note: Instead of forwarding (pipe) emails that arrive at the subscribe / unsubscribe address to the filter.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, please follow the instructions at 9.7.

Instructions for servers using cPanel:

To redirect email to this script, all you need to do is to use cPanel's "Forwarders" within the "Mails" section. There add forwarders from:
subscribe@yourdomain.com and unsubscribe@yourdomain.com
to:
filter.pl

Instructions for using .qmail-subscribe + .qmail-unsubscribe (servers running qmail):

To redirect email to this script, create new .qmail-subscribe and .qmail-unsubscribe files and upload them in ASCII mode into that directory on your server which contains all the .qmail-.... files.

This file is the new file that replaced the rc.local.init file on the old Host4Profit servers. In other words, if your with Host4Profit, use this file and not the other three that will be mentioned later. If you are on the new Host4Profit servers, the other three files (.forward, .rc.local.init or procmailrc) will do nothing. Also, only ONE of these files should be on any system: .qmail-subscribe (+ .qmail-unsubscribe), .forward, .rc.local.init or procmailrc. If you're not on a Host4Profit server, you'll need to contact your web hosts technical support staff and ask them which file is the right choice for your server (this is usually the hardest part of the install for non Kiosk or Host4Profit servers).

The content of the files has to be:
1st line:  |/usr/bin/perl filter.pl
2nd line:  <empty line>

username = Your hosting service username. On Host4Profit this is 8 digits.

The files needs to be saved in UNIX / Linux format!

When uploading this file, upload it to the 'username-mail' directory on your server, where username is your hosting service username.

Please note that the above example is Host4Profit specific. If you're on another server, please contact your web hosts technical support staff and ask them for the proper path.

Instructions for using .rc.local.init (servers running procmail):

This file is used on the old Host4Profit servers or on Alabanza based hosting only (Alabanza is the company Host4Profit buys from... you can tell their hosting by the control panel).

The following lines need to be adjusted:
1st line:  DOMAIN=(yourdomain.com)
2nd line:  | filter.pl

Just substitute yourdomain.com for your actual domain name. For example, if your domain was http://add2it.com, change yourdomain.com to add2it.com.

Instructions for using .procmailrc (servers running procmail):

This file is preferred over the .forward file. Ask your web hosts technical support staff if they will allow you to use this if possible. If you're on a Kiosk or Host4Profit server, please disregard this file, as it doesn't need to be installed.

In this line: * ^TOsubscribe@yourdomain.com

You would replace "yourdomain" with your actual domain name.

The other line in this file is modified just like the .rc.local.init file, the line with the path in it:

| filter.pl

Nothing else on this file needs to be modified.

Instructions for using .forward (servers running sendmail):

This file is to only be used as a last resort, and is not for use on Kiosk or Host4Profit or Alabanza based servers. You'll need to contact your web hosts technical support staff and ask them what file they prefer you use.

The following line need to be adjusted:
\catchalluser,"|/usr/bin/perl filter.pl"

There are 3 parts to editing this line. If you're with Kiosk or Host4Profit, don't even worry about this file.

On the left hand side, you'll see the name catchalluser. The Catchalluser name really depends on what you setup as the Catchalluser name and really on the system configuration. In some cases you have control over it, in some cases you don't. For example, if you're using the name default@yourdomain.com as a funnel to forward all misdirected mail that goes to usernames that don't exist on your mail server, then all this email would be redirected to the email address of your choice.

In the case above, 'default' would be your Catchalluser name. Log into the place where you edit and add email addresses. If you have any doubt, contact your web hosts technical support staff and ask them.

In the middle, you'll see /usr/bin/perl. That's simply the path to Perl and you'll need to modify that to your unique path to Perl which can vary slightly depending on which hosting service you're with.

This has been tested on the servers of Kiosk and Host4Profit.

Add2it.com uses Kiosk.

- Send out scheduled messages automatically to subscribers

- This script will also call the bounce.pl and filter.pl scripts. If you entered POP3 account data in the "Script Settings" section those scripts will pick up and process the emails in those mailboxes.

This script needs to be called by a cron job (Unix / Linux) or scheduled tasks (Windows). The way to setup a cron job or scheduled tasks may vary from host to host. If you are not sure about how to do this, please contact your web hosts technical support staff. With Kiosk and Host4Profit you can simply set up cron jobs in the control panel.

Note: If your web hosts does not permit cron jobs or scheduled tasks, add instead this HTML code at the bottom of your index.htm file right before </body>:
<script language="JavaScript1.1" src="schedule.pl"></script>

On Unix / Linux:

The cron job line to call the script once every 5 minutes will need to look like this:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * schedule.pl

Note: If your on a Kiosk or Host4Profit server or with any other host that provides cron job setup in a control panel, you can completely ignore the following part of this chapter.

For everyone else:

A cron event is an automatic feature to call a script at given intervals. In the case of this script, to call the script e.g. each full hour or every 5 minutes to continue to send the scheduled messages.

Out of all the setup objectives in this manual, this one is without a doubt going to be the most complicated and tricky, especially for the beginner. However, if your host will run a cron event for you, you can skip this chapter. If not, and you're a beginner, you might want to contact someone you know that's familiar with SSH, secure Telnet or running cron events.

In either case, you'll need to run a cron event on a 'cron.txt' file that contains the above cron job line.

First of all, you'll need to verify with your hosting service that you do indeed have SSH capabilities. You can simply contact them and request information on that. Just ask them to activate SSH for you and ask them if they'll run the cron for you. If they will run it for you, then just give them the path to the path to the 'cron.txt' file that contains the above cron job line.

You'll need to have SSH to do this, unless someone does it for you in which case they'll need SSH. You can go to http://www.vandyke.com and download a free, 30 day evaluation copy of Secure CRT. This will give you the ability to run the cron.

You only need to run the cron once!

SecureCRT includes strong cryptography. U.S. export regulations for encryption software require an eligibility screen before downloading is allowed. This means they'll need some basic information about you before you download the program. After downloading, simply install the program and it will put an icon on your Windows desktop.

After downloading SecureCRT, the first thing you need to do with it is create an "Identity File". An identity file is required for RSA authentication.

Setting Up RSA Authentication:

Overview of RSA Authentication:

RSA authentication uses a public-private key pair to authenticate and log in to an SSH1 Server. It offers a higher level of authentication security than password authentication by requiring both the private key and the passphrase that protects the private key in order to complete authentication.

Setting up RSA authentication for a SecureCRT session is a multi-step process. Identity files are created with the RSA key generation wizard. The identity file is defined for global or session-specific use in the advanced SSH options dialog. Then the public key is added to the authorized_keys file located on the SSH server (your hosting service).

Note: Only SSH1 supports RSA authentication.

Creating Identity Files:

To create an RSA identity file:

a) In the connect dialog, select the SSH1 session with which you would like to use the identity files.

b) Open the session options dialog and in the connection category, click the advanced button.

c) Select the general tab and click on the create identity file button in the identity ID section.

d) Follow the instructions in the RSA key generation wizard to create your identity files. Once your public-private key pair has been generated by the RSA key generation wizard, you will be prompted for the path and filename in which your private key will be stored. Be sure to specify a secure location for this file such that you are the only individual with access to it. The public key will be placed in a file with the same basename as the private key file, but with an extension of .pub.

Using Your Identity Files:

Once you have created your identity files, there are several steps that will need to be completed so that you can make use of them with SecureCRT. The necessary steps are:

1) Transfer the identity.pub file to the remote machine
2) Put the contents of the identity.pub file in your authorized_keys file on the remote machine
3) Configure SecureCRT to use the identity file with RSA authentication.

1. Transfer the Identity File to the SSH1 Server

In order to use your public key you must transfer the xxxxxxxx.pub file created by the key generation wizard to the ~/.ssh/ directory on the SSH1 server. One of the easiest ways to transfer this file to the SSH1 server is to use the ZModem file transfer feature provided by SecureCRT. If the remote machine does not have ZModem installed, you will need to use an FTP client to transfer the identity file to the remote machine. Another way to transfer the identity file to the remote machine is to copy and paste the contents of the identity file. This is how it works with Host4Profit. To accomplish this, use Notepad.exe to open the identity file and copy the contents of the identity file to the clipboard. On the remote machine, create a file using your favorite editor and paste the contents of the clipboard using the paste button.

2. Update the authorized_keys File on the Remote Machine

Once you have transferred the identity.pub file to the remote machine, you must update the authorized_keys file on the remote machine. The following steps outline this update process.

a) Connect to the remote SSH1 server using SSH1 and password authentication.

b) Append the contents of the public key file created with the RSA key generation wizard to the file ~/.ssh/authorized_keys on the remote host. The default name of the public key file is identity.pub. Create the ~/.ssh/authorized_keys file if it does not already exist. If you want multiple authorized keys, append the contents of the public key file to the authorized_keys file. The simplest way to do this is typically:

% cat identity.pub >> ~/.ssh/authorized_keys

(note that the name of the identity file can be different than the example)

Note on placing public keys: The format of the authorized_keys file requires that each entry consist of a single long line. If you use copy and paste to add a public key to the ~/.ssh/authorized_keys file, make sure that the entry contains no additional newline characters.

3. Configure SecureCRT to use your Identity Files

The identity file created by the key generation wizard contains both your new public key and your new private key. To configure SecureCRT to use the identity file:

a) In the Connect dialog, select the SSH1 session with which you would like to use the identity file.

b) Open the Session Options dialog and in the Connection category, change the Authentication setting from Password to RSA.

c) If you have more than one identity file, you may need to click on the advanced button and verify that the session is using the session-specific key you have created.

d) Click on the OK button to save the changes. If you supplied a passphrase when you created your key, you will be prompted to enter it during the connection process.

In closing, this can be tricky for most people, so you might want to contact a support professional to do this for you if you have any doubts. Just refer them to this text. If this process doesn't seem familiar to you and you're not confident by now about this process, I would recommend having someone help you through at least this phase of the install.

You might also see if your web hosts technical support staff will walk you through the installation.

If you would like to know more about cron jobs, I can recommend this page:
http://www.aota.net/Script_Installation_Tips/cronhelp.php3

On Windows:

If you have direct access to a Windows NT/2000/XP/2003 server machine you can use "Scheduled Tasks" from the Control Panel, pointing to the location of the "schedule.bat" batch script file.

It is recommended to redirect its output to a log file. For example, use

C:\path_to_your_home\mrp\schedule.bat > mrp_cronjob.log

as entry in the Start Task box. This creates a "mrp_cronjob.log" file which always holds the output of the last batch process.

The schedule.bat would then call:

C:\Perl\bin\perl.exe schedule.pl

- add a non-offensive pop-up subscribe window to your web pages which allows visitors to subscribe to your lists without entering any data

To automatically capture information means to be able to capture the visitors name and email address BEFORE the page even loads by extracting it from their email software. This is just one of the things that makes Add2it MailResponder Pro 500% better at collecting opt-in subscribers.

There are only 3 steps to install the code. You'll need to make sure all 3 parts of code are installed properly. These 3 pieces of code will need to be installed on each and every page you want to collect subscribers at.

Install the following code between your <HEAD></HEAD> tags:

<script language="JavaScript" src="add2it-optin.js"></script>
<script language="JavaScript"><!--
var buttonText = "Click here to subscribe to the FREE More4you Newsletter";
var email = "subscribe-listID@yourdomain.com";
var emailSubject = "subscribe";
var buttonBgColor = "#003399";
var buttonBgColorOver = "#FFFF99";
var buttonTextColor = "#FFFF99";
var buttonTextColorOver = "#003399";
var displayText = "Subscribe to the FREE More4you Newsletter and get:\n\n -> More tips, training and tutorials for webmasters and entrepreneurs...\n     everything you need to make your website and business a success!\n\nThis is all completely automatic - just hit the button below!\n\nComplete privacy: Your email address will not be revealed to third parties";
var forwardURL = "";
//--></script>

Just copy the code and paste it into your HTML document and change the email address as well as any text or color as you like.

This code will still work even if your friend allows you to collect subscribers from their website. Also, you can collect subscribers from free servers, eBooks and auctions with this code!

Add the following command parameter to your <BODY> tag:

onload='Go(displayText)'

or add this Java Script code in a web page before the </BODY> tag:

<script language="JavaScript"><!--
Go(displayText);
//--></script>

Here's a real world example of this code installed inside your body tag:

<BODY onload='Go(displayText)' bgColor=#FFFF99 vLink=#990000 link="#CC0000">

Notice that snippet of code above as just one of the command parameters.

Add the following code somewhere within the body of your document, that is, within the <BODY></BODY> tags:

<script language="JavaScript"><!--
showButton(buttonText, email, emailSubject, buttonBgColor, buttonBgColorOver, buttonTextColor, buttonTextColorOver);
//--></script>

This code above needs to go on each page and can be put e.g. on the very bottom. If somebody clicks on the button that will appear here, the script will capture their information just like the popup window.

To sum this chapter up, all 3 code segments listed above need to be installed on each page you wish to collect subscribers on. These 3 code segments can be installed on any server including free sites and eBay or even your friends websites if they'll let you and you'll keep adding more and more subscribers as long as the script is running from one centralized source!

- Add subscribers through another Perl script

A Perl script needs to call scriptsub.pl the following way:

require "scriptsub.pl";
&mrp_scriptadd ($mrp_path,$list,$ENV{'REMOTE_ADDR'},$email,$fname,$lname);

$mrp_path => server path to Add2it MailResponder Pro ( )
$list     => list ID
$email    => email address of the subscriber
$fname    => firstname of the subscriber
$lname    => lastname of the subscriber

Additional field data needs to be in the proper $ftt_thetag variables (thetag represents the tag of the field).

- Remove subscribers through another Perl script

A Perl script needs to call scriptunsub.pl the following way:

require "scriptunsub.pl";
&mrp_scriptremove ($mrp_path,$list,$ENV{'REMOTE_ADDR'},$email);

$mrp_path => server path to Add2it MailResponder Pro ( )
$list     => list ID
$email    => email address of the subscriber

- Automatically subscribe to a list

They can call sub.pl with this links:
(preferred language)
e.g.

(any other language)
e.g.

A form will ask the new subscriber for:
F = First name, L = Last name, M = all additional fields
(+ all required fields)
The administrator can use any or all letters in any order.

or they can call sub.pl with this links:
(preferred language)
e.g.

(any other language)
e.g.

The subscriber will not be asked any additional question and will be right away subscribed to the list.

or they can call sub.pl with this links:
(preferred language, ignores required fields)
e.g.

(any other language, ignores required fields)
e.g.

A form will be ask the subscriber for his / her email address, first name and last name. "News-Ad-No.3" will automatically be written in the 4th field.

Or the administrator can provide one of the forms below on a web site.

To add an address to one list:

<form method="POST" action="sub.pl">
<p>Email address:*<br>
<input type="text" name="email" size="20"><br>
First name:<br>
<input type="text" name="fname" size="20"><br>
Last name:<br>
<input type="text" name="lname" size="20"><br>
<input type="hidden" name="task" value="subscribe">
<input type="hidden" name="list" value="list">
<input type="hidden" name="language" value="language-sub-dir">
<p><input type="submit" value="Add Address"></p>
</form>

To add an address to several lists:

<form method="POST" action="sub.pl">
List:<br>
<select name="list" size="3" multiple>
<option value="list1">List title 1</option>
<option value="list2">List title 2</option>
<option value="list3">List title 3</option>
</select><br>
Press and hold 'CTRL' to select several lists.
<p>Email address:*<br>
<input type="text" name="email" size="20"><br>
First name:*<br>
<input type="text" name="fname" size="20"><br>
Last name:*<br>
<input type="text" name="lname" size="20"><br>
<input type="hidden" name="task" value="subscribe">
<input type="hidden" name="language" value="language-sub-dir">
<p><input type="submit" value="Add Address"></p>
</form>

The administrator can remove the input tag of any field which data the subscriber doesn't have to provide.

Question:

There are some discussion of the new California and European spam laws and how it affects publishers. As such, there should be a checkbox that indicates a new subscriber understands that the publication contains commercial advertisements from the publisher and third party advertisers that must be checked before a person can complete their subscription.

Is this something that you could easily add to the form for subscribing with Add2it MailResponder Pro?

You can read more here: http://www.learnsteps4profit.com/antispam.html

Answer:

While thinking about how I can best add that feature, I found a simply solution that works with all versions of Add2it MailResponder Pro. :)

Simply add the following HTML code to your signup form:

<script language=JavaScript><!--
function CheckForm() {
if (form.confirm.checked != true) {
alert("You didn't confirm that you understand that the publication contains commercial advertisements from the publisher and third party advertisers.");
document.form.confirm.focus();
return false;
}
}
//--></script>
<input type="checkbox" name="confirm" value="Confirm"> I understand that the publication contains commercial advertisements from the publisher and third party advertisers.

And change the <form method="POST" action="sub.pl"> tag to:

<form method="POST" action="sub.pl" name=form onSubmit="return CheckForm()">
Then people can only subscribe, when they confirm that they understand that the publication contains commercial advertisements from the publisher and third party advertisers.

- Automatically subscribe subscribers to a list

Subscribers can subscribe to a certain list with an email to an email address. Hereby the content of the email message or subject doesn't matter.

Note: Instead of forwarding (pipe) emails that arrive at the subscribe address to the subfilter.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, please follow the instructions at 9.7.

Instructions for servers using cPanel:

To redirect email to this script, all you need to do is to use cPanel's "Forwarders" within the "Mails" section. There add forwarders from:
subscribe@yourdomain.com
to:
subfilter.pl

Instructions for using .qmail-subscribe-^listname^ (servers running qmail):

To redirect email to this script, create new .qmail-subscribe-^listname^ file and upload it in ASCII mode into that directory on your server which contains all the .qmail-.... files.

This file is the new file that replaced the rc.local.init file on the old Host4Profit servers. In other words, if your with Host4Profit, use this file and not the other three that will be mentioned later. If you are on the new Host4Profit servers, the other three files (.forward, .rc.local.init or procmailrc) will do nothing. Also, only ONE of these files should be on any system: .qmail-subscribe-^listname^, .forward, .rc.local.init or procmailrc. If you're not on a Kiosk or Host4Profit server, you'll need to contact your web hosts technical support staff and ask them which file is the right choice for your server (this is usually the hardest part of the install for non Kiosk or Host4Profit servers).

The content of the file has to be:
1st line:  |/usr/bin/perl subfilter.pl
2nd line:  <empty line>

username = Your hosting service username. On Host4Profit this is 8 digits.

The files needs to be saved in UNIX / Linux format!

When uploading this file, upload it to the 'username-mail' directory on your server, where username is your hosting service username.

Please note that the above example is Host4Profit specific. If you're on another server, please contact your web hosts technical support staff and ask them for the proper path.

Instructions for using .rc.local.init (servers running procmail):

This file is used on the old Host4Profit servers or on Alabanza based hosting only (Alabanza is the company Host4Profit buys from... you can tell their hosting by the control panel).

The following lines need to be adjusted:
1st line:  DOMAIN=(yourdomain.com)
2nd line:  | subfilter.pl

Just substitute yourdomain.com for your actual domain name. For example, if your domain was http://add2it.com, change yourdomain.com to add2it.com.

Instructions for using .procmailrc (servers running procmail):

This file is preferred over the .forward file. Ask your web hosts technical support staff if they will allow you to use this if possible. If you're on a Kiosk or Host4Profit server, please disregard this file, as it doesn't need to be installed.

In this line: * ^TOsubscribe-^listname^@yourdomain.com

You would replace "yourdomain" with your actual domain name.

The other line in this file is modified just like the .rc.local.init file, the line with the path in it:

| subfilter.pl

Nothing else on this file needs to be modified.

Instructions for using .forward (servers running sendmail):

This file is to only be used as a last resort, and is not for use on Kiosk or Host4Profit or Alabanza based servers. You'll need to contact your web hosts technical support staff and ask them what file they prefer you use.

The following line need to be adjusted:
\catchalluser,"|/usr/bin/perl subfilter.pl"

There are 3 parts to editing this line. If you're with Kiosk or Host4Profit, don't even worry about this file.

On the left hand side, you'll see the name catchalluser. The Catchalluser name really depends on what you setup as the Catchalluser name and really on the system configuration. In some cases you have control over it, in some cases you don't. For example, if you're using the name default@yourdomain.com as a funnel to forward all misdirected mail that goes to usernames that don't exist on your mail server, then all this email would be redirected to the email address of your choice.

In the case above, 'default' would be your Catchalluser name. Log into the place where you edit and add email addresses. If you have any doubt, contact your web hosts technical support staff and ask them.

In the middle, you'll see /usr/bin/perl. That's simply the path to Perl and you'll need to modify that to your unique path to Perl which can vary slightly depending on which hosting service you're with.

This has been tested on the servers of Kiosk and Host4Profit.

Add2it.com uses Kiosk.

- Automatically unsubscribe from a list

They can call unsub.pl with this links:
(preferred language)
e.g.

(any other language)
e.g.

Or the administrator can provide one of the forms below on a web site.

To remove an address from one list:

<form method="POST" action="unsub.pl">
<input type="hidden" name="task" value="unsubscribe">
<input type="hidden" name="list" value="list">
<input type="hidden" name="language" value="language-sub-dir">
<p>Email address:<br>
<input type="text" name="email" size="30"><br>
<input type="submit" value="Remove Address"></p>
</form>

You can also just use a "thelist" tag without the "list" tag within the unsubscribe form and the script will unsubscribe from all lists:

<input type="hidden" name="thelist" value="list">

Or you can use a "thelist" & "list" tags combination to limit that unsubsribe request to certain lists:

<input type="hidden" name="thelist" value="list">
<input type="hidden" name="list" value="list|list2|list3">

To remove an address from several lists:

<form method="POST" action="unsub.pl">
List:<br><select name="list" size="3" multiple>
<option value="list1">List title 1</option>
<option value="list2">List title 2</option>
<option value="list3">List title 3</option>
</select><br>
Press and hold 'CTRL' to select several lists.<br>
<input type="hidden" name="task" value="unsubscribe">
<input type="hidden" name="language" value="language-sub-dir">
<p>Email address:<br>
<input type="text" name="email" size="30"><br>
<input type="submit" value="Remove Address"></p>
</form>

- Automatically unsubscribe subscribers from a list

Subscribers can unsubscribe from a certain list with an email to an email address. Hereby the content of the email message or subject doesn't matter.

Note: Instead of forwarding (pipe) emails that arrive at the unsubscribe address to the unsubfilter.pl script, you can let the script pick-up the emails in the POP3 email box setup for this purpose. To do this, please follow the instructions at 9.7.

Instructions for servers using cPanel:

To redirect email to this script, all you need to do is to use cPanel's "Forwarders" within the "Mails" section. There add forwarders from:
unsubscribe@yourdomain.com
to:
unsubfilter.pl

Instructions for using .qmail-unsubscribe-^listname^ (servers running qmail):

To redirect email to this script, create new .qmail-unsubscribe-^listname^ file and upload it in ASCII mode into that directory on your server which contains all the .qmail-.... files.

This file is the new file that replaced the rc.local.init file on the old Host4Profit servers. In other words, if your with Host4Profit, use this file and not the other three that will be mentioned later. If you are on the new Host4Profit servers, the other three files (.forward, .rc.local.init or procmailrc) will do nothing. Also, only ONE of these files should be on any system: .qmail-unsubscribe-^listname^, .forward, .rc.local.init or procmailrc. If you're not on a Kiosk or Host4Profit server, you'll need to contact your web hosts technical support staff and ask them which file is the right choice for your server (this is usually the hardest part of the install for non Kiosk or Host4Profit servers).

The content of the file has to be:
1st line:  |/usr/bin/perl unsubfilter.pl
2nd line:  <empty line>

username = Your hosting service username. On Host4Profit this is 8 digits.

The files needs to be saved in UNIX / Linux format!

When uploading this file, upload it to the 'username-mail' directory on your server, where username is your hosting service username.

Please note that the above example is Host4Profit specific. If you're on another server, please contact your web hosts technical support staff and ask them for the proper path.

Instructions for using .rc.local.init (servers running procmail):

This file is used on the old Host4Profit servers or on Alabanza based hosting only (Alabanza is the company Host4Profit buys from... you can tell their hosting by the control panel).

The following lines need to be adjusted:
1st line:  DOMAIN=(yourdomain.com)
2nd line:  | unsubfilter.pl

Just substitute yourdomain.com for your actual domain name. For example, if your domain was http://add2it.com, change yourdomain.com to add2it.com.

Instructions for using .procmailrc (servers running procmail):

This file is preferred over the .forward file. Ask your web hosts technical support staff if they will allow you to use this if possible. If you're on a Kiosk or Host4Profit server, please disregard this file, as it doesn't need to be installed.

In this line: * ^TOunsubscribe-^listname^@yourdomain.com

You would replace "yourdomain" with your actual domain name.

The other line in this file is modified just like the .rc.local.init file, the line with the path in it:

| unsubfilter.pl

Nothing else on this file needs to be modified.

Instructions for using .forward (servers running sendmail):

This file is to only be used as a last resort, and is not for use on Kiosk or Host4Profit or Alabanza based servers. You'll need to contact your web hosts technical support staff and ask them what file they prefer you use.

The following line need to be adjusted:
\catchalluser,"|/usr/bin/perl unsubfilter.pl"

There are 3 parts to editing this line. If you're with Kiosk or Host4Profit, don't even worry about this file.

On the left hand side, you'll see the name catchalluser. The Catchalluser name really depends on what you setup as the Catchalluser name and really on the system configuration. In some cases you have control over it, in some cases you don't. For example, if you're using the name default@yourdomain.com as a funnel to forward all misdirected mail that goes to usernames that don't exist on your mail server, then all this email would be redirected to the email address of your choice.

In the case above, 'default' would be your Catchalluser name. Log into the place where you edit and add email addresses. If you have any doubt, contact your web hosts technical support staff and ask them.

In the middle, you'll see /usr/bin/perl. That's simply the path to Perl and you'll need to modify that to your unique path to Perl which can vary slightly depending on which hosting service you're with.

This has been tested on the servers of Kiosk and Host4Profit.

Add2it.com uses Kiosk.

You will find the Add2it MailResponder Pro Support Forum at:
http://add2it.com/cgi-bin/diskus/show.cgi?11/11

You can subscribe to the Add2it Scripts Update + Announcement List at:
http://add2it.com/mrp/sub.pl?scripts=!FLM