Free mime software for linux

MIME-tool is a little mime encoding tool I slapped together when I needed something on a production box at work (productions = no C development environment, only the ancient K&R compiler required for god-knows-what sys-admin task).
The resulting program will compile happilly on both the crippled C compilers bundled with some commercial *nix distributions, and on full ANSI/ISO C compilers like gcc.
I wrote this program when I needed a tool to construct MIME encoded emails with file attachments in job scripts on a production box. Being a production box it didnt have any development tools installed. However, the box DID have a K&R C compiler that appears to be necessary for some administrative task or another (configuring the kernel?). If you tried to compile even fairly simple ANSI/ISO C source the compiler bitched and moaned about all the stuff it didnt support, which will stop most folk (at least those who dont know anything about the history of the C programming language) from building their own binaries.
Since Im old enough to actually have written C code back before we had the ANSI/ISO standard and all the accompanying niceties, I was not stymied by a the lack of ANSI/ISO support. Its really not all that hard to write K&R compliant code, so long as you dont need the compiler to check your function calls for you. For a program this small, however, thats not much of a concern.
Since the program is meant to be compiled on systems with minimal support (there is no telling what unrestrained IT staff will decide must be removed in the interest of system security) I didnt bother to include a makefile. On every system I have tried, however, the program compiled with the simple incantation
cc -o mime mime.c
but your selected target system may require extra special magics.
The program supports the basic MIME standard: The caller can select the content type (application/octet-stream, text/plain, or user specified), content type encoding (7bit, 8bit, binary, base64 or auto-detected) and the boundry string (defaults to "=_MIME_CONTENT_BREAK_="). Further, the caller may specify the e-mail subject, to address, from address, carbon copy address and text for a prolog and epilog. The content type and encoding may be specified separately for each attached file.
The programs calling format is:
mime [-dDvV] [-S subject] [-F from-address] [-T to-address]
[-C carbon-copy address] [-P prolog-text] [-E epiplogue-text]
[-B boundry] {[-78abqux] [-t content-type] filename}
-d low detail debugging
-D high detail debugging
-v verbose messages
-V very verbose messages
-7 7-bit ASCII encoding
-8 8-bit ASCII encoding
-a application/octet-stream content type
-b binary encoding
-q quoted-printable encoding
-t text/plain content type
-u unknown encoding, auto-detect
-x base64 encoding
Theres really not much to this program. Once you know how the MIME messages are constructed you could do most of it manually (except for the base64 encoding, which would require a program like this), but if there are any problems with it, I would like to know about them.
Enhancements:
- A typo in the online help message was fixed.
- A known bugs section was added to the manpage.
- Proper quoting and folding were added to the filename header.

MIME::Lite is a low-calorie MIME generator Perl module.

SYNOPSIS

use MIME::Lite;
Create a single-part message:
### Create a new single-part message, to send a GIF file:
$msg = MIME::Lite->new(
From =>me@myhost.com,
To =>you@yourhost.com,
Cc =>some@other.com, some@more.com,
Subject =>Helloooooo, nurse!,
Type =>image/gif,
Encoding =>base64,
Path =>hellonurse.gif
);
Create a multipart message (i.e., one with attachments):
### Create a new multipart message:
$msg = MIME::Lite->new(
From =>me@myhost.com,
To =>you@yourhost.com,
Cc =>some@other.com, some@more.com,
Subject =>A message with 2 parts...,
Type =>multipart/mixed
);

### Add parts (each "attach" has same arguments as "new"):
$msg->attach(Type =>TEXT,
Data =>"Heres the GIF file you wanted"
);
$msg->attach(Type =>image/gif,
Path =>aaa000123.gif,
Filename =>logo.gif,
Disposition => attachment
);
Output a message:
### Format as a string:
$str = $msg->as_string;

### Print to a filehandle (say, a "sendmail" stream):
$msg->print(*SENDMAIL);
Send a message:
### Send in the "best" way (the default is to use "sendmail"):
$msg->send;

In the never-ending quest for great taste with fewer calories, we proudly present: MIME::Lite.

MIME::Lite is intended as a simple, standalone module for generating (not parsing!) MIME messages... specifically, it allows you to output a simple, decent single- or multi-part message with text or binary attachments. It does not require that you have the Mail:: or MIME:: modules installed.

You can specify each message part as either the literal data itself (in a scalar or array), or as a string which can be given to open() to get a readable filehandle (e.g., "
You dont need to worry about encoding your message data: this module will do that for you. It handles the 5 standard MIME encodings.

If you need more sophisticated behavior, please get the MIME-tools package instead. I will be more likely to add stuff to that toolkit over this one.

Writemime project is a simple C++ package that makes it easy to create and send MIME (Multipurpose Internet Mail Extension) messages in a C++ program.

Writemime is free and covered by a BSD-like license.

Writemime will let you create two kinds of MIME messages:

Simple messages with a single body part.
Multipart/mixed messages with multiple body parts.

Creating a message is trivially easy, and Writemime will handle all encoding issues internally.
There is also a driver program which will let you access most of the functionality from the unix command line. Type writemime -h after compiling the package to get a hopefully helpful usage message.

The driver provides a somewhat degraded way to access Writemime functionality from a non-c++ program.

MIME::Base64 is an encoding and decoding of base64 strings.

SYNOPSIS

use MIME::Base64;

$encoded = encode_base64(Aladdin:open sesame);
$decoded = decode_base64($encoded);

This module provides functions to encode and decode strings into and from the base64 encoding specified in RFC 2045 - MIME (Multipurpose Internet Mail Extensions). The base64 encoding is designed to represent arbitrary sequences of octets in a form that need not be humanly readable. A 65-character subset ([A-Za-z0-9+/=]) of US-ASCII is used, enabling 6 bits to be represented per printable character.

The following functions are provided:

encode_base64($str)
encode_base64($str, $eol);

Encode data by calling the encode_base64() function. The first argument is the string to encode. The second argument is the line-ending sequence to use. It is optional and defaults to "n". The returned encoded string is broken into lines of no more than 76 characters each and it will end with $eol unless it is empty. Pass an empty string as second argument if you do not want the encoded string to be broken into lines.
decode_base64($str)

Decode a base64 string by calling the decode_base64() function. This function takes a single argument which is the string to decode and returns the decoded data.
Any character not part of the 65-character base64 subset is silently ignored. Characters occurring after a = padding character are never decoded.

If the length of the string to decode, after ignoring non-base64 chars, is not a multiple of 4 or if padding occurs too early, then a warning is generated if perl is running under -w.

If you prefer not to import these routines into your namespace, you can call them as:

use MIME::Base64 ();
$encoded = MIME::Base64::encode($decoded);
$decoded = MIME::Base64::decode($encoded);

FireMIME is a library providing an easy to use, callback-based interface for parsing MIME-encoded messages.

It parses messages in accordance with RFC2045 and RFC2046, attempting to follow all rules set out in those documents while still allowing leniency with some common errors. FireMIME uses libfirestring for string handling.

This allows it to be completely 8bit clean, including allowing anywhere in messages.

MIME::Parser is a experimental class for parsing MIME streams.

SYNOPSIS

Before reading further, you should see MIME::Tools to make sure that you understand where this module fits into the grand scheme of things. Go on, do it now. Ill wait.
Ready? Ok...

Basic usage examples

### Create a new parser object:
my $parser = new MIME::Parser;

### Tell it where to put things:
$parser->output_under("/tmp");

### Parse an input filehandle:
$entity = $parser->parse(*STDIN);

### Congratulations: you now have a (possibly multipart) MIME entity!
$entity->dump_skeleton; # for debugging

Examples of input

### Parse from filehandles:
$entity = $parser->parse(*STDIN);
$entity = $parser->parse(IO::File->new("some command|");

### Parse from any object that supports getline() and read():
$entity = $parser->parse($myHandle);

### Parse an in-core MIME message:
$entity = $parser->parse_data($message);

### Parse an MIME message in a file:
$entity = $parser->parse_open("/some/file.msg");

### Parse an MIME message out of a pipeline:
$entity = $parser->parse_open("gunzip - < file.msg.gz |");

### Parse already-split input (as "deliver" would give it to you):
$entity = $parser->parse_two("msg.head", "msg.body");

Examples of output control

### Keep parsed message bodies in core (default outputs to disk):
$parser->output_to_core(1);

### Output each message body to a one-per-message directory:
$parser->output_under("/tmp");

### Output each message body to the same directory:
$parser->output_dir("/tmp");

### Change how nameless message-component files are named:
$parser->output_prefix("msg");

Examples of error recovery

### Normal mechanism:
eval { $entity = $parser->parse(*STDIN) };
if ($@) {
$results = $parser->results;
$decapitated = $parser->last_head; ### get last top-level head
}

### Ultra-tolerant mechanism:
$parser->ignore_errors(1);
$entity = eval { $parser->parse(*STDIN) };
$error = ($@ || $parser->last_error);

### Cleanup all files created by the parse:
eval { $entity = $parser->parse(*STDIN) };
...
$parser->filer->purge;

Examples of parser options

### Automatically attempt to RFC-1522-decode the MIME headers?
$parser->decode_headers(1); ### default is false

### Parse contained "message/rfc822" objects as nested MIME streams?
$parser->extract_nested_messages(0); ### default is true

### Look for uuencode in "text" messages, and extract it?
$parser->extract_uuencode(1); ### default is false

### Should we forgive normally-fatal errors?
$parser->ignore_errors(0); ### default is true
Miscellaneous examples
### Convert a Mail::Internet object to a MIME::Entity:
@lines = (@{$mail->header}, "n", @{$mail->body});
$entity = $parser->parse_data(@lines);

alterMIME is a small program which is used to alter your mime-encoded mailpacks as typically received by Xamime, Inflex and AMaViS.
Main features:
- Insert disclaimers
- Insert arbitary X-headers
- Modify existing headers
- Remove attachments based on filename or content-type
- Replace attachments based on filename
Enhancements:
- The FFGET engine has been updated.
- Fixed Outlook Calendar kludging has been fixed.
- BASE64 disclaimer insertions have been added.