Updated email ldapdata information from AD doesn't save to user table

Okay, so I'm using LDAP integration with the case-tracker module and I've run into a weird problem:

We are currently migrating from one e-mail domain to another. The first time a user logs in, it saves the e-mail address to the user table when that user gets created in _ldapauth_save_user(). So, we change people's info in AD and when I go to view the user profile, sure enough it displays correctly.

However, going into the database, I can still see that the users table has the incorrect value in it. This poses a problem because the casetracker module is trying to send updates and it queries from the database directly... so when it tries to send e-mails out, it pulls either the wrong address (or in some cases) nothing at all.

To make matters worse, since I'm loading these values from within the user_load hook, I can't just call user_save because user_load calls user_save when it's done to refresh itself, and it ends up calling itself recursively.

This leaves me with two question:

1. Is it possible to make ldap_auth write it's changes back to the table so this works right?
2. Is the casetracker module gathering the e-mail address of a user in an improper fashion?

Any thoughts or comments would be appreciated.