On 2/20/06, Erik Espinoza <[EMAIL PROTECTED]> wrote:
>

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 "&my@domain.com" > .qmail-admin' in /var/qmail/alias

what about ownership of these files? and file permissions?

also, if the system is generating  mail to an alias and I have not created .qmail-  file for it...what happens to it? Can I create a catchall for aliases?

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.

Hmmm...didnd't notice that in process lists ;-( must become more observant!
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 ;)

No. that was not my point. I had heard about this project in various mailing lists, much before I actually joined.

My point actually was the time lag between the source rpm of smapassasin & clam release and release of toaster rpms of the same. My assumption was that  if no major changes were added, the originals would be much faster acquired. However since you say that the  software  is patched to run under  daemontools...then my assumtion goes down the drain. I hope though that  the time lag would not be much ;-)

>  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'
Thanks for all the info.

With best regards.
Sanjay.

Reply via email to