smtpclient

It appears that .NET's SmtpClient is creating emails with an extra dot in host names if the dot was to appear at the beginning of a MIME encoded line (e.g. test.com sometimes shows up as test..com). Example code: [TestMethod] public void TestEmailIssue() { var mail = new System.Net.Mail.MailMessage(); var smtpClient = new System.Net.Mail.SmtpClient(); mail.To.Add("Test@test.com"); mail.Subject = "Test"; mail.From = new System.Net.Mail.MailAddress("test@test.com"); mail.Body = "Hello this is a short test of the issue:" +" <a href='https://test.com/'>https://test.com/</a>: "; smtpClient

I need to validate the username and password set in an SmtpClient instance before sending mail. Using this code: SmtpClient client = new SmtpClient(host); client.Credentials = new NetworkCredential(username,password); client.UseDefaultCredentials = false; // Here I need to verify the credentials(i.e. username and password) client.Send(mail); How can I validate whether the user identified by the credentials is allowed to connect and send a mail? There is no way. SmtpClient bascially can not validate the usernamepassword without contacting the serve it connects to. What you could do is do it

This is related to a question I asked the other day on how to send email . My new, related question is this... what if the user of my application is behind a firewall or some other reason why the line client.Send(mail) won't work... After the lines: SmtpClient client = new SmtpClient("mysmtpserver.com", myportID); client.Credentials = new System.Net.NetworkCredential("myusername.com", "mypassword"); is there something I can do to test client before I try sending? I thought about putting this in a try/catch loop, but I'd rather do a test and then pop up a dialog saying: can't access smtp or

For educational purposes, I need to send an email through an SMTP server, using SMTP's fundamental and simple rules. I was able to do that using smtp4dev . I telnet localhost 25 and and commands are: I want to do the same thing, using Gmail SMTP server. However, it requires authentication and TLS. I can't figure out how to do that for Gmail. Here's a screenshot of telnet smtp.gmail.com 587 : I searched and found many links including Wikipedia's article about STARTTLS command. But I'm not able to use TLS and authenticate to Gmail's SMTP server using command line (or sending commands myself in

I'm a bit perplexed on how to manage SmtpClient now that it is disposable, especially if I make calls using SendAsync. Presumably I should not call Dispose until SendAsync completes. But should I ever call it (e.g., using "using"). The scenario is a WCF service which mails out email periodically when calls are made. Most of the computation is fast, but the sending of email can take a second or so, so Async would be preferable. Should I create a new SmtpClient each time I send mail? Should I create one for the entire WCF? Help! Update In case it makes a difference, each email is always