I've been using various versions of Mercury for some four years now on my home network; It's fully functioned with more features added every release. I can confirm that installation and configuration is really simple and you just can't argue with the price. Mercury also offers integration with Novell NetWare (not that I need it).
Mercury's only failing? It's hard to find on most Software Distribution web sites and conequently, relativly few people seem to use it. Last time I looked, there werealso no proposals to port it to UNIX of any flavour (but then, there's no shortage of mail servers there). A great package!
Discussion on:
View:
Show:
I am totally agreed with Mr. David Heydecker.
I have been also using Mercury/32 for the last 3.5 years on my home IP lan and found it extremely cool. I have checked it with various proxies & firewalls and it worked smoothly with everything in everycondition.
It is extremely flexible and not in any way inferior than any commercial product.
I have been also using Mercury/32 for the last 3.5 years on my home IP lan and found it extremely cool. I have checked it with various proxies & firewalls and it worked smoothly with everything in everycondition.
It is extremely flexible and not in any way inferior than any commercial product.
Thanks so much for your feedback. I have used Pegasus since WFW was The Windows OS. I have always been happy with its' response and security.
I've always been the one in the back row, vaunting the value of Mercury/32 and Pegasus, and now it is good to see such positive replies.
Thank you.
I've always been the one in the back row, vaunting the value of Mercury/32 and Pegasus, and now it is good to see such positive replies.
Thank you.
Having used Mercury to support a small LAN for many years, I've gained a few insights and ideas that might be helpful to those considering this excellent E-mail server:
1. You can configure your clients to send all mail via SMTP, thus eliminatingthe need for a publicly-accessible mail queue. This also means somewhat better security since Mercury's working directories need not be shared and need no global permissions. It also reduces disk I/O on the Mercury server somewhat, since requests come in "over the wire" rather than on disk
2. Configure Pegasus to send all mail through Mercury, so that Pegasus users do not need write access to each others' inbox directories
3. Make liberal use of Mercury's mailing list feature. It is fast and works at least as well as Exchange groups. Encourage your users to use distribution lists for their own mass mailings.
Kudos to David Harris and team for this excellent program! (Now if he can just manage better integration with Windows NT...)
1. You can configure your clients to send all mail via SMTP, thus eliminatingthe need for a publicly-accessible mail queue. This also means somewhat better security since Mercury's working directories need not be shared and need no global permissions. It also reduces disk I/O on the Mercury server somewhat, since requests come in "over the wire" rather than on disk
2. Configure Pegasus to send all mail through Mercury, so that Pegasus users do not need write access to each others' inbox directories
3. Make liberal use of Mercury's mailing list feature. It is fast and works at least as well as Exchange groups. Encourage your users to use distribution lists for their own mass mailings.
Kudos to David Harris and team for this excellent program! (Now if he can just manage better integration with Windows NT...)
I have a non-profit I arranged a server to be donated to, they need an internal email server- Mercury looks great, I am going to give it a try.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
