[quote user="royhink"]

I would really appreciate some configuration pointers as I am a non-IT Tech trying to install Mercury32 on my Win2003 server.

This install only needs to handle outgoing email thru our smtp host, Rackspace, which requires authentication. Plus, there is only 3 'users', the three ShopSite eCommerce platforms on the server. ShopSite sends out a confirmation email after the purchase.[/quote]
Before going any further, I want to be absolutely clear on something...  Those "ShopSite eCommerce platforms" are running on the same server that you have installed Mercury on, right?  I'm going to continue based on that assumption; but if it's wrong, PLEASE say so ASAP.

[quote]ShopSite simply asks for a smtp host name.[/quote]
That should be OK -- i.e., not a problem.

[quote]I've installed Mercury32 with  MercuryS, MercuryC and MercuryX,[/quote]
I agree with "dilberts_left_nut" on this one -- you do not need the MercuryX module for this application; and in the interest of simplicity, you probably ought to disable it.

[quote]and configured MercuryC with the host name and credentials, and get the following:

Sendmail failed; SMTP server error: 553 We do not relay non-local mail, sorry.[/quote]
This is of course the critical part; but here, I'm not nearly so certain that "dilberts_left_nut" was correct.  The mention of Sendmail implies that it may be your smarthosting provider (i.e., Rackspace) which is generating that error message.  If that is correct, then it would seem that MercuryC is failing to properly authenticate itself with Rackspace's SMTP server.  I suggest that you double-check the MercC configuration settings, especially make sure that "Authenticate via prior POP3 connection" is NOT checked, and that you have correctly entered the username and password that Rackspace gave you in the appropriate fields (yes, upper/lower case counts!).

[quote]I also want to be sure that it is restricted to only sending from the ShopSite stores.[/quote]
Way back when I first set up Mercury (v3.01, IIRC), I needed to do something similar because the server itself was co-located some 3,000 miles away, and effectively open to the general internet (hence, proper authentication and strict relaying control was absolutely required); but the mail client (a very old version of Eudora) that I was loathe to abandon (and still am, mostly -- at least to the degree that I still use Windows at all, which is waning steadily) did not support SMTP AUTH.  My solution was to run two copies of Mercury...  One on a local box to which my desktop system(s) could connect to directly via the LAN, which in turn relayed to the "real" mail server at the co-lo site.  This scenario largely mimics your situation; where the "local copy" is analogous to your Merc install, and my co-located and remotely administered Merc server corresponds to your smarthosting provider's (i.e. Rackspace's) SMTP server.  The key to making it all work, while still keeping it secure, was to create two specific entries in the "Connection Control" pane of the (local) MercS configuration screen:  Namely, a general "Refuse" definition for the entire IPv4 netspace (0.0.0.0 - 255.255.255.255), followed by an "Allow" entry for just the local LAN segment (192.168.0.0 - 192.168.0.255), then UNcheck all four checkboxes under "Relaying control".  With this setup, any workstation on my local network could connect to the local copy of Merc and relay mail through it, without needing to use SMTP AUTH (or any authentication at all, for that matter); but since ONLY clients on my local network could connect to it at all, it was still protected against unauthorized relaying (such as by spammers).

[quote]Any help greatly appreciated.[/quote]
You're quite welcome.  I hope this has been helpful.

I would really appreciate some configuration pointers as I am a non-IT Tech trying to install Mercury32 on my Win2003 server.

 This install only needs to handle outgoing email thru our smtp host, Rackspace, which requires authentication. Plus, there is only 3 'users', the three ShopSite eCommerce platforms on the server. ShopSite sends out a confirmation email after the purchase.

ShopSite simply asks for a smtp host name.

I've installed Mercury32 with  MercuryS, MercuryC and MercuryX, and configured MercuryC with the host name and credentials, and get the following:

Sendmail failed; SMTP server error: 553 We do not relay non-local mail,

sorry.

I also want to be sure that it is restricted to only sending from the ShopSite stores.

 Any help greatly appreciated.

That error is generated by MercS, denying relaying to your script.

Read the help section on "Local Domains" and "Relaying Restrictions".

You probably don't need MercX, but if you do, there is a patch to fix a bug in it in the Download section of the forum.

MercP or I should also be there to monitor the admin account.

Thanks for the quick reply.

I modified the relay restrictions and Mercury32 is sending out emails.

Just so I understand, with these settings, only WTP3 can use Mercury to send emails, correct?

Maybe. It depends of course on how you modified the relaying restrictions.

In MercuryS configuration, Connection control at least "Use strict local relaying restrictions" should be checked. You should allow your webshops to send mail by adding a connection control entry for the IP address or IP range used with "Connections from this address range may relay mail though this server" checked. (Or you could use authentication.)

/Rolf