Bump
Still looking for some help with this. I would like to make sure i have the install done correctly before proceeding.
Downloaded and read through the manula a bit. here is what I currently have-one PC running one copy of pmail (v.441)
Have 5 PCs running XP Pro and one file server running Win2000-all new eqpt.
Very basic no frills office environment.
Not sure what mode current install is in (don't think it matters...)
We would like to run pmail from the server with one public mailbox for the business email. Right now, only one person can get to emial on one PC. No need for multiple mailboxes or users. Very basic. I understand that there may need to be multiple user accts...
I see where I can install pmail on the server physically-but what would be the best mode Multiuser or Network-assuming Network, but what would the differences be between the modes?
Do I understand correctly that I would need to install pmail on each PC, or can we drop a shortcut on each PC desktop and run it down the wirefrom the server?
Lastly, if I can install it on the server and run it from the server, I would need to set up one public tree and get the mail to run through it just like it is on the single PC.
Please feel free to offer as much detail as desired. Would like to get this set up and working the first time around. And keep the existing mail if possible, but not a huge deal if not, there is only 5-10 email a day and they are deleted within a week. Like I said-very basic business operations. Nothing complicated. Thanks
Andrew
Here is the info from the existing install: (in standalone mode)
Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2006, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.
WinPMail version: Version 4.41 (Win32), Jul 16 2006
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: C:\PMAIL\MAIL\Admin
New mailbox location: C:\PMAIL\MAIL\Admin
TMP environment variable: C:\DOCUME~1\OFFICE~1\LOCALS~1\Temp
TEMP environment variable: C:\DOCUME~1\OFFICE~1\LOCALS~1\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
- WINSOCK version: (Not loaded)
- WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
Commandline: -roam -A
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Also, I was wrong about the kept email-they have a ton of folders with archived mail-we will need to preserve all that and get it into the new install on the server...
> Downloaded and read through the manual a bit. here is what I currently
> have-one PC running one copy of pmail (v.441)
>
> Have 5 PCs running XP Pro and one file server running Win2000-all new
> eqpt.
>
> Very basic no frills office environment.
>
> Not sure what mode current install is in (don't think it matters...)
>
> We would like to run pmail from the server with one public mailbox for
> the business email. Right now, only one person can get to emial on one
> PC. No need for multiple mailboxes or users. Very basic. I understand
> that there may need to be multiple user accts...
>
> I see where I can install pmail on the server physically-but what
> would be the best mode Multiuser or Network-assuming Network, but what
> would the differences be between the modes?
Here's the basic Pegasus Mail Multiuser process. I've thrown Mercury/32 into the loop since an office environment with multiple users really should be using it.
1. Install WinPmail in the multiuser mode on the Win2000 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.
>
> Do I understand correctly that I would need to install pmail on each
> PC, or can we drop a shortcut on each PC desktop and run it down the
> wirefrom the server?
>
> Lastly, if I can install it on the server and run it from the server,
> I would need to set up one public tree and get the mail to run through
> it just like it is on the single PC.
>
> Please feel free to offer as much detail as desired. Would like to
> get this set up and working the first time around. And keep the
> existing mail if possible, but not a huge deal if not, there is only
> 5-10 email a day and they are deleted within a week. Like I said-very
> basic business operations. Nothing complicated. Thanks
If you want to maintain the existing mail copy the existing mail to the server to c:\pmail\mail\admin before doing the install in step 1.
>
> Andrew
Thanks for the replay, i did pull the newest version down to the server and installed it. Unless i really missed something, it never prompted me to choose single, multi, or network. I only rember dial-up or network. Tools, About, Info shows it installed in standalone mode.
No one will be sending each other email with this program. I only want to make the mail folder available to two other workstaions, and that really will mean only one other one, the third one will probably never look at it anyway. Basically, they use this app as the mail client for the business, but there are very few emails running through this. THe majority of communications is with 3-4 other companies. I really need to keep this simple.
I want the 2-3 workstatins to see the same mail folder. I think I can do this with a public folder, but not sure how to get the mail pop into and out of the public folder-it may not work this way.
I want the 2-3 workstations to see the same mail folder. I think I can
do this with a public folder, but not sure how to get the mail pop into
and out of the public folder-it may not work this way.
The public folder is not accessible via either POP3 nor IMAP4. This best way to do this is with a regular mailbox and IMAP4. Multiple users can connect to the same mailbox using IMAP4 via Mercury/32.
Um, poor choice of words on my part. Not using "POP" mail. Using the pmail app either running standalone app on each workstation or (prefered) running the app from the server down the wire.
I want the 2-3 people to be able to open pmail and see the same mailbox. And see the archive or "old" mail folders that they have saved.
My question was trying to understand how to get the mail out of the traditional "inbox and into the public folder automatically, or eliminate the traditional "inbox" altogether or make it transparent-it's there cause it has to be but no one knows it or messes with it....this is all fluid and flexable. It doesen't matter to me how I get there, I just don't have the necessary understanding of the product I need. I think what I want to do can be done, I just need to work out a few things.
It sounds like you need a NewMail rule, that is called when either opening or closing, that uses the "always do" action, and select Move to move each message to the public folder.
Martin
I saw in the guide that i could use a new mail rule. It may come to that.
Would like to revisit this issue and see if I can make some progress.
Can someone address the install in the server? I pulled the latest version and installed on a win 2003 server edition platform. I watched for the prompt for Stand alone, multiuser or network. I never got that prompt. When it was done i checked and the details show it installed as Standalone. So, do I uninstall it and try again? I know I didn't miss it. Or am I missing something...
I'll try and take this one issue at a time untill I get it done. Thanks!
