liberal liberate libertine liberace

In order to add a server to an existing qmail installation -- do the following:

1) add the appropriate line into the /var/qmail/users/assign file
2) run qmail-newu to build the cdb file
3) update /var/qmail/control/rcpthosts (or maybe morercpthosts)
4) update /var/qmail/control/virtualdomains

Of course, your vpopmail UID and GID 's must be the same in both systems

Levels: Emerg Alert Crit err warning notice info debug

Facilities: kern user (default) mail daemon auth lpr news uucp cron local0 local1 local2 ... local7

Bayes needs perl module: DB_File:

1) Berkeley DB must be installed -- it installs in BerkeleyDB.x.x in /usr/local
2) when compiling DB_File -- you must edit config.in and enter the version of Berkeley you're using for LIBS and INC.
3) perl Makefile.PL ; make ; make install
4) for Bayesian filter, a directory called Bayesian includes process.pm needs to be in the @INC path of perl -- I put it in /usr/local/bin/Bayespam and did a ln -s to /usr/local/lib/perl5/site_perl (or something similar)

5) create the database:
bayes_process_email.pl \\
--good /export/home/vpopmail/domains/graves.com/dgraves/Maildir/cur \\
--spam /export/home/vpopmail/domains/graves.com/dgraves/Maildir/.spam/cur \\
-o /export/home/dgraves/bayes_rating.db

6) edit and install the .qmail file for whatever mailbox you want this to work on

® alt 0174
© alt 0169
™ alt 0153

pkginfo will give info on an installed package
pkgchk -l will give info on the installed pieces of a package

ipfilter --
allow in tcp/udp from any to any port = 22 keep state flags S allows a syn in, and everything else in that session, even with a
block quick in all
block quick out all right behind it.

In theory there is no difference between practice and theory but in practice there is.

isainfo -v will tell you which your architecture is

dnsq by default does not request a recursive query -- so it's only good for testing authoritative servers -- just an fyi

What a cool program

Copying directory foo and its contents from here to there :

rsync -avz /dir/foo remote:/dir/bar < -- you end up with a directory /dir/bar/foo

rsync -avz /dir/foo/ remote:/dir/bar < -- you end up with foo's files in /dir/bar

to use ssh as transport: export RSYNC_RSH=/path/to/ssh