Several script versions listed don't match current release versions for the products. For example:
1) Wordpress is 2.03 (script says 2.02, but I'm pretty sure it just installed the 2.03 version even though it still says it is 2.02)

2) SquirrelMail is 1.50, but current version is 1.51 (some security fixes, etc).

So, two questions:

a) How to I upgrade something AHEAD of the official Virtualmin install (and get Virtualmin to recognize this) Specifically, I want to do the SquirrelMail upgrade, if you want to use that as an example

b) Any documentation on how the scripting process is setup, etc. so that I could dig aound and figure some of this out? (I'm a lightweight with linux, however).

I am just another Virtualmin user, but here are my comments:

1) The actual latest stable version of SquirrelMail is 1.4.6. Version 1.5.1 is considered a development version. With SquirrelMail, the even numbers (1.0.x, 1.2.x, 1.4.x, etc.) are stable, and the odd numbers (1.1.x, 1.3.x, 1.5.x, etc.) are development quality. That said, Virtualmin does display 1.4.5 and 1.5.0. So, these should be updated to 1.4.6 and 1.5.1.

2) My personal preference is that SquirrelMail be installed by the server administrator as a one-time, server-wide installation, instead of using the per-domain script installers. I think this is much easier to maintain and makes more sense than having multiple copies of it running in each domain. See my post on this topic:

Re: virtual server mail alias

3) To answer your first question ("a"), the best way to get the scripts updated is to open a ticket in the bug tracker that a new version to an existing script installer has been released. That way, it will be updated for everyone. Note that script installers are currently only updated when a whole new Virtualmin version is released; they can not be updated independently unless you do it yourself. Nevertheless, Jamie has been very quick about releasing new versions once he knows about them.

4) Regarding your second question ("b"), Joe has posted a great intro to creating your own script installers. See his post in the Developers forum:

Tip: Create new Script Installers for your CGI scripts

FYI, I have opened[A HRef="http://www.virtualmin.com/bug-tracker/bug?bug%5fnumber=426">Bug #426 to request these script installer updates, along with a bunch of others.

Also, I noticed that Joe may now be assisting with these updates too per[A HRef="http://www.virtualmin.com/bug-tracker/bug?bug%5fnumber=401">Bug #401.

Hey Guys,

Yep, I'm in the midst of a huge overhaul...I probably need to just roll them out in bits and pieces, since there are so many scripts supported now!

Next release will have at least a dozen or so updates, I promise.

Thanks for responses. I wouldn't know how to install once serverwide. I assume someone could also install a local (development) version if the system wide version was the release version, etc. That's the only hitch I'd see.

I'll wait for the script updates.

Could you add the spam assassin configuration plugins as part of the "standard" squirrelmail install? I've tried installing them, and nothing :( worked afterwards. Had to uninstall everything and reinstall...