Free macintosh inn software for linux

Slackintosh is a port of Slackware GNU/Linux to PPC (Macintosh).

Russell Kroll was the first person who ported Slackware to PPC (http://slackintosh.exploits.org), but the project stalled with an unfinished 9.1 ..

I (Adrian) started again from scratch porting 10.1 to PPC, and ive stolen the name Slackintosh...

Please note that this port was not done by Russell, dont send him Bugreports.

I used the the Sources + SlackBuild files from Slackware 10.1. ..but i had to make a few changes:

The new Binutils from 10.x didnt like GCC, i used the 9.1 Version to build everything. The Installer uses BusyBox 1.0 and Linux 2.4 is not included, only 2.6.11.5 (Runs better on PPC .. imho)

Its not finished: Not all packages are ported. Youll get gcc, X, Mozilla, XFCE, Gimp.. but no
monsters like KDE & Co.

The installer maybe somewhat funky.. Missing packages are still listed and the yaboot installation isnt tested very well...

..but you should be able to get it running. It won the WFM (WorksForMe) price. (Tested on a MiniMac & iBook2)

AMaViS-ng is a modular rewrite of amavisd and amavis-perl. It scans email for malicious code inside attachments and archive files, stopping delivery if malicious code is found.

Most people will say: "A virus scanner? For UN*X? Why? Viruses do not work in a UNIX environment." On the first glance they are right (even if there are at least two viruses which run under Linux - well, actually they are Trojan Horses)

On the second view though, imagine a heterogene network environment where can exist UNIX and Windows systems.Now think of an UN*X server that serves Windows and/or Macintosh workstations via a POP3 service. Would it not be nice to ensure attachments coming via email are scanned for viruses before they reach a system they are able to infect? Well - that is what this package is for. It resides on the server that handles your incoming mails. When a mail arrives, instead of being delivered via procmail directly, is parsed through a script that extracts all attachments from the mail, unpacks (if needed) and scannes them using a professional virus scanner program.

ngbatch project is a newsgroup/rmgroups batcher for INN.

SYNOPSIS

< ngbatch -n > < group > [ < flag > [ < creator > ] ]

< ngbatch -r > < group >

< ngbatch -e > [ < -D > ] [ < -w > < days > ] [ < -h > < days > ]

This program executes newgroup and rmgroup controls in a delayed way, to help against newgroup/rmgroup wars. The idea is that (a) rmgroups are remembered for some time, and (b) rmgroups get priority over newgroups, so that a newgroup will be ignored if a rmgroup for this group (from a trusted issuer) has already arrived. A newgroup is executed only after a wait period, in case it gets rmgrouped soon.

Each newgroup/rmgroup control message is written into a batch file. A cron job collects commands from this batch file and executes only those newgroups for which no rmgroup was received.

Setting Up

Change your control scripts for newgroup and rmgroup so that they call B< ngbatch > with the appropriate parameters instead of B< ctlinnd > (you probably should make that depend on hierarchies). Make sure that only trusted rmgroupers are active in the I< control.ctl > file.

Run < ngbatch -e > periodically from crontab.

OPTIONS

< -n > < group > [ < flag > [ < creator > ] ]

Batch up a newgroup control for < group >. < flag > defaults to "y", < creator > defaults to nothing.

< -r > < group >

Batch up and execute a rmgroup control for < group >.

< -e >

Execute a batch run: for all batched newgroup commands, check if the wait time has elapsed. If yes, execute the newgroup command only if no rmgroup for the same group was batched. Rewrite the batch file with the commands still to be remembered.

< -D >

Show the commands on standard output instead of executing < ctlinnd >.

< -w> < days >

Set the newgroup wait time to < days > (default 3).

< -h > < days >

Set the rmgroup remember time to < days > (default 30).

infobot is an IRC bot written in Perl 5 which implements a sort of artificial intelligence by learning information ("factoids") from channel discussions and then responding intelligently to queries about this accumulated information.

In the beginning, we had to type URLs out, or, at best, wade through a set of hierarchic bookmarks for a URL. But what about when you dont know what youre looking for? If you just want to name it, and find out where it is? (Of course, archie has done this for years.)

What makes infobots different from a lycos or a set of bookmarks is that he learns by observing, and that you can query him in intuitive ways.

Internet Relay Chat is a set of client and server which use a protocol. People get on and chat in near-real-time; rather than wait for your netnews replies, you can ask a question and get ignored or answered while you wait.

Url has been sitting on the EFNet channel #macintosh, where hes picked up quite a few factoids from the local community*.

Url, purl, and rurl are perl scripts that once ran under sirc. In fact, it would also run under MacPerl and my barebones port of MacSirc. However, I ended up writing a little irc front-end for it of my own because sirc would hang (rather than, say, crash gracefully).

Directory Synchronize is the small handy utility you always missed! Directory Synchronize is small, reliable, and fast. And best of all - it is Open Source; released under the GPL you are free to use and distribute it.
Directory Synchronize synchronizes the contents of one directory to another. That means you can use it to backup your data on a regular basis to another computer or another harddrive.
Or you can use Directory Synchronize to synchronize the data on your laptop with the data on your desktop.
Programmed in real platform independent Java you can use Directory Synchronize on nearly every computer platform including Windows, Linux and Macintosh.
Use the Directory Synchronize GUI for starting, pausing and stopping a synchronization.
Or use the GUI to easily create and store a configuration and use the command line to automatically start it every time you boot up your computer.
Enhancements:
- Some bugs have been solved.
- If a file can not be accessed, only a warning is issued instead of issuing a critical error and halting synchronization.
- If you select a directory instead of a file as a log for a directory definition, a line-separator was added instead of a file-separator.
- Some NullPointerExceptions in console mode have been fixed.
- The " " wildcard can be used for the path of the global log, and the " " wildcard can be used for the name of the current directory definition in the directory definition log filename.

The OSSP lmtp2nntp program is an LMTP service for use in conjunction with a Mail Transfer Agent (MTA) like Sendmail or Postfix, providing a reliable real-time mail to news gateway.

Input messages get their headers slightly reformatted to match Usenet news article format. The article is then posted or feeded into a remote NNTP service (like INN). Delivery must take place immediately or the transaction fails.

OSSP lmtp2nntp relies on the queueing capabilities of the MTA in order to provide a fully reliable service. For this the program returns proper delivery status notification which indicates successful completed action, persistent transient failure or permanent failure.

Convert::BinHex can extract data from Macintosh BinHex files.

ALPHA WARNING: this code is currently in its Alpha release. Things may change drastically until the interface is hammered out: if you have suggestions or objections, please speak up now!

SYNOPSIS

Simple functions:

use Convert::BinHex qw(binhex_crc macbinary_crc);

# Compute HQX7-style CRC for data, pumping in old CRC if desired:
$crc = binhex_crc($data, $crc);

# Compute the MacBinary-II-style CRC for the data:
$crc = macbinary_crc($data, $crc);

Hex to bin, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Hex2Bin") which keeps internal conversion state:
# Create and use a "translator" object:
my $H2B = Convert::BinHex->hex2bin; # get a converter object
while (< STDIN >) {
print $STDOUT $H2B->next($_); # convert some more input
}
print $STDOUT $H2B->done; # no more input: finish up

Hex to bin, OO interface. The following operations must be done in the order shown!
# Read data in piecemeal:
$HQX = Convert::BinHex->open(FH=>*STDIN) || die "open: $!";
$HQX->read_header; # read header info
@data = $HQX->read_data; # read in all the data
@rsrc = $HQX->read_resource; # read in all the resource

Bin to hex, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Bin2Hex") which keeps internal conversion state:
# Create and use a "translator" object:
my $B2H = Convert::BinHex->bin2hex; # get a converter object
while (< STDIN >) {
print $STDOUT $B2H->next($_); # convert some more input
}
print $STDOUT $B2H->done; # no more input: finish up

Bin to hex, file interface. Yes, you can convert to BinHex as well as from it!
# Create new, empty object:
my $HQX = Convert::BinHex->new;

# Set header attributes:
$HQX->filename("logo.gif");
$HQX->type("GIFA");
$HQX->creator("CNVS");

# Give it the data and resource forks (either can be absent):
$HQX->data(Path => "/path/to/data"); # here, data is on disk
$HQX->resource(Data => $resourcefork); # here, resource is in core

# Output as a BinHex stream, complete with leading comment:
$HQX->encode(*STDOUT);

PLANNED!!!! Bin to hex, "CAP" interface. Thanks to Ken Lunde for suggesting this.
# Create new, empty object from CAP tree:
my $HQX = Convert::BinHex->from_cap("/path/to/root/file");
$HQX->encode(*STDOUT);

BinHex is a format used by Macintosh for transporting Mac files safely through electronic mail, as short-lined, 7-bit, semi-compressed data streams. Ths module provides a means of converting those data streams back into into binary data.

Dabo is a three-tier, cross-platform database application development framework, written in Python with the wxPython GUI toolkit.
Dabos authors, Ed Leafe and Paul McNett, have strong backgrounds in database application development using the awesome and underrated Microsoft Visual FoxPro development environment.
While Visual FoxPro shines at developing data-centric applications, it has one limitation that cannot be ignored: it only runs on Microsoft Windows, and Ed and Paul both have clients that want their applications to run on Linux and Macintosh. We are sure we are not alone in this regard: it is a multi-platform world with more diverse needs than one vendor can fulfill.
Ed and Paul got to talking one day: Paul had been researching various multiplatform GUI toolkits for about 18 months, and Ed has lots of experience developing the Visual FoxPro Codebook framework. We decided to work together to make a framework for developing robust data-centric applications for multi-platform deployment. Weve come up with a design that is simple, flexible, and robust, and weve begun developing our own client applications using the Dabo framework.
Dabo is not complete, but is very capable now for many needs.
Currently, Dabo only supports MySQL and Firebird backends (with PostgreSQL almost done), but in the near future it will support all databases that have drivers that conform to the Python dbapi. These databases include:
- MySQL (already supported)
- PostgreSQL(already supported)
- Firebird (already supported)
- Oracle
- DB2
- MS-SQL and MSDE
- Sybase
- PySQLite
- Berkeley DB