[cobalt-users] Help! raq3 catch all mailbox

[Dan Bakstad <dbakstad@xxxxxxx>]

Dear cobalt users,

Any help on this topic would be appreciated.  We've looked at
probably a hundred posts on this subject for raq2, but can't seem to get
there.  We don't know if there is possibly something different
required on the raq3.

We have just installed a raq3, and have an ip based domain (not switched
with Internic yet, testing with ip number).  This client requires
email addressed to a user without a mailbox or alias to be forwarded to
his isp account.  So we have set up a user (savela), with forwarding
to this isp account.  There are several other users also set up for
this domain.  We are testing the email using sendmail from a simple
form installed under this account on the raq.  The majority opinion
in the posts is to add an alias to the user which is to become the
catch-all mailbox - using
"@www.domainname"
as the alias.

In our testing before setting up this alias, test email to each mailbox
works fine.  Test email to mailboxes which have forwarding to
another email address works.  Test email to users which have
multiple forwarding addresses works (we had to update the /etc/aliases
file per posts and all worked fine, seems like they should have put that
in the GUI).  The user which will be the catch all (savela) has his
mail forwarded to an isp account, and that works fine. 
Problem:  when
"@www.savela.com"
or "@savela.com" is set up as an alias, ALL mail goes to
savela, and to no one else.  So, although the catch-all is working,
email to other users is not delivered to their mailboxes, only to the
catch all savela.

We have not manually updated the virtusertable.  Although some posts
contained instructions on how to update the virtusertable, we have not
done so.  There were differing instructions on when/how to run
"make"?, and since we are newbies, were hesistant to get
outside the browser interface in an area that we are not
knowledgeable.  We updated the aliases table to handle forwarding to
multiple email addresses for other users.

Currently an alias of 
"@www.savela.com" 
is set up for user "savela", and pasted below are what we think
are the relevant lines created in the virtusertable and aliases
files.  At this point, email sent to any address at this domain is
delivered only to my isp account (last line in the aliases file).

/etc/virtusertable

# This file is automatically generated
# Please put custom changes at the end
# Cobalt Networks 1998

info@xxxxxxxxxxxxxx     infosavela
majordomo-owner@xxxxxxxxxxxxxx  majordomo_site5-owner
owner-majordomo@xxxxxxxxxxxxxx  owner-majordomo_site5
resumes@xxxxxxxxxxxxxx  resumesavela
majordomo@xxxxxxxxxxxxxx        majordomo_site5
@www.savela.com savela

# accept-email-at-domain routes
@savela.com     %1@www.savela.com
# Put custom additions below (Do not change/remove this line).

/etc/aliases

#
#       @(#)aliases     8.2 (Berkeley) 3/5/94
#
#  Aliases in this file will NOT be expanded in the header from
#  Mail, but WILL be visible over networks or from /bin/mail.
#
#       >>>>>>>>>>      The program "newaliases" must be run after
#       >> NOTE >>      this file is updated for any changes to
#       >>>>>>>>>>      show through to sendmail.
#

# Basic system aliases -- these MUST be present.
MAILER-DAEMON:  postmaster
postmaster:     root

# General redirections for pseudo accounts.

(cut out a bunch of root redirection stuff here)

thamilton:      abc@xxxxxxxxxxxxxxxx
infosavela:     xyz@xxxxxxxxxxxxxxxx, abc@xxxxxxxxxxxxxxxx
resumesavela:   xyz@xxxxxxxxxxxxxxxx, abc@xxxxxxxxxxxxxxxx
savela: dbakstad@xxxxxxxxxxxxx

Thanks in advance if anyone can get us going in the right
direction.
Dan Bakstad