Free bulk software for linux

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.

Convert::BulkDecoder is a Perl module to extract (binary) data from mail and news messages.

SYNOPSIS

use Convert::BulkDecoder;
my $cvt = new Convert::BulkDecoder::;
# Collect the articles into an array ref.
my $art = [];
# Decode.
my $res = $cvt->decode($art);
die("Failed!") unless $res eq "OK";
print "Extracted ", $cvt->{size}, " bytes to file ", $cvt->{file}, "n";

Convert::BulkDecoder can be used to decode binary contents as included in email and news articles. It supports UUdecoding, ydecoding and MIME attachments. The contents may be split over multiple articles (files), but must be supplied to the decode() function in one bulk.

For yencoded contents, it is possible to verify file consistency using length and checksum tests.

RTx::RT34::Bulk::CF::Edit is a Perl module to allow bulk editing of custom fields.

BlinkFlash is a commandline tool for uploading images to winkflash, a mail order digital photo printer.
It can also create new albums, set photo notes (which are printed on the backs of photos) and download photos.
Usage:
blinkflash 1.3 the unofficial winkflash commandline client
usage: ./blinkflash.py [action arguments]
actions:
list-albums -list all albums
create-album < album-name > -create a new empty album
upload < album-name > file[,file,..,..] -upload file(s) to an album
list-images < album-name > -list images in album
download-image < album-name > < filename > -download image (to filename.jpg)
download-album < album-name > -download a whole album
set-notes < album-name > < filename > < notes > -set an images notes
bulk-upload < album-name > < inputfile > -upload files and set notes
for the bulk action the format is filename < tab > alias < tab > notes
eg. IMG012.JPG photo1 Holiday day one
IMG013.JPG photo2 Duncans brother bill
(if run twice, only new files will be uploaded)
some examples:
./blinkflash.py johnsmith b2xtf list-albums
./blinkflash.py johnsmith b2xtf create-album Holiday 2004
./blinkflash.py johnsmith b2xtf upload Holiday 2004 img01.jpg img02.jpg
./blinkflash.py johnsmith b2xtf set-notes Holiday 2004 img01.jpg day 1
./blinkflash.py johnsmith b2xtf bulk-upload Holiday 2004 filesandnotes.txt
**if logged in with a web browser you must log out and log in to see changes**
Enhancements:
- Download image. You can download your images (and whole albums) which makes winkflash useful for image backups.
- Fixed bug setting notes for USA accounts

Squeak is a full-featured implementation of the Smalltalk programming language and environment based on (and largely compatible with) the original Smalltalk-80 system.
Squeak has very powerful 2- and 3-D graphics, sound, video, MIDI, animation and other multimedia capabilities -- and one of the most impressive development environments ever created.
It also includes a customisable framework for creating dynamic HTTP servers and interactively extensible Web sites. The entire Squeak system is open source software, distributed freely with a liberal license.
Main features:
- real-time sound and music synthesis written entirely in Smalltalk
- extensions of BitBlt to handle color of any depth and anti-aliased image rotation and scaling
- network access support that allows simple construction of servers and other useful facilities
- it runs bit-identical on many platforms (Windows, Mac, Unix, and others)
- a compact object format that typically requires only a single word of overhead per object
- a simple yet efficient incremental garbage collector for 32-bit direct pointers
- efficient bulk-mutation of objects

sqlDESKTOP is a computerized manual filing system arranged just like an ordinary office with pictures of real cabinets and real folders. You can arrange by project, by department or whatever makes sense to you.
sqlDESKTOP doesnt tell you how to organize, it lets you do things your own way. Documents are easy to find because you dont have to remember the exact name of the document or where you put it. Instead, you can visually locate what you are looking for in a familiar office environment and click on it.
Main features:
- Marketing report (Microsoft Word file)
- sales forecast (star office file)
- Resellers agreements (data shared with his salesmen team)
- Photos of company plant (Album photo)
- Order records (database query)
- E-commerce site (Internet Web page)
- Press release (Email sent to journalists)
- Customers feedback forum (Internet Newsgroup)
Enhancements:
- MySQL release 5, SqlServer 2005 (the free version of SqlServer), DB2, Oracle, and Derby - Cloudscape are supported.
- A server component was added for small networks without a DBA: sqlDESKTOPserver.
- The Derby - Cloudscape database is embedded with sqlDESKTOPserver.
- A back up feature was added for the single user version.
- Support for digital photos was improved.
- You can save a photo with bulk talk or in comics format into a JPEG file.
- You can mail a photo with bulk talk or in comics format directly to traditional email client application.

Db:Documentum is a Documentum API interface for Perl.
SYNOPSIS
use Db:Documentum qw(:all);
scalar = dmAPIGet( );
$sessionID = dmAPIGet("connect,docbase,username,password");
scalar = dmAPIExec( );
$rv = dmAPIExec("next,c,$collection_id");
scalar = dmAPISet( , );
$api_stat = dmAPISet("set,c,last,object_name","My Document");
See scripts in /etc for more examples.
The Db:Documentum module provides a Perl interface to the client API libraries for the Documentum Enterprise Document Management System (EDMS98/4i/5). You must have already obtained the necessary libraries and purchased the necessary licenses from Documentum before you can build this module. For more information on Documentum, see http://www.documentum.com/
This module provides an interface to the three listed API functions: dmAPIGet, dmAPIExec, and dmAPISet. For most purposes, these are the only functions you need to use, as the bulk of the API is implemented as server methods accessed by one of the API commands. dmAPIExec returns a scalar (1 or 0) which can be evaluated to determine success (1 for success, 0 for failure). dmAPISet also returns a scalar, but takes two arguments, the method argument and the value to use. dmAPIGet takes a single argument and returns a string containing the results. This string, which may contain an object or query collection identifier can be used later with other method calls.
This module, by default, does not import all of its symbols into the calling packages namespace. Therefore, the Documentum API commands must be called with the fully-qualified package path:
Db:Documentum:dmAPIGet
To use the module functions without having to supply the module name, use the second form of the "use" statement shown here:
use Db:Documentum qw (:all);
That said, check your Documentum documentation for complete information on how to interact with the Documentum server.
Check the version of this module with: >perl -MDb:Documentum -e Db:Documentum:version

brip is a Bulk / stream Resolution of IP addresses and hostnames.
Main features:
- Resolve IP addresses and/or hostnames in bulk
- Can read from STDIN, commandline or file
- Can be used for quick commandline lookups, like host, dig and nslookup
- Automatically detects which of the three is on your system, and uses whichever is available, in that order of preference
Usage: brip [ options ] [ { hostname | ipaddress } ]
Options:
-r Output is in hostname ipaddress format, the reverse of the default output (/etc/hosts format)
-s Output is in the form of a sed script, which can be used for bulk substitution within existing data (such as a log file).
If a hostname cannot be resolved in this mode, it is repeated back into the output, but in uppercase. This is done to offer some (possible) distinction for unresolvable hostnames without changing their value.
-F separator
Used in conjunction with the -s option, to assure proper delineation of hostnames or ipaddresses in data to which the sed substitutions are being applied
-R resolver
Specify a specific resolver, among host, dig or nslookup.
-v Run in verbose mode
-f inputfile
Read data from a file. Any trailing tokens on the commandline will be looked up along with the contents of the file.
ipaddress, hostname...
Any number of IP addresses and/or hostnames can appear on the commandline, and will be forward or reverse resolved as appropriate. If none are specified on the commandline, they will be read from STDIN.