Then you need to basically copy the add_subs2 function from the pro version. Within this function you can strip out any SQL related code, the reference to the banned_domains file, and of course any occurrence of $FORM{'list'} (making sure to remove the trailing slash too since the paths are relative) since the basic version only supports one list.

Or... you can just add the addresses manually to the subscribers.txt file if you really need to. The format for the file is just simply the address followed by a return. I would say that's the easier option.

OK. I am a glutton for punishment. The thing is that the person that will be manually adding subscribers won't have FTP access so a web based option will work better.

I added the query thingamajiggy in the right spot I think and I now actually get to the page where I can add subscribers but after I click add nothing happens. I feel like I am so close yet so far. I deleted the sql and banned stuff, although I wasn't sure about the $FORM{'list'} part. Could you take a peek at it when you get a spare moment?

<p align="justify">Here you can add subscribers to your subscribers.txt file. Each address must be seperated by a newline (no commas, semicolons, colons, intestines, or spaces!), just like the subscribers.txt file itself. These addresses are added automatically (the addresses will not have to be confirmed).</p>

<form action="$script" method="POST">

<textarea name="subs" cols=50 rows=15></textarea><BR><BR>

Do you want your subscribers to be subscribed as HTML or plain text subscribers?

For starters, if you haven't already, you should probably go ahead and make sure the line use CGI::Carp "fatalsToBrowser"; is uncommented.

The line where subscribers are going to be written to the subscribers.txt file (the one with the sorta sarcastic error message...) needs to be opened with +>> so that it is appended (or created if it somehow doesn't exist). So, the line should be:
open(SUBS,"+>>subscribers.txt") || die "can't open susbcribers.txt... WHAT???";

Also, you need to remove some of the enclosing curly braces from what used to be an else statement (which it isn't anymore since you removed all the SQL stuff).

I don't quite know if this will fix it, but it's a start. Maybe at least now you'll get an error message...