LO78211: "DON'T ACCEPT MESSAGE" MAIL RULE NOT WORKING

APAR status

• Closed as fixed if next.

Error description

• Software:
  
  Server: Lotus Domino (r) Server (64 Bit) (Release 8.5.3FP3 for
  Windows/64)
  Client: Lotus Notes Revision 20130802.1125-FP5 (Release
  8.5.3FP5)
  
  We have some end-users complaining that mail rules with an
  action of
  "Delete (don't accept message)" are not firing correctly.  If I
  look at
  their mail database, messages matching the rule don't show up
  in the
  Inbox, but are in All Documents.  Other mail rules (move to
  folder,
  send copy to other user, etc) seem to work fine.  The problem
  only
  occurs for some users, but if a user has the problem, it will
  apply to
  all "Don't Accept Message" rules in their mail DB.
  
  I don't see any error messages on the console when I send test
  messages
  to an affected user, and if I look at the raw $FilterFormula_XX
  field
  via NotesPeek, the rule looks good.  For example, a mail rule
  with a
  Condition of Subject contains "Dots File Notification" AND
  Sender is
  "dots@allantgroup.com", and an Action of "Don't Accept Message"
  compiles to this formula:
  
  CondSubject_C := @LowerCase( Subject ); CondSender_I := @Name
  ([Abbreviate];@Trim(@Unique( From:Principal:SMTPOriginator ) )
  ) ; @If
  ((  @Contains( CondSubject_C;"dots expected file notification")
  &
  (CondSender_I =  "dots@allantgroup.com") ) ;
  (@Do((@DeleteDocument)));
  "" )
  
  It's as if @DeleteDocument action is working halfway (the
  message is
  removed from the Inbox, but the deletion itself fails silently).
  
  Is this a known issue, and if not, are there any debugging
  options I
  can enable to help troubleshoot this?
  

Local fix

• no fix yet
  - as per PAE we can create a new SPR for the issue is similar
  to SPR RCDX6SNNAD via v60 codestream
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# RSFO9E5PBB.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R850 PSN

     UP