Max's Blog

昨晚小汪子过来，看见偶统计ip的程序，说。。。其实一行就可以做到了。。。

cat access_log|awk ‘{print $1}’|sort |uniq -c|sort -nr

 狂晕ing，对linux命令还是不熟悉啊。。。

今天mima的tomcat又挂掉了，写一段够短的程序分析一下独立ip数量。。。

本来用sed写，写到一半好像写不下去了。。。

cat access_log | sed “s/ – – .*//”  |sort |????

然后用perl写了一个

perl countip.pl access_log |head

countip.pl

#!/usr/bin/perl
while(<>){
                chomp();
                $_ =~ s/ – – .+//g;
                $count{$_}++;
}
foreach $word (sort by_count keys %count){
        print “$word occurs $count{$word} times\n”;
}
sub by_count {
        $count{$b} <=> $count{$a}
}

sort使用了一个子例程作参数来定义排序规则

昨天写发送邮件的时候用了spring一个property loader，今天发现所有struts2的页面都返回input validation错误了。。。查了半天，查到fielderror是某个mail的properties，为啥struts2回去读那个properties呢。。。原来是spring loader惹的祸。。。

  <bean id=”MailProperties” class=”org.springframework.beans.factory.config.PropertiesFactoryBean”>
  <property name=”location”>
  <value>/WEB-INF/classes/pwrl.mail.properties</value>
  </property>
 </bean>

 就是这个PropertiesFactoryBean的东东，和struts2的 org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor 存在一些数据共享关系，再详细看看源代码才知道。。。

今天写个后台发送，连到smtp要登录的，我见java mail里面api默认就可以在connect的时候输入密码，以为直接用就可以啦，谁知道sun 的smtp实现default不打开auth，google一下，记录一些文档。。。还搜到某个猪头说session参数就只有一开始那几个，其实可以有很多很多的。。。

明天回去还要加上 msg.saveChanges();  不知道有啥用。。。

好像是保存message状态和header的，The send method calls the saveChanges method on the message before sending it.  看来不用改了。。。

Package com.sun.mail.smtp Description

An SMTP protocol provider for the JavaMail API that provides access to an SMTP server. Refer to RFC 821 for more information.

When sending a message, detailed information on each address that fails is available in an SMTPAddressFailedException chained off the top level SendFailedException that is thrown. In addition, if the mail.smtp.reportsuccess property is set, an SMTPAddressSucceededException will be included in the list for each address that is successful. Note that this will cause a top level SendFailedException to be thrown even though the send was successful.

The SMTP provider also supports ESMTP (RFC 1651). It can optionally use SMTP Authentication (RFC 2554) using the LOGIN, PLAIN, and DIGEST-MD5 mechanisms (RFC 2592 and RFC 2831).

To use SMTP authentication you’ll need to set the mail.smtp.auth property (see below) and provide the SMTP Transport with a username and password when connecting to the SMTP server. You can do this using one of the following approaches:

• Provide an Authenticator object when creating your mail Session and provide the username and password information during the Authenticator callback.Note that the mail.smtp.user property can be set to provide a default username for the callback, but the password will still need to be supplied explicitly.This approach allows you to use the static Transport send method to send messages.
• Call the Transport connect method explicitly with username and password arguments.This approach requires you to explicitly manage a Transport object and use the Transport sendMessage method to send the message. The transport.java demo program demonstrates how to manage a Transport object. The following is roughly equivalent to the static Transport send method, but supplies the needed username and password:

Transport tr = session.getTransport(“smtp”);

tr.connect(smtphost, username, password);

msg.saveChanges(); // don’t forget this

tr.sendMessage(msg, msg.getAllRecipients());

tr.close();

When using DIGEST-MD5 authentication, you’ll also need to supply an appropriate realm; your mail server administrator can supply this information. You can set this using the mail.smtp.sasl.realm property, or the setSASLRealm method on SMTPTransport.

SMTP can also optionally request Delivery Status Notifications (RFC 1891). The delivery status will typically be reported using a “multipart/report” (RFC 1892) message type with a “message/delivery-status” (RFC 1894) part. JavaMail does not currently provide direct support for these new MIME types, but you can process them as any other “multipart” or “message” content, using MimeMultipart and MimeMessage objects.

See below for the properties to enable these features.

Note also that THERE IS NOT SUFFICIENT DOCUMENTATION HERE TO USE THESE FEATURES!!! You will need to read the appropriate RFCs mentioned above to understand what these features do and how to use them. Don’t just start setting properties and then complain to us when it doesn’t work like you expect it to work. READ THE RFCs FIRST!!!

The SMTP protocol provider supports the following properties, which may be set in the JavaMail Session object. The properties are always set as strings; the Type column describes how the string is interpreted. For example, use

        props.put("mail.smtp.port", "888");

to set the mail.smtp.port property, which is of type int.

In general, applications should not need to use the classes in this package directly. Instead, they should use the APIs defined by javax.mail package (and subpackages). Applications should never construct instances of SMTPTransport directly. Instead, they should use the Session method getTransport to acquire an appropriate Transport object.