This is almost the same as the process outlined above, you should read that first then return here. Have been migrated, the file will contain entries like this.ġ092718001 by (SERVER) Migrating to SurgeMail with SurgeMail on a different server. You can also check the users_yymm.rec in the surgemail directory to see which users You can check the status page to see how the migration is going (migrated). So the complete vdomain block in surgemail.ini will now look like this. That is all!, now you leave SurgeMail in this setup for maybe a month, to give your users time to migrateĪfter that you can remove the migration settings and remove your old server completely. The second setting tells SurgeMail to check the rcpt exists on the old server before sending it there. The first setting tells SurgeMail to send any mail for a user that doesn't exist to 127.0.0.1 port 1025 To send that mail to the old server still. Migrated will be rejected by SurgeMail as the user doesn't exist, so we need to tell SurgeMail Now the problem is, that any mail coming into SurgeMail on port 25 for a user that hasn't been If your users didn't login as on the old server and rather just logged in as user The user into that old server and collect all their mail and add them to SurgeMail's database. So that tells SurgeMail to check on that ip and port when a user pops, SurgeMail will then log If we are migrating pop we will use the old_pophost setting Redirect was="abuse" was="postmaster" was="support" now we add in our migration settings.
Now you look for the domain section in surgemail.ini for the domain you want to migrate vdomain address="" name=".nz"
#SURGEMAIL MIGRATION WINDOWS#
Then you should stop SurgeMail, edit surgemail.ini in /etc on the windows directory.
#SURGEMAIL MIGRATION INSTALL#
Now you install SurgeMail on the same machine, at this point you setup the domains on SurgeMail You now change old server to run on ports 10 Let's say you have oldserver running on ports 25 and 110 You can put both imap and pop migration settings in surgemail.ini if you have both imap and pop accounts to be migrated. The below example is for migrating pop accounts accross, but if you wish to migrate imap accounts then just need to use the imap settings instead.Ĭhange old_pophost_nodomain to old_imaphost_nodomain Still use the migration method by making the old server run on different ports. If you want to migrate to SurgeMail and put SurgeMail on the same machine as your existing server you can Migrating to SurgeMail with SurgeMail on a different server Migrating to SurgeMail with SurgeMail on same server. Migrating to SurgeMail with SurgeMail on same server