[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] Unable to send mail to other owned raq



Yes, we've explained how backwards it is.  They don't care, and they've had
their email addresses for a very long time.  'Why would you want to do that'
is not the issue here.  I need to forward their emails - period.

We just got off the phone with Cobalt Tech and they (a) understand that our
client is not making an outrageous request, and (b) couldn't make it work
right out of the box either.  They did, however, come to a resolution.

The answer?  When we set up www.domaincg.com and set the switch to accept
email, it didn't take.  That's right, the switch was set in the admin to
Accept Email for Domain, but it didn't take.  The Cobalt tech saw that it
was 'set', but it wasn't actually.  We unchecked it, saved changes, checked
it, and saved again.  All works as advertised, client's happy, I'm happy,
but kinda disappointed in the group here.

Finally, the client's site has been fully migrated to the 'cg' domain.  The
only reason the 'DomainID' domain exists is to receive their email.  Yes,
they are hard-headed.  They pay us a great deal of money and send us
business constantly, so we put up with them.  The customer is always right
(even if they're wrong.)

Jay

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Carrie
Bartkowiak
Sent: Tuesday, March 06, 2001 11:33 AM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] Unable to send mail to other owned raq


> I have two domains that are causing the issue.  One is 'domainid.com', the
> other is 'domaincg.com'.  All email for users at 'domaincg.com' must be
> routed individually to specific addresses at 'domainid.com'.  The reason -
> the client has been 'domainid.com' forever, so many people have their
> @domainid.com addresses.  They are migrating to 'domaincg.com', but for
the
> foreseeable future want all mail to route to their 'old' email addresses.

This makes no sense to me.
If they are migrating to the new 'domaincg.com' name, why not route all mail
to that address?
Also, use that address in their emails so when they reply to someone it is
automatically set as coming from that address, and the person's email
program will add the *new* address to the address book.

You don't migrate to a new name/address by taking everything that goes to
the new addy and sending it back to the old addy.

Have you explained this to the client and how backwards it is?
There's really no use migrating at all with this setup - may as well just
have domaincg.com be nothing more than a pointer to domainid.com and have it
as an additional way to get to the site/business, rather than attempting to
migrate and loop-de-loop between the two.

CarrieB

_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users