Automatic migration + honouring forwards

I want to migrate away from another mail server.  I don't
mind using nwauth 
to store the migrated users.  This works fine.

Of 1500 users, I have 60 with mail forwards.  I don't want
to have to wait 
until these accounts  migrate locally.  In fact, many won't,
because 
they're mail forwards.

I need to import my mail forward settings and vacation
prompts BEFORE I 
start migrating these users.  I assume this is all set with

nwauth -set username password
fwd="recipient1,recipient2"

However, the user password is unknown.  If I set it as
(NULL), POP auth 
fails and there is no import.  I'd rather not rely on the
old encoded 
password, because it's the weaker DES encryption.

How can I set up a batch of such users ahead of time so they
password can 
still be learned through the migration?

- SteveP

Tricky, the best option I can suggest (and I know it's not
great) is to use and aliases file (see the alias_file 
setting) to define the forward rules, that way the accounts
will still auto create.  The down side is the user can't 
modify those rules when/if they do login. But at least it
will allow the login/migration to still occur if they login,

at which point you could remove the entry from aliases.txt I
guess.

	ChrisP.


Steve Perrault wrote:
> I want to migrate away from another mail server.  I
don't mind using 
> nwauth to store the migrated users.  This works fine.
> 
> Of 1500 users, I have 60 with mail forwards.  I don't
want to have to 
> wait until these accounts  migrate locally.  In fact,
many won't, 
> because they're mail forwards.
> 
> I need to import my mail forward settings and vacation
prompts BEFORE I 
> start migrating these users.  I assume this is all set
with
> 
> nwauth -set username password
fwd="recipient1,recipient2"
> 
> However, the user password is unknown.  If I set it as
(NULL), POP auth 
> fails and there is no import.  I'd rather not rely on
the old encoded 
> password, because it's the weaker DES encryption.
> 
> How can I set up a batch of such users ahead of time so
they password 
> can still be learned through the migration?
> 
> - SteveP
> 
> 

At 09:56 PM 4/20/2008, you wrote:
>Tricky, the best option I can suggest (and I know it's
not great) is to 
>use and aliases file (see the alias_file setting) to
define the forward 
>rules, that way the accounts will still auto create. 
The down side is the 
>user can't modify those rules when/if they do login. But
at least it will 
>allow the login/migration to still occur if they login,
at which point you 
>could remove the entry from aliases.txt I guess.
>
>         ChrisP.
>
>
>Steve Perrault wrote:
>>I want to migrate away from another mail server.  I
don't mind using 
>>nwauth to store the migrated users.  This works
fine.
>>Of 1500 users, I have 60 with mail forwards.  I
don't want to have to 
>>wait until these accounts  migrate locally.  In
fact, many won't, because 
>>they're mail forwards.
>>I need to import my mail forward settings and
vacation prompts BEFORE I 
>>start migrating these users.  I assume this is all
set with
>>nwauth -set username password
fwd="recipient1,recipient2"
>>However, the user password is unknown.  If I set it
as (NULL), POP auth 
>>fails and there is no import.  I'd rather not rely
on the old encoded 
>>password, because it's the weaker DES encryption.
>>How can I set up a batch of such users ahead of time
so they password can 
>>still be learned through the migration?
>>- SteveP



Thanks for the reply, Chris.  I ended up just migrating the
customers and 
then changing the forward from the web administration. 
Which leads me to 
an important question:

How can I manually add a particular customer without the
auto-migration 
blowing out his settings the first time he logs in?

- SteveP