RE: [cobalt-users] Email query

["Robyn LeGris" <legris@xxxxxxx>]

Hi Ian,
I had the same problem and searched the archives and cobalt for on and off
for 3 days (God forbid I ask a question that has already been answered).
Cobalt had a fix, but it didn't work.
The problem with the archives is if you don't know the specific phrase that
was used for your problem you don't find the specific answer "everyone" on
the list says is there. For instance
catchall and catch-all and catch all, and what if you don't even know the
term "catch all". so I can understand your frustration, I feel it too!
After Jeff's very helpful post I finally found the patch file.  The link to
it is on
http://list.cobalt.com/pipermail/cobalt-users/2000-February/005005.html
which is the answer from tech support.  However the link was incorrect, it
should be:
ftp://ftp.cobaltnet.com/pub/users/duncan/raq3/raq3-catchall-2.patch.bz2
Also, this changes the install directions because the file name is
different.  They must have changed the patch file, since this post.

Is anyone else tired of wading through the Q posts in the digest? shouldn't
that topic be moved off list?

Sincerely
Robyn LeGris
http://1-choice.com



Message: 18
From: "1st Web Internet Services" <admin@xxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Subject: RE: [cobalt-users] Email query
Date: Fri, 3 Mar 2000 21:44:12 -0000
charset="iso-8859-1"
Reply-To: cobalt-users@xxxxxxxxxxxxxxx

Sure I realise that, but I thought that a 'catch all' would catch all those
emails that did not match any aliases already listed for that domain. So
mervyn and ian would be despatched, but tom would go to ian. And then if a
tom were to be added he would get his mail, which would no longer go to ian.

I will search the archives again, for if Fathi is correct it should be in
the recent months lists. (mind you the list includes a month for 2022!)

Ian.
Date: Fri, 03 Mar 2000 13:50:22 -0800
To: cobalt-users@xxxxxxxxxxxxxxx
From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
Subject: RE: [cobalt-users] Email query
Reply-To: cobalt-users@xxxxxxxxxxxxxxx

At 07:58 PM 3/3/00 +0000, you wrote:
>Thanks for nothing.
>
>I have looked through the archives, but I cannot find the answer. I always
>try to research the answers first,

This has been actively discussed starting February 15th, and a fix was
posted by a cobalt employee on February 16th.  I don't have a RaQ3, so I
didn't memorize the posts or mark them in any special way.

But I just found them again, in a matter of a few moments by searching my
archives looking for "RaQ3" and "catchall" in the BODY of the messages.

Here's what I found:

The first post, stating the problem:

2/15/00 01:24 PM -0500 Debbie Doerrlamm  [cobalt-users] catch all address

The first post addressing a definitive fix:

2/16/00 10:41 AM -0800 Duncan Laurie     [cobalt-users] raq3 catch-all
alias problems (& solution)

A followup post, explaining the errors in thinking in the first post, and
enumerating what Cobalt plans on doing for the fix:

2/16/00 10:13 PM -0800 Duncan Laurie     RE: [cobalt-users] raq3 catch-all
alias problems (& solution)

Browsing the archives of posts for the last month would have found the same
posts, I'm sure.

>but then I thought the idea of this list
>was to assist, or have I got it wrong?

Don't be so quick to brand me as nonhelpful.  You'll make some enemies that
way <wry grin>.

>You might know the answers, but many others do not. That is why we are on
>the list.

A bit of searching of the list is always a good idea first, especially
since this topic was so recently covered.

Certainly anyone else could have replied with specific answers.

>If anyone can assist me I would be grateful.

I think I just did.  If you can't find the posts now, let me know, and I'll
find them and forward them to you.

Jeff

--
Jeff Lasman <jblists@xxxxxxxxxxxxx>