| 20 |
REQUIREMENTS |
REQUIREMENTS |
| 21 |
------------ |
------------ |
| 22 |
in general: |
in general: |
| 23 |
|
XML::Parser |
| 24 |
|
XML::Dumper |
| 25 |
Digest::MD5 |
Digest::MD5 |
| 26 |
|
Mail::Internet |
| 27 |
for type1 pings |
for type1 pings |
| 28 |
GnuPG (1.0.7) |
GnuPG (1.0.7) |
| 29 |
GnuPG::Interface (0.33) |
GnuPG::Interface (0.33) |
| 30 |
for type2 pings |
for type2 pings |
| 31 |
a mixmaster installation - this requirement will be changed |
a mixmaster installation |
| 32 |
FIXME what else |
FIXME what else |
| 33 |
|
|
| 34 |
|
|
| 35 |
SETUP |
SETUP |
| 36 |
----- |
----- |
| 37 |
FIXME |
|
| 38 |
|
o Create a new unix user named »pinger« (You can actually use any name you wish |
| 39 |
|
but I will refer to the user as pinger in this document). |
| 40 |
|
|
| 41 |
|
o Make sure you have the perl libraries mentioned above and GnuPG installed |
| 42 |
|
properly. |
| 43 |
|
|
| 44 |
|
o Create a mixmaster client installation in ~pinger/Mix |
| 45 |
|
echolot needs to have its own installation because it will mess with mix' |
| 46 |
|
mlist.txt file, the public mixmaster keyring, and type2.list. |
| 47 |
|
Don't bother putting current keyrings there. |
| 48 |
|
|
| 49 |
|
o Check the homedir setting pingd.conf |
| 50 |
|
|
| 51 |
|
o Set my_localpart and my_domain in pingd.conf to the appropriate values |
| 52 |
|
for your pinger. Mail to my_localpart@my_domain needs to reach echolot. |
| 53 |
|
|
| 54 |
|
o Make sure your MTA supports user defined mailboxes. so that |
| 55 |
|
my_localpart+anything@my_domain also reaches echolot. |
| 56 |
|
^^^^^^^^^ |
| 57 |
|
If you use another character instead or + to indicate a user defined |
| 58 |
|
extension set recipient_delimiter accordingly in pingd.conf. |
| 59 |
|
|
| 60 |
|
o Mail should be delivered to /home/pinger/mail which must be a Maildir mailbox, i.e |
| 61 |
|
there are 3 directories: /home/pinger/mail/tmp, /home/pinger/mail/cur and |
| 62 |
|
/home/pinger/mail/new. Qmail, postfix and procmail can do this. |
| 63 |
|
|
| 64 |
|
Example snipped for procmail: |
| 65 |
|
|
| 66 |
|
:0 |
| 67 |
|
$HOME/mail/ |
| 68 |
|
|
| 69 |
|
(the trailing slash is important!) |
| 70 |
|
|
| 71 |
|
|
| 72 |
|
o run »./pingd --verbose« start |
| 73 |
|
|
| 74 |
|
o run »./pingd add <address> <address> <address>..« in another terminal |
| 75 |
|
look at the first terminal where you started pingd. It should print |
| 76 |
|
something about adding addresses. |
| 77 |
|
|
| 78 |
|
o run »./pingd getkeyconfs« to request new remailer-key and remailer-conf |
| 79 |
|
immediatly. |
| 80 |
|
|
| 81 |
|
o pingd can be stopped with |
| 82 |
|
»./pingd stop« or with Ctrl+C on the terminal where it runs. |
| 83 |
|
|
| 84 |
|
When everything works you may start pingd with |
| 85 |
|
|
| 86 |
|
o »./pingd --detach --verbose start« |
| 87 |
|
|
| 88 |
|
o You can tail the output file to get the debugging output: |
| 89 |
|
»tail -f output« |
| 90 |
|
|
| 91 |
|
|
| 92 |
|
|
| 93 |
|
CONFIGURATION |
| 94 |
|
------------- |
| 95 |
|
|
| 96 |
|
Run »./pingd dumpconf« to see a list of all available configuration options. |
| 97 |
|
You may add them to the pingd.conf file. After changing that file you need to |
| 98 |
|
restart pingd. |
| 99 |
|
|
| 100 |
|
|
| 101 |
|
|
| 102 |
|
Please report bugs and feature requests to Peter Palfrader |
| 103 |
|
<peter@palfrader.org>. |
| 104 |
|
|