John...

Thanks for the great suggestion. I think that it will provide a good alternative for those places that don't want to turn on relaying en masse from their real mail server.

Thanks again...

...Douglas

>Douglas,
>
>Have you considered setting up your own mail server using IIS and SMTP Virtual Server on a server you might have control over? Once that is done you can use the 'real' mail server as the smart host, therefore the smart host will only need to relay from the server you configure, and you can set up all the relays you wish to the virtual server. We use Lotus Notes, and SQL Server does not play well with it at all, but using SMTP Virtual Server proved to be a viable alternative that our administrators accepted because they wanted everything to route through Notes vs. us setting up our own Exchange Server. Basically SQL Server's sends mail to the virtual server which hands it off to the smart host.
>
>Anyway it might give you some ideas.
>
>John
>
>>Hello....
>>
>>We are planning on adding a feature to our existing vfp app that will allow users to email reports. At the moment, I am looking at using one packages from West-Wind (wwIPStuff), Marshall (See4FP) or IDS-Mail. (also CDONTS)
>>
>>I am figuring that we'll go the SMTP route rather than MAPI.
>>
>>My questions concern more of what will be required on the customer end of things. I have read about the need for Relaying to be turned on at the mail server. In fact, I ran the west-wind sample code yesterday and encountered the error "550 - Relaying prohibited". When I spoke with our network admin about this, he was reluctant to turn on relaying. He suggested that this might be the case when we need to install on our customer's systems too. Has anyone else encountered this response? If so, is there any way around this? And, are there any other requirements for the user's mail server to be able to accept email requests (send/receive) from a vfp app??
>>
>>Thanks.....
>> Douglas