WLW(Windows Live Writer)是微软开发的一个离线的日志编辑软件，一定程度上实现了所见即所得。你可以使用WLW写完博文之后，然后发布到博客上去。

WLW支持博客平台，我所知道的包括Wordpress 和微软的共享空间（那是当然的喽）。

要想使用WLW在Wordpress blog（比如COST-Blog）上写日志，需要以下步骤：

1. 在博客管理界面启用XML-RPC发布协议：

首先登录自己的博客，在管理界面右上角选择“设置”，然后选择“撰写”，也就是在类似这个链接

http://blog.cost.edu.cn/你的博客/wp-admin
          /options-writing.php

的页面下方选择启用XML-RPC服务，然后保存更改；

2. 下载WLW:http://get.live.com/writer/overview

    安装WLW

3. 打开WLW，在菜单“日志”下选择“添加日志帐户”

然后选择“其他日志服务”，

下一步输入你的博客地址、用户名、口令就可以了

元旦前就动手了，到现在还没有完工，有点廉颇老矣的感觉。不过还是把搭建这个平台的过程简单记录下来吧。

早在2008年底，我就请东北大学的吴炜鑫帮我安装好了这个wordpress-mu版本，我开始琢磨plugin, themes 等等。元旦在家几乎登录不上学校的网站，想起来清华以前的学生问的一个问题，这么慢，为什么还要有个CERNET?

元旦后对付完几个报告，总算可以痛痛快快琢磨一下了。于是1月5日折腾到夜里3点。下了几个themes，在其中一个上动大手术了，还算顺利。几番移花接木，看上去很美。

一个大问题一直没有解决好：用户注册时发给用户的邮件总是收不到，比如清华的信箱。gmaild的信箱收到了，却被过滤到垃圾邮件里去了。仔细检查系统发给root的邮件，发现给清华发邮件的过程中，好像被当成垃圾邮件站点了：
  

—– Transcript of session follows —– … while talking to mta0.tsinghua.edu.cn.:
>>> STARTTLS dialogue
<<< 454 TLS missing certificate: error:02001002:system library:fopen:No such file or directory (#4.3.0)
>>> DATA
<<< 553 http://www.spamhaus.org/query/bl?ip=202.112.57.10
>>> RSET
<<< 550 Too many unexpected actions. (#5.5.0)
554 5.0.0 Service unavailable

第二天郑先伟检查后，根据CBL的解释，给出以下几条原因：
 202.112.57.10可能被列入ＣＢＬ的原因分析：
　　１、转发垃圾邮件已经排除
　　２、被入侵或感染病毒，通过流量监测也被排除
　　３、没有按照标准的格式发送邮件被ＣＢＬ检测到了，它认为这不是一台合法的邮件服务器，这是最可能的原因。
我已经申请从名单中删除地址了，但是不确定恢复时间需要多久。我们还需要做的事情包括：
　　１、在防火墙上开放202.112.57.10的２５端口　（以开放）
　　２、修改网页发送邮件的程序

这台服务器本来不是邮件服务器，sendmail没有仔细配置。发现这台机器的25端口开放以后从外面依然连不上。

郑先伟估计是sendmail.cf配置的问题，原来sendmial.cf的25端口绑在127.0.0.1上，所以外面无法连接 。改成202.112.57.10就好了。但愿CBL把它打入垃圾邮件就是这个问题，别再折腾我了。

根据CBL的要求，提交了解封的申请，不知道什么时候才能生效。

附：ＣＢＬ规则的原文

Mail Server Naming Problems
The CBL uses a variety of techniques to determine what IPs are behaving highly suspiciously and are likely have been compromised into sending spam or viruses.

You have been directed here because there is a possibility that your IP may have been listed as result of misconfiguration or broken mailer software.

Here, we’re primarily concerned with mail servers announcing non-RFC-compliant names via the HELO (NOT the welcome banner!) during SMTP port 25 connections it makes (NOT connections to it!).

However, this set of pages is intended to find out what’s wrong, whatever it is, whether it be a hostname, mailer, or autoresponder misconfiguration, or an outright machine compromise.

First and foremost, however, if this IP address is a NAT/PAT gateway/firewall/router, please read about securing your NAT first. Until you have secured your NAT/PAT (if you have one), the following instructions will be of little use.
Identifying the Problem Area
There are two basic types of detections that land an IP in this page. RFC2821 section 4.1.1.1 says that there are only two legal types of HELO/EHLO a mail server can issue - either a fully qualified domain name (eg: “mail.example.com”) or an “IP literal” (eg: “[1.2.3.4]“).

The listings that land in this page are:

HELO “localhost”, “localhost.localdomain”, and other generic “unconfigured” names.
HELOs that are bare IP addresses (without enclosing square brackets).
Listings on the former are most common in UNIX-derived systems (such as Linux, xBSD, MacOS X) etc. Alternately, it may be a misconfiguration in a mail-sending custom application, using libraries such as perl’s Net::SMTP (which must be explicitly configured to use a specific HELO string).

Listings on the latter are due to a variety of things, most often improperly configured Windows mail servers or mail applications (address verifiers, challenge/response, bulk mailers etc).

In all cases, the first thing you should do is identify whether the main mail server software is helo’ing properly. If not, it needs to be fixed. If it is helo’ing properly, you need to identify what _other_ mail sending applications (that send email direct to the recipient without going through your main mail servers) exist, and check those.