Free imap4 rfc software for linux

SAP::Rfc is a Perl module that contains RFC Function calls against an SAP R/3 System.

SYNOPSIS

# WARNING - as of SAP::Rfc 1.40 USER and PASSWD are case sensitive ready for
# R3 7.x
use SAP::Rfc;
$rfc = new SAP::Rfc(
ASHOST => myhost,
USER => ME,
PASSWD => secret,
LANG => EN,
CLIENT => 200,
SYSNR => 00,
TRACE => 1 );

my $it = $rfc->discover("RFC_READ_TABLE");

$it->QUERY_TABLE(TRDIR);
$it->ROWCOUNT( 2000 );
$it->OPTIONS( ["NAME LIKE RS%"] );

# or pass a list of hash refs like so:
$it->OPTIONS( [ { TEXT => "NAME LIKE RS%" } ] );

$rfc->callrfc( $it );

print "NO. PROGS: ".$it->tab(DATA)->rowCount()." n";
print join("n",( $it->DATA ));

$rfc->close();

SAP::Rfc - is a Perl extension for performing RFC Function calls against an SAP R/3 System. Please refer to the README file found with this distribution. This Distribution also allows the creation of registered RFCs so that an SAP system can call arbitrary Perl code created in assigned callbacks.

The best way to describe this package is to give a brief over view, and then launch into several examples. The SAP::Rfc package works in concert with several other packages that also come with same distribution, these are SAP::Iface, SAP::Parm, SAP::Tab, and SAP::Struc. These come together to give you an object oriented programming interface to performing RFC function calls to SAP from a UNIX based platform with your favourite programming language - Perl. A SAP::Rfc object holds together one ( and only one ) connection to an SAP system at a time. The SAP::Rfc object can hold one or many SAP::Iface objects, each of which equate to the definition of an RFC Function in SAP ( trans SE37 ). Each SAP::Iface object holds one or many SAP::Parm, and/or SAP::Tab objects, corresponding to the RFC Interface definition in SAP ( SE37 ).

For all SAP::Tab objects, and for complex SAP::Parm objects, a SAP::Struc object can be defined. This equates to a structure definition in the data dictionary ( SE11 ). Because the manual definition of interfaces and structures is a boring and tiresome exercise, there are specific methods provided to automatically discover, and add the appropriate interface definitions for an RFC Function module to the SAP::Rfc object ( see methods discover, and structure of SAP::Rfc ).

Please note that USER and PASSWD are now case sensitive - this change has the potential to break backward compatibility.

GMail::IMAPD is an IMAP4 gateway to Googles webmail service.

SYNOPSIS

# Start an IMAP-to-Gmail daemon on port 1143

use GMail::IMAPD;

my $daemon=GMail::IMAPD->new(LocalPort=>1143,
LogFile=>gmail_imapd.log,
Debug=>1);
$daemon->run();

# Or if you prefer to use your own server socket,
# you can do something like:

my $i2g=GMail::IMAPD->new(LogFile=>imapd.log);

for(;;){
my $s=someserver();
$i2g->procimap($s);
}

This module allows users to access their Gmail account with an IMAP client by running a server which accepts IMAP connections.

libmsntp is a full-featured, compact, portable SNTP library. SNTP (RFC 2030) is a simplified version of NTP (RFC 1305), which allows precise synchronization of system clocks over a best-effort network.

libmsntp provides SNTP client and server functionality in a shared library with a simple API.

libmsntp is implemented as a thin layer on top of msntp, N.M. Maclarens command-line SNTP utility. msntp is compact, straightforward, and elegant, and Im indebted to Nick, and to the Cambridge High Performance Computing Facility, for providing the msntp source to the public.

Installation:

To install, type "make install". You may need to be the superuser. libmsntp installs into /usr/local by default; to install to a different location, edit the Makefile and change the PREFIX variable.

libmhash is a free library which provides a uniform interface to a large number of hash algorithms. These algorithms can be used to compute checksums, message digests, and other signatures.
The HMAC support implements the basics for message authentication, following RFC 2104. In the later versions some key generation algorithms, which use hash algorithms, have been added.
At the time of writing this, the library supports the algorithms:
SHA1, SHA160, SHA192, SHA224, SHA384, SHA512, HAVAL128, HAVAL160, HAVAL192, HAVAL224, HAVAL256, RIPEMD128, RIPEMD256, RIPEMD320, MD4, MD5, TIGER, TIGER128, TIGER160, ALDER32, CRC32, CRC32b, WHIRLPOOL, GOST, SNEFRU128, SNEFRU256.
Enhancements:
- A SIGBUS bug was fixed for unaligned data.

URI::Escape is a Perl module to escape and unescape unsafe characters.

SYNOPSIS

use URI::Escape;
$safe = uri_escape("10% is enoughn");
$verysafe = uri_escape("foo", " -377");
$str = uri_unescape($safe);

This module provides functions to escape and unescape URI strings as defined by RFC 2396 (and updated by RFC 2732). A URI consists of a restricted set of characters, denoted as uric in RFC 2396. The restricted set of characters consists of digits, letters, and a few graphic symbols chosen from those common to most of the character encodings and input facilities available to Internet users:

"A" .. "Z", "a" .. "z", "0" .. "9",
";", "/", "?", ":", "@", "&", "=", "+", "$", ",", "[", "]", # reserved
"-", "_", ".", "!", "~", "*", "", "(", ")"

In addition, any byte (octet) can be represented in a URI by an escape sequence: a triplet consisting of the character "%" followed by two hexadecimal digits. A byte can also be represented directly by a character, using the US-ASCII character for that octet (iff the character is part of uric).

Some of the uric characters are reserved for use as delimiters or as part of certain URI components. These must be escaped if they are to be treated as ordinary data. Read RFC 2396 for further details.

OpenCAP is a server for Internet calendaring by following the specifications of the IETF (RFC CAP 4324).

Cap4j is the RFC 4234 CAP implementation. OpenCap project is the implementation of Cap4j calendar store.

Why another calendaring project ?

Ideally, Internet Calendaring should allow every Internet user to schedule meeting with each-other like they send mails. Unfortunately, Internet Calendaring suffers from a lack of interoperability. Thats why its so important to follow such standards.

Twisted Mail project provides client and server implementations of SMTP, POP3, and IMAP4.
These differentiate themselves from the Python standard library implementations both by presenting a much higher-level, easy-to-use interface and in their server components, which allow the implementation of custom servers for each protocol without dealing with protocol-level issues.
Twisted Mail includes a simple demonstration email server which accepts messages over SMTP, stores them in a Maildir arrangement, and can serve them to clients over POP3.
Enhancements:
- The IMAP4 client now properly quotes usernames and passwords when necessary.
- It also handles unsolicited FLAGS responses.
- The IMAP4 server can now parse multiple literals in a single command and to FETCH requests with multiple BODY parts.
- A bug where Deferreds returned from IMAP4 client methods would not receive connection lost notification has been fixed.
- Startup time on OS X has been improved.
- The SMTP server has been sped up.
- The POP3 mailbox API has been expanded to allow Deferreds to be returned in some cases.