[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Catchall email
- Subject: RE: [cobalt-users] Catchall email
- From: Clive Harper <CHarper@xxxxxxxxxxxx>
- Date: Thu Jun 28 21:47:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Thanks Wouter (is that right?),
The catchall now works using the @www.domain.com address but I have
an even stranger problem it seems
I should say before I go into the problems that they seem to have got
worse since I have installed the last set of patches/kernel.
If I enter an Email Server Alias under Site Settings e.g. domain.com and try
sending mail to user@xxxxxxxxxx I get the message "config error: mail
loops back to me (MX problem?)".
If I go to Server Management -> Control Panel -> Email -> Email server
parameters the alias I just entered is not in the Host/Domain aliases list,
so if I add it manually and save changes then go back into Email server
parameters it is still not there.
The only way I can get domain.com to appear under Host/Domain Aliases is
to leave the Email Server Alias empty then add domain.com manually to the
Host/Domain Aliases list.
This means that I can sent/receive mail Ok but only for actual users, if
I try and send a mail to an Alias it gives the error "User unknown".
I have searched the list for a solution to this problem, and it appears
that there are quite a few people having problems like this with Email
the question is has anyone been able to successfully configure their
system to work fully, that is to be able to send mail to users & aliases
without problems?
--
Clive
>
> yes, the solution is to modify the catch-all rules to be
> @www.domain.extension
> Please note that when the hostname is different from www, for instance
> mail, the catch-all should be @mail.domain.extension. that's
> exactly why
> the @domain.extension options was dropped. Also please note
> that making
> the catch-all be @www.domain.extension still means that
> sending mail to
> non-existing-user@xxxxxxxxxxxxxxxx will be accepted by the catch-all.
>