Michael,

>>>When I run the DTS package (using execute package) the mail gets sent. However if it is done as a scheduled task, then the jobs gets stuck at this point.

>When you manually run the package, say from your workstation, it's running using your identity. When you schedule it, it uses the identity configured in the job.

>Make sure that the identity used by SQL Server is NOT the local system account. Try using a Domain account that you know has access to Exchange.

The package runs correctly from the SQL Server. The SQL Server is logged into a Domain account (ntadmin) and the package will run when executing it directly on the server (using execute package).

It is only when the package is scheduled that I have the problem. I have bypassed similar problems when connecting to a remote server which requires a different password to the normal domain account by using the NET USE command as the first step in the schedule. This has to be done because SQL Server Agent uses a new session for running the scheduled job. There must be an equivalence for Exchange, but I can't figure it out!

Any ideas?

Cheers
Steve Lea