Free bulkmail software software for linux

Billing Software project allows your business to track invoicing and allows your customers to view their invoices online and easily export them to Excel for saving or printing.
Invoices can also be emailed to customers right from the online application for convenience and efficiency.
Enhancements:
- This release fixes some minor bugs in the XML portions of the library files.

Job Costing Software project is the first step to improving profitablity on your projects. A web-based job costing product makes it easy to view or update your job costs quickly.
View your project cost status in real time to make more accurate decisions. Export your costs to an excel spreadsheet for reporting or printing.
Two user levels allow your suppliers to enter costs directly without the ability to edit other costs. Improve your project decision making with free job costing software.
Everybody knows how important it is to create an accurate estimate of a jobs total costs. Unfortunately, most project managers are so busy they dont have time to gather the information needed to accurately calculate costs as the job progresses.
Job costing software makes the cost projections for you, freeing up your time to better manage the project.
Enhancements:
- This release fixed a few bugs in the database library files.

Mail::Bulkmail is a platform independent mailing list module.

SYNOPSIS

use Mail::Bulkmail /path/to/conf.file

my $bulk = Mail::Bulkmail->new(
"LIST" => "~/my.list.txt",
"From" => "Jim Thomason" ,
"Subject" => "This is a test message",
"Message" => "Here is my test message"
) || die Mail::Bulkmail->error();

$bulk->bulkmail() || die $bulk->error;

Dont forget to set up your conf file!

Mail::Bulkmail gives a fairly complete set of tools for managing mass-mailing lists. I initially wrote it because the tools I was using at the time were just too damn slow for mailing out to thousands of recipients. I keep working on it because its reasonably popular and I enjoy it.

In a nutshell, it allows you to rapidly transmit a message to a mailing list by zipping out the information to them via an SMTP relay (your own, of course). Subclasses provide the ability to use mail merges, dynamic messages, and anything else you can think of.

Mail::Bulkmail 3.00 is a major major major upgrade to the previous version (2.05), which was a major upgrade to the previous version (1.11). My software philosophy is that most code should be scrapped and re-written every 6-8 months or so. 2.05 was released in October of 2000, and Im writing these docs for 3.00 in January of 2003. So Im at least 3 major re-writes behind. (philosophy is referenced in the FAQ, below)

But thats okay, because were getting it done now.

3.00 is about as backwards compatible to 2.00 as 2.00 is to 1.00. That is to say, sorta. Ive tried to make a note of things where they changed, but Im sure I missed things. Some things can no longer be done, lots are done differently, some are the same. You will need to change your code to update from 1.x or 2.x to 3.00, though. Thats a given.

So whats new for 3.00? Lots of stuff.

Immediate changes are:

* code compartmentalization
* multi-server support
* conf file

The immediate change is that the code is now compartmentalized. Mail::Bulkmail now just handles ordinary, non-dynamic mailings. See Mail::Bulkmail::Dynamic for the merging and dynamic text abilities from the prior versions.

Server connections are no longer handled directly in Mail::Bulkmail (Smtp attribute, Port attribute, etc.), there is now a separate Mail::Bulkmail::Server object to handle all of that.

And everything subclasses off of Mail::Bulkmail::Object, where I have my super-methods to define my objects, some helper stuff, and so on.
Its just a lot easier for me to maintain, think about it, etc. if its all separated. Its also easier for you, the user, if you want to make changes to things. Just subclass it, tweak it, and use it. Very straightforward to modify and extend now. 2.x and below *could* do it, but it wasnt really that easy (unless you were making very trivial changes). This should rectify that.

Another major change is the addition of multi-server support. See the docs in Mail::Bulkmail::Server for more information. You can still specify one SMTP relay if thats all youve got, but if you have multiple servers, Mail::Bulkmail can now load balance between them to help take the stress off. No matter what, the biggest bottleneck to all of this is network performance (both to the SMTP relay and then from the relay to the rest of the world), so i wanted to try and help alleviate that by using multiple servers. I know that some people were doing that on there own with small changes, but this allows you to do it all invisibly.
And finally, finally, finally there is a conf file. Documentation on the format is in Mail::Bulkmail::Object. Its pretty easy to use. This is the conf file format that I designed for my own use (along with most of the rest of Mail::Bulkmail::Object). The software also has the ability to read multiple conf files, if so desired. So no more worrying about asking your sysadmin to tweak the values in your module somewhere up in /usr/lib/whatever

Just have him create the conf file you want, or pass in your own as desired.
conf_files are specified and further documented in Mail::Bulkmail::Object, in an internal array called @conf_files, right at the top of the module. To specify a universal conf file, put it in that array (or have your sysadmin do so). Alternatively, you can also add a conf_file via the conf_files accessor.

Mail::Bulkmail->conf_files(/path/to/conf_file, /path/to/other/conf_file); #, etc.

But the recommended way is to specify your conf file upon module import.

use Mail::Bulkmail 3.00 "/path/to/conf/file";

In addition, there is the usual plethora of bug fixes, tweaks, clean-ups, and so on.

And yes, the horrid long-standing bug in the Tz method is fixed! No, honest.
Im also trying a new documentation technique. The pod for a given method is now in the module by that method, as opposed to everything being bunched up at the bottom. Personally, I prefer everything being bunched up there for clarities sake. But from a maintenance point of view, spreading it all out makes my life much easier.

Dispatch Software is a software that saves time, money and increase your customer satisfaction. 100% free online, web-based dispatch software makes it easy to keep track of your vehicles.
Easily view what each vehicle will be doing each day. Export the daily schedule to a printable spreadsheet file for your driver to take on the road. View all units on one page for faster scheduling.
Dispatch drivers can view schedules ahead of time for better planning and time management.
Installation:
-copy all files to your web host
-use phpmyadmin or your mysql interface to run site.sql against your database.
-open site.xml and edit the database section with your database details.
-go to index.php and login with username of admin with a password of test.
-be sure to change the passwords for the admin and regular user.
Setup the site.xml file with your database settings as follows.
< database type="mysql" >
< server >database server address< /server >
< login >database login< /login >
< password >database password< /password >
< default >mysql database name< /default >
< /database >
Add this to your .htaccess file to prevent viewing of the xml config file.
< Files ~ ".xml" >
Order allow,deny
Deny from all
Satisfy All
< /Files >
Enhancements:
- A bug in the main library file for the dispatching system was fixed.

Simple Website Software (SWS) is my attempt to provide software to generate a reasonably modern looking web site while requiring a minimal amount of effort to set up, yet keeping the HTML pages independent so they can be easily editted and verified outside the web site.
SWS requires PHP version 4.1 or above and consists of only a small number of files. It uses cascading style sheets (CSS) to control the basic look and feel and has the basic layout, but not appearance) of that shown to the left. If you want a web site which has different components than those you see here, SWS is not for you.
There are only a few components to your basic SWS web page:
1. Banner - an optional box across the top of the page. This is provided as a file containing a fragment of HTML.
2. Left hand menus - a required set of links organized in one or more blocks. Each block has a title and consists of zero or more static links. This is provided as a file containing partial HTML address tags.
3. Middle - is where the basic HTML you provide is shown. This is provided as a file which is often named similar to your PHP program.
4. Right hand menus - an optional set of links, similar to those on the left hand side.
5. Footer - generated HTML which shows a copyright and date for each page of HTML.
Main features:
- SWS pages are rended quite fast by your PHP web server. There is no operating system dependency here - you may use a Unix (Linux) or Windows-based server. The only software requirement is that you have PHP available. You code each page in PHP, but the PHP is very simple and almost always looks the same. You dont need to be much of a PHP coder.
- SWS requires no database to render its pages.
- Any authentication uses the normal web server mechanism (e.g. .htaccess files for Unix Apache).
- Menus can be selectively displayed based on what section of the web site is being displayed. If one selects vacations, then you can show a menu of vacation links. Move elsewhere and the menu disappears.
- Menus can be selectively displayed based on whether the user is authenticated (logged in) or not. Different menu blocks can be shown to different people.
- A utility program called showfilelist.php is provided to generate simple lists of links. This program reads a simple ASCII file and generates the HTML for you keep your interface very simple.
- An entire SWS installation and setup consists of only a half dozen files, all centralized in one directory. Your basic HTML remains in HTML files so you can develope it and test it as you normally would. You only use a small PHP program to tie it all together so the pages have the correct look and feel. This keeps things easy for you to create and maintain your web site.
Enhancements:
- The release includes minor changes to make the code more compatible with PHP 5.
- There is no need to upgrade unless you are having problems.
- This software is considered stable.

TVU networks lets you reach global TV audiences cost-effectively and with secure content protection.

TVU Broadcasting software lets you deliver your content to the TVUplayer software for free. You must first sign up for a free broadcasting channel by visiting this link: http://www.tvunetworks.com/bdcenter/viewLogin.do

After logging in with your account, supply a stream source of any sort and start sharing your media with the world.

Bio::Genex::Software is Perl module with methods for processing data from the GeneX DB table: Software.

SYNOPSIS

use Bio::Genex::Software;

# instantiating an instance
my $Software = Bio::Genex::Software->new(id=>47);

# retrieve data from the DB for all columns
$Software->fetch();

# creating an instance, without pre-fetching all columns
my $Software = new Bio::Genex::Software(id=>47);

# creating an instance with pre-fetched data
my $Software = new Bio::Genex::Software(id=>47, fetch_all=>1);

# retrieving multiple instances via primary keys
my @objects = Bio::Genex::Software->get_objects(23,57,98)


# retrieving all instances from a table
my @objects = Bio::Genex::Software->get_all_objects();

# retrieving the primary key for an object, generically
my $primary_key = $Software->id();

# or specifically
my $sw_pk_val = $Software->sw_pk();

# retreving other DB column attributes
my $name_val = $Software->name();
$Software->name($value);

my $version_val = $Software->version();
$Software->version($value);

my $type_val = $Software->type();
$Software->type($value);

my $con_fk_val = $Software->con_fk();
$Software->con_fk($value);

Each Genex class has a one to one correspondence with a GeneX DB table of the same name (i.e. the corresponding table for Bio::Genex::Software is Software).
Most applications will first create an instance of Bio::Genex::Software and then fetch the data for the object from the DB by invoking fetch().

However, in cases where you may only be accessing a single value from an object the built-in delayed fetch mechanism can be used. All objects are created without pre-fetching any data from the DB. Whenever an attribute of the object is accessed via a getter method, the data for that attribute will be fetched from the DB if it has not already been. Delayed fetching happens transparently without the user needing to enable or disable any features.

Since data is not be fetched from the DB until it is accessed by the calling application, it could presumably save a lot of access time for large complicated objects when only a few attribute values are needed.