I want to send email from my ASP.NET and Web service application,So I use SmtpMail and MailMessage class, In my developing computer I didn't do any setting(I mean Virtual Mail Server in IIS) but when I use my dial up connection and my mail server(both are from the same ISP),it works OK(if I use another dialup connection from another ISP it does not work). Now my question is if I upload my application and I use mail server in that domain, can I be sure that it will send emails?
This all comes down to configuring your SMTP server. When you connect to one ISP, your SMTP Virtual Server routes messages to it and your ISP allows it either because they allowing relaying from anywhere (EXTREMELY stupid and the cause for a lot of SPAM being sent) or from connected clients. The other ISP probably doesn't allow you to relay either because they don't allow relaying from clients at all, or because your SMTP Virtual Server is configured to use a domain that it won't relay (like the domain for your other ISP).
When you put the application on a production server, make sure it has CDO installed, either from the SMTP Virtual Services or from Microsoft Exchange, either of which is a CDO server. These must be configured correctly to either relay mail for their own domain (which pretty much goes without saying) or to forward to anther SMTP server to relay the messages (which is what your SMTP Virtual Services on your workstation is doing).
Heath Stewart wrote: When you put the application on a production server, make sure it has CDO installed, either from the SMTP Virtual Services or from Microsoft Exchange, either of which is a CDO server.
I still do not register any domain, my customer have to do it, but I have to tell him the requirements. What does CDO stands for?(Abbreviate of what), does SMTP Virtual Service is an UI tools which is availabe for the admin of users and isn't it automaticlly set usually or always should be registered by hand? Sorry, maybe these are dumb questions but I don't have so much admining experience.
CDO is Collaborative Data Objects, and your clients don't have to worry about that. It's a simple MAPI COM server (or extended MAPI, don't remember off-hand) for client applications to use. Both the SMTP Virutal Services and Microsoft Exchange provide CDO. All they need to worry about is that their SMTP server - no matter what it is - is configured properly, which most likely isn't a problem since - if it wasn't - no mail will be sent and received. Also note that the SmtpMail.SmtpServer doesn't have to be the localhost.
It pretty good and easy to use. Currently I have it in several of my websites for mail delivery. Have never had bug of any type. Nice part is that there is no configuring of the server machine you are using as with .NET's built in mail handling. Makes it really easy to deploy.
Sorry for disturb you again. I download the source code zip files,but afetr it complete the download and I try to open it,it say its corrupted file. Would you please do me a favor and send me that zip file.I don't know whats the problem with it.
About that OpenSmtp Server, I got in a problem. Could you tell me how do you use when you want to so authentication? It seems its just some lines but I can't do it.I post some message in its furom too but could tell me somme sample code too?
About that OpenSmtp Server, I got in a problem. Could you tell me how do you use when you want to so authentication? It seems its just some lines but I can't do it.I post some message in its furom too but could tell me somme sample code too? Thanks