<p>Solved! Well, sort of. </p><p> I returned the Iomega NAS, got a Philips NAS, and had the whole thing set up in 20 minutes. </p><p> It seems this problem was simply caused by the way the Iomega handles the sharing, and Pegasus somehow choked on it. </p><p>Interestingly, if you now type "pegasus mail iomega" into google, this thread comes up. [:)] </p><p> Thank you Thomas R. Stephenson and dkocmoud  for all your time on this matter! </p>

<p>This is the first time in 14 years using pegasus that I've encountered a problem this tricky: I'm having trouble getting Pegasus to work when the mailbox is located on a Iomega Home Network Hard Drive.(this one: <a href="This%20is%20the%20first%20time%20in%2014%20years%20using%20pegasus%20that%20I%27ve%20encountered%20a%20problem%20this%20tricky:%20I%27m%20having%20trouble%20getting%20Pegasus%20to%20work%20when%20the%20mailbox%20is%20located%20on%20a%20Iomega%20Home%20Network%20Hard%20Drive.%28this%20one:%20http://www.iomega.com/support/manuals/home-nhd-k108w15/en/net/main.html#home%29%20%20The%20NAS%20is%20connected%20via%20ethernet%20to%20a%20router,%20is%20using%20SMB%20to%20serve%20files,%20and%20has%20the%20latest%20firmware%20installed.%20It%20has%20a%20single%20share%20without%20any%20password%20on%20it.%20%20%20I%20can%20access%20the%20share%20and%20can%20write%20and%20read%20files%20and%20folders%20to%20and%20from%20it.%20The%20PC%20is%20running%20XP%20SP3.%20%20%20For%20now,%20I%27m%20trying%20pretty%20much%20the%20simplest%20setup%20possible:%20a%20single-user%20install%20where%20at%20least%20the%20mailbox%20is%20located%20on%20the%20NAS.%20I%27ve%20tried%20this%20both%20with%204.4%20and%20the%204.5%20beta.%20%20When%20installing%20pegasus%20on%20this%20share,%20it%20will%20only%20show%20an%20empty%20new%20mail%20folder%20when%20the%20installation%20is%20complete.%20There%20is%20no%20main%20folder,%20and%20any%20folder%20that%20is%20created%20has%20disappeared%20from%20the%20folder%20list%20by%20the%20next%20time%20pegasus%20has%20started.%20%20I%27ve%20tried%20creating%20the%20share%20in%20different%20ways,%20i.e.%20using%20the%20sharename%20or%20the%20IP-address,%20without%20any%20success.%20Using%20the%20pconfig%20utility,%20I%27ve%20tried%20using%20the%20sharename,%20the%20ip%20and%20the%20UNC,%20also%20without%20any%20success.%20Among%20the%20combinations%20of%20UNC%20and%20drive-letter%20was%20the%20one%20suggested%20here%20%28http://community.pmail.com/forums/thread/13751.aspx%29.%20%20I%20also%20tried%20to%20install%20pegasus%20locally%20%28without%20any%20problems%20of%20course%29,%20and%20then%20tried%20to%20move%20the%20mailbox%20to%20the%20NAS.%20After%20copying,%20I%20ended%20up%20again%20with%20only%20the%20new%20mail%20folder.%20Also,%20copying%20external%20pmm/pmi%20files%20into%20the%20mailbox%20location%20doesn%27t%20have%20any%20effect.%20When%20I%20do%20this%20in%20a%20locally%20installed%20instance,%20those%20files%20show%20up%20without%20any%20problem.%20%20When%20I%20use%20a%20share%20on%20a%20second%20XP-based%20computer%20to%20install%20pegasus,it%20experiences%20no%20difficulties.%20I%20won%27t%20be%20able%20to%20access%20the%20systems%20again%20until%20tomorrow,%20but%20the%20next%20thing%20I%20want%20to%20try%20is%20to%20enable%20IPX/SPX/NetBIOS%20and%20see%20if%20that%20helps...%20%20Any%20suggestions%20in%20the%20meantime%20what%20could%20cause%20this%20behaviour%20are%20much%20appreciated%21%20%20" title="This is the first time in 14 years using pegasus that I've encountered a problem this tricky: I'm having trouble getting Pegasus to work when the mailbox is located on a Iomega Home Network Hard Drive.(this one: http://www.iomega.com/support/manuals/home-nhd-k108w15/en/net/main.html#home) The NAS is connected via ethernet to a router, is using SMB to serve files, and has the latest firmware installed. It has a single share without any password on it. I can access the share and can write and read files and folders to and from it. The PC is running XP SP3. For now, I'm trying pretty much the simplest setup possible: a single-user install where at least the mailbox is located on the NAS. I've tried this both with 4.4 and the 4.5 beta. When installing pegasus on this share, it will only show an empty new mail folder when the installation is complete. There is no main folder, and any folder that is created has disappeared from the folder list by the next time pegasus has started. I've tried creating the share in different ways, i.e. using the sharename or the IP-address, without any success. Using the pconfig utility, I've tried using the sharename, the ip and the UNC, also without any success. Among the combinations of UNC and drive-letter was the one suggested here (http://community.pmail.com/forums/thread/13751.aspx). I also tried to install pegasus locally (without any problems of course), and then tried to move the mailbox to the NAS. After copying, I ended up again with only the new mail folder. Also, copying external pmm/pmi files into the mailbox location doesn't have any effect. When I do this in a locally installed instance, those files show up without any problem. When I use a share on a second XP-based computer to install pegasus,it experiences no difficulties. I won't be able to access the systems again until tomorrow, but the next thing I want to try is to enable IPX/SPX/NetBIOS and see if that helps... Any suggestions in the meantime what could cause this behaviour are much appreciated! " mce_href="This is the first time in 14 years using pegasus that I've encountered a problem this tricky: I'm having trouble getting Pegasus to work when the mailbox is located on a Iomega Home Network Hard Drive.(this one: http://www.iomega.com/support/manuals/home-nhd-k108w15/en/net/main.html#home) The NAS is connected via ethernet to a router, is using SMB to serve files, and has the latest firmware installed. It has a single share without any password on it. I can access the share and can write and read files and folders to and from it. The PC is running XP SP3. For now, I'm trying pretty much the simplest setup possible: a single-user install where at least the mailbox is located on the NAS. I've tried this both with 4.4 and the 4.5 beta. When installing pegasus on this share, it will only show an empty new mail folder when the installation is complete. There is no main folder, and any folder that is created has disappeared from the folder list by the next time pegasus has started. I've tried creating the share in different ways, i.e. using the sharename or the IP-address, without any success. Using the pconfig utility, I've tried using the sharename, the ip and the UNC, also without any success. Among the combinations of UNC and drive-letter was the one suggested here (http://community.pmail.com/forums/thread/13751.aspx). I also tried to install pegasus locally (without any problems of course), and then tried to move the mailbox to the NAS. After copying, I ended up again with only the new mail folder. Also, copying external pmm/pmi files into the mailbox location doesn't have any effect. When I do this in a locally installed instance, those files show up without any problem. When I use a share on a second XP-based computer to install pegasus,it experiences no difficulties. I won't be able to access the systems again until tomorrow, but the next thing I want to try is to enable IPX/SPX/NetBIOS and see if that helps... Any suggestions in the meantime what could cause this behaviour are much appreciated! ">http://www.iomega.com/support/manuals/home-nhd-k108w15/en/net/main.html#home</a>) The NAS is connected via ethernet to a router, is using SMB to serve files, and has the latest firmware installed. It has one share without any password on it. I can access the share and can write and read files and folders to and from it. The remaining hardware is straigthforward: two pc's running XP SP3 in a workgroup. Antivirus is NOD32. For now, I'm trying pretty much the simplest setup possible: a single-user install where at least the mailbox is located on the NAS. I've tried this both with 4.4 and the 4.5 beta. The final goal is using the NAS in the same way I use a currently installed copy of pegasus on a share on an XP machine. I don't need multiple mailbox or multi-user support: it's sufficient that pegasus can be run on one PC if the other is occupied. When installing pegasus on the NAS share, it will only show an empty new mail folder when the installation is complete. There is no main folder, and any folder that is created has disappeared from the folder list by the next time pegasus has started. I've tried creating the share in different ways, i.e. using the sharename or the IP-address, without any success. Using the pconfig utility, I've tried using the sharename, the ip and the UNC to point to the mailbox, also without any success. Among the combinations of UNC and drive-letter was the one <a href="/forums/thread/13751.aspx" mce_href="/forums/thread/13751.aspx">suggested in this thread.</a> I also tried to install pegasus locally (without any problems of course), and then tried to move the mailbox to the NAS. After copying, I ended up again with no folders except the new mail folder. Also, copying external pmm/pmi files into the mailbox location doesn't have any effect. When I do this in a locally installed instance, those files show up without any problem. When I use a share on a second XP-based computer to install pegasus,I have no difficulties either. </p><p>I won't be able to access the systems again until tomorrow, but the next thing I will try is to enable IPX/SPX/NetBIOS and see if that helps... Any suggestions in the meantime on what could cause this behavior are much appreciated! </p>

<P>What are you using as the actual URL path for the NAS device, share, and folder?</P> <P>e.g.</P> <P><A href="file://nasdevice/sharename/mail">\\nasdevice\sharename\mail</A></P> <P>Please copy the newmail directory path, as shown on the Info text under the Help -> About Pegasus Mail... menu option and paste it into a reply to this thread.</P>

<p>It's \\iomega\iomega\MAIL</p><p>The newmail directory path is  \\iomega\iomega\MAIL\Admin</p><p>Here are some screenshots to show what's happening:</p><p> First I did a clean install of pegasus on C:, and ended up with the normal main folder containing the welcome message:</p><p><img src="http://www.rozema.lu/pegasus/screen0.gif" mce_src="http://www.rozema.lu/pegasus/screen0.gif" width="553" height="362"> </p><p>Then I moved the mailbox location to the network share, and ended up with this :</p><p><img src="http://www.rozema.lu/pegasus/screen1.gif" mce_src="http://www.rozema.lu/pegasus/screen1.gif" width="515" height="312"> </p><p> I also used pconfig to manually change the home & new mailbox settings, like so:</p><p> <img src="http://www.rozema.lu/pegasus/pconfig.gif" mce_src="http://www.rozema.lu/pegasus/pconfig.gif" width="601" height="305"> </p><p>Originally, after pegasus installed itself on C:, the mailbox values read: c:\pmail\mail\~N.   </p>

<p>What happens when you map the \\iomega\iomega to a drive like z: and then set the pconfig home and new mail directory spec to  to z:\pmail\~n?</p><p> </p><p> </p>

<P>It behaves exactly the same. Something else I now noticed is that when using a location on the NAS as mailbox, pegasus will open with a "Welcome to pegasus 4.4. Pegasus has detected that you have previously used an older version of Pegasus on this mailbox" message everytime. </P> <P>Pegasus must be seeing at least part of the mailbox, because when I deliberately misspell the path, it opens with the "User name please" dialog box. Misspelling the name of a path on the local drive gives the same result. </P>

<blockquote>It behaves exactly the same. Something else I now noticed is that when using a location on the NAS as mailbox, pegasus will open with a "Welcome to pegasus 4.4. Pegasus has detected that you have previously used an older version of Pegasus on this mailbox" message everytime.</blockquote>This means that it's finding the mail directory and the pmail.ini file on start up but it's not writing it on closing to update the file.  Does the user have all rights to their mail directories? 

<p> </p><p>The rights should be ok. I can CRUD files & folders from the windows Explorer. On the NAS there is only the option to password-protect a share, not to specifically differentiate between rights. Right now, there are no passwords set. </p><p> If I look at the properties of the share from within Explorer however, I noticed that the Read-only checkbox was ticked with a grey background which cannot be removed. I fiddled around a bit with <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;326549" mce_href="http://support.microsoft.com/default.aspx?scid=kb;en-us;326549">these</a> instructions from microsoft, without any result. Then I found out that the same greyed-out checkbox is present on a share on an XP-box, on which pegasus can store its mailbox without any problems. The files in the folders are all writable. </p><p> Somehow there seems to be a difference in how the NAS handles sharing as opposed to how Windows does this, which has no effect while using the share from within explorer, but somehow throws pegasus in disarray. I have a feeling that the only solution may be to return the NAS and try a different brand or model... </p>