ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon 2018 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Documentation & Release Information
DrillDown Icon Known Issues (non-release related)
DrillDown Icon Configuration Information
DrillDown Icon Troubleshooting
DrillDown Icon Hardware & OS System Requirements
DrillDown Icon Tools
DrillDown Icon SMTP Authentication Tester
DrillDown Icon RCP Creator Utility for Respooling Messages
DrillDown Icon Other Product Technical Information
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
 
RCP Creator Utility for Respooling Messages

 

Product: All
Version & Build: All
 


What is this utility used for?

To assist customers in respooling email messages. 

 

If you have a large number of messages in someone's inbox or orphaned MSG files in the spool that you want to resend through the server, you first need to regenerate the RCP files.  Our spool system needs an MSG (Message) and RCP (Recipient file or "envelope").  If you copy an MSG file into Spool\Invirus without the corresponding RCP file second, the MSG file will hang there indefinitely.  The RCP file tells Modus who the real recipient is.

 

The RCPCreator starts with an MSG file and generates the necessary RCP file based on the header information contained in the MSG file.

 

 

WARNING: Before beginning the process, please keep these important facts in mind:

 

1. When moving messages back into the spool (e.g., either to the Invirus or Incoming folders) the MSG portion of the message must be moved first, then the corresponding RCP file second. This is because the program will attempt to process RCPs as soon as they arrive in the spool.  If the MSG isn't there, the RCP will be processed without it, leaving orphaned MSG files.  You would then have to repeat the RCP creation process.

 

2. If you must respool messages, it's recommended to copy them to the Invirus or Incoming folders for reprocessing (use Incoming if the messages have already gone through the scanner).  It is not recommended that you copy them into the Holding/Domains folders.  Why?  There is a "garbage collection" process built into the program: if an MSG file is placed in the Holding directory without a corresponding RCP file somewhere in the Domains directory, that MSG file will be deleted.  This behavior doesn't occur in the Invirus or Incoming directories.  Therefore, if an MSG is placed there without the RCP, the MSG file will remain until you either reprocess it or delete it manually.

 

 

 

How do I use the rcpcreator?

RCPCREATOR accepts five parameters:

-m <source MSG file name> [Required]
-r  <desired RCP file name> [Required]
-d <default domain on server> [Required]
-z <destination folder> [Required]
-t  <forced recipient> (optional)

 

 

Example:

 

You have an MSG file called B000012345.MSG and your server's default domain is widget.com.  You would generate your RCP file in this manner:

 

RCPCREATOR -m B000012345.MSG -r B000012345.RCP -d widget.com -z c:\temp

 

This will copy the MSG and generate the RCP file in c:\temp.

 

 

Details about the parameters:

-m <source MSG file name> [Required]

  • Where the MSG file you're generating the RCP file from is located

 

-r <desired RCP file name> [Required]

  • The destination RCP file you want to create

 

-d <default domain on server> [Required]

  • Default domain on your server

 

-z <destination folder> [Required]

  • Where you want to put the new MSG/RCP files

 

-t <forced recipient> (optional)

  • If you want to override the "TO" field in the message with a new recipient


 

What do you do if you have a large number of MSG files?

Write a batch file using a macro-capable text editor:

Use dir/b:

B0011706441.MSG
B0011706442.MSG
B0011706443.MSG
B0011706444.MSG
B0011706445.MSG

 

Using the editor's keystroke recording capability, you start with the first line:

rcpcreator -m B0011706441.MSG -r B0011706441.RCP -d widget.com -z c:\output
B0011706442.MSG
B0011706443.MSG
B0011706444.MSG
B0011706445.MSG

 

You simply replay the macro X times, where X = number of remaining entries:

rcpcreator -m B0011706441.MSG -r B0011706441.RCP -d widget.com -z c:\output
rcpcreator -m B0011706442.MSG -r B0011706442.RCP -d widget.com -z c:\output
rcpcreator -m B0011706443.MSG -r B0011706443.RCP -d widget.com -z c:\output
rcpcreator -m B0011706444.MSG -r B0011706444.RCP -d widget.com -z c:\output
rcpcreator -m B0011706445.MSG -r B0011706445.RCP -d widget.com -z c:\output

 

Finally, run the batch file.  In the example above, all of the MSG/RCP pairs should be in c:\output.  Move the MSGs into your spool\invirus or spool\incoming and then move the RCP files.
 
Attachments
Modified 10/21/2011
Keywords: respool, orphan, MSG, RCP
Article ID: 947