David Young wrote on 12/09/2008 10:33:19 AM:


> The individual command already uses the * wildcard character, such as:
>
> Quiet change * [log in to unmask] [log in to unmask]
>
> If the usernames remained the same, it wouldn't be a problem, but
> they're more personalized on the new e-mail host.  Fo instance:
>
> Quiet change * [log in to unmask] [log in to unmask]
>
> I hope that helps explain things.

>> ====
>> CHANGE(*) listname|* newaddr
>> CHANGE(*) listname|* oldaddr|pattern newaddr|*@newhost
>> ====

If the LHS was not changing you could use the second form of the command:

QUIET CHANGE * *@exchange.uta.edu *@mavs.uta.edu

Looks like you're going to have to script the changes since the LHS is
changing too.  Maybe you can have all of your script files written with 100
changes each.  Then time how long it takes to process each one and write a
shell script to launch each set of change commands at intervals of 2 -4
times (or more) the time it take to process each set.  That way, you would
only batter and bruise, not completely crush  the server.