[quote user="lanwanman"]
Thomas: Thanks for your reply. The installation of Mercury server and theDepends on a couple of things. If you have a XP system laying around not doing anything i would use it. If you can tell Exchange to only use port 25 on one IP inerface and mercury/32 on the other I would run them both on the same system. It no best practice here, do what you need to in your setup.distribution list setup seem fairly straightforward. Only one thing...I'm
running an Exchange server on my network. I have some concerns. I
realize some of my concerns may beyond the scope of this forum. Any
input on the following?
1. What is best practice? Install Mercury server on the Exchange Server or on a separate server?
2. Will I be able to add my Exchange Server email domain name to Mercury server without any conflicts with Exchange Server?No, every SMTP host needs it's own domain. Or course you can use Mercury/32 as the front end to Exchange (handy for filtering, anti-spam, and anti-virus) running on a port other than port 25. Check the Mercury downloads section for the Petr Jaklin WSMTPEx program.
3. What smtp server am I using to send out the distribution list? The Exchange Server or one created by Mercury?Agains depends. Mercury/32 MercuryE can send direct or using MercuryC via the Exchange (or other SMTP host) as a relay host. I would perfer to offload the mailing list to MercuryE to keep the load off Exchange.
4. Do I need to be concerned about getting blacklisted? Why or why not?You are always concerned about blacklisting. The people getting your mailings, even if they are not on a double authenticated opt-in to the list, can quite easily report your mailing as spam and get the IP address blacklisted. I've not had that happen but then I'm only running reunion type mailing lists. If you are doing commericial type mailings it's a lot more of a problem.
[/quote]
<blockquote>[quote user="lanwanman"]</blockquote><blockquote>Thomas:&nbsp; Thanks for your reply.&nbsp; The installation of Mercury server and the
distribution list setup seem fairly straightforward. Only one thing...I'm
running an Exchange server on my network. I have some concerns. I
realize some of my concerns may beyond the scope of this forum. Any
input on the following?
1. What is best practice? Install Mercury server on the Exchange Server or on a separate server?</blockquote>Depends on a couple of things.&nbsp; If you have a XP system laying around not doing anything i would use it.&nbsp; If you can tell Exchange to only use port 25 on one IP inerface and mercury/32 on the other I would run them both on the same system.&nbsp; It no best practice here, do what you need to in your setup.
<blockquote>2. Will I be able to add my Exchange Server email domain name to Mercury server without any conflicts with Exchange Server?</blockquote>No, every SMTP host needs it's own domain.&nbsp; Or course you can use Mercury/32 as the front end to Exchange (handy for filtering, anti-spam, and anti-virus) running on a port other than port 25.&nbsp; Check the Mercury downloads section for the Petr Jaklin WSMTPEx program.&nbsp;
<blockquote>3. What smtp server am I using to send out the distribution list? The Exchange Server or one created by Mercury?</blockquote>Agains depends.&nbsp; Mercury/32 MercuryE can send direct or using MercuryC via the Exchange (or other SMTP host) as a relay host.&nbsp; I would perfer to offload the mailing list to MercuryE to keep the load off Exchange.
<blockquote>4. Do I need to be concerned about getting blacklisted? Why or why not?</blockquote>You are always concerned about blacklisting.&nbsp; The people getting your mailings, even if they are not on a double authenticated opt-in to the list, can quite easily report your mailing as spam and get the IP address blacklisted. I've not had that happen but then I'm only running reunion type mailing lists.&nbsp; If you are doing commericial type mailings it's a lot more of a problem.
<blockquote>[/quote]</blockquote>
