cdo发送邮件问题 如果此路行不通,还有没有其它发邮件的方法不用有争议的组件,不过CDO这个东西发邮件还真简单,不用验证,一发就出,有点舍不得放下 解决方案 » 免费领取超大流量手机卡,每月29元包185G流量+100分钟通话, 中国电信官方发货 帮你找了一点动东 ,我是没有用过,贴过来你看看 *******************************************************使用Socket撰写邮件发送程序 当然,如果您觉得SmtpMail不能满足您的需求,CDO又不够直截了当,那就只能自己动手了;其实如果您很熟悉Socket编程,自己写一个发送邮件的程序并不很难,以下就是一个例子。首先,我们简单介绍一下带验证的SMTP服务器如何使用AUTH原语进行身份验证,其详细的定义可以参考RFC2554。具体如下:1)首先,需要使用EHLO而不是原先的HELO。2)EHLO成功以后,客户端需要发送AUTH原语,与服务器就认证时用户名和密码的传递方式进行协商。3)如果协商成功,服务器会返回以3开头的结果码,这是就可以把用户名和密码传给服务器。4)最后,如果验证成功,就可以开始发信了。下面是一个实际的例子,客户端在WinXP的Command窗口中通过"telnet smtp.263.NET 25"命令连接到263的smtp服务器发信:220 Welcome to coremail System(With Anti-Spam) 2.1EHLO 263.NET250-192.168.30.29250-PIPELINING250-SIZE 10240000250-ETRN250-AUTH LOGIN250 8BITMIMEAUTH LOGIN334 VXNlcm5hbWU6bXlhY2NvdW50334 UGFzc3dvcmQ6bXlwYXNzd29yZA==235 Authentication successfulMAIL FROM:[email protected]250 OkRCPT TO:[email protected]250 OkData354 End data with <CR><LF>.<CR><LF>This is a testing email.haha..250 Ok: queued as AC5291D6406C4QUIT221 Bye上面的内容就是发信的全过程。其中与身份验证有关的主要是第九到第十四行:AUTH LOGIN "客户端输入334 VXNlcm5hbWU6 "服务器提示“Username:="bXlhY2NvdW50 "客户端输入“myaccount="的Base64编码334 UGFzc3dvcmQ6 "服务器提示“Password:="bXlwYXNzd29yZA== "客户端输入“mypassword="的Base64编码235 Authentication successful "服务器端通过验证从上面的分析可以看出,在这个身份验证过程中,服务器和客户端都直接通过Socket传递经过标准Base64编码的纯文本。这个过程可以非常方便的用C#实现,或者直接添加到原有的源代码中。另外,有些ESMTP服务器不支持AUTH LOGIN方式的认证,只支持AUTH CRAM-MD5方式验证。但是这两者之间的区别只是文本的编码方式不同。实现此功能的源代码可以在SourceForge.NET http://sourceforge.NET/projects/opensmtp-net/ 上找到下载。下面给出了一个简单的伪码:public void SendMail(MailMessage msg) { NetworkStream nwstream = GetConnection(); WriteToStream(ref nwstream, "EHLO " + smtpHost + "\r\n"); string welcomeMsg = ReadFromStream(ref nwstream); // implement HELO command if EHLO is unrecognized. if (IsUnknownCommand(welcomeMsg)) { WriteToStream(ref nwstream, "HELO " + smtpHost + "\r\n"); } CheckForError(welcomeMsg, ReplyConstants.OK); // Authentication is used if the u/p are supplied AuthLogin(ref nwstream); WriteToStream(ref nwstream, "MAIL FROM: <" + msg.From.Address + ">\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.OK); SendRecipientList(ref nwstream, msg.To); SendRecipientList(ref nwstream, msg.CC); SendRecipientList(ref nwstream, msg.BCC); WriteToStream(ref nwstream, "DATA\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.START_INPUT); if (msg.ReplyTo.Name != null && msg.ReplyTo.Name.Length != 0) { WriteToStream(ref nwstream, "Reply-To: \"" + msg.ReplyTo.Name + "\" <" + msg.ReplyTo.Address + ">\r\n"); } else { WriteToStream(ref nwstream, "Reply-To: <" + msg.ReplyTo.Address + ">\r\n"); } if (msg.From.Name != null && msg.From.Name.Length != 0) { WriteToStream(ref nwstream, "From: \"" + msg.From.Name + "\" <" + msg.From.Address + ">\r\n"); } else { WriteToStream(ref nwstream, "From: <" + msg.From.Address + ">\r\n"); } WriteToStream(ref nwstream, "To: " + CreateAddressList(msg.To) + "\r\n"); if (msg.CC.Count != 0) { WriteToStream(ref nwstream, "CC: " + CreateAddressList(msg.CC) + "\r\n"); } WriteToStream(ref nwstream, "Subject: " + msg.Subject + "\r\n"); if (msg.Priority != null) { WriteToStream(ref nwstream, "X-Priority: " + msg.Priority + "\r\n"); } if (msg.Headers.Count > 0) { SendHeaders(ref nwstream, msg); } if (msg.Attachments.Count > 0 || msg.HtmlBody != null) { SendMessageBody(ref nwstream, msg); } else { WriteToStream(ref nwstream, msg.Body + "\r\n"); } WriteToStream(ref nwstream, "\r\n.\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.OK); WriteToStream(ref nwstream, "QUIT\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.QUIT); CloseConnection();}private bool AuthLogin(ref NetworkStream nwstream){if (username != null && username.Length > 0 && password != null && password.Length > 0){ WriteToStream(ref nwstream, "AUTH LOGIN\r\n"); if (AuthImplemented(ReadFromStream(ref nwstream))) { WriteToStream(ref nwstream, Convert.ToBase64String( Encoding.ASCII.GetBytes(this.username.ToCharArray())) + "\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.SERVER_CHALLENGE); WriteToStream(ref nwstream, Convert.ToBase64String(Encoding.ASCII.GetBytes( this.password.ToCharArray())) + "\r\n"); CheckForError(ReadFromStream(ref nwstream), ReplyConstants.AUTH_SUCCESSFUL); return true; }}return false;} 我用cdo 组件发email 换了几个空间,没有什么问题 ? 奇怪 在微软中国社区帮你找到的一点资料CDO是Collaboration Data Objects的简称,它是一组高层的COM对象集合,并经历了好几个版本的演化,现在在Windows2000和Exchange2000中使用的都是CDO2.0的版本(分别为cdosys.dll和cdoex.dll)。CDOSYS构建在SMTP协议和NNTP协议之上,并且作为Windows2000 Server的组件被安装,您可以在系统目录(如c:\winnt或c:\windows)的system32子目录中找到它(cdosys.dll)。由于Exchange2000的CDO组件cdoex.dll会更新原有的Windows2000的CDO组件cdosys.dll,所以如果您希望继续使用cdosys.dll,您必须先通过regsrv32.exe卸载掉cdoex.dll。 在做论坛的时候遇到两个难题,希望大家帮帮忙。 label控件调用 创建文件夹的问题 源码.. 一个页面里的事件触发另一页面里的事件??怎么写 今天高兴,散分 请进,帮忙解决这个问题!!!! 大家救救我吧! 怎么样在installshield建立虚拟目录 如此问题,真是令人费解----各位兄弟,请进来看一下 求教这段程序用vb.net 该如何写? 翻越了五座大山,终于看到星星了!散分!顺祝大家国庆快乐!
*******************************************************
使用Socket撰写邮件发送程序
当然,如果您觉得SmtpMail不能满足您的需求,CDO又不够直截了当,那就只能自己动手了;其实如果您很熟悉Socket编程,自己写一个发送邮件的程序并不很难,以下就是一个例子。
首先,我们简单介绍一下带验证的SMTP服务器如何使用AUTH原语进行身份验证,其详细的定义可以参考RFC2554。
具体如下:
1)首先,需要使用EHLO而不是原先的HELO。
2)EHLO成功以后,客户端需要发送AUTH原语,与服务器就认证时用户名和密码的传递方式进行协商。
3)如果协商成功,服务器会返回以3开头的结果码,这是就可以把用户名和密码传给服务器。
4)最后,如果验证成功,就可以开始发信了。
下面是一个实际的例子,客户端在WinXP的Command窗口中通过"telnet smtp.263.NET 25"命令连接到263的smtp服务器发信:
220 Welcome to coremail System(With Anti-Spam) 2.1
EHLO 263.NET
250-192.168.30.29
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-AUTH LOGIN
250 8BITMIME
AUTH LOGIN
334 VXNlcm5hbWU6
bXlhY2NvdW50
334 UGFzc3dvcmQ6
bXlwYXNzd29yZA==
235 Authentication successful
MAIL FROM:[email protected]
250 Ok
RCPT TO:[email protected]
250 Ok
Data
354 End data with <CR><LF>.<CR><LF>
This is a testing email.
haha.
.
250 Ok: queued as AC5291D6406C4
QUIT
221 Bye上面的内容就是发信的全过程。其中与身份验证有关的主要是第九到第十四行:
AUTH LOGIN "客户端输入
334 VXNlcm5hbWU6 "服务器提示“Username:="
bXlhY2NvdW50 "客户端输入“myaccount="的Base64编码
334 UGFzc3dvcmQ6 "服务器提示“Password:="
bXlwYXNzd29yZA== "客户端输入“mypassword="的Base64编码
235 Authentication successful "服务器端通过验证
从上面的分析可以看出,在这个身份验证过程中,服务器和客户端都直接通过Socket传递经过标准Base64编码的纯文本。这个过程可以非常方便的用C#实现,或者直接添加到原有的源代码中。
另外,有些ESMTP服务器不支持AUTH LOGIN方式的认证,只支持AUTH CRAM-MD5方式验证。但是这两者之间的区别只是文本的编码方式不同。
实现此功能的源代码可以在SourceForge.NET http://sourceforge.NET/projects/opensmtp-net/ 上找到下载。下面给出了一个简单的伪码:
public void SendMail(MailMessage msg)
{
NetworkStream nwstream = GetConnection(); WriteToStream(ref nwstream, "EHLO " + smtpHost + "\r\n");
string welcomeMsg = ReadFromStream(ref nwstream); // implement HELO command if EHLO is unrecognized.
if (IsUnknownCommand(welcomeMsg))
{
WriteToStream(ref nwstream, "HELO " + smtpHost + "\r\n");
}
CheckForError(welcomeMsg, ReplyConstants.OK); // Authentication is used if the u/p are supplied
AuthLogin(ref nwstream); WriteToStream(ref nwstream, "MAIL FROM: <" + msg.From.Address + ">\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.OK); SendRecipientList(ref nwstream, msg.To);
SendRecipientList(ref nwstream, msg.CC);
SendRecipientList(ref nwstream, msg.BCC); WriteToStream(ref nwstream, "DATA\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.START_INPUT); if (msg.ReplyTo.Name != null && msg.ReplyTo.Name.Length != 0)
{ WriteToStream(ref nwstream, "Reply-To: \"" + msg.ReplyTo.Name + "\" <" +
msg.ReplyTo.Address + ">\r\n"); }
else
{ WriteToStream(ref nwstream, "Reply-To: <" + msg.ReplyTo.Address + ">\r\n"); }
if (msg.From.Name != null && msg.From.Name.Length != 0)
{ WriteToStream(ref nwstream, "From: \"" + msg.From.Name + "\" <" +
msg.From.Address + ">\r\n"); }
else
{ WriteToStream(ref nwstream, "From: <" + msg.From.Address + ">\r\n"); }
WriteToStream(ref nwstream, "To: " + CreateAddressList(msg.To) + "\r\n");
if (msg.CC.Count != 0)
{ WriteToStream(ref nwstream, "CC: " + CreateAddressList(msg.CC) + "\r\n"); } WriteToStream(ref nwstream, "Subject: " + msg.Subject + "\r\n"); if (msg.Priority != null)
{ WriteToStream(ref nwstream, "X-Priority: " + msg.Priority + "\r\n"); } if (msg.Headers.Count > 0)
{
SendHeaders(ref nwstream, msg);
}
if (msg.Attachments.Count > 0 || msg.HtmlBody != null)
{
SendMessageBody(ref nwstream, msg);
}
else
{
WriteToStream(ref nwstream, msg.Body + "\r\n");
}
WriteToStream(ref nwstream, "\r\n.\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.OK);
WriteToStream(ref nwstream, "QUIT\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.QUIT);
CloseConnection();
}private bool AuthLogin(ref NetworkStream nwstream)
{
if (username != null && username.Length > 0 && password != null && password.Length > 0)
{
WriteToStream(ref nwstream, "AUTH LOGIN\r\n");
if (AuthImplemented(ReadFromStream(ref nwstream)))
{
WriteToStream(ref nwstream, Convert.ToBase64String(
Encoding.ASCII.GetBytes(this.username.ToCharArray())) + "\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.SERVER_CHALLENGE);
WriteToStream(ref nwstream, Convert.ToBase64String(Encoding.ASCII.GetBytes(
this.password.ToCharArray())) + "\r\n");
CheckForError(ReadFromStream(ref nwstream), ReplyConstants.AUTH_SUCCESSFUL);
return true;
}
}
return false;
}
CDO是Collaboration Data Objects的简称,它是一组高层的COM对象集合,并经历了好几个版本的演化,现在在Windows2000和Exchange2000中使用的都是CDO2.0的版本(分别为cdosys.dll和cdoex.dll)。CDOSYS构建在SMTP协议和NNTP协议之上,并且作为Windows2000 Server的组件被安装,您可以在系统目录(如c:\winnt或c:\windows)的system32子目录中找到它(cdosys.dll)。
由于Exchange2000的CDO组件cdoex.dll会更新原有的Windows2000的CDO组件cdosys.dll,所以如果您希望继续使用cdosys.dll,您必须先通过regsrv32.exe卸载掉cdoex.dll。