Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

Best way to migrate Netware Mode legacy user to Standalone Mode?

  •  07-06-2011, 8:41

    • egads is not online. Last active: 07-06-2011, 23:59 egads
    • Not Ranked
    • Joined on 07-14-2007
    • San Francisco
    • Member
    • Points 30

    Best way to migrate Netware Mode legacy user to Standalone Mode?

    Hello,

    We're migrating our last Netware (6.5) file server to Windows, and time has come to move our last Pegasus user (me) from Netware Mode to Standalone.  'Problem is, Pegasus is so dependable and it's been so long since I've had to do any real technical support of my own account that I'm not sure the best way to do this.  I started by moving the home mailbox location from the old network drive to my local hard drive, but that leaves the pmail.ini and white and black lists, etc. still on the about-to-be-retired Netware file server (\\BRKFILESEA0V).  I still have the Netware 32bit client on my XP Pro workstation and can (for the time being) flip back and forth from the Netware side to the Windows side - 'tried using pconfig.exe, but of course when I'm logged in as a Netware user I have the correct context but pconfig 'sees' the Netware environment and doesn't offer standalone, and when I'm logged in on the Windows side Pegasus can't find the pmail.ini, etc.   I'd like to migrate the existing setup rather than do a clean install, because I have a number of IMAP and POP profiles set up to pull email from a variety of legacy accounts (AOL, etc.) that still need to be monitored on a regular basis.   

    Here's a dump from the About/Info window my Pegasus (v 4.61).   Any advice (including the "just go to {link} and read carefully" kind)  would be most appreciated. 

     

    Thank you,

    Ed Sullivan

     

    WinPMail version: Version 4.61 (Win32), Feb  5 2011
    Language resources: Standard UK English resource set
    Extension Manager version: 1.13
    Operating mode: Network
    User name and ID: speedy.EPSBERKELEY.EPS, 0
    Windows version: 5.1
    Windows flag word: 0
    WINPMAIL.EXE directory: C:\PMAIL\Programs
    Home mailbox location: C:\EMAIL\SPEEDY\PMAIL
    New mailbox location: \\BRKFILESEA0V\DATA\users\speedy\PMAIL
    TMP environment variable: C:\DOCUME~1\egads\LOCALS~1\Temp
    TEMP environment variable: C:\DOCUME~1\egads\LOCALS~1\Temp
    LAN-based SMTP support: Y, Y, N
    NetWare MHS support: Y, N, N
      - MHS path is L:\
    Built-in TCP/IP support: Enabled
      - WINSOCK version: WinSock 2.0
      - WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
    Commandline: -roam
    Active -Z options: 32768
    PMR variable: F:\PMAIL
    PML variable: F:\PMAIL
    MAI variable: (None)
    NB variable: L:\MHS\NB
    Autofiltering folders: 0 (0 active, 0 inactive)
    Last new mail count: 13

    NICA module: Novell NetWare NDS Mode
    NICA module version: 1.2 release 0, Jul 13 1999
    Configuration context: EPSBERKELEY.EPS
    Default server version: 5.70 rev 6, 127 user
    Connections: Highest, 20; Current, 2
    Shell/Requester version: 4.91.4
    Mercury spool directory: \\BRKFILESEA0V\SYS\Pmail\queue
    New mailbox location algorithm: 0
     

View Complete Thread

Contact | Advertise | Host provider: PraktIT | Terms of Use | Privacy Statement
Copyright © 2007-2011 David Harris / Peter Strömblad. | Pegasus Mail Home Page