Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Domino > Domino messaging > Preventing repeated Router, SMTP and IMAP crashes caused by problem messages
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Preventing repeated Router, SMTP and IMAP crashes caused by problem messages

Preventing repeated Router, SMTP and IMAP crashes caused by problem messages Processing a problem message repeatedly can cause a server crash. If a message being processed at the time of a Router, SMTP, or IMAP crash remains in the mail.box database or mail file, processing the message again when ...
Community articlePreventing repeated Router, SMTP and IMAP crashes caused by problem messages
Added by ~Rex Rejipybergikle | Edited by ~Rex Rejipybergikle on November 22, 2013 | Version 9
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: crash
Preventing repeated Router, SMTP and IMAP crashes caused by problem messages

Processing a problem message repeatedly can cause a server crash. If a message being processed at the time of a Router, SMTP, or IMAP crash remains in the mail.box database or mail file, processing the message again when the server is restarted can cause another server crash.

In IBM® Domino® 9.0.1 Social Edition 9.0.1, at the time of the crash, Domino now uses an exception handler to save the information identifying the message that caused the crash to the file system. Upon server restart, Domino uses the information to find the message and quarantine it.

File names and actions related to a problem message

Task: Router

Directory where information on the problem message is saved after a crash

IBM_TECHNICAL_SUPPORT/routerfaultdata

What Domino does upon restart

Moves the problem message to an .NSF in the following location, with the time of the crash specified in the file name, for example: IBM_TECHNICAL_SUPPORT/routerbadmsg_servername_yyyy_mm_dd@hh_mm_ss.badnsf

Task: SMTP

Directory where information on the problem message is saved after a crash

IBM_TECHNICAL_SUPPORT/SMTPSubmitCrash

What Domino does upon restart

SMTP rejects the message with the following error:
554 Unable to import message

Task: IMAP

Directory where information on the problem message is saved after a crash

IBM_TECHNICAL_SUPPORT/IMAPFetchCrash

What Domino does upon restart

Moves the problem message to an .NSF in the following location, with the time of the crash specified in the file name, for example:
IBM_TECHNICAL_SUPPORT/imap_servername_yyyy_mm_dd@hh_mm_ss.badnsf

The next time Domino fetches the problem message, this error appears:
[The content of this message could not be retrieved. Please contact IBM support to report this issue.]

  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (9)Nov 22, 2013, 7:36:24 AM~Rex Rejipybergikle  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility