Free mime encoded mailpacks software for linux

MIME::EncWords is a Perl module created to deal with RFC-1522 encoded words (improved).

SYNOPSIS

MIME::EncWords is aimed to be another implimentation of MIME::Words so that it will achive more exact conformance with MIME specifications. Additionally, it contains some improvements. Following synopsis and descriptions are inherited from its inspirer, with description of improvements and clarifications added.

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...

use MIME::EncWords qw(:all);

### Decode the string into another string, forgetting the charsets:
$decoded = decode_mimewords(
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= ,
);

### Split string into array of decoded [DATA,CHARSET] pairs:
AT decoded = decode_mimewords(
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= ,
);

### Encode a single unsafe word:
$encoded = encode_mimeword("xABFranxE7oisxBB");

### Encode a string, trying to find the unsafe words inside it:
$encoded = encode_mimewords("Me and xABFranxE7oisxBB in town");

Fellow Americans, you probably wont know what the hell this module is for. Europeans, Russians, et al, you probably do.

For example, heres a valid MIME header you might get:

From: =?US-ASCII?Q?Keith_Moore?= < moore AT utk.edu >
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= < keld AT dkuug.dk >
CC: =?ISO-8859-1?Q?Andr=E9_?= Pirard < PIRARD AT vm1.ulg.ac.be >
Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=
=?ISO-8859-2?B?dSB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?=
=?US-ASCII?Q?.._cool!?=

The fields basically decode to (sorry, I can only approximate the Latin characters with 7 bit sequences /o and e):

From: Keith Moore < moore AT cs.utk.edu >
To: Keld J/orn Simonsen < keld AT dkuug.dk >
CC: Andre Pirard < PIRARD AT vm1.ulg.ac.be >
Subject: If you can read this you understand the example... cool!

Supplement: Fellow Americans, Europeans, you probably wont know what the hell this module is for. East Asians, et al, you probably do.
For example, heres a valid MIME header you might get:

Subject: =?EUC-KR?B?sNTAuLinKGxhemluZXNzKSwgwvzB9ri7seIoaW1w?=
=?EUC-KR?B?YXRpZW5jZSksILGzuLgoaHVicmlzKQ==?=

The fields basically decode to (sorry, I cannot approximate the non-Latin multibyte characters with any 7 bit sequences):

Subject: ???(laziness), ????(impatience), ??(hubris)

jMimeMagic project is a Java library for determining the MIME or content type of files or streams.
Enhancements:
- The build system has been migrated to maven 1.x.
- Subversion is now used.
- A hinting flag has been added for file extensions hints.
- The ability to disable sub-matches for MIME-only detection has been added, and still needs work (e.g. submatch until a MIME is found).
- Content detection plugins are now supported.
- Logging has been switched over to commons-logging.
- This release cleans up Javadoc and enables site generation.
- There is other miscellaneous cleanup.

Bundle::Encode is a Perl bundle to install Encode modules and dependencies.

SYNOPSIS

perl -MCPAN -e install Bundle::Encode

CONTENTS

Text::Iconv
Module::Build
Module::Build::Compat
Test::Simple
Test::More
Unicode::Japanese
CGI
ExtUtils::CBuilder
XML::Parser::Expat
IO::File
MIME::Base64
Getopt::Std
Getopt::Long
Unicode::Normalize
Font::TTF
Compress::Zlib
Spiffy
Cwd
File::Find
File::Path
FindBin
Config
Test::Builder
Test::Base
HTML::Entities::Pictogram
XSLoader
IDNA::Punycode
Net::IDN::Nameprep
Unicode::Normalize
Unicode::String
Scalar::Util
Encoding::BER
encoding::split
encoding::warnings
HTML::Encoding
Term::Encoding
XML::Encoding
Template::Provider::Encoding
Catalyst::Plugin::Unicode::Encoding
Email::MIME::Encodings
Convert::Charmap
Encode
Encode::IBM
Encode::compat
Encode::InCharset
Encode::JIS2K
Encode::ZapCP1252
Encode::Unicode::Japanese
Encode::HEBCI
Encode::Detect
Encode::HanConvert
Encode::Registry
Encode::TECkit
Encode::UTR22
Encode::DoubleEncodedUTF8
Encode::First
Encode::JavaScript::UCS
Encode::JP::Mobile
Encode::Punycode
Encode::BOCU1
Encode::BOCU1::XS
Encode::EUCJPMS
Encode::CNMap
Encode::Unicode::UTF7
Encode::IMAPUTF7
Encode::Mapper

MIME::Head is a MIME message header (a subclass of Mail::Header).

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...

Construction

### Create a new, empty header, and populate it manually:
$head = MIME::Head->new;
$head->replace(content-type, text/plain; charset=US-ASCII);
$head->replace(content-length, $len);

### Parse a new header from a filehandle:
$head = MIME::Head->read(*STDIN);

### Parse a new header from a file, or a readable pipe:
$testhead = MIME::Head->from_file("/tmp/test.hdr");
$a_b_head = MIME::Head->from_file("cat a.hdr b.hdr |");

Output

### Output to filehandle:
$head->print(*STDOUT);

### Output as string:
print STDOUT $head->as_string;
print STDOUT $head->stringify;

Getting field contents

### Is this a reply?
$is_reply = 1 if ($head->get(Subject) =~ /^Re: /);

### Get receipt information:
print "Last received from: ", $head->get(Received, 0), "n";
@all_received = $head->get(Received);

### Print the subject, or the empty string if none:
print "Subject: ", $head->get(Subject,0), "n";

### Too many hops? Count em and see!
if ($head->count(Received) > 5) { ...

### Test whether a given field exists
warn "missing subject!" if (! $head->count(subject));
Setting field contents
### Declare this to be an HTML header:
$head->replace(Content-type, text/html);
Manipulating field contents
### Get rid of internal newlines in fields:
$head->unfold;

### Decode any Q- or B-encoded-text in fields (DEPRECATED):
$head->decode;

Getting high-level MIME information

### Get/set a given MIME attribute:
unless ($charset = $head->mime_attr(content-type.charset)) {
$head->mime_attr("content-type.charset" => "US-ASCII");
}

### The content type (e.g., "text/html"):
$mime_type = $head->mime_type;

### The content transfer encoding (e.g., "quoted-printable"):
$mime_encoding = $head->mime_encoding;

### The recommended name when extracted:
$file_name = $head->recommended_filename;

### The boundary text, for multipart messages:
$boundary = $head->multipart_boundary;

MIME::Words is a Perl module to deal with RFC-1522 encoded words.

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...

use MIME::Words qw(:all);

### Decode the string into another string, forgetting the charsets:
$decoded = decode_mimewords(
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= ,
);

### Split string into array of decoded [DATA,CHARSET] pairs:
@decoded = decode_mimewords(
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= ,
);

### Encode a single unsafe word:
$encoded = encode_mimeword("xABFranxE7oisxBB");

### Encode a string, trying to find the unsafe words inside it:
$encoded = encode_mimewords("Me and xABFranxE7oisxBB in town");

Fellow Americans, you probably wont know what the hell this module is for. Europeans, Russians, et al, you probably do.

For example, heres a valid MIME header you might get:

From: =?US-ASCII?Q?Keith_Moore?= < moore@cs.utk.edu>
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= < keld@dkuug.dk>
CC: =?ISO-8859-1?Q?Andr=E9_?= Pirard < PIRARD@vm1.ulg.ac.be>
Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=
=?ISO-8859-2?B?dSB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?=
=?US-ASCII?Q?.._cool!?=

The fields basically decode to (sorry, I can only approximate the Latin characters with 7 bit sequences /o and e):

From: Keith Moore < moore@cs.utk.edu>
To: Keld J/orn Simonsen < keld@dkuug.dk>
CC: Andre Pirard < PIRARD@vm1.ulg.ac.be>
Subject: If you can read this you understand the example... cool!

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.

Encode::PerlIO is a detailed document on Encode and PerlIO.

Overview

It is very common to want to do encoding transformations when reading or writing files, network connections, pipes etc. If Perl is configured to use the new perlio IO system then Encode provides a "layer" (see PerlIO) which can transform data as it is read or written.

Here is how the blind poet would modernise the encoding:

use Encode;
open(my $iliad,:utf8,iliad.utf8);
my @epic = < $iliad >;
print $utf8 @epic;
close($utf8);
close($illiad);

In addition, the new IO system can also be configured to read/write UTF-8 encoded characters (as noted above, this is efficient):

open(my $fh,>:utf8,anything);
print $fh "Any x{0021} string N{SMILEY FACE}n";

Either of the above forms of "layer" specifications can be made the default for a lexical scope with the use open ... pragma. See open.

Once a handle is open, its layers can be altered using binmode.

Without any such configuration, or if Perl itself is built using the systems own IO, then write operations assume that the file handle accepts only bytes and will die if a character larger than 255 is written to the handle. When reading, each octet from the handle becomes a byte-in-a-character. Note that this default is the same behaviour as bytes-only languages (including Perl before v5.6) would have, and is sufficient to handle native 8-bit encodings e.g. iso-8859-1, EBCDIC etc. and any legacy mechanisms for handling other encodings and binary data.
In other cases, it is the programs responsibility to transform characters into bytes using the API above before doing writes, and to transform the bytes read from a handle into characters before doing "character operations" (e.g. lc, /W+/, ...).

You can also use PerlIO to convert larger amounts of data you dont want to bring into memory. For example, to convert between ISO-8859-1 (Latin 1) and UTF-8 (or UTF-EBCDIC in EBCDIC machines):

open(F, ":utf8", "data.utf") or die $!;
while (< F >) { print G }

# Could also do "print G < F >" but that would pull
# the whole file into memory just to write it out again.

More examples:

open(my $f, ":encoding(iso-8859-2)")
open(my $h, ">:encoding(latin9)") # iso-8859-15