[BlueOnyx:25085] Re: Unable to change domain

[Michael Aronoff]

I tried this but did not see the OID. I just submitted a support 
request.

Thanks,
________________________________
M Aronoff Out – maronoff at gmail.com

I'm a great believer in luck, and I find
the harder I work the more I have of it.
   - Thomas Jefferson

------ Original Message ------
From: "Michael Stauber" <mstauber at blueonyx.it>
To: blueonyx at mail.blueonyx.it
Sent: 9/8/2021 5:54:27 PM
Subject: [BlueOnyx:25084] Re: Unable to change domain

>Hi Michael,
>
>>  I have a client that has moved their website but are leaving their email
>>  with us.
>>
>>  I want to change the domain in the GUI to mail.theirdomain.com instead
>>  of www.theirdomain.com <http://www.theirdomain.com> but when I try to do
>>  so it gives me the following error:
>>
>>      Sorry, the email alias, \, is already in use on this system. Please
>>      choose another.
>>
>>      The operation failed. Unable to update the email information for the
>>      users who belong to this site.
>>
>>
>>  I removed all the aliases from the one user and that did not help. Any
>>  other ideas?
>Yeah, there seems to be an errant 'EmailAlias' or 'ProtectedEmailAlias'
>in CODB. This is a bit tricky to find.
>
>First of all, edit /usr/sausalito/handlers/base/email/validate_alias.pl
>and turn on debugging. In line 13 and 14 of that handler you have this:
>
># Debugging switch:
>$DEBUG = "0";
>
>Change it to this:
>
># Debugging switch:
>$DEBUG = "1";
>
>Perform the GUI transaction again and run "tail -f /var/log/messages"
>while you do so. The enabled debugging will output some extra info into
>the log.
>
>Line 172 of that handler reads like this:
>
>&debug_msg("Inside fail(): aliasInUse $alias - $code \n");
>
>That generates the debugging on failure. Sadly it won't tell us the
>exact Object ID.
>
>But check lines 160-162 in that handler, which read like this:
>
>     if (scalar(@conflicts)) {
>         &fail($cce, $obj->{alias}, 2);
>     }
>
>Change that section to this:
>
>     if (scalar(@conflicts)) {
>	&debug_msg("Checking OID: $obj->{OID} \n");
>         &fail($cce, $obj->{alias}, 2);
>     }
>
>If you do that, then /var/log/messages will print "Checking OID: <OID>"
>right before the "Inside fail(): aliasInUse ..." line and you know the
>OID of the Object that's causing grief.
>
>You can then fire up /usr/sausalito/bin/cceclient and run a "GET <OID>"
>to take a look at the object and fix it via "SET <OID> <key> = <value>"
>or you can simply run a "DESTROY <OID>" and just destroy the faulty
>object in question.
>
>Once that object is gone the error should be gone as well and you can
>undo any code changes you made by reinstalling the components of
>base-email this way:
>
>yum reinstall base-email-*
>
>If you need any assistance with this, then please open a "Support
>Ticket" via the GUI with the checkbox "Allow Access" ticked and include
>an exact description about which Vsite (and User) has the problem and on
>what GUI page I can recreate the error.
>
>--
>With best regards
>
>Michael Stauber
>_______________________________________________
>Blueonyx mailing list
>Blueonyx at mail.blueonyx.it
>http://mail.blueonyx.it/mailman/listinfo/blueonyx