If you have the account information already you should be able to setup your application to use that. One way is to look at the Outlook settings to find the SMTP server they are using. Another way is to run a port scan on the network to find any server with port 25 open although the IT department should really be helping you.
I would make a point to notify your POC,point of contact, about the situation. Its rather unprofessional of them.



>Hi Douglas -
>
>I'm very interested in whatever solution you find as I have a situation that sounds similar to yours, except I have no chance to configure *anything* on the Exchange Server.
>
> I have a client with multiple small installations, all on their own DSL except for two larger ones that are behind a corporate firewall. Those are using Exchange Server instead of direct SMTP or whatever it is you call the kind of setup you would have at home with a DSL and a router.
>
>I have WWIPStuff and things work fine, until I get behind the corporate firewall and then I don't even know the name/ip address or whatever you call it of the Exchange Server and the IT department that set everything up seems unable or unwilling to give me any answers.
>
>The workstation where my app will run has email accounts. It would be fine for my app to use one of these accounts to send out email from my app.
>
>If you find a solution involving using one of the established accounts - basically anything that requires nothing of this IT department - I'd very much appreciate hearing about it.
>
>TIA
>
>
>>Yes...they will access a mail server, probably MS Exchange 5.5 or 2000. The mail server should always be behind the firewall and is not publicly accessible. The mail server would only be used by the user accounts in the domain and our application. The email from our application needs to be sent via a dummy mail account (an account that is specificially created for our application, not a real user). So...if I understand you correctly....we could use that user name and password to authenticate...as the WestWind libs now provide support for authenticated email. The reason we were thinking of IP restrictions...is that would provide a way to turn on relaying of email without opening up the server to the world of spam.
>>
>>
>>>They need to access a mail server of some sort. The best method probably is not using IP restrictions then and instead using username/password authentication.
>>>If you server is behind a firewall then ip restrictions are probably pointless anyway. If it is publicly accessible then username/password is the most common form of protection.