注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

mylotustips的博客

IBM Lotus协作产品家族经验分享

 
 
 

日志

 
 
关于我

欢迎大家使用SR向IBM800提交问题http://www.ibm.com/support/servicerequest 可以随时查看问题状态,上传文件

网易考拉推荐

邮件调回问题诊断方法  

2012-04-12 13:44:46|  分类: Domino服务器 |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
 
 
关于message recall的配置要求和工作原理可以参考如下文档。
http://www.ibm.com/developerworks/cn/lotus/notes8-recall/

如果从特定用户的mail file里面无法recall,按照如下方法进行debug
1.        先在服务器notes.ini里面添加如下debug参数,添加的方法是在服务器控制台敲如下命令,无需重启服务器或者任务。
set config console_log_enabled=1
set config debug_threadid=1
Set config debugrouter=3
Set config log_mailrouting=40

重现问题之后收集数据, console.log里面能查看到类似如下日志。

07/26/2007 03:30:43 PM  Router: Delivery to local recipient Final User/Mail8 is ready with 1 messages
07/26/2007 03:30:43 PM  Router: Delivery thread 00000008 searching for work
07/26/2007 03:30:43 PM  Router: Signaling an idle delivery thread
07/26/2007 03:30:43 PM  Router: Message 006B2E6D Recall for Final User/Mail8. Requested criteria is 4
Requested criteria是发起recall请求的人,在recall message的时候,是否选择了recall read mail,如果recall read&unread mail,那么这个值是4,如果只选择了recall unread mail,那么这个值是2

07/26/2007 03:30:43 PM  Router: Message 006B2E6D Recall for Final User/Mail8. Criteria changed to 2 via User Mail Preference
这个日志的意思是,因为Final User/Mail8设置了mail policy来recall message,并且里面选择了Allow recall of messages with unread status: unread only, 所以mail policy会强制将Requested criteria转化为2,如果设置了不允许别人从该用户邮箱里面recall message,这段日志会是User Mail Preference has feature disabled.

07/26/2007 03:30:43 PM  Router: Message 006B2E6D Recall for Final User/Mail8. Period set to 302400.
Period Set的单位是分钟,是配置文档或者mail policy里面Do Not Allow recall of messages older than的值,测试的结果发现mail policy优先于配置文档。

07/26/2007 03:30:43 PM  Router: Message 006B2E6D Recall for Final User/Mail8. Message is '0' minutes old. (Delivered Date 07/26/2007 03:30:33 PM).
这段日志是在定位需要召回的邮件,并且查看邮件的age。

07/26/2007 03:30:43 PM  Router: Message 006B2E6D Recall for Final User/Mail8. Request signed on 07/26/2007 03:30:53 PM by Admin Mail8/Mail8 according to /Mail8.
这段日志表明了recall的发起者和被recall的收件人,如果发起者和最早的From或者Principal域不匹配,那么recall会失败,也会有相应的日志体现。

07/26/2007 03:30:43 PM  Router: Recall:  Checking NoteID 4358 for user CN=Admin Mail8/O=Mail8 in mailfile mail\finuser
07/26/2007 03:30:43 PM  Router: Recall: NoteID 4358 has been marked read by user  CN=Admin Mail8/O=Mail8 in mailfile mail\finuser
07/26/2007 03:30:43 PM  Router: Message 006B2E6D. Message 006B2849 for Final User/Mail8 failed to be recalled by Admin Mail8/Mail8.  OFEB376DD1:ADF87D6A ON85257324:006B2849

2.        如果日志能帮忙我们诊断recall failure的原因外,还可以参考一下recall产生的Message Recall Status文档,查看文档属性如下所示。
邮件调回问题诊断方法 - mylotustips - mylotustips的博客
 

Current values for RecallStatus:
0        Unknown recall status
1        Recall failed
2        Recall succeeded

Current values for RecallFailureReason:
0        Unknown failure reason (or recall did not fail)
1        Message was not found in the recipient's mail file
2        Message has been deleted from the recipient's mail file already
3        Recall was not allowed

Current values for RecallMessageStatus:
0        Message status unknown
1        Message not found in recipient's mail file
2        Message has not been accessed in recipient's mail file (not implemented)
3        Message is not marked read in recipient's mail file
4        Message is marked read in recipient's mail file
5        Message has been deleted from recipient's mail file

Current values for RecallErrorCode (only available if DebugRouter>=1) in addition to possible status returned from NoteOpen and NoteDelete calls:
13356        Recall succeeded
13357        Recall failed
13358        Recall requests cannot be sent over SMTP
13359        Failed to send recall status report
13360        Recall request was not signed
13361        Recall request signature does not match Principal or From of the target message
13362        Error processing an item on recall request
13363        Item on recall request was not signed
13364        Message Recall feature not enabled on the server
13365        No Principal or From items on target message        
13366        Cannot locate message in recipient's mail file
13367        Cannot verify signature on recall request
13368         Invalid UNID specified for the target message in the recall request
13369        MessageID specified in the recall request does not match the target message
13370         Recall is disabled for this mail file (either due to Mail Policy or mail file preference)
13371        Cannot recall a message sent to yourself

3.        案例分享。
设置好mail policy之后,message recall如何体现到用户邮箱库,是通过calendar profile来记录的,如果mail policy不生效,那么在用户的邮箱库calendar profile里面没有PolicyRecallCriteriaPolicyRecallCriteriaPeriod,相反如果mail policy生效的话,是能看到这两个域的,并且里面的值和我们在Policy Synopsis里面查看到该用户的PolicyRecallCriteriaPolicyRecallCriteriaPeriod相同的。

所以如果对mail policy里面message recall有改动,首先要先从Policy Synopsis—Detailed--Mail里面确认用户的PolicyRecallCriteriaPolicyRecallCriteriaPeriod更新过来了,然后可以运行tell adminp process mail policy, 通过notespeek去用户邮箱库里面确认calendar profilePolicyRecallCriteriaPolicyRecallCriteriaPeriod也更新了。这样才能真正生效。

如果calendar profile里面的值不知何故是错误的值,通过更新之后仍然不能解决的话,那么建议通过脚本的方式删除旧的calendar profile
  评论这张
 
阅读(1064)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017