you are so right about the it guy -I am constantly getting projects - like the one I'm doing now which - is making me go from xp to win 7 then adjusting everything around it - like pulling sales from stores - and after this I'll be off to other things

but maybe it is an excuse - I really like win 7 and office 2010

We have 9 locations connected bt Sonic Wall Firewall - we want to e-mail freely inside the Intranet yet strictly control Internet access. In our IP Address scheme our first and second octave throughout

the locations are the same the third is for location the fourth is for computer - all computer names in each location are the same, ie scan or blah or whatever - how do I get us connected?

have downloaded pmai land merc now and years ago - frustrated both times but then again I am lame

> We have 9 locations connected bt Sonic Wall Firewall - we want to e-mail freely inside the Intranet yet strictly control Internet
> access. In our IP Address scheme our first and second octave throughout
> the locations are the same the third is for location the fourth is
> for computer - all computer names in each location are the same, ie scan or blah or whatever - how do I get us connected?

I assume that you have TCP/IP connections between the various locations. I also assume that you only want a single location to access outside the Intranet for e-mail.

1.  Install WinPmail in the multiuser mode on the "server".  Use c:\pmail
    for the program; c:\pmail\mail for the mail directories.

2.  Run PCONFIG.exe from the WinPMail program directory and change the HOME and
    NEW mail directory specification to the \\server\vol\pmail\mail\~8
    format.

3.  Go to the remote workstations and install a shortcut to the common
    program.

Ok, now you have the basic mail system setup.  You can send mail to each other using Pegasus Mail.  

4.  Install Mercury/32 on this same server pointing to the Pegasus Mail
    directory structure.  Use MercuryD, MercuryS, MercuryC at least. Use
    \\server\vol\mercury\queue for the mail spool directory.

5.  Point MercuryD at all of your POP3 mailboxes to download the mail to
    your Pegasus Mail user directories.

You now can send and receive Internet mail via Pegasus Mail.  The mail is delivered to the Pegasus Mail directories automatically.  You send mail simply but putting the output files into the Mercury/32 mail spool directory.  This is accomplished automatically with a Pegasus Mail User Defined Gateway.  

6.  If you want to maintain other POP3/IMAP4 clients, point the client at
    the at your Mercury/32 host as a POP3 and SMTP host using the Pegasus
    Mail username and password to pickup the mail.

You can do a complete inbound and outbound mail archive with this setup using a simple Mercury/32 "Always" filter that put a copy in a users mail directory.

Now it seems that merc has disappeared - I tell the program to run - the initial screen comes on and it disappears.....

I went to control panel to delete and reinstall but it is not listed......I paid the fee for the "service" to run but it keeps asking for the license which i keep putting in.....

Probably related - after I edited the pconfig.exe file in pmail - it just crashes - will not start up...

I think the only really good thing - the short cut on workstations seems to work just fine.

From this pc I run an sql server, control my AS400, use Advanced Scheduler, Have many command queues in pcanywhere, use net-op, winfax - is this too much? 

[quote user="rich"]

Now it seems that merc has disappeared - I tell the program to run - the initial screen comes on and it disappears.....[/quote]

That is usuall;y a symptom of a missing or corrupt mercury.ini[quote]

I went to control panel to delete and reinstall but it is not listed......[/quote]

To uninstall, just delete the Mercury directory, everything is in there[quote]

I paid the fee for the "service" to run but it keeps asking for the license which i keep putting in.....[/quote]

Forget about running as a service until you get it configured correctly, just start mercury.exe[quote]

Probably related - after I edited the pconfig.exe file in pmail - it just crashes - will not start up...

I think the only really good thing - the short cut on workstations seems to work just fine.

From this pc I run an sql server, control my AS400, use Advanced Scheduler, Have many command queues in pcanywhere, use net-op, winfax - is this too much? 

[/quote]

Check your permissions for the Merc & Pmail files. Exclude Mercury & Pmail from any AV you have running.

Mercury's requirements are really low, if it was working ok before Mercury won't be adding much load.

Re-installed Merc-

set up pmail with 4 user addresses - went to pmail/programs/pconfig + changed per above -

when I started pmail after that the users were coming back nonexistant - misdirected file?

Are you sure the folder you mapped to is accessible?

You did use Pconfig to point to a folder that's shared over the network, yes? This folder needs to have appropriate permissions, for both access and sharing. You should not have included a drive letter unless you know that each machine across the network that will run this instance of Pmail has the same drive letter mapping to that folder.

Apologies for stepping into this conversation but as it's slow over Christmas I thought I'd offer what [little] help I could to keep things ticking over.

folder mapped to is

C:pmail\mail

changed pconfig to

\\server\vol\pmail\mail\~8

how do Iconnect the two - this is only on my pc - after which from what I gather - I just need to shortcut pmail to all computers in our network (lan only behind firewalls) - about 32-33 computers - no internet access...

Please tell me you didn't literally put "\\server\vol..."?

You replaced them with the hostname of the PC on which Pegasus is installed [server] and the sharename of the folder/drive [volume], didn't you? Something like:

\\nevada\c\pmail\mail\~8

Once it's right, you have everyone run the server instance of Pegasus via a shortcut on each PC and lo and behold, you have internal e-mail! We can work on your Mercury setup after Pegasus is working.

I am sorry but yes I am that lame.....on the other hand a few weeks ago I put in 13 registers in a store had had no problems with the network, atm, scales, printers, servers etc.....shoulda went to school for this stuff......

Everything works - put pegasus in another computer on the same exact network and another one in a store outside of corporate - both work....tomorrow I'll start putting everywhere........but.......I do not want locations to see everyone on address list - how can I filter list so only managers see managers, bookkeepers see bookkeepers, no-one sees the owners, etc ?

How can I set a password with a username?

how can I assign a password with a user name?

how can I assign a password with a user name?

Outside of corp most of our computers have multple users under admin only.....anyway - I put pmail on about 22 computers - some worked well from the start (half) - the computers running

windows 2000 seem to have the most problems - when I direct them to my computer some see my computer (when I do a search), some do not and some say I have too many users on my pc -

I was showing the owner pmail on his computer and it was good - until I exited out and wanted to enter in again - then it crashed- not good....any help?

Should I go to merc - anything in Internet Information Services? I am afraid that as soon as a computer goes out the TCP IP connection will be lost and will  constantly have to be reset......what to do, what to do?

Is the shared Pegasus installed on a computer running Windows 2000 Professional, XP Professional, Vista Professional (or whatever it's called!)?

I seem to remember that these desktop OSs only allow a maximum of 10 or 15 concurrent connections to shared folders. That might explain your connection problems.

You need to have it installed on a server OS. Alternatively, you'll have to have enough installations on separate PCs that all staff can work at once. However, in that case you'll then HAVE to have Mercury to tie all those Pegasus installs together...

My comp is a terabyte of 500 gig xp pro and 500 gig windows7 ultimate - looking at the 2 - I think xp can share 10 connections & win 7 20 connections I have pmail on xp.... Choices to try merc, try win 7 since our use will not be heavy, or give it to the owners brother who has win serve 2003?

Since I am kinda a control freak - and I have merc- should I install on xp or win 7 and since I have already proven how lame I am - anyone have instructions for the lame?

I don't know the connection limit for Windows 7 but even if it's 20, that's not enough by the sounds of it. Even installing Mercury on Windows 7 won't help - you still have over 20 PCs needing (possibly) to talk at once. The limit applies to the shared folder, no matter whether Pegasus or Mercury is using it.

Don't fall into the trap of "most of the time it'll be no more than 8 people at once, so 20 should easily cover it". The boss will quite rightly tan your hide if you give him a system which, one day, when the office is busy, starts falling over simply because you thought you'd never see so much traffic. Work out the max and ensure you can deal with it.

Here are a few options for how you might move forward:

A) Invest in a new server with a server OS, such as Windows Server 2008. Even an old copy of Windows 2000 Server on an old PC will do you fine and might be cheaper.

B) Use the server of the person you mentioned. Such a decision (using non-company resources) would clearly need to be OKd by your boss.

C) Install an appropriate, free, non-Windows OS on your server that provides a mail server program. You'd not need Mercury but I imagine that set-up and security would be more complex.

D) Find two or three desktop PCs in the company that could reliably be used as "mini-servers" and then install Pegasus onto these. Each of these would service no more than ten specific employees, and so everyone could use the mail system at once if necessary. However, these separate installs of Pegasus will not be able to "talk" to each other, so you'll then need Mercury to be installed on one, central server and set the Pegasus installs to route all mail through Mercury.

Of course, after I've typed all that, Thomas or 'Dilbert' will pipe up with "actually, forget all that - if he does X, Y and Z, he'll be fine". It's been a while since I actually played with a live network, so I definitely yield to any advice from those sages...

[:)]

Some planning might be in order, rather than just hacking it up so that it works today.

If you install it on your dual boot 'workstation', what happens to your mail system if you reboot into Win7?

For a system that needs to be available to users all the time you should have a dedicated machine for 'server' functions.

I don't know too much about using Pegasus on a network share with multiple users, but you will run into those connection limits on recent non-server MS systems.

If you just want a company mail server then Mercury, without integrating Pegasus, will do fine on any OS (even Linux via WINE). There will be no problem with connection limits as all connections will be via TCP on the appropriate mail ports & the limits only apply to SMB connections to file shares.

You can use ANY mail clients with Mercury, so if some want to use Outlook (???) or Eudora or Mutt or whatever, it will work.

If you really want the extra control & functionallity of a single central install of Pegasus (still can be separate from Mercury) then you will need to have it on a server OS or a Linux server with a SAMBA share, or maybe even Win98 [H] (I don't recall any share connection limits on that, last time I used it as a 'server')

You should make a list of your specific requirements, and formulate a plan to satisfy those requirements in a reliable manner, before you start installing stuff.

Servers - actually I have gone numerous times to the guy who signs my check -for a server - but - too many people have told him it would be too labor intensive - at every turn I volunteer (maybe too stupid to know what I would be getting myself into), Then it becomes what would be the next best thing - and I've known about pmail and merc for some time - but never had that need to do "today" - that I have now (for corp growing reasons). I actually do plan......but I do have limitations - I look around for tools that would best suit my needs and go for it.

I did "do the installs" under win7 and every comp that gave me a problem came up.....This is step one - step 2 after they see what step 1 will do - would be to get the server - I kinda think that I am being practical.....

If Outlook could be used with merc with no internet access - I would like to hear about it.

My company is reactive - they do not have anti-virus installed on comp - when they have a problem they get it then let it expire - that is a major factor in my thinking - gotta get around the duck in the middle of the road...