[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] E-mail setup / catch-all address
- Subject: Re: [cobalt-users] E-mail setup / catch-all address
- From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
- Date: Mon May 21 13:32:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
"Gregory Ogorek" <greg@xxxxxxxxxxxxxx> wrote:
> >I'm still lost when it comes to the assignment of site e-mail aliases (or
> >forwarding addresses). Let's say I have a domain xyz.com, and require
the
> >following e-mail aliases (e-mail@domain -> forwarding address):
>
> >[1] clinton@xxxxxxx -> bill@xxxxxxxxxxx
> >[2] bush@xxxxxxx -> george@xxxxxxxxxxx
> >[3] staff@xxxxxxx -> bill@xxxxxxxxxxx, george@xxxxxxxxxxx
> >[4] ...@xxxxxxx -> bill@xxxxxxxxxxx (catch-all account)
>
<snip>
> 3. Create a list by clickin on the "List Management" button on the left
side
> of your Site Managment interface. Click "Add Mailing List". Enter a List
> Name and Password. The blue question mark icons to the left of each item
> can give you details if you look to the bottom of your browser. The List
> Name would be staff (without the @xyz.com). Enter bill and george in the
> External Recipients window. One per line.
</snip>
Greg was correct on 1,2 and 4. His solution for 3 will work, but unless you
need a GUI solution, setting up a mailing list will cause additional
overhead on the server, is overkill and may lead to behavior you don't
want - like messages with certain administrative keywords getting bounced to
the list admin. There are several solutions that do not involve the GUI or
mailing lists. The solution I prefer is to create a record in sendmail's
virtusertable file pointing staff@xxxxxxx to a dummy username as follows:
staff@xxxxxxx staff_xyzcom
Then in sendmail's aliases file add a record:
staff_xyzcom: bill@xxxxxxxxxxx, george@xxxxxxxxxxx
Then run the following commands from the shell:
makemap hash /etc/virtusertable < /etc/virtuserable (substitute correct
location if your file is somewhere else)
newaliases
kill -HUP `head -1 /var/run/sendmail.pid`
Other solutions involve using a .forward file or a procmail recipe (powerful
solution, probably too advanced for a newbie, but hard to judge original
poster's skills). Just thought I'd mention alternatives. I generally use
the method I described for #3, but I rely heavily on procmail for spam
filter, compressed mail archiving, autoresponders, folder routing, etc.
--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/