Archived Projects

The projects below have been archived because they’re no longer being maintained, however they may still be of some use.

Although these apps may run on modern web servers, they’re old and don’t have the design or features of modern web applications.  Some of them were written in the mid-1990’s.

Feel free to download and install these apps at your own risk.

Secure Form Processor

(This product has been re-booted as SimpleSecure WordPress Plugin) This legacy version is a Perl form processor that encrypts messages using GPG or PGP (or other encryption methods).  It continues to be used on production sites. Perl source code is included.  Last updated in 2002.



A Perl script used to submit a website to multiple search engines.  At one time this script had a huge install and user base. This is largely unnecessary these days however some people continue to use the script.  Last updated in 2002.



An ancient web-based personal management organizer with calendar, tasks and email. The features were interesting at the time however the script is grossly outdated. This code may have some use as reference for it’s email parsing and attachment handling.  Last updated in 2002.


Web Toolz

A collection of Perl scripts, mainly utilities used by webmasters and server administrators. Among the useful scripts are some that display disk usage and allow stateless terminal access to hosts that do not offer shell access.  Last updated in 2003.


12 Comments on “Archived Projects

Brian Theasby
September 18, 2010 at 4:22 pm

I get

Use of uninitialized value in hash element at

Set up used for latest database downloads

Glen Davis
October 6, 2010 at 6:49 am

I get an “Application Error: 000” when I run the script after install.


October 15, 2010 at 4:30 pm

@glen I’m not sure which script you’re running, lemme know so I can fix it if necessary. Thanks.

November 26, 2010 at 11:51 pm

In setting up SimpleSecure 3.33 when I submit an attached file, the resulting email also has the encrypted and the unencrypted file as attachments.

What do I need to do to keep it from sending the unencrypted attachment?


November 29, 2010 at 9:58 pm

I got it figured out. I didnt set the attachment field name to be the same as what I specified in AttNameLookup.

December 4, 2010 at 11:08 am

hi – is it possible to get de-dupulator?

December 12, 2010 at 8:50 pm

@martin – i moved servers and some of the download files apparently didn’t transfer over. I just re-uploaded the de-duper installer, you can grab it from here:

January 21, 2011 at 7:11 am

Questions about simplesecure 3.33

– Attachments are not encrypted –
I’ve installed the script, I’ve upload the gpg public key, and I test the html form, and it encrypts the data, but not the attachment(s) that I send.
I’ve read the Glenn answer to the question he made, but not helped me find out the solution.

Can you explain what do I need to do, to have it also encrypting the files that are send trough it?
What options and configurations I need to make to have it sending the attachment’s (I need at least 2) also encrypted.

-reCAPTCHA inclusion in it, Spam protection-
Despite the recent problems with reCAPTCHA I would like to know how to integrate reCAPTCHA in the SimpleSecure 3.33, I’ve done this in a modified version of BFormMail (using this instructions: ), but I have no idea how to make this in SimpleSecure 3.33.

– Scripts says the connection is not secure-
The script doesn’t recognize that the script is in a secure connection AES-256 (https://) with a valid certificate from comodo, and if I select “RequireSSL” in “Recipients” it won’t accept the connection, saying “SimpleSecure.ProcessForm: This form must be submitted in secure (SSL) mode. Visitors: Please contact the site administrator for assistance. Administrators: Either update your form tag ‘action’ parameter to begin with ‘https://’ or update Recipient #1 so that RequireSSL = ‘No’.” although is in a valid encrypted address (https://URLofTHEsite.tld/).
Is this a error in the script?

January 26, 2011 at 10:29 pm

@Joao I haven’t looked at that script for at least 5 years so my memory is very rusty. I’m sorry I know nobody wants to hear that but it’s the truth. I think the attachment thing was added later and it probably does not encrypt that part of the message unfortunately. adding reCAPTCHA is a great idea, I don’t know what would need to be done – probably some session handling code in SimpleSecure would need to be added.

The script is not secure warning – that one i have never heard before but it does rely on the server to report it and I have seen a million different servers all report things differently so, who knows, maybe yours works differently when reporting SSL connections.

if somebody would want to take over coding SimpleSecure I would be more than happy to help.

February 1, 2011 at 9:18 pm

Thanks, for answering :)

It probably was added later, because I wasn’t able to make it send the attachments encrypted… and that would be a very nice feature… that I think no one else have.

To add reCAPTCHA to perl it says in their page: what is needed, but unfortunately I don’t have knowledge to apply that.

The ssl error is here:

Also are missing some important features to me like what FormMail have:
– referers check
– Forbidden strings (like: viagra, http://, etc.)
– Banned IP addresses

Also the ID of the form could be something that the person defines in order to make the automation of sending spam more difficult because they not only have to find the script address but also have to know the ID that webmaster have give.

A verification for the mandatory fields by the script, based on the ID of the form used.

And a forbidden field would be also good to prevent automated submission (the field could be empty and invisible or be empty and visible but content could not be submitted in order to detect a bot that completes all fields…. and would go to the blacklist).

Yes, I know, some of them can be bypassed… but at least the SSecure is not an “open relay” that anyone with it’s address can send spam to (ok… spam only to the recipient… but it will get it).

Would be great if anyone with knowledge take over coding SimpleSecure to correct the bugs (attachments) and add what is missing: reCAPTCHA and the others (like referers chek , Forbidden strings, …).

When it was BFormMail I have add the reCaptcha, but I really need the encryption part of the SimpleSecure, but with the “more” security of BFormMail (yes, FormMail is not the safest script, but at least is a little more difficult than SimpleSecure to be spammed by automated tools).

February 9, 2011 at 1:31 am

hey joao, those are all great ideas. i want to do another release one day but i don’t know when that will be just due to so many projects and priorities. if any developers are out there listening, it would be great to have contributions to this open source script.

February 17, 2011 at 3:16 am

Thanks for answering. I hope some developers out their listening can do that work, or in the lack of that, that you can “find” time to do the update to the script. I’ve read that you have to many projects and priorities, that this has to come later than sooner, when you can, I will be delighted to use the new version with that features :) … and I think many others 😛 when the word spreads.

Leave a Reply

Your email address will not be published. Required fields are marked *