Friend & Love project is a dating system script. Its features include profiles, adult profiles, sending of kisses, notes, emails, and winks, viewing of tracks, a display of whos online and whos new, and profile searches.

What the script will do for you

· Checks server requirement.
· Checks all files, directories are original, current version and present on your sever after upload.
· Checks if any file or directory has been corrupted during the upload.
· Checks files and directories permission.
· Setup database.
· Setup the simple configuration file for you.

What the script will not do

· Not help you to upgrade from previous version (Ubolratana1.1.5SP). This one supports only fresh install. We recommend you to not use this script for live website during beta version.
· Not help you for full configuration. You have to download config.php to change some variables by yourself.

Whats New in This Release:

· This release removes the md5 hash check and enhances the installer.
· It includes newsletter registration.
· Some unused images have been removed.
· Minor bugs in several files have been fixed.

@Mail can be used as a WebMail Client for accessing existing POP3 or IMAP mailboxes. When using @Mail, users can access email resources via a web-browser or wireless device.

Here are some key features of "@Mail":

· WebMail plugin for accessing existing POP3/IMAP accounts
· The HTML interface of @Mail is brandable. Customize the layout of @Mail to suit your organization.
· Offers users an attractive and feature-rich WebMail service at your domain(s).
· Shared Address Book and Scheduler features and user-customizable settings.
· Complete source-code included.
· Full WebAdmin control panel provides web-based administration interface.

As a WebMail Client, users can access @Mail via any browser or wireless device. Requests are handled by the Webserver (Apache) which runs the @Mail application (use of mod_perl or apache-perl is recommended).

User settings, Address Book, Scheduler tasks, profiles and account information are stored in a MySQL database. Email message delivery and storage remain on the POP3 or IMAP server, which is accessed by the WebMail client of @Mail.

Limitations:

· 30-day evaluation

Whats New in This Release:

· This release includes improvements for running under Apple Safari with the Simple Ajax Interface, a complete port of the Web admin API (admin-lite.php) for PHP, a port of the wireless interface to PHP, an improved subadmin module, improved spell-check across all interfaces, fixed Calendar support for Simple non-Ajax interface, a spam settings panel in the simple interface, and an improved function for converting between HTML and plain text when switching editors.

Lingua::RU::Charset is a Perl extension for detecting and converting various russian character sets: KOI8-r, Windows-1251, CP866, ISO-8859-5, X-Mac-Cyrillic, russian text in english letters, russian part of Unicode and UTF-8. Lingua::RU::Charset module can be especially useful for computers with broken cyrillic locales (like foreign web hosts).

SYNOPSIS

use Lingua::RU::Charset qw (:CHARSET);
use Lingua::RU::Charset qw (:CONVERT);
use Lingua::RU::Charset qw (:CONVERT :CHARCASE);
use Lingua::RU::Charset qw (any2koi koi2lc koi2uc);

More documentation and examples coming soon...

NOTE

Unfortunately I dont have time to implement the Unicode and UTF-8 subroutines. But I am sure that such functions would be useful for interesting Perl scripts exchanging russian data with Java servlets. So you are welcome to submit some code!

Mail::MboxParser::Mail::Convertable is a Perl module that can convert mail for sending etc.

SYNOPSIS

use Mail::MboxParser;

[...]

# $msg is a Mail::MboxParser::Mail-object
my $mail = $msg->make_convertable;

$mail->delete_from_header(date, message-id);
$mail->replace_in_header(to, john.doe@foobar.com);
$mail->add_to_header( [cc, john.does.brother@foobar.com],
where => BEHIND );
$mail->send(sendmail);

This class adds means to convert an email object into something that could be send via SMTP, NNTP or dumped to a file or filehandle. Therefore, methods are provided that change the structure of an email which includes adding and removing of header-fields, MIME-parts etc and transforming them into objects of related modules.

Currently, only basic manipulation of the header and sending using Mail::Mailer is provided. More is to come soon.

This class works non-destructive. You first create a Convertable-object and do any modifications on this while the Mail-object from which it was derived will not be touched.

Template::Plugin::Translit::RU is a filter for converting cyrillic text into transliterated one and back.

SYNOPSIS

Use as filters.
[% USE Translit::RU translit detranslit %]
[% FILTER translit( koi ) %]
...
This text would stay unchanged because it is not cyrillic.
...
[% END %]
Use as object. First argument - text for conversion. Second optional argument - charset (koi is default).
[% USE plTranslit = Translit::RU %]
[% plTranslit.translit( without cyrillic text is useless ) %]
[% plTranslit.detranslit( kirilitca, win ) %]

Template::Plugin::Translit::RU is Template Toolkit filter which allows to convert cyrillic text into transliterated latin text. Currently two most popular charsets are supported - koi8-r and windows-1251. Also back conversion supported.

Mail::SendEasy can send plain/html e-mails through SMTP servers (platform independent). Supports SMTP authentication and attachments.

This modules will send in a easy way e-mails, and doesnt have dependencies. Soo, you dont need to install libnet.
It supports SMTP authentication and attachments.

USAGE:

OO

use Mail::SendEasy ;

my $mail = new Mail::SendEasy(
smtp => localhost ,
user => foo ,
pass => 123 ,
) ;

my $status = $mail->send(
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { print $mail->error ;}

STRUCTURED

use Mail::SendEasy ;

my $status = Mail::SendEasy::send(
smtp => localhost ,
user => foo ,
pass => 123 ,
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { Mail::SendEasy::error ;}

Mail::QmailRemoteXS is a lightweight C-code (XS) SMTP send function based on Qmails qmail-remote.

SYNOPSIS

use Mail::QmailRemoteXS;

$ret = Mail::QmailRemoteXS::mail($to_domain,$from_address,$to_address,$msg,$helo,$net_timeout,$net_timeoutconnect);

This module provides a single function mail that sends an email via SMTP. It uses an XS implementation of Qmails qmail-remote binary written in C so is very lightweight and fast (compared to Net::SMTP).

The difference between Mail::QmailRemote (IKEBE Tomohiro) and Mail::QmailRemoteXS is that the former requires the qmail package to be installed and simply invokes a wrapper around the qmail-remote binary for each send. This module statically links code based on qmail-remote and has no dependencies other that a working resolver.

FUNCTIONS

mail

$ret = Mail::QmailRemoteXS::mail($to_domain,$from_address,$to_address,$msg,$helo,$net_timeout,$net_timeoutconnect);

Send an email message $msg (which includes rfc822 headers) to $to_address from $from_address using $helo as the SMTP HELO greeting. $net_timeoutconnect is for the initial SMTP connection and $net_timeout is for the wait time for SMTP responses.
See Qmails qmail-remote manpage for more information and details on the return value $ret.

Mail::LMLM is a list of Mailing Lists Manager.

SYNOPSIS

use Mail::LMLM;

my $renderer =
Mail::LMLM->new(
extra-classes => %extra_mailing_list_classes,
title => "List of the Foo Mailing Lists",
headline => "Foo Mailing Lists",
lists => @lists,
prolog => &prolog,
epilog => &epilog,
);

$renderer->render();

The Mail::LMLM module allows users to easily manage HTML directories of mailing lists of various mailing list managers and hosts.

To use it create a new module of type Mail::LMLM with a new method, while initializing it with the list of mailing lists (in order of listing), and other parameters. Then, invoke the render() function to create the HTML files within the current directory.

fortune-mod-ru is a collection of cookie files in Russian. It includes the following categories:

· armenian (questions to Armenian Radio)
· citates (citations of great people)
· computer (sysadmins, PC and other)
· fomenko (aphorisms from Fomenko)
· M$ (dedicated to Micro$oft)
· murphy (Murphy laws)
· programming (programmers and programming).

fortune-mod-ru also includes aphorisms from the collection of Nikolay Vekshin (http://aforizmi.narod.ru).

Whats New in This Release:

· New fortunes have been added (amur, b0, b11, b12, b13, b2, d1, d21, d41, e0, e12, and e13).
· There are major fixes in kascheys collection, and minor fixes in do_you_know.
· The citates fortune has been added.
· .u8 symlinks have been added for supporting of recoding on the fly.

tidyup-mail software is especially useful for russian/ukrainian/belarusian users but however can help those who reads mail from people that uses such brain-damaged web-mailers as yahoo mail.

Fatigue with xterm when reading mail from mutt? Tired to press "Do Full reset" every time when terminal becames full of garbage? This program is for you! It removes unsafe characters for email & makes xterm happy!

Note that all documentation comes in russian language. Check for your local russian hacker.

Mail::Sendmail is a simple platform independent mailer.

SYNOPSIS

use Mail::Sendmail;

%mail = ( To => you@there.com,
From => me@here.com,
Message => "This is a very short message"
);

sendmail(%mail) or die $Mail::Sendmail::error;

print "OK. Log says:n", $Mail::Sendmail::log;

Simple platform independent e-mail from your perl script. Only requires Perl 5 and a network connection.

Mail::Sendmail contains mainly &sendmail, which takes a hash with the message to send and sends it. It is intended to be very easy to setup and use.

Here are some key features of "Mail::Sendmail":

· Automatic time zone detection, Date: header, MIME quoted-printable encoding (if MIME::QuotedPrint installed), all of which can be overridden.
· Bcc: and Cc: support.
· Allows real names in From:, To: and Cc: fields
· Doesnt send an X-Mailer: header (unless you do), and allows you to send any header(s) you want.
· Configurable retries and use of alternate servers if your mail server is down
· Good plain text error reporting

Limitations:

· Headers are not encoded, even if they have accented characters.
· No suport for the SMTP AUTH extension.
· Since the whole message is in memory, its not suitable for sending very big attached files.
· The SMTP server has to be set manually in Sendmail.pm or in your script, unless you have a mail server on localhost.
· Doesnt work on OpenVMS, I was told. Cannot test this myself.

Mail 2 Wordpress is an SMTP mailrobot for posting wordpress blog entries via SMTP mail.

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.

Mail::SpamCannibal is a HOWTO Install SpamCannibal.

Create a user account for the SpamCannibal client. The mail client should not be run as a root user, to do so creates an unacceptable security risk.

Check the /etc/passwd and /etc/group files to make sure that uid and gid assignments for the new user are not already used, then run groupadd and adduser.

groupadd -g 95 spam

adduser

Login name for new user []: spam

User id for spam [ defaults to next available]:

Initial group for spam [users]: spam

Additional groups for spam (seperated
with commas, no spaces) []:

spams home directory [/home/spam]: /usr/local/spamcannibal

spams shell [/bin/bash]:

spams account expiry date (YYYY-MM-DD) []:

OK, Im about to make a new account. Heres what you entered so far:

New login name: spam
New UID: [Next available]
Initial group: spam
Additional groups: [none]
Home directory: /usr/local/spamcannibal
Shell: /bin/bash
Expiry date: [no expiration]

This is it... if you want to bail out, hit Control-C. Otherwise, press
ENTER to go ahead and make the account.

you fill in the rest......

Mail::IMAPTalk is an IMAP client interface with lots of features.

SYNOPSIS

use Mail::IMAPTalk;

$IMAP = Mail::IMAPTalk->new(
Server => $IMAPServer,
Username => foo,
Password => bar,
Uid => 1 )
|| die "Failed to connect/login to IMAP server";

# Append message to folder
open(my $F, rfc822msg.txt);
$IMAP->append($FolderName, $F) || dir $@;
close($F);

# Select folder and get first unseen message
$IMAP->select($FolderName) || die $@;
$MsgId = $IMAP->search(not, seen)->[0];

# Get message envelope and print some details
$MsgEV = $IMAP->fetch($MsgId, envelope)->{$MsgId}->{envelope};
print "From: " . $MsgEv->{From};
print "To: " . $MsgEv->{To};
print "Subject: " . $MsgEv->{Subject};

# Get message body structure
$MsgBS = $IMAP->fetch($MsgId, bodystructure)->{$MsgId}->{bodystructure};

# Find imap part number of text part of message
$MsgTxtHash = Mail::IMAPTalk::find_message($MsgBS);
$MsgPart = $MsgTxtHash->{plain}->{IMAP-Partnum};

# Retrieve message text body
$MsgTxt = $IMAP->fetch($MsgId, "body[$MsgPart]")->{$MsgId}->{body};

$IMAP->logout();

This module communicates with an IMAP server. Each IMAP server command is mapped to a method of this object.

Although other IMAP modules exist on CPAN, this has several advantages over other modules.

It parses the more complex IMAP structures like envelopes and body structures into nice Perl data structures.

It correctly supports atoms, quoted strings and literals at any point. Some parsers in other modules arent fully IMAP compatiable and may break at odd times with certain messages on some servers.

It allows large return values (eg. attachments on a message) to be read directly into a file, rather than into memory.

It includes some helper functions to find the actual text/plain or text/html part of a message out of a complex MIME structure. It also can find a list of attachements, and CID links for HTML messages with attached images.

It supports decoding of MIME headers to Perl utf-8 strings automatically, so you dont have to deal with MIME encoded headers (enabled optionally).

While the IMAP protocol does allow for asynchronous running of commands, this module is designed to be used in a synchronous manner. That is, you issue a command by calling a method, and the command will block until the appropriate response is returned. The method will then return the parsed results from the given command.