CDOSYS on WinXP Pro [RESOLVED][AH HAHAHAHA]

Does anyone know about configuring CDOSYS on XP Pro or in general.

I talk about tthis in this thread: http://vbforums.com/showthread.php?s=&threadid=304934

It's towards the end. I'm pretty hung up here. I can't complete my testing until I resolve this.

I have tried setting the SmtpServer property but I get on of two errors depending on if I use my default smtp on my local machine or if I try to use the actual smtp on the our host.

For local I get cannot connect to server and for the host I get authintication required or not a gateway.

The host is no help here. The guy hates me because he keeps screwing up the e-mail settings..... last week he had the IMAP setup as shared and I could read all the e-mail for all the websites he hosts some of them being credit union sites...... yet he hates me for telling him........ guy is a real jerk......

Sometimes if I get totally hung up, I take a completely different tack. There's this older email system that was really popular around 1999 called JMAIL. I just did a search and saw some references to it on the web. JMAIL is free ASP component.

Anyway, depending on your projects requirements, you could conceivably test using JMAIL until you can figure out what's going on with CDOSYS. Also, sometimes working with a different system, will shed light on the problems with the system that's not working.

Another thing I've used in the past is CDONTS. Is that not available in XP?

cudabean

To be honest I don't know about CDONTS on WinXP. I'm pretty frazzled right now. I have to handle all the customer end of everything and the coding end. I'm behind schedule and I haven't been getting any sleep. Man can I whine or what....

I will look into the JMAIL though. I'm actually thinking of just doing a hack to bypass the e-mail if the site is running on my local machine. I mean since it works on the server and the e-mail code is straight forward I could work around it in test. I have to have three meetings about doing this though(#$%^**@)

Why is it that the problems that take the longest to fix are always so simple...?

Code:

---

System.Web.Mail.SmtpMail.SmtpServer = System.Environment.MachineName;

---