I think I might try the Linux route after I get everyone settled into the new system.  I'm on a deadline of getting this in place by the end of the day Tuesday.  I thought I had it squared away until I realized I had a mess with the 10 user limit.  I'm switching everyone to IMAP this weekend because I refuse to send more money to micro$oft.  The reason I asked about the shared folder in the earlier post is because I didn't need to log into the xp machine to view the archive folder over IMAP. 

For now it looks like I'm going to manually administer the individual addressbooks on a per client basis.  Being only 20 local users it won't be that bad.  Maybe this could be added to a future version.  When you create an address book, have the ability to browse to a shared version.  Luckly we don't have a heavy turnover.

I am running Mercury in network mode on a XP Pro OS.  Does this mean that no more than 10 users will be able to log into Pmail and be running itle on their PC waiting for mail?

[quote user="cynist"]I am running Mercury in network mode on a XP Pro OS.  Does this mean that no more than 10 users will be able to log into Pmail and be running itle on their PC waiting for mail?[/quote]

You just made my day!   Thanks.

[quote user="cynist"]I am running Mercury in network mode on a XP Pro OS.  Does this mean that no more than 10 users will be able to log into Pmail and be running itle on their PC waiting for mail?[/quote]

However if you are running Pegasus Mail from the server with users running it via a shortcut... then the answer is yes.

Now you're raining on my party.  This is exactly what I'm doing.  The only way around this is to install PMail on each client or put Mercury on a server os. [:'(]  Is it still possible for all the individual clients to still utilize their existing mailbox on the server?

So I just installed the pmail client to my computer and I must say this was very easy since I was able to point everything to the directory on the server.  I answered my own question above.  Now that I did this the local client will still look at the config files in my mail directory on the server and not locally?  I used to have a shared address book and it's not there anymore.  Where do I need to place this address book so all locally installed clients will still share it?

Now I need some real help.  I received a message and tried to reply to it.  Now I keep getting an SMTP error message box popping up.  I says that a network error occured connecting to the host.  "2: Bad address \\N\queue\.  Now what?

I think I figured out the problem.  For some reason in the Internet mail options I had the shared path to the queue.  Once I replaced it with the internal ip address it was happy.  I still need help with the shared address book.

[quote user="cynist"]So I just installed the pmail client to my computer and I must say this was very easy since I was able to point everything to the directory on the server.  I answered my own question above.  Now that I did this the local client will still look at the config files in my mail directory on the server and not locally?  I used to have a shared address book and it's not there anymore.  Where do I need to place this address book so all locally installed clients will still share it?[/quote]

That setup requires a login to the OS for this to work.  You will probably run into the same 10 concurrent users limit.  You can though use IMAP4 to point at the Mercury/32 MercuryI server without any limit.   For the system addressbook you have the same problem,  if the addressbook is on the server share the users must login to the server to make the share connection.  You can though use the Mercury/32 PH server and point the PH server at the system addressbook to make it available.

[quote user="Thomas R. Stephenson"] 

 You can though use the Mercury/32 PH server and point the PH server at the system addressbook to make it available.

[/quote]

I have that done but how does the user access the PH server from the client?

I have that done but how does the user access the PH server from the client?

If I utilize IMAP and have public folders on the xp server.  Will this also run me into the 10 concurrent connections problem?  If so, what if I placed only the public folder on another server os?  The only public folder I have would be an archive folder.

[quote user="Thomas R. Stephenson"]

They use the PH extension of PMail.  It comes with PMail and you should be able to see the client in Addresses |  PH directory client.
[/quote]

Is there a way to get the progam to list all the users at once and not just the specific one you type in?

[quote user="cynist"]If I utilize IMAP and have public folders on the xp server.  Will this also run me into the 10 concurrent connections problem?  If so, what if I placed only the public folder on another server os?  The only public folder I have would be an archive folder.[/quote]

Any time the user must go through the OS to make a connection the connection limit comes into play.  IMAP4 is not going through the OS; using the public folders on the server requires connecting to the host to make a connection to the shared directory. If you put the public folders on a server that does not have the user limit then there is no problem.  That said, almost all systems have some sort of limit.  The Netware system I have is for 25 users and so only 25 users may login.  If you had a Windows server you still would be limited but the number of user licenses you had purchased.  Even our VAX servers had user limits.   Not sure about Linux though but since it is OSF type software I really doubt if it sets a limit on the number of user connections even to the workstation version.

[quote user="cynist"][quote user="Thomas R. Stephenson"]They use the PH extension of PMail.  It comes with PMail and you should be able to see the client in Addresses |  PH directory client.[/quote]

Is there a way to get the program to list all the users at once and not just the specific one you type in?[/quote]

Not that I know of.  You can though use substrings in the search and all users matching the substring should show up.

A SAMBA server on a small linux distro has no limit on connections (until you reach the limits of the hardware).

If you have a spare (old, redundant) box or even a virtual box (VMware server etc) you could set up a minimal distro (DamnSmallLinux, FREESCO, Puppy etc.) to provide an umlimited SMB share.

The FREESCO option doesn't even require a hard drive in the machine, you can mount the Windows share (1 user connection) then share it to as many as you want from the SAMBA server :)