This topic is to discuss the documentation of toaster.conf and toaster-watcher.conf.
Now that Matt has given me moderator powers in this forum (insert obligatory evil laugh here) I'm moving things around a bit -- this topic will be for discussion of the docs, questions and answers, suggestions, etc. The docs themselves will be in other topics.
toaster.conf
http://www.tnpi.biz/support/phpBB/viewtopic.php?t=80toaster-watcher.conf
http://www.tnpi.biz/support/phpBB/viewtopic.php?t=81
Matt answered a few of my questions be email, and I've edited the docs to include his answers.
davidcl |
...snip...that's my first pass at explaining the toaster.conf file. Any comments or suggestions will be appreciated.
|
*F*a*n*t*a*s*t*i*c* JOB DAVID!!!!
As a matter of fact, I'd hope that matt puts a pointer to YOUR messages in
Sooner, rather than later...
Great job...
(and I'll have stuff from my OPENBSD version too,[eventually] I hope...)
MarkB
Question:
line 2 server_country (should sample # be # 01 (US country code)
Line 3: Where is toaster_pkg_site called from, and is it actually just
the web site of OS Location?
**in other words, it appears that this and os_release could together be the key used to ftp specific packages from for downloading when needed.
ie: can you safely say :
toaster_pkg_site =
ftp://openbsd.secsup.org/pub/openbsd ??
toaster_os_release = 3.4 ??
...snip...
The version of FreeBSD should be expressed in the form of a tag name. Possible options are:
- 4-stable
- 5-stable
- 5-current
- RELENG_4_9
[/list:u]
[Is this correct?]
Sounds Just like OpenBsd which has
3.1
3.2
3.4
[/list:u]
and which actually controls your download process too!
Well, on FreeBSD you update the local copy of your ports tree using a tool called cvsup. I'm pretty sure both of those are used as parameters to cvsup, to tell it which cvsup server to contact and which tag name to use when checking out updates.
You might save yourself a lot of pain by looking at what software is being installed by toaster_setup.pl and installing it manually the OpenBSD way.
For those awaiting them, I'm hoping to post the rest of the first-attempt toaster_watcher.pl docs very soon.
(Okay, I edited this, because the original date I promised didn't happen!)
On the line
admin_home= /usr/home # where you store home directories
Are we talking a bout the normal home dirctory where we store websites? or is this a whole other home?
Randy Jordan
davidcl |
####################################### TOASTER######################################cvsup_server_preferred = fastest # fastest or a hostnamecvsup_server_country = UStoaster_pkg_site = ftp://ftp.freebsd.orgtoaster_os_release = 4-stabletoaster_dl_site = http://www.tnpi.biz # select a mirrortoaster_dl_url = /internet/mail/toaster
This section contains settings about where the various componenents in the toaster should be downloaded from. In most cases, the only things you're likely to change are your country, and the version of FreeBSD you are using.
|
admin_home= /usr/home # where you store home directories
Are we talking a bout the normal home dirctory where we store websites? or is this a whole other home?
Randy Jordan
Anonymous |
admin_home= /usr/home # where you store home directories
Are we talking a bout the normal home dirctory where we store websites? or is this a whole other home?
Randy Jordan
|
Under unix-like operating systems, every user has a home directory somewhere on the system. Although a user's home directory can be set to be any directory on the system, it's usual that they be collected in a single place, usually /usr/home. The primary website on a FreeBSD box is usually stored in /usr/local/www/data.
If you're doing virtual web hosting on your mail server, you might have any number of arrangements for home directories and website roots, so I can't easily guess where your home directories are. But home directories are not the same as website root directories.
I've made significant updates to the already-posted sections of the docs. In particular, I figured out how Matt's mailadmin script works and filled in the blanks in the docs for the Mail::Toaster::Admin section of toaster.conf.
The remaining documentation will be done very soon.
The current version of the toaster (3.35) now includes these docs. If you've installed Toaster 3.35 on your machine, you can view docs for the conf files by typing
perldoc toaster.conf
or
perldoc toaster-watcher.conf
Currently the docs here in the forum are somewhat more complete than the ones distributed with the toaster, but we'll try to fix that by the next release.
Because You're GREAT!
Thank you for this excellent documentation!
Peter Brenzy
purplecat.net
While David is finishing up working down the toaster-watcher.conf sections, I thought I would go ahead and paste in a clip I dug out of the mail list archives from
Matt:http://www.tnpi.biz/cgi-bin/ezmlm.cgi/3/6139Quote: |
####################################### # Maildir Old Message Cleanup # #######################################
maildir clean interval = 7 # days between cleanup runs maildir clean Read = 0 # remove read messages maildir clean Unread = 0 # remove unread messages (days) maildir clean Sent = 90 # sent messages over x days are removed maildir clean Trash = 14 # trashed messages over x days are removed maildir clean Spam = 14 # spam messages over x days are removed
maildir clean Spam learn = 1 # feed spam through sa-learn (SpamAssassin) maildir clean Read learn = 1 # feed ham through sa-learn (SpamAssassin) maildir clean Read learn days = 0 # only learn from messages older than x days
maildir clean is a function of toaster watcher. You can think of it as the master switch for all the message cleanup options. If that's set, it'll create a log in /var/log/mail and maintain a brief log it's activity. The way toaster-watcher.pl cleans messages is roughly as follows:
Get a list of domains
Then, for each domain, we get a list of users. Then, one mailbox at a time, we peruse through each mailbox looking for messages that match the settings in the config file. When we find matching messages, we deal with them accordingly. For example, with the default settings, if we find any messages in the Spam folder that are more than 14 days old, we'll feed those messages through sa-learn and then delete them.
The same goes for Ham messages in the Read folder.
For each user of each domain, we check through their read messages and feed the ones older than 0 days through sa-learn teaching it that they are ham. If you only want messages older than a few days to be learned as ham (giving users a chance to move any missed spam from their read box to Spam) then bump up maildir clean Read learn days.
Make sense?
Matt
|
Today, made extensive changes to the qmail-smtpd portion of toaster-watcher.conf, including an explanation of RWLs, and an explanation of the smtpd memory settings.
Okay, completed first draft of toaster-watcher.conf docs.
As always, please post any comments, suggestions, changes.
http://www.tnpi.biz/support/phpBB/viewtopic.php?t=81
Just to make I configured my toaster.conf and toaster-watcher.conf
properly:
The host name of the machine is tomq.
My internet domain is: atoyf.com
My internal IP is 192.168.0.5
FQDN: tomq.atoyf.com
When I sent/receive my emails they came in such format (before the toaster upgrade, now they don't come hehehe):
mail@atoyf.comNow:
Toaster.conf:
admin_adminhost = tomq.atoyf.com # the "master" server in
a cluster
admin_fileservers = tomq.atoyf.com # all file servers in
this array
admin_mailservers = tomq.atoyf.com
toaster-watcher.conf:
toaster_hostname = tomq.atoyf.com
Thank you much for your help and tips and just a FYI - I'm just a student and not a multi-million dollar company... Best Regards, Anton
Anton,
The settings you posted look just fine. However, none of those settings has a damn thing to do with your ability to receive mail.
Just a quick note on the config file docs.
Now that the initial revision of the docs are done, available on the web, and distributed with the toaster, Matt and I have both been making patches to the docs when Matt releases a new version of the toaster. Although the docs will probably lag the config files by a version or too, you can assume that the docs distributed with the toaster are reasonably complete.
Last night, for example, I sent Matt a bunch of changes to the docs. Now every config option available in 3.38 is included. These docs are live on
http://www.tnpi.biz now, and will be included with the next distribution of the Toaster tarball.