Free rfc 822 software for linux

This Tcl script may be used to extract MIB, PIB and ASN.1 modules from an RFC document.

Unlike most extractors, this script is smart enough to recognize ASN.1-style comments prior to or within the module header, use of the "TagDefaults" part of the module header (not used by MIB modules), module headers that are broken across multiple lines, and macros.

RFC::RFC822::Address is a Perl module for RFC 822 style address validation.

SYNOPSIS

use RFC::RFC822::Address qw /valid/;

print "Validn" if valid abigail@example.com;

This module checks strings to see whether they are have the valid syntax, as defined in RFC 822 [1]. One subroutine, valid, can be imported, which takes a single string as argument. If the string is valid according to RFC 822, a true value is returned, else a false value is returned.

CAVEATS and BUGS

This module sets the variable $Parse::RecDescent::skip. This will influence all other Parse::RecDescent parsers. And this parser will break if you set $Parse::RecDescent::skip to another value. It doesnt look that it is possible to set an alternative skip value for each parser, other than setting the skip value on each production.

Example A.1.5 in RFC 822 is wrong. It should use "Galloping Gourmet"@ANT.Down-Under.

This module should have been named RFC::822::Address. However, perl 5.004 doesnt like the 822 part, and at the time of this writing MacPerl is still at 5.004.

This module is slow.

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.

Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822.

SYNOPSIS

use Mail::RFC822::Address qw(valid validlist);

if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}

if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}

Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.

This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.

valid ( address )

Returns true or false to indicate if address is an RFC822 valid address.

validlist ( addresslist )

In scalar context, returns true if the parameter is an RFC822 valid list of addresses.

In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list

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.

utftpd is a TFTP server with fine-grained access control, support for blksize (RFC 2348) and timeout options, and support for revision control. You can assign three different kinds of rights to every client:
read
the right to read a file.
write
the right to write to an already existing file.
create
the right to create a file.
Clients may be specified by a single ip address or a range of addresses or by ip address and mask.
Enhancements:
- the server now uses adaptive timeout.
- the server now unlinks the received file if it was not received completely.
- the server now includes a workaround for the "Sorcerers Apprentice Syndrome" (as its called by RFC 1123)

mimetic is a powerful, full featured, STL-based, standards compliant C++ MIME library.
mimetic is a GPL MIME library written in C++ designed to be easy to use and integrate but yet fast and efficient.
Im a fan of the C++ Standard Library so mimetic has been built around the standard lib. This means that youll not find yet another string class or list implementation and that youll feel comfortable in using this library from the very first time.
mimetic doesnt use exceptions but it heavily uses templates so a mostly standard compliant C++ compiler is required. I developed it using GCC 3.x and tested on most Unixes.
When it comes to performance the stdlib is important (and GCCs is not the fastest library around) so mimetic code include some classes that are not strictly needed but are there just to improve performance (for ex. the File class for memory mapped file access).
Most classes functionalities and behavior will be clear if you ever studied MIME and its components; if you dont know anything about Internet messages youll probably want to read some RFCs to understand the topic and, therefore, easily use the library whose names, whenever possible, overlap terms adopted in the standard RFC documents. At the very least: RFC 822, RFC 2045 and RFC 2046.
Very easy to use
This was, from the beginning, one of the objectives of mimetic.
If you know the MIME standard youll rarely need online documentation.
Full featured
Everything you expect to find in a MIME library is already into mimetic, if youll not find it is because your requirements are probably insane :) Oh well cryptography is not in the library yet, but it will some day.
Standard compliant
mimetic tries to follow current standards as closely as possible.
STL based
This could be a very big advantage if you know the STL and want to integrate mimetic into your STL based project. Youll have same powerful concepts and classes fully applicable to emails. If you dont know the STL so this is a good opportunity to learn it! A very good reference (yet freely readable) is the Dinkum C++ Library Reference.
Compile-time codec chains
Codec chains are template based so that codecs are chained together by the compiler using inline functions whenever possible to speed up runtime performance. Creating a codec chain will sound very familiar if you know Unix pipes:
codec0 | codec1 | codec2 | ... | last_codec
Jump to a more complete example
Portable
Ive personally tested it on Linux, {Open,Free,Net}BSD, Solaris, Mac OS X. It uses Autotools to compile so porting on any Unix system should be easy.
You can also easily compile mimetic on Windows using files in win32 directory (thanks to Andreas Gruen who worked on Windows port). Project files come out Visual Studio 2003 .NET.
For questions regarding Windows port you can contact Andreas at
More then 50 test functions, more then 2500 checks
cutee has been used for Unit Testing and there are a lot of tests the run automatically every time someone compiles mimetic. This doesnt mean that its bug free but it helps.
Open source
Source code of the library, tests and examples are bundled into the distribution package. All except codec code (that is heavily template based) is very readable so if Documentation is not good enough for you sources can be your primary reference.
HTML documentation
Library documentation is generated from source code by Doxygen. You can browse it online of generate yourself for offline browsing.
Enhancements:
- Iterator parser bugfixes, a DateTime fix, and Solaris support.

KSendfile is a native SAFT client. Compared to the Bitnet up to now there was no asynchronous file transfer service defined in the Internet. The existing standard file transfer, the ftp, is a synchronous service: an interactive login on both ends of the file transfer is mandatory for the user to set up a connection between both points.
If a user A wants to send a file to user B they have the following choices:
- ftp to a recipients account B
In this case one has to know the password of the recipients account. If A and B are not the identical person, severe questions of security arise and it is not the method of choice. Even if account A and B belong to the same person, the typed ASCII password characters for ftp access will travel open (readable) as ordinary TCP packets through the network.
- ftp using an anonymous ftp server
The file has to be uploaded by A onto the anonymous ftp server using an ftp session. After that A has to notify B about this using e-mail informing this user about the fact that the file is ready for download now. B can get the file now by doing another ftp transfer. This procedures requires a common reachable ftp server, with an upload (write access) facility. During the time the file resides on the anonymous ftp server it is open to anyone, it may be readable, writeable, changeable or erasable.
- sending a file via e-mail
A is sending a file to B enclosed into an e-mail. According to RFC 822 a mail must contain characters from the NVT-ASCII character set, which is a subset of the 7 bit ASCII character set. The file transfer via e-mail is limited to English text documents or the text to be sent must be encoded properly, of course using the NVT-ASCII character set. Encoding procedures like uuencode or MIME are available. It is not a pleasure to use either of them, they dont support all file ownership attributes and they will enlarge the amount of data to be transferred by encoding. In addition to this most of the existing MTAs are not designed to handle large amount of data transfers.
To avoid all the described disadvantages the SAFT-protocol (Simple Asynchronous File Transfer) has been developed and the sendfile software has been created as a reference implementation for UNIX platforms.
Enhancements:
- Fixed a bug in ksendfilenetclient::sendFile when getting status code 531
- Added Resend Function
- Fixed bug in ksendfilenetclient::sendfile in the date function
- Now sends the file date, not the actual system date.