Free bulk email service software for linux

LaTeX Service project is a small service which converts LaTeX into an image.
It returns a LaTeX rendering of selected text as a TIFF image.
Enhancements:
- Many things could be improved, its just a 0.1 release... but it works

Thunderbird Service Menu is a service menu that will allow you to right click on a file and attach it to a new E-mail from Thunderbird.

Just extract the "AttachToThunderbirdMail" config file to "/usr/share/apps/konqueror/servicemenus" and it should work.

Son of Service (SOS) is a multiuser volunteer management database for non-profits, charities, schools, churches, and clubs. SOS will keep track of your volunteers, their contact information, availability, work history, comments, reminders, and relationships.

It will help you quickly find the right volunteer for the job and e-mail him, and it will make reports about how you are using volunteers.

SOS is a helpful tool for organizations with many volunteers or multiple volunteer coordinators.

Your organization helps people for free, and your volunteers work for free. So you know there is a "free lunch."

SOS is free. Its free from charge: notice there is no menu option for purchasing or ordering. But SOS also provides freedom from many restrictions. Download the program, install it, and use it without buying expensive licenses.

Use it on as many systems with as many users and volunteers as you have. Use your choice of server operating system and RDBMS. (You dont need to buy a RDBMS or other server software.) You can even modify SOS to meet your specific needs because the full source is available to you.

dl Download Ticket Service project is a minimalist and rough download ticket service with automatic expiration, written in PHP. Ive been using this service as an email-attachment replacement for my company, but there are no plans on extending it. It will remain minimal: no fancy features, just bug fixes.
Installation:
Copy the "htdocs" directory to a directory of choice under your web server. Configure the needed parameters inside "include/config.php" to reflect the external url, main password, etc. The "include" directory must not be accessible: if you use apache, the included .htaccess file should be sufficient; consult your web server documentation otherwise.
A spool directory outside of the web server root must be accessible to the web server process. In the example "include/config.php" this is configured as "/var/spool/dl". If you web server runs as "nobody:nogroup", issue:
mkdir -p -m770 /var/spool/dl
chgrp nogroup /var/spool/dl
to create correctly this directory.
The maximal upload limit is determined by several PHP configuration parameters:
file_uploads: must be "On".
upload_tmp_dir: ensure enough space is available.
upload_max_filesize: change as needed.
post_max_size: must be at least 1M larger than upload_max_filesize.
The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter. You can also set these parameters with ini_set() inside "include/config.php" or through apaches directives to localize them to the installation path.
There are several bugs in the dba_open() function in PHP 4.x which cannot be fixed. If you can, upgrade PHP to at least 4.3.5. If you cannot upgrade, you need to configure the "$dbHandler" parameter to something available to your PHP installation (usually db3/db2/dbm) and use the Berkeleys DB "db4_load" utility to create an empty database:
echo | db4_load /var/spool/dl/data.db
echo | db4_load /var/spool/dl/user.db
chmod 770 /var/spool/dl/*.db
chgrp nogroup /var/spool/dl/*.db
Depending on your system, you may have to use "db3_load/db2_load/etc" instead of "db4_load". Sometimes these utilities are part of "db*-util" packages under several linux distributions. If you have PHP 4.3.5 or greater, this is done automatically.
Ticket expiration is performed automatically when any web page is requested. This means that expired downloads will still occupy space on the spool directory until a web page is first serviced. If you need to ensure that the spool is purged regularly (for very low traffic servers), setup a scheduled job that requests the "http://dl.example.com/d/" page. Under UNIX, setup a cron entry like this:
0 0 * * * wget -q -O /dev/null "http://dl.example.com/d/" > /dev/null
Version restrictions:
- Tested with all mayor and minor browsers.
- Tested with PHP 4.2/4.3.
- Byte ranges are currently not supported.
- The submit button is not disabled correctly with Internet Explorer 6 (works on other graphical browsers however).

Peco::Service is a Perl module with service specifications for Peco IoC containers.

SYNOPSIS

use Peco::Service;

$service = Peco::Service->new( $class, @depends, $create, %attrs );
$service = Peco::Service::Factory->new( ⊂routine, @depends );
$service = Peco::Service::Constant->new( $value );

SERVICE TYPES

Peco::Service

A generic service registration class.

Peco::Service::Factory

Factory service registration class. Takes a coderef which is called each time this service is accessed.

Peco::Service::Constant

For constant or scalar values.

Email::Store is a framework for database-backed email storage.

SYNOPSIS

use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once

Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );

...

Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.

Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

As you probably know, Yahoo Mail does not provide free POP access to its users any more. You can still use your YM account for free, but you have to use a Yahoo Mail web site to access your account.
This is not very convenient as you always have to be online, you cannot use your favourite e-mail client to read your messages, and so on. You can easily immagine the disadvantages of having to manage all your corespondence via web.
When Yahoo disabled its free POP access, the first thing that came to my mind was to change my e-mail account. But then I realized, there are far too many people used to my current Yahoo Mail address, that I am used to my YM address very much too and I thought - if Yahoo closes a free service, the other services will follow sooner or later. So changing an e-mail service/account wasnt really solution.
That is when I have decided to write YoSucker as a simple portable perl application, that would simulate a user actions to retrieve my mail to my local inbox. Yahoo Mail Sucker simply connects to the Yahoo Mail web site, parses the HTML code and fetches new messages.
With time I have added lots of other features and functionality (like support for multiple accounts, support for procmail, support for local Yahoo Mail sites, for proxy connection and much more) but the basic idea still stay the same...
Main features:
- secure SSL login
- support for multiple accounts
- encrypted passwords for enhanced security
- transaction safe writes
- support for various folders (including BULK mail)
- support for multiuser environment
- support for multiple mailboxes in one config file
- support for procmail (output to a pipe)
- support for localized Yahoo Mail sites
- support for proxy
- support for basic proxy authorization
- support of command line parameters
- powerful digest feature for listing mailbox content
- handles virtually unlimited number of messages
- LeaveOnServer, EmptyTrash and OnlyNew features
- restore message unread flag feature
- powerful CLEAN option
- quota storage warning system
- session Respawn feature
Enhancements:
- This things been around too long be be a prototype any longer.
- Filtered the annoying "Yahoo! Domain Keys" message in From header