"catch-all" ain't workin'

"catch-all" ain't workin'

Posted by: microcars
Posted on: 2004-09-18 20:42:00

since "*" became "catch-all" it doesn't seem to work on at least one of my domains.

do I have to change "catch-all" back to "*" ?

I get like...zero spam with 5 domains, so I LIKE the catch-all or "*" email address function.

grrrr....

Re: "catch-all" ain't workin'

Posted by: torbie
Posted on: 2004-09-19 10:00:00

Mine is not working either. The email and site issues over the past several weeks are really becoming troubling.

Dave - Torbie Arts Photography

Re: "catch-all" ain't workin'

Posted by: Mark
Posted on: 2004-09-19 10:22:00

I'm getting this too.

No wonder I haven't been receiving any mail recently.

<mark-web@example.com>:
66.33.205.124 does not like recipient.
Remote host said: 550 <mark-web@example.com>: User unknown
Giving up on 66.33.205.124.

I emailed support, but this is really not good. How long has it been broken? Did they not test this change at all?

Re: "catch-all" ain't workin'

Posted by: everinjoy
Posted on: 2004-09-19 12:00:00

One of mine doesn't work, too (or at least has a serious delay going on). :(

Re: "catch-all" ain't workin'

Posted by: fribhey
Posted on: 2004-09-20 10:23:00

are you using the new spam beta filter on the domain where the catch all is no longer working? if so then that might be why because it won't allow a catch all email account.

Re: "catch-all" ain't workin'

Posted by: microcars
Posted on: 2004-09-20 16:04:00

no, no spam beta filter being used and now my "catch-all" is mysteriously working again.

I'm sure I will find something else to whine and complain about soon though......;-)

Re: "catch-all" ain't workin'

Posted by: will
Posted on: 2004-09-20 16:28:00

This has been fixed as of yesterday evening. One of our backend machines didn't get updated with the CVS pushout, so there were some instances of domains not getting configured properly.