vesselescape
IS-IT--Management
Re: GNet2k
We use Mercury as well. Have multiple isp based email accounts, and Mercury will poll all accounts in whatever order and timeframe you specify. Mail can be routed in a number of ways.
Example:
Pop Boxes on
default@mydomain.com
help@mydomain.com
info@mydomain.com
Pop Box on anotherdomain.com
ourcompany@anotherdomain.com
Local Users
user1
user2
user3
help
main
Routing
Remote pop boxes polled by mercury every 30 seconds.
All mail not adderessed to specific box on (ie: info@mydomain.com or help@mydomain.com) is routed to the default@mydomain.com pop box by the isp's mailserver. (eg: user1@mydomain.com)
After retreiving remote mail, Mercury examines to: fields and routes mail to local boxes if it finds them. (eg: user1@mydomain.com) Unknown addresses are routed to "main" user mail box for sorting by designated party. Mail to "help" is routed to "user2" (using alias "help@mydomain.com = user2@mydomain.com) Mail to "user3" is routed to local mailbox and forwarded to user3@iamonvacation.com as well.
All mail address to ourcompany@anotherdomain.com is routed to "main"
All local mail is routed to appropriate user by Mercury. All outbound mail is delivered to the smtp server at for delivery.
Only took about one hour to set up and configure Mercury on a win2k network. Using Pegasus mail as a client. They were written to work together, and we have been using Pegasus for about 6 years now.
Mercury should probably be run as a service under win2k. It does not write to the registry, so if you do not like the way it works, removal has mininum impact on the network.
We use Mercury as well. Have multiple isp based email accounts, and Mercury will poll all accounts in whatever order and timeframe you specify. Mail can be routed in a number of ways.
Example:
Pop Boxes on
default@mydomain.com
help@mydomain.com
info@mydomain.com
Pop Box on anotherdomain.com
ourcompany@anotherdomain.com
Local Users
user1
user2
user3
help
main
Routing
Remote pop boxes polled by mercury every 30 seconds.
All mail not adderessed to specific box on (ie: info@mydomain.com or help@mydomain.com) is routed to the default@mydomain.com pop box by the isp's mailserver. (eg: user1@mydomain.com)
After retreiving remote mail, Mercury examines to: fields and routes mail to local boxes if it finds them. (eg: user1@mydomain.com) Unknown addresses are routed to "main" user mail box for sorting by designated party. Mail to "help" is routed to "user2" (using alias "help@mydomain.com = user2@mydomain.com) Mail to "user3" is routed to local mailbox and forwarded to user3@iamonvacation.com as well.
All mail address to ourcompany@anotherdomain.com is routed to "main"
All local mail is routed to appropriate user by Mercury. All outbound mail is delivered to the smtp server at for delivery.
Only took about one hour to set up and configure Mercury on a win2k network. Using Pegasus mail as a client. They were written to work together, and we have been using Pegasus for about 6 years now.
Mercury should probably be run as a service under win2k. It does not write to the registry, so if you do not like the way it works, removal has mininum impact on the network.