Spam:*****, Migrating to SurgeMail from Post.Office

Hello everyone,

I'm very excited about being able to utilize the many
features of  
SurgeMail in the not to distant future. I have one major
question at  
this point. Has anyone one here ever migrated from
Post.Office to SM.  
I have a few customers who have hundreds of emails that they
just  
can't live without stored in our current system. I know in
theory it  
should work, but I was hoping for some input from someone
that has  
actually done the deed.

Thanks,

Alan K. Jackson
Ad-Vantage Multimedia

I did a few years ago. It worked well with just a few
hiccups. Aliases are
not migrated, so they have to be re-created in SurgeMail.


-----Original Message-----
From: Alan Jackson [mailto:alanadvr.net] 
Sent: Wednesday, July 25, 2007 12:06 PM
To: surgemail-listnetwinsite.com
Subject: [SurgeMail List] Spam****,
Migrating to SurgeMail from
Post.Office

Hello everyone,

I'm very excited about being able to utilize the many
features of  
SurgeMail in the not to distant future. I have one major
question at  
this point. Has anyone one here ever migrated from
Post.Office to SM.  
I have a few customers who have hundreds of emails that they
just  
can't live without stored in our current system. I know in
theory it  
should work, but I was hoping for some input from someone
that has  
actually done the deed.

Thanks,

Alan K. Jackson
Ad-Vantage Multimedia

Alan Jackson wrote:
> Hello everyone,
> 
> I'm very excited about being able to utilize the many
features of
> SurgeMail in the not to distant future. I have one
major question at
> this point. Has anyone one here ever migrated from
Post.Office to SM. I
> have a few customers who have hundreds of emails that
they just can't
> live without stored in our current system. I know in
theory it should
> work, but I was hoping for some input from someone that
has actually
> done the deed.

As a matter of fact, I did that very thing last night.  I
used listacct
to get the address to pop-login mappings, then put the pop
logins in an
sql db to validate addresses against.  Also, I wrote a
script to
generate the surgemail alias map to the mailboxes (which
have to go in
two places: /usr/local/surgemail/domuser.dat is a global
table, then you
have to put the user specific ones in each user's
xfile/aliases.txt
file).  It's non-trivial, but not too hard either...

The other this is we're using dmail webmail client on the
old server,
and not yet ready to switch users to a new one.  Because the
server name
it's connecting to changed, I had to go rename all the user
directories
as the server name is part of the user directory name.

The one thing I can't figure out at the moment is the dmail
webmail
client refuses to connect to the new server to get mail ---
it seems to
have the server name's old ip address stuck somewhere even
though I've
rebooted the box, flushed dns and even put the ip address in
the static
hosts file.  everything else (nslookup, cygwin's telnet) go
to the right
server, but not dmail...