Re: [cobalt-developers] email and the raq3i

[Jessica <jmoira@xxxxxxxxxx>]

Hi Kevin,
This is a strategic issue, not a "code" issue.
I suggest you look at a combination of use of the tools in the interface,
and the configuration of your DNS.

Yes, it has often been done as a matter of course in Academic institutional
administration,
and I often encountered it at many of the early commercial startups on the net
where, for example, a porn operator had several or many sites,
and rather than sort mail from many sources locally,
mainly because they were porn operators and not technically adept,
everything came to one single account such as "email@xxxxxxxxxxxxxxxx"
from many and various sites sources and names
and they sorted it via a desktop application, such as Eudora,
and replied with any alias they chose, adding and removing aliases,
then, through the "aliases" and "newaliases" procedures,
and now, with a cobalt, through the httpd interface.
Thus in 5 minutes, I can add "bambi@xxxxxxxxxxxx" by simply adding
"bambi" as an aliased user to this master account.
You simply redirect the mx record to use one mail server.
As far as serving mail for offsite hosts;
as long as you have the proper DNS authority pointinfg the mx record to
this one server, it will work.

Re: testing your mail using I.P. address

You need to remember that the syntax for use of an i.p. address for
directing email require the use of brackets, i.e. " email@[123.457.000.678]
and that your email account at the server would reference the server name
i.e. "user@xxxxxxxxxxxxxxxxxxx"  as described,
but you would still have to identify for what domain you were accepting email,
and you would still need to identify an already configured user.
When your server is first set up, if you identify an authorized domain,
then you will aready have one user working before you sit down,
Example "admin@xxxxxxxxxxxxxxxxxxxxxxxxx"
available by DNS as the record is universally propogated.

Hope some of this helps,

Jessica McDonald Ph.D.





At 10:22 AM 7/8/00 -0400, you wrote:
> When I first set up web hosting on my raq3i, I needed to send all email to a
> different server, and this was easily done using an MX record. When It came
> time to locally start receiving mail, I ran into an interesting set of
> problems. The first thing I did was set the MX records to point to my raq's
> IP address. This worked except that the raq refused to accept any email...
>
> Then, I realized that I needed to check "accept email for domain" on all 26
> domains that I had set up. Once this was completed, I realized that the GUI
> had removed several hosts from the    Host/Domain Aliases  box in the email
> parameters section. This of course resulted in those removed domains not
> being able to receive email. However, I can't seem to figure out why certain
> domains were removed (some were, most were not). Has anyone else experienced
> this bug? Does anyone know why it occurs?
>
> Lastly, I am thinking of setting up all email accounts under one host,
> pop.mydomain.com. Doing this requires me to change the cobalt code to allow
> domains other than the original domain to be entered as email aliases. Has
> anyone done this successfully? What problems might I incurr by doing this?
>
> Kevin
>
>
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers