Dear Stu,

The best way to deal with this is to create an E-mail account with a UID
like a1234567 or whatever unique identifier you have available to you. Then
associate a nickname (Nice Name) to the account like
[email protected]. You can also use set the reply as address to
match the nice name through the E-mail Settings API. In this way when they
change their name for whatever reason you simply add another nickname and
update the reply as so it matches.

This means that their old E-mail address continues to function and also
their new name becomes the primary name they use for E-mail. They still
login with the same account name and also you do not need to migrate data
around.

As long as the E-mail address you change them to is unique in your domain
this solution expands to N name changes.

Yours sincerely

David Ruwoldt

On Thu, Dec 4, 2008 at 1:16 AM, Anirudh (Google) <[email protected]> wrote:

>
> Hi Stu,
>
> Migration of entire user data is indeed the workaround.
>
> Few Google Apps email migration solutions for your reference:
> http://www.google.com/support/a/bin/answer.py?hl=en&answer=57920
>
> POP can be used to retrieve emails to desktop clients. In particular,
> you can use Email Uploader (Windows platform) utility to push emails
> to Google Apps accounts from a wide variety of datasources without you
> having to write any code:
> http://mail.google.com/mail/help/email_uploader.html
>
> -Anirudh
>
> On Dec 1, 12:47 pm, Stu Winchester <[email protected]>
> wrote:
> > Sorry, I just noticed "One workaround is to create a new user and to
> > migrate and share data from the old user to the new user. " in the
> > FAQ.  I suppose this means that for every user that wants to change
> > their username I will have to go in programmatically and read each
> > email and push it into their new gmail account....
> >
> > On Dec 1, 4:09 pm, Stu Winchester <[email protected]> wrote:
> >
> > > Hello,
> >
> > > I'm using the Google provisioning API to provision a number of
> > > accounts into our own google domain based on a primary username key
> > > which is unique across the organization.  However, in some instances
> > > people marry / divorce, etc and want their username key changed, which
> > > will also result in having to change the google userId.
> >
> > > Is there an easy way to do this?  Is it possible?  We don't want the
> > > creation of nicknames, some people can be quite insistant that all
> > > traces of their previous name are removed!
> >
> > > Many Thanks,
> >
> > > Stu.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Apps APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-apps-apis?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to