| 1 |
Mixmaster for Debian
|
| 2 |
--------------------
|
| 3 |
|
| 4 |
Mixmaster is both a remailer client and a remailer server. The Debian package
|
| 5 |
supports both uses while client only is default.
|
| 6 |
|
| 7 |
More information on using Mixmaster is available in the Mixmaster FAQ
|
| 8 |
available at http://mixmaster.sourceforge.net/faq.shtml
|
| 9 |
|
| 10 |
|
| 11 |
Notes for clients and remailers
|
| 12 |
===============================
|
| 13 |
|
| 14 |
It is absolutely imperative that you have current stats before attempting any
|
| 15 |
use of the remailer network. The Debian package for Mixmaster has a tool to
|
| 16 |
update stats and keyrings from pingers (individuals who collect keys and stats
|
| 17 |
and publish them for use by others).
|
| 18 |
|
| 19 |
This tool, mixmaster-update, has a few built-in stats sources. It is possible
|
| 20 |
that they are all obsolete by the time you make use of this package. In that
|
| 21 |
case configure /etc/mixmaster/update.conf and specify URLs to keyrings and
|
| 22 |
stats yourself.
|
| 23 |
|
| 24 |
mixmaster-update is usually run from cron or ip-up (you get asked by debconf).
|
| 25 |
If you did specify you want to do it manually please make sure you run it as
|
| 26 |
the remailer user (su mixmaster -c "mixmaster-update").
|
| 27 |
|
| 28 |
Both mixmaster and mixmaster-update also support user configuration besides
|
| 29 |
system-wide configuration. This is usually stored in ~/.Mix
|
| 30 |
|
| 31 |
Debian's mixmaster package is built without Nym support as that is not
|
| 32 |
considered usable by the package maintainers and upstream.
|
| 33 |
|
| 34 |
Integration with Mail User Agents
|
| 35 |
---------------------------------
|
| 36 |
|
| 37 |
Mutt on Debian is compiled with mixmaster support. You probably want to set
|
| 38 |
mixmaster = "/usr/bin/mixmaster-filter -m -S". The script mixmaster-filter
|
| 39 |
makes sure your From: header line (and other lines, consult the manual page)
|
| 40 |
are not passed on to Mixmaster. Mutt does set it! "-m" instructs Mixmaster
|
| 41 |
to read a mail message from stdin while "-S" tells it to send out the entire
|
| 42 |
pool immediatly - if you don't use it you will collect your mail in ~/.Mix/
|
| 43 |
without ever sending them (of course you may choose to run mixmaster -S at a
|
| 44 |
later time too).
|
| 45 |
|
| 46 |
[if _Your_ mail user agent also has mixmaster support, please let me know
|
| 47 |
by filing a wishlist bug on the package - PP]
|
| 48 |
|
| 49 |
Using user specific stats rather than system wide stats
|
| 50 |
-------------------------------------------------------
|
| 51 |
|
| 52 |
By default Debian's mixmaster package uses the stats and keyrings in
|
| 53 |
/var/lib/mixmaster/used-stats. They are updated by cron, in ppp-up, or
|
| 54 |
manually as configured by the system administrator.
|
| 55 |
|
| 56 |
In order to use your own stats as a user place pubring.mix, mlist.txt and
|
| 57 |
type2.list in your ~/.Mix/ directory, and add PUBRING, TYPE2REL, and TYPE2LIST
|
| 58 |
to your ~/.Mix/mix.cfg file like this:
|
| 59 |
|
| 60 |
PUBRING pubring.mix
|
| 61 |
TYPE2REL mlist.txt
|
| 62 |
TYPE2LIST type2.list
|
| 63 |
|
| 64 |
Note that type2.list is optional, but if it is there it may have a bad
|
| 65 |
influence if it does not match your mlist.txt file. Be aware that if you
|
| 66 |
don't override the global config in your local mix.cfg file the global
|
| 67 |
setting from /etc/mixmaster/client.conf will be used. Setting it in your
|
| 68 |
mix.cfg as given above and not having the file should work tho.
|
| 69 |
|
| 70 |
|
| 71 |
Notes for Mixmaster in remailer mode
|
| 72 |
====================================
|
| 73 |
|
| 74 |
You can configure mixmaster for remailer mode in
|
| 75 |
/etc/mixmaster/remailer.conf and start the daemon using the init script in
|
| 76 |
/etc/init.d. Note that mixmaster does not listen on the network, it
|
| 77 |
just processes its mail from the mailspool.
|
| 78 |
|
| 79 |
Make sure mail to your remailer address reaches mixmaster. The Mixmaster
|
| 80 |
daemon reads /var/mail/mixmaster regularly and processes its mail removing
|
| 81 |
old mails.
|
| 82 |
|
| 83 |
If you receive mail directly at this host this is probably very straight
|
| 84 |
forward. You can change the location where mixmaster should search for
|
| 85 |
new mail by setting MAILIN in /etc/mixmaster/remailer.conf. It may either
|
| 86 |
be a mbox file or a Maildir folder (with / at the end of the directory
|
| 87 |
name)
|
| 88 |
|
| 89 |
If you want to query a pop3 server for mails you can either use fetchmail or
|
| 90 |
similar or configure mixmaster to pop the mails. See
|
| 91 |
/etc/mixmaster/remailer/pop3.cfg and the mixmaster(1) manual page.
|
| 92 |
|
| 93 |
|
| 94 |
You should probably subscribe to the Remailer Operators' Mailinglist.
|
| 95 |
Subscription instructions and the archive can be found at
|
| 96 |
<URL:http://lists.mixmin.net/mailman/listinfo/remops>.
|
| 97 |
|
| 98 |
Once you are happy with everything make sure your remailer gets known by
|
| 99 |
announcing it to news:alt.privacy.anon-server and the Remailer Operators'
|
| 100 |
mailinglist.
|
| 101 |
|
| 102 |
You can also ask fellow Remailer Operators to give it a test run before
|
| 103 |
announcing it to the public on this list.
|
| 104 |
|
| 105 |
You may also want to disable your Mail Transfer Agent's logging so that there is
|
| 106 |
no trace of who used your remailer.
|
| 107 |
|
| 108 |
Please make sure you have your network operator's consent before you start a
|
| 109 |
remailer and that you handle abuse complaints in a timely and proper fashion.
|
| 110 |
|
| 111 |
|
| 112 |
-- Peter Palfrader <weasel@debian.org> and
|
| 113 |
-- Colin Tuckley <colint@debian.org> Wed, 21 Nov 2007 20:04:55 +0000
|
Parent Directory
| 
Revision Log