Free axigen outlook connector software for linux

Squirrelmail Outlook Skin Theme is based on the layout (visual interface) of the M$ Outlook 2003 over Squirrelmail (1.4.8).

Mail::Addressbook::Convert is a Perl module that can convert to and from many e-mail addressbooks.

SYNOPSIS

These modules allow to to convert between the following e-mail addressbook formats
From To csv csv ( Note: MS Outlook. Outlook Express and many other mailers will export and import into this format) tsv tsv (tab-separated ascii, Outlook and OE also do these) pine pine ccMail Eudora Eudora Pegasus Pegasus Juno Lidf Ldif (Netscape 4 exports in this format ) Mailrc Spry

This distribution will convert email addressbooks between many common formats. Some examples are Pine, Eudora, Pegasus, csv.

The documentation here is general. For details on conversion, each module has pod documentation specific to its conversion

As an example

To use to convert between Pine and Eudora as an example, you would do the following

use Mail::Addressbook::Convert::Pine;

use Mail::Addressbook::Convert::Eudora;

my $Pine = new Mail::Addressbook::Convert::Pine();

my $Eudora = new Mail::Addressbook::Convert::Eudora();

my $PineInFile ="pineSample.txt"; # name of the file containing the Pine data

my $raIntermediate = $Pine->scan($PineInFile);

my $raEudora = $Eudora->output($raIntermediate); # reference to an array containing a Eudora addressbook

All modules follow this template except Pegasus. Pegasus stores its address books in multiple files. See the documentation in Pegasus.pm

Jiplet is short for Java SIP Servlet. Jiplet Container project is an open-source container for server-side SIP applications. An application developer can create a SIP application written in Java using the Jiplet API and deploy the application in the container.
The container provides a number of framework services including support for SIP message parsing and formatting, scoped variables, authentication and authroization, thread-pooling, logging, custom class loading, management interface, etc. It enables application developer to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture.
In fact, it fits very well with the J2EE paradigm for software development and deployment. The jiplet container software can either be run as a standalone Java application or deployed as a service residing in a J2EE server. When running as a J2EE service, the jiplet container can access many of the features offered by the J2EE server.
In addition, The jiplet container is built with the service provider model in mind. In this model, a service provider can host customized SIP applications from their customers in a secure manner similar to the servlet hosting offered by many service providers.
The jiplet container is very similar to a Java HTTP servlet container in concept. A Java HTTP servlet is a Java class that handles HTTP messages from web browsers. Similarly, a jiplet is a Java class that handles SIP messages from SIP user agents (SIP phones and SIP servers).
A servlet container like Apache Tomcat can host one or more web applications (contexts), each consisting of one or more servlets. Similarly, the jiplet container can host one or more SIP applications (contexts) consisting of one or more jiplets.
Similar to the servlet API authored by Sun Microsystems, the jiplet container provides a set of Java classes that jiplet applications extend or use. The services provided by these classes are very similar to those of the servlet API including scoped variables, request forwarding from one jiplet to another, etc.
As in a servlet container, new jiplet applications, or contexts, can be deployed using a zipped file called spr (war is the Java servlet terminology). Since there are differences between the HTTP and SIP protocols, the servlet and the jiplet containers have some notable differences.
However, the jiplet is not a formal specification like the servlet specification. It is also not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users. There are many similarities between the jiplet and the SIP servlet in terms of features. If you are familiar with SIP servlets, you will feel right at home with the jiplet container.
We are planning to continue developing the jiplet container based on feedback provided by that the open-source community. We are hoping that open-source developers will extend this tool and the specification instead of a committee.
Main features:
- Open-source API for developing server-side SIP applications. Based on the JAIN-SIP API.
- Offers component-based development model.
- Servlet-like development and runtime environment.
- Access to powerful JAIN-API from SIP applications.
- JMX management interface for interfacing with management systems.
- Web-based user interface for managing jiplet applications.
- Support for scoped variables including application, session, request, transaction and dialog-scoped variables.
- Support for forwarding SIP messages from one jiplet to another.
- Container-managed authentication and authorization.
- Support for application timers.
- Can run as a standalone application or it can be integrated with JBOSS as a J2EE service.
- Comprehensive support for the service-provider model.
Enhancements:
- The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
- The new listening point architecture has been integrated into the Jiplet Container SIP connector.
- One connector can now use more than one IP address for SIP messaging.
- Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
- The Jiplet Container message proxying has been updated to work in a multi-homed environment.
- The software has been tested with Jboss 4.0.5.GA.

Nuxeo Core is an embeddable document management core, based on Nuxeo Runtime. Nuxeo Core provides all necessary low-level services to define, store, manage, audit, request and search content.
It is the kernel of Nuxeo 5 and can also be embedded in third-party applications to provide advanced content management features.
It can run on any Java platform, can be easily extended using plug-ins (thanks to Nuxeo Runtime) and implements JCA (Java EE Connector Architecture) to be easily plugged into existing applications or information systems.
Enhancements:
- This release fixes a bug related to document removal.

OutOfOffice answers your email with the message you have set when you are out of your office.

OutOfOffice is like Outlooks Out of office function, but you dont need Outlook or Exchange.

OpenOffice::OODoc::Intro is a Perl module for an introduction to the Open OpenDocument Connector.

The main goal of the Open OpenDocument Connector (OODoc) is to allow quick application development in 2 areas:

- replacement of old-style, proprietary, client-based macros for intensive and non-interactive document processing;
- direct read/write operations by enterprise software on office documents, and/or document-driven applications.

OODoc provides an abstraction of the document objects and isolates the programmer from low level XML navigation, UTF8 encoding and file compression details. For example:

use OpenOffice::OODoc;
my $document = ooDocument(file => filename.odt);
$document->appendParagraph
(
text => Some new text,
style => Text body
);
$document->appendTable("My Table", 6, 4);
$document->cellValue("My Table", 2, 1, "New value");
$document->save;

The script above appends a new paragraph, with given text and style, and a table with 6 lines and 4 columns, to an existing document, then inserts a value at a given position in the table. It takes much less time than the opening of the document with your favourite text processor, and can be executed without any desktop software connection. A program using this library can run without any OpenOffice.org installation (and, practically, OODoc has been tested on platforms where OpenOffice.org is not available yet).

More generally, OpenOffice::OODoc provides a lot of methods (probably most of them are not useful for you) allowing create/search/update/delete operations with document elements such as:

- ordinary text containers (paragraphs, headings, item lists); - tables and cells; - sections; - images; - styles; - page layout; - metadata (i.e. title, subject, and other general properties).

Java iCal Group Scheduler enables several users to get together for a meeting, by using JICAL to translate their iCalendar files into their available free/busy time and post it automatically to your Web server.

This project enables Ximian Evolution desktop users to book meetings with each other (and Outlook users) via a Web server storing their Free/Busy information as specified in RFC2445.

It works with Evolution, Korganiser, Apple iCal, and MS Outlook (for meetings), and enhances your workgroup and personal calendar views. Shell scripts for converting to various image formats are also included.

OpenGroupware.org is a set of applications for contact, appointment, project, and content management. OpenGroupware.org is comparable to Exchange and SharePoint portal servers.

It is accessible using Web interfaces and various native clients, including Outlook. Its servers run on almost any GNU/Linux system, can synchronize with Palm PDAs, and are completely scriptable using XML-RPC.