Free body software for linux

FLV::Body is a flash video file data structure.

METHODS

This is a subclass of FLV::Base.

$self->parse($fileinst)

Takes a FLV::File instance and extracts the FLV body from the file stream. This method throws exceptions if the stream is not a valid FLV v1.0 or v1.1 file.

There is no return value.

$self->serialize($filehandle)

Serializes the in-memory FLV body. If that representation is not complete, this throws an exception via croak(). Returns a boolean indicating whether writing to the file handle was successful.

$self->get_info()

Returns a hash of FLV metadata. See File::Info for more details.

$self->get_tags()

Returns an array of tag instances.

$self->count_video_frames()

Returns the number of video tags in the FLV stream.

$self->count_audio_packets()

Returns the number of audio tags in the FLV stream.

$self->count_meta_tags()

Returns the number of meta tags in the FLV stream.

$self->last_start_time()

Returns the start timestamp of the last tag, in milliseconds.

$self->get_meta($key);
$self->set_meta($key, $value);

These are convenience functions for interacting with an onMetadata tag at time 0, which is a common convention in FLV files. If the 0th tag is not an FLV::MetaTag instance, one is created and prepended to the tag list.

See also get_value and set_value in FLV::MetaTag.

Mail::Message::Body is the data of a body in a message.

INHERITANCE

Mail::Message::Body has extra code in
Mail::Message::Body::Construct
Mail::Message::Body::Encode

Mail::Message::Body
is a Mail::Reporter

Mail::Message::Body is extended by
Mail::Message::Body::File
Mail::Message::Body::Lines
Mail::Message::Body::Multipart
Mail::Message::Body::Nested
Mail::Message::Body::String

Mail::Message::Body is realized by
Mail::Message::Body::Delayed

SYNOPSIS

my Mail::Message $msg = ...;
my $body = $msg->body;
my @text = $body->lines;
my $text = $body->string;
my IO::Handle $file = $body->file;
$body->print(*FILE);

my $content_type = $body->type;
my $transfer_encoding = $body->transferEncoding;
my $encoded = $body->encode(mime_type => text/html,
charset => us-ascii, transfer_encoding => none);n";
my $decoded = $body->decoded;

The encoding and decoding functionality of a Mail::Message::Body is implemented in the Mail::Message::Body::Encode package. That package is automatically loaded when encoding and decoding of messages needs to take place. Methods to simply build an process body objects are implemented in Mail::Message::Body::Construct.

The body of a message (a Mail::Message object) is stored in one of the many body types. The functionality of each body type is equivalent, but there are performance differences. Each body type has its own documentation with details about its implementation.

mod_asis is an Apache module for sending files which contain their own HTTP headers.

This module provides the handler send-as-is which causes Apache to send the document without adding most of the usual HTTP headers.

This can be used to send any kind of data from the server, including redirects and other special HTTP responses, without requiring a cgi-script or an nph script.

For historical reasons, this module will also process any file with the mime type httpd/send-as-is.

Usage:

In the server configuration file, associate files with the send-as-is handler e.g.
AddHandler send-as-is asis

The contents of any file with a .asis extension will then be sent by Apache to the client with almost no changes. Clients will need HTTP headers to be attached, so do not forget them. A Status: header is also required; the data should be the 3-digit HTTP response code, followed by a textual message.

Heres an example of a file whose contents are sent as is so as to tell the client that a file has redirected.

Status: 301 Now where did I leave that URL
Location: http://xyz.abc.com/foo/bar.html
Content-type: text/html

< HTML >
< HEAD >
< TITLE >Lame excusesRus< /TITLE >
< /HEAD >
< BODY >
< H1 >Freds exceptionally wonderful page has moved to
< A HREF="http://xyz.abc.com/foo/bar.html" >Joes< /A > site.
< /H1 >
< /BODY >
< /HTML >

Notes: the server always adds a Date: and Server: header to the data returned to the client, so these should not be included in the file. The server does not add a Last-Modified header; it probably should.

eProxy software is an SMTP proxy server framework specially designed for use in conjunction with Postfix version 2.1 and higher. However, it does also work as a frontend proxy however security wise I trust on the postfix smtpd.

What can eProxy be used for?
It is very fast and utilizes multi-threading. It is especially fast when it comes to your actual content filtering where you can use the speed of C/C++ in comparison to the interpreted language. It is very easy to use.

There are a few SMTP PROXY implementations out there but all I found are developed in either Perl or Python and some of them are extremely complex to use. This implementation makes it very easy to develop your own content filter in C+ and you only have to implement it in any of the following functions from(string from), to(string to), body(string body) and return a positive number to allow delivery and a negative number to disallow delivery.

You can of course still call to your processing/content filter "script(s)" via a popen(), system() or exec() call and run them through this method.

What do you need to (re)implement
Theres actually one source file that is of interest for you and thats the emailHandling.cpp file. In here the following functions are defined:

string getDomainName(string email);
int from(string from);
int rcptto(string to);
int body(string body);
void email(string email);

string getDomainName(string email); This is a convenience method to simply obtain the domainname part of an email address.

void email(string email); In this function you can do something to the email or part of it depending where you BOUNCED the email. It can be used to for instance store all emails in an archive or waiting box, waiting for manual release when an email is a suspect.

int from(string from); In this function you can do checking on the MAIL FROM part of an SMTP session. When your return a negative number the transaction is cancelled with a 550 error, when you return a positive number (larger than 0) then the MAIL FROM is accepted. The string from contains the email address

int rcptto(string to); In this function you can do checking on the RCPT TO part of an SMTP session. The string to contains the email address. Return a negative number to bounce the email return a positive number (large than 0) to continue.

int body(string body); In this function you will implement your actual body part scanning. Only when your result code is a positive number (larger than 0) then the body is send forth to the secondary (delivery) SMTP server. If it is bounced by your code it will not send the DATA command and the data stream, instead it will send a QUIT command and close the socket to the secondary server.

libcomms purpose of this library is to facilitate handling structured messages between programs. The messages consist of three parts: a keyword, a body and a delimiter.

The delimiter denotes the end of the message. Examples of a delimiter can be a simple newline ("n") for single line messages, or a double ("nn") newline for multi-line messages.

The keyword is used to identify the message. In the receiving program, it is used to dispatch the body to a handler function.

The body is everything between the keyword and the delimiter.

An example of the usage of this library might be to facilitate the communication between a GUI frontend and a program doing calculations in the background (the "backend").

Since the messages are human-readable (as opposed to shared memory or binary messages), it would enable the backend to be tested separately from the frontend, either by a human or by a testing script.

BUILDING THE LIBRARY

Invoking the "make" command gives you a list of all possible options.

The usual invocation for a system-wide installation of the library would be to do "make all", "make test", login as root, and then do a "make install".

Alternatively you can embed the library in your own program, by sticking it into a subdirectory, and invoking "make static" there.

USING THE LIBRARY

See the manual pages launch_program.3 and kill_program.3 on how to use the
functions.

MT blogmail is a small Python script that allows you to send an email (including an attached image) and have it posted to your MovableType blog.
You need something like Procmail to filter your mail and send messages from a
specific address to the blogmail.py script.
blogmail.py can now also poll a POP3 server and process any messages on the server
posting them to your blog for you.
Download blogmail.tar.bz2, unzip and save it somewhere convenient as blogmail.py,
make sure it is executable. (you might need to right-click and save as)
./blogmail.py --help
for all the usage information. You can also edit the script to set defaults.
The body of a message should be in the following format:
XBlogTitle: foo
XBlogPublish: [0|1]
XBlogUsername: mike
XBlogPassword: secret
XBlogid: 1
XBlogUri: http://blog.host.com/mt/mt-xmlrpc.cgi
XBlogAllowComments: [0|1]
XBlogConvertBreaks: [0|1]
XBlogKeywords: foo,baz,bar
XBlogCategories: flob,grob,blurck
All text between is posted as the body of the blog, the XBlog* fields
are parsed and sent via XML-RPC.
XBlogTitle is the only mandatory XBlog* field.
If the message is a multi-part mime message then the first text/plain section is considered to be the body of the post. the first image/* section will be taken
as an image to send to the server. Images are saved in:
images/ddMmmYY/HHMMSS_
and an image tag is added to the beginning of the post (style
tags with a float and you can have the body of the post beside and wrapping
around the bottom of the image).
Enhancements:
- o added command line options for pop3/file usage

Spamresponder provides a simple and radical spam filter using DNS validation and challenge/response.

Spamresponder is a very simple and radical spam filter, combining DNS validation with the challenge/response approach. It will go through all mail messages in /var/mail/$USER, looking for specific "trusted" strings in the header and body parts of the mail.

It will delete and send an automatic reply to messages which have no "trusted" strings inside them. Those replies will include one of the "trusted" strings, so the recipient just needs to reply to this confirmation message.

The MailFrom-address of an email containing a trusted string becomes a trusted string itself.

Rigs of Rods is a truck simulator based on soft body physics.
Rigs of Rods is a simulation game based on a custom advanced soft body physics engine.
In a vast open world, you can drive trucks, control cranes and fly airplanes. The chassis and wheels deform according to the stress they bear, and crashes are interesting to see too!
The linux version is still a release candidate under compatibility testing.
The main issue is that it is compiled with a GCC 4.1.1 compiler, and there are many incompatible C++ ABI out there. So it will probably work on a gcc 4.1.1 system, and break on a gcc 3.4 or 3.6 system. I dont know if there is an easy fix to that. Be aware that upgrading your gcc may break badly your system if not done correctly, so do it at your own risk.
Also, if you see the config box, but the game crashes, check the sanity of your GLX system first (test with another GLX program) because it breaks easily. It works with NVidia drivers, but I have not tested the ATI ones.
Read the README.LINUX file for more important informations.
Enhancements:
- Boats, with a small wahoo, a Class 1 speedboat contributed by cdquicksilver, and a very large high sea tug, the Smit Rotterdam, that has a rollable platform.
- A new terrain, called "island", that is still under construction but that will soon replace the two classic RoR terrains, because they are not realistic islands.
- Infinite sea with waves. Take the Smit and sail far from the island: you will encounter high swells offshore. You can even configure the wave fields (see the datawavefield.cfg file).
- A separate configurator program. Now you must start the RoRconfig program first, to choose your configuration options, save them, then start RoR.
- Serious bugfixing: camera shaking has been dramatically reduced, and the "crash on plane crash" problem is mostly eliminated.
- Addition of the Challenger car contributed by hemicuda.