>  Just installed my first qmailtoaster. Loved the install..now to operations
> ;-)

Glad you liked the install

>  1. I just assumed that the scripts added the default system mail
> users/aliases like root, postmaster etc. but it does not seem so. My toaster
> is working but I am not getting any system mail to root etc. Also, root with
> no domain name also does not reach. What needs to be done? and how do I add
> it to the scripts, so that it gets done automagically on my next servers?

In /var/qmail/alias there are a few .qmail files. These are the system
aliases. Simply point .qmail-root, .qmail-postmaster and
.qmail-mailer-daemon to whatever e-mail address you want. This is done
by 'echo "&[EMAIL PROTECTED]" > .qmail-root'. Remember to have the & and
be sure you do this for each alias. If you want to create more system
aliases, do so. For example if you have a local account called admin,
type 'echo "&[EMAIL PROTECTED]" > .qmail-admin' in /var/qmail/alias

>  2. Ran freshclam and it said it needs to be updated...Basically means that
> the toaster rpms are a bit behind the normal rpms of clam & spamassasin...at
> least these two are available as binary? Why not use the binaries directly &
> update them routinely with yum? What changes does the toaster does to the
> sources of these that we don't use the normal binaries? How does one get the
> toaster install keep up with anti-virus & anti-spam because at least the
> virus is a dangerous issue with people using Windoze as workstation & Spam
> is the biggest botheration...rest all features can wait. Please advise so I
> can think of how do I maintain my mail-servers.

Not all distributions that are supported by QmailToaster have
spamassassin and clam packages. In addition, those packages are not
configured to integrate properly with the qmailtoaster, IE run via the
supervise command.

The spamassasin is up to date, the new version of the clamav-toaster
is available at my site,
http://www.kabewm.com/pages/projects/qmailtoaster.php

I believe Nick hasn't had a chance to update the page, but this has
been widely used by others running the QmailToaster. Anyone on this
list will tell you that I am a contributor and a trustworthy source ;)

Just remember, the procedure for installing the new clamav is as follows:

# service qmail stop
# rpm -e clamav-toaster
# rpm -Uhv clamav-toaster-*.rpm
# freshclam
# service qmail start


>  3. Can someone please point me to a list of patches that go into the
> qmailtoaster.com install, so that I can compare it with other  installs like
> qmailrocks.org and any other.

Sure, type 'rpm -qi qmail-toaster'

>  4. I have never created source rpms. Though I have installed programs from
> source. I want to move from installing from source to creating a source rpm.
> I like this approach of qmailtoaster with qmail, so I want to start helping
> add features that I want, after I learn how. What are the best resources,
> other than rpm how-to. Any step by step tutorial would be most welcome. If
> someone has documented the way qmailtoaster is built, I would like to have
> that so that I can build a toaster for djbdns, if one does not exist (if I
> can) and if one does exist...the URL please ;-)

I can't help you with that. Most of my rpm knowledge comes from
opening up a few rpm's and looking at the examples on how things are
done. Occasionally I go to rpm.org for help with macros. As far as
building from source, you can always use checkinstall to register
programs you build from source in the rpm database.

>  With best regards.
>  Sanjay.
>
>

---------------------------------------------------------------------
     QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to