DOCSLIB.ORG

Microsoft Exchange 2007 Journaling Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Microsoft Exchange 2007 Journaling Guide Digital Archives Updated on 12/9/2010 Document Information Microsoft Exchange 2007 Journaling Guide Published August, 2008 Iron Mountain Support Information U.S. 1.800.888.2774 [email protected] Copyright © 2008 Iron Mountain Incorporated. All Rights Reserved. Trademarks Iron Mountain and the design of the mountain are registered trademarks of Iron Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. Entities under license agreement: Please consult the Iron Mountain & Affiliates Copyright Notices by Country. Confidentiality CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity, directly or indirectly, or to any third person without the prior written consent of Iron Mountain. Disclaimer While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without notice and should not be considered a commitment by Iron Mountain. Iron Mountain Incorporated 745 Atlantic Avenue Boston, MA 02111 +1.800.934.0956 www.ironmountain.com/digital Contents Microsoft Exchange 2007 Journaling Guide 1 Contents 3 Chapter 1: Supported Data Formats 5 Chapter 2: Enabling Exchange Server 2007 Journaling 7 Create a Journal Contact 8 Create a Journal Rule 11 Appendix A: Supported File Formats for Ingesting and Indexing Assets 13 Digital Archives: Microsoft Exchange 2007 Journaling Guide 3 Contents 4 Digital Archives: Microsoft Exchange 2007 Journaling Guide Chapter 1: Supported Data Formats 1 ChapterSupported 1: Data Formats Before configuring your Microsoft Exchange server to journal messages to Iron Mountain, it is important to understand the data formats that Iron Mountain accepts to ingest and index data. To insure that Iron Mountain can ingest and index data that a customer transmits to Iron Mountain’s Digital Record Center for Compliant Messaging (DRC-CM), the data must meet all of the following format requirements: l The data must be in RFC-2822 compliant format or in the format created by Lotus Notes for internal email. RFC-2822 is the standard format used by most mail servers to transmit text messages. See http://www.faqs.org/rfcs/rfc2822.html for more information about the RFC-2822 standard. l The data must contain only ASCII characters. l The data must have a date stamp that is not in the future. The following table contains, without limitation, common reasons why Iron Mountain can not fully ingest and index journaled messages: Reason Description Encrypted data Encryption prevents unauthorized access to message content. As such, Iron Mountain cannot view, index, or display any parts of a message (including attachments) that are encrypted. Malformed message Iron Mountain can not fully ingest and index any message that headers does not have a properly formatted message header. The message headers include the To, From, Date, and/or Subject fields. Messages containing Iron Mountain can not fully ingest and index any message that non-ASCII includes, without limitation, double-byte characters and system- characters generated messages. Messages with a The journaling process occurs after the sender has sent a future date message. Therefore, all message date stamps must have a date that occurs in the past. Iron Mountain will not ingest or index messages with future date stamps. Digital Archives: Microsoft Exchange 2007 Journaling Guide 5 1 Chapter 1:Supported Data Formats Reports Iron Mountain will email a report to the customer's designated administrator on a weekly basis. This report shows the disposition of the assets that Iron Mountain received during the prior week. The report includes a count of assets that Iron Mountain has rejected. Because Iron Mountain has rejected the data, it is, therefore, not available in the DRC- CM archive. Iron Mountain will post any messages that it rejects to a secure FTP site on a weekly basis. If you want to send the message again for ingestion, retrieve the rejected data from the FTP site to remediate it. Once the data is in the proper format, re-submit the data to Iron Mountain for ingestion by posting the messages back to the FTP site. 6 Digital Archives: Microsoft Exchange 2007 Journaling Guide Chapter 2: Enabling Exchange Server 2007 Journaling 2 ChapterEnabling 2: Exchange Server 2007 Journaling This chapter describes how to configure your Microsoft® 2007 Exchange server environment to enable journaling from the server to IronMountain. To enable journaling with the Exchange 2007 server,you must have access to the Exchange Management Console and perform the following two tasks: l Create a Journal Contact, on page 8 l Create a Journal Rule, on page 11 Digital Archives: Microsoft Exchange 2007 Journaling Guide 7 Chapter 2:Enabling Exchange Server 2007 Journaling 2 Createa JournalContact Create a Journal Contact To create a journal contact, complete the following steps: 1. Open the Exchange Management Console. 2. In the hierarchy tree, expand Recipient Configuration and, then select Mail Contact. The Mail Contact pane displays in the middle pane. 3. In the right Actions pane, click New Mail Contact. The New Mail Contact Introduction dialog box opens. 8 Digital Archives: Microsoft Exchange 2007 Journaling Guide Chapter 2: Enabling Exchange Server 2007 Journaling Createa JournalContact 2 4. Select New Contact and click Next. The New Mail Contact/ Contact Information dialog box opens. 5. Use the Browse button, if necessary, to select an entry in the Organizational unit. 6. Type an entry in the Name and Alias fields for the contact that you are creating. 7. Click Edit next to the External e-mail address field.. The SMTP Address dialog box opens. 8. Type the SMTP address provided by your project manager in the E-mail address field. Digital Archives: Microsoft Exchange 2007 Journaling Guide 9 Chapter 2:Enabling Exchange Server 2007 Journaling 2 Createa JournalContact 9. Click OK. You return to the New Mail Contact Dialog box. 10. Click Next. The New Mail Contact/New Mail Contact dialog box opens. 11. Click Next.The New Mail Contact/Completion dialog box opens. 12. Click Finish. 10 Digital Archives: Microsoft Exchange 2007 Journaling Guide Chapter 2: Enabling Exchange Server 2007 Journaling Create a JournalRule 2 Create a Journal Rule After you create the SMTP journal contact, create a journal rule using the Exchange Management Console. To create a journal rule, perform the following steps: 1. Launch the Exchange Management Console. 2. Expand Organization Configuration in the left pane, and then select Hub Transport. The Hub Transport tabs appear in the middle pane. 3. Select the Journaling tab in the center pane, and then select New Journal Rule in the right pane. 4. Follow these guidelines to complete the dialog box : a. Type a name for the rule in the Rule name field. b. Click the Browse button next to the Send journal reports to e-mail address box. The Select Recipient dialog box opens. Select the mail contact you created in Create a Journal Contact, and then click OK. You return to the New Journal Rule dialog box. c. Select the desired Scope in the New Journal Rule dialog box. The dialog box defaults to Global-all messages. The following table explains the different selections in the Scrope group. Digital Archives: Microsoft Exchange 2007 Journaling Guide 11 Chapter 2:Enabling Exchange Server 2007 Journaling 2 Createa JournalRule Scope Action Global When you select this option, the Exchange server journals all mes- sages to Iron Mountain, regardless of where the messages come from or to whom the messages are being sent. Internal When you select this option, only messages sent and received by mailboxes within the Exchange Server organization are journaled. External When you select this option, messages sent to recipients outside of the Exchange Server organization are journaled. Messages sent to recipients within your Exchange Server organization are also jour- naled. 5. [Optional] To enable premium journaling, select Journal messages for recipient. Click the Browse button, and, then select a distribution list or an individual email address that you want to journal. NOTE Premium journaling creates journal rules for entire groups within your organization (distribution list) or for a single mailbox recipient (contact).To use this feature, you must have an Exchange Enterprise Client Access License (CAL). 6. Select the Enable Rule check box to enable the journal rule. If you clear the check box, Exchange still creates the rule, but you can activate it at a later date. 7. Click New, and then click Finish. 12 Digital Archives: Microsoft Exchange 2007 Journaling Guide Appendix A: Supported File Formats for Ingesting and Indexing Assets Appendix A: Supported File Formats for Ingesting and Indexing Assets This appendix contains a list of the file types that Iron Mountain recognizes for ingestion and indexing. Iron Mountain supports the detection of close to 400 different file types, including most current, common file formats and many uncommon and extinct file formats. The following table contains the supported format names and, where possible, the best available MIME type match.The default content-type is application/octet-stream. This MIME type appears in italics for all formats without a specific content-type.This table also contains a description of the format and its extension. FMT# Format name MIME Content type Notes 0 Unknown application/octet-stream Any unrecognized file gets this type by default. 1 AES Multiplus application/octet-stream Legacy Word Processor by AES Data. 2 ASCII Text text/plain Plain ASCII Text (.TXT) 3 MS-DOS® application/x-msdos-program MS-DOS Batch File (.BAT) Batch File 4 Applix® Asterix application/octet-stream Legacy Word Processor by Applix.
Recommended publications
  • The Microsoft Office Open XML Formats New File Formats for “Office 12”

    The Microsoft Office Open XML Formats New File Formats for “Office 12”

    The Microsoft Office Open XML Formats New File Formats for “Office 12” White Paper Published: June 2005 For the latest information, please see http://www.microsoft.com/office/wave12 Contents Introduction ...............................................................................................................................1 From .doc to .docx: a brief history of the Office file formats.................................................1 Benefits of the Microsoft Office Open XML Formats ................................................................2 Integration with Business Data .............................................................................................2 Openness and Transparency ...............................................................................................4 Robustness...........................................................................................................................7 Description of the Microsoft Office Open XML Format .............................................................9 Document Parts....................................................................................................................9 Microsoft Office Open XML Format specifications ...............................................................9 Compatibility with new file formats........................................................................................9 For more information ..............................................................................................................10
  • Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework

    Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework

    Build it with Nitrogen The fast-off-the-block Erlang web framework Lloyd R. Prentice & Jesse Gumm dedicated to: Laurie, love of my life— Lloyd Jackie, my best half — Jesse and to: Rusty Klophaus and other giants of Open Source— LRP & JG Contents I. Frying Pan to Fire5 1. You want me to build what?7 2. Enter the lion’s den9 2.1. The big picture........................ 10 2.2. Install Nitrogen........................ 11 2.3. Lay of the land........................ 13 II. Projects 19 3. nitroBoard I 21 3.1. Plan of attack......................... 21 3.2. Create a new project..................... 23 3.3. Prototype welcome page................... 27 3.4. Anatomy of a page...................... 30 3.5. Anatomy of a route...................... 33 3.6. Anatomy of a template.................... 34 3.7. Elements............................ 35 3.8. Actions............................. 38 3.9. Triggers and Targets..................... 39 3.10. Enough theory........................ 40 i 3.11. Visitors............................ 44 3.12. Styling............................. 64 3.13. Debugging........................... 66 3.14. What you’ve learned..................... 66 3.15. Think and do......................... 68 4. nitroBoard II 69 4.1. Plan of attack......................... 69 4.2. Associates........................... 70 4.3. I am in/I am out....................... 78 4.4. Styling............................. 81 4.5. What you’ve learned..................... 82 4.6. Think and do......................... 82 5. A Simple Login System 83 5.1. Getting Started........................ 83 5.2. Dependencies......................... 84 5.2.1. Rebar Dependency: erlpass ............. 84 5.3. The index page........................ 85 5.4. Creating an account..................... 87 5.4.1. db_login module................... 89 5.5. The login form........................ 91 5.5.1.
  • Getting Started with Libreoffice 3.4 Copyright

    Getting Started with Libreoffice 3.4 Copyright

    Getting Started with LibreOffice 3.4 Copyright This document is Copyright © 2010–2012 by its contributors as listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/), version 3.0 or later. Contributors Jean Hollis Weber Jeremy Cartwright Ron Faile Jr. Martin Fox Dan Lewis David Michel Andrew Pitonyak Hazel Russman Peter Schofield John A Smith Laurent Balland-Poirier Cover art: Drew Jensen Christoph Noack Klaus-Jürgen Weghorn Jean Hollis Weber Acknowledgements This book is adapted and updated from Getting Started with OpenOffice.org 3.3. The contributors to that book are listed on page 13. Feedback Please direct any comments or suggestions about this document to: [email protected] Publication date and software version Published 10 September 2012. Based on LibreOffice 3.5.6. Documentation for LibreOffice is available at http://www.libreoffice.org/get-help/documentation Contents Copyright..................................................................................................................................... 2 Note for Mac users...................................................................................................................... 8 Preface.................................................................................................................................. 9 Who is this book for?................................................................................................................
  • LYX Frequently Asked Questions with Answers

    LYX Frequently Asked Questions with Answers

    LYX Frequently Asked Questions with Answers by the LYX Team∗ January 20, 2008 Abstract This is the list of Frequently Asked Questions for LYX, the Open Source document processor that provides a What-You-See-Is-What-You-Mean environment for producing high quality documents. For further help, you may wish to contact the LYX User Group mailing list at [email protected] after you have read through the docs. Contents 1 Introduction and General Information 3 1.1 What is LYX? ......................... 3 1.2 That's ne, but is it useful? . 3 1.3 Where do I start? . 4 1.4 Does LYX run on my computer? . 5 1.5 How much hard disk space does LYX need? . 5 1.6 Is LYX really Open Source? . 5 2 Internet Resources 5 2.1 Where should I look on the World Wide Web for LYX stu? 5 2.2 Where can I get LYX material by FTP? . 6 2.3 What mailing lists are there? . 6 2.4 Are the mailing lists archived anywhere? . 6 2.5 Okay, wise guy! Where are they archived? . 6 3 Compatibility with other word/document processors 6 3.1 Can I read/write LATEX les? . 6 3.2 Can I read/write Word les? . 7 3.3 Can I read/write HTML les? . 7 4 Obtaining and Compiling LYX 7 4.1 What do I need? . 7 4.2 How do I compile it? . 8 4.3 I hate compiling. Where are precompiled binaries? . 8 ∗If you have comments or error corrections, please send them to the LYX Documentation mailing list, <[email protected]>.
  • Background Information History, Licensing, and File Formats Copyright This Document Is Copyright © 2008 by Its Contributors As Listed in the Section Titled Authors

    Background Information History, Licensing, and File Formats Copyright This Document Is Copyright © 2008 by Its Contributors As Listed in the Section Titled Authors

    Getting Started Guide Appendix B Background Information History, licensing, and file formats Copyright This document is Copyright © 2008 by its contributors as listed in the section titled Authors. You may distribute it and/or modify it under the terms of either the GNU General Public License, version 3 or later, or the Creative Commons Attribution License, version 3.0 or later. All trademarks within this guide belong to their legitimate owners. Authors Jean Hollis Weber Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgments This Appendix includes material written by Richard Barnes and others for Chapter 1 of Getting Started with OpenOffice.org 2.x. Publication date and software version Published 13 October 2008. Based on OpenOffice.org 3.0. You can download an editable version of this document from http://oooauthors.org/en/authors/userguide3/published/ Contents Introduction...........................................................................................4 A short history of OpenOffice.org..........................................................4 The OpenOffice.org community.............................................................4 How is OpenOffice.org licensed?...........................................................5 What is “open source”?..........................................................................5 What is OpenDocument?........................................................................6 File formats OOo can open.....................................................................6
  • Dassault Systèmes SA

    Dassault Systèmes SA

    Dassault Systèmes S.A. -- Company History Contact Angel Investors Login Services Company Forum Blog Buzz PDM/PLM that works World class Teamcenter PDM/PLM is now affordable and deployable! www.acuityinc.com [acronym] online Commune. Share. Explore. Public Sector Design Community www.acronymonline.org Mouthwatering Food Gifts Get Happiness Delivered With H& D. Gourmet Chocolate, Fruit & Treats! www.Harrya Company Histories: # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Search thousands of company histories: Dassault Systèmes S.A. Get 50 expert sample business plans and put your great idea down on paper! Find Angel Investors in your area Address: 9, quai Marcel Dassault BP 310 92156 Suresnes Cedex France Telephone: (33) 1 40 99 40 99 Fax: (33) 1 42 04 45 81 http://www.dsweb.com Statistics: Public Company Incorporated: 1981 Employees: 1,672 Sales: FFr 1.96 billion (US$ 335 million) (1997) Stock Exchanges: Paris NASDAQ Ticker Symbol: DASTY SICs: 7372 Prepackaged Software; 7371 Computer Programming Services; 5045 Computers, Peripherals, and Software Company History: Dassault Systèmes S.A. is the world's leading developer of CAD/CAM/CAE (computer-assisted design, manufacturing, engineering) software, with a product family of more than 120 interrelated component software packages enabling the implementation of design, analysis, manufacturing, and post-production support systems tailored to clients' specific needs. Dassault's CATIA and CADAM software products permit engineering and product design teams, generally working across a network, to develop prototype products, as well as to provide software-based modeling, assembly, testing, analysis and other procedures using three-dimensional images, eliminating the expense of building physical models and prototypes during a product's initial design phase.
  • Docuarchive Product Sheet

    Docuarchive Product Sheet

    DocuArchive Product Sheet Contents 1 What this document contains ............................................................................................... 3 2 DocuArchive Server components ........................................................................................ 3 2.1 DocuArchive ArchiveServer ..................................................................................................... 3 2.1.1 Hardware and software requirements ...................................................................................... 3 2.1.2 Runtime environment ............................................................................................................... 3 2.1.3 Supported storage technologies .............................................................................................. 4 2.1.4 Quantitative characteristics ...................................................................................................... 5 2.2 DocuArchive MediaServer ....................................................................................................... 6 2.2.1 Runtime requirements .............................................................................................................. 6 2.2.2 Hardware and software requirements ...................................................................................... 6 2.3 DocuArchive DBServer ............................................................................................................ 6 2.3.1 Hardware and software requirements .....................................................................................
  • Nucleic Acids Research

    Nucleic Acids Research

    Nucleic Acids Research Executive editors R.T.Walker, Birmingham, UK B.E.Griffin, London, UK P.Pearson, Baltimore, MD, USA R.J.Roberts, Cold Spring Harbor, R.B.Hallick, Tucson, AZ, USA J.M.Rosen, Houston, TX, USA NY, USA J.E.Hearst, Berkeley, CA, USA I.C .Eperon, Leicester, UK N.C.Martin, Louisville, KY, USA M.J.Gait, Cambridge, UK W.R.McClure, Pittsburgh, PA, USA Editorial board M.Beato, Marburg, FRG W.T.Garrard, Dallas, 7X, USA S.E.V.Phillips, Leeds, UK A.J.Berk, Los Angeles, CA, USA F.Giannelli, London, UK R.H.Reeder, Seattle, WA, USA A.P.Bird, Edinburgh, UK P.J.Hagerman, Denver, CO, USA C.W.Schmid, Davis, CA, USA J.L.Bos, Utrecht, The Netherlands C.Helene, Paris, France Y.Shimura, Kyoto, Japan H.Buc, Paris, France A.J.Jeffreys, Leicester, UK R.Simpson, Bethesda, MD, USA K.Calame, New York, NY, USA C.J.Leaver, Oxford, UK D.Soll, New Haven, CT, USA N.Chua, New York, NY, USA H.Lehrach, London, UK B. Sollner-Webb, Baltimore, MD, USA D.A.Clayton, Stanford, CA, USA D.M.J.Lilley, Dundee, UK S.Spadari, Pavia, Italy A.Das, Farmington, CT, USA T.Lindahl, London, UK R.H.Symons, Adelaide, Australia M.L. DePamphilis, Nutley, NJ, USA S.M.Linn, Berkeley, CA, USA H.F.Tabak, Amsterdam, The M.P.Deutscher, Farmington, CT, USA J.T.Lis, Ithaca, NY, USA Netherlands J.E.Donelson, Iowa City, IA, USA R.McMacken, Baltimore, MD, USA S.Tilghman, Princeton, NJ, USA F.Eckstein, Gottingen, FRG D.A.Melton, Cambridge, MA, USA I.Tinoco, Jr, Berkeley, CA, USA J.D.Engel, Evanston, IL, USA J.R.Nevins, Durham, NC, USA Y.Wang, Shanghai, China P.T.Englund, Baltimore, MD,
  • Netpbm Format - Wikipedia, the Free Encyclopedia

    Netpbm Format - Wikipedia, the Free Encyclopedia

    Netpbm format - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Portable_anymap Netpbm format From Wikipedia, the free encyclopedia (Redirected from Portable anymap) The phrase Netpbm format commonly refers to any or all Portable pixmap of the members of a set of closely related graphics formats used and defined by the Netpbm project. The portable Filename .ppm, .pgm, .pbm, pixmap format (PPM), the portable graymap format extension .pnm (PGM) and the portable bitmap format (PBM) are image file formats designed to be easily exchanged between Internet image/x-portable- platforms. They are also sometimes referred to collectively media type pixmap, -graymap, [1] as the portable anymap format (PNM). -bitmap, -anymap all unofficial Developed Jef Poskanzer Contents by 1 History Type of Image file formats 2 File format description format 2.1 PBM example 2.2 PGM example 2.3 PPM example 3 16-bit extensions 4 See also 5 References 6 External links History The PBM format was invented by Jef Poskanzer in the 1980s as a format that allowed monochrome bitmaps to be transmitted within an email message as plain ASCII text, allowing it to survive any changes in text formatting. Poskanzer developed the first library of tools to handle the PBM format, Pbmplus, released in 1988. It mainly contained tools to convert between PBM and other graphics formats. By the end of 1988, Poskanzer had developed the PGM and PPM formats along with their associated tools and added them to Pbmplus. The final release of Pbmplus was December 10, 1991. In 1993, the Netpbm library was developed to replace the unmaintained Pbmplus.
  • Sharing Files with Microsoft Office Users

    Sharing Files with Microsoft Office Users

    Sharing Files with Microsoft Office Users Title: Sharing Files with Microsoft Office Users: Version: 1.0 First edition: November 2004 Contents Overview.........................................................................................................................................iv Copyright and trademark information........................................................................................iv Feedback.................................................................................................................................... iv Acknowledgments......................................................................................................................iv Modifications and updates......................................................................................................... iv File formats...................................................................................................................................... 1 Bulk conversion............................................................................................................................... 1 Opening files....................................................................................................................................2 Opening text format files.............................................................................................................2 Opening spreadsheets..................................................................................................................2 Opening presentations.................................................................................................................2
  • IBM PC Club IBM PC Club

    IBM PC Club IBM PC Club

    San Jose PC CI ub Newsletter Document Number SJPCN03 May 4, 1982 Edited by Bonnie Lamb F98/142 San Jose 8 + 276-3653 VM(SJEVMl/LAMB) IBM PC Club IBM PC Club CONTENTS IBM SAN JOSE PC NEWSLETTER 1 Errata 1 April Meeting . 2 Special Interest Groups (SIG) 3 Survey Results ....... 3 San Jose PC Club Profile 5 Tips and Techniques 6 Programming notes 8 Electrohome 1302 Color Monitor with the PC 11 VOLKSWRITER Comparison to EASYWRITER 12 PC Puzzler 14 I nstall Notes 16 PC Club Program Library Directory 17 PC Add-Ons .... 19 SORT Comparisons 20 Help Wanted/Help Offered 21 Classified 22 PC Newsletter Articles 23 ii SJPCN03 05/04/82 IBM PC Club IBM SAN JOSE PC NEWSLETTER This month's newsletter has some survey results, sort performance information, a crossword puzzle (don't peek at the answers), and other good stuff. Time is short, we should have gone to press yesterday, so I'll close with next month's activity schedule: DATE DAY TIME LOCATION EVENT May 11 Tue. 5 p.m. STL Cafeteria PC Club Meeting May 12 Wed. 7:30p.m. DYSAN Santa Clara SVCC May 18 Tue. 5 p.m. STL K210 Phototypsetting SIG May 25 Tue. 5 p.m. STL K210 Visiclub (SIG) Meeting June 1 Tue. 5 p.m. STL K210 Advisory Meeting ERRATA The Silicon Valley Computer Club (SVCC) has found a bug in the BIOS modification that was printed in SJPCNOI to allow double-sided floppies. Details of symptoms and a possible fix are in the works. Look in next month's newsletter for this in­ formation.
  • DECEMBER 1984 Editorial

    DECEMBER 1984 Editorial

    SECRET UJUJUVC!JUJUJlb f5l5CBl!JWVU~ !D~~WCB~ Cf l!l U1 v ffil! f] Ill~(! ffi g 00 (!{il C!J l! '7 00 {iJ U1 ~ [1{iJ w~ NOV-DEC 1984 EO 1. 4. (c) P .L. 86- 36 . TRENDS IN HF COMMUNICATIONS (U) •••••••••••• • ••• J.._ ___---..._.1. \\:>............ 1 • SWITCHBOARD: • PAST, PRESENT AND FUTURE (U) •• ~ ............. I • • \ I .......... 5 \ OUT OF MY DEPTH (U) .......................•............•...; .. i .. \ ... ·........ 7 . • • • • • • • • • • • • • • • • • • • • • • ! I ...\ .......... s 1 EXPLORING A DOS DISKETTE (U)................... I ...... :; , ........ 12 HUMAN FACTORS (U) •••••••••••••••••••••••••••••• I l ........ 22 CAN YOU TOP THIS? (U) ........................... E. Leigh Sawyer ... , \~ ••••••• 24 PERSONAL COMPUTING IN A GROUP (U).............. • •••••• 25 FACTION LINE (U) ••• , •••••••••••••••••••••••• • ••• Cal Q. Lator •••••••••••••• • 35 NSA-CROSTIC NO. 59 (U) •••.•••••••••••••••••••••• D.H.W.;.,, ••••••••••••••••• 36 'flllS BOC\'.JMBNT <JONTl.INS <JOBl'JWORB MATl'JRIAh Ghi'tSSIFIEB BY tfSA/SSSM lH 2 SECRET BEGI:a\-SSIFY 0N. 0r igiriet iug Agency's Betezminatior:t Reqaized Declassified and Approved for Release by NSA on 'I 0- '16-2012 pursuant to E 0 . 13526, MOR Case # 54 77B OCID: 4009933 Published by Pl, Techniques and Standards EO 1. 4. ( c) P~L. 86-36 VOL. XI, No. 11-12 NOVEMBER-DECEMBER 1984 Editorial PUBLISHER BOARD OF EDITORS Edi.tor ...•••......_I _______ ... 1(963-3045s .) Product ion .•....•. I .(963-3369s) . : : : :· Collection .••••••..•••• i------.jc963-396ls) Computer Security •: ' •••••• 1 ,(859-6044) Cryptolinguist ics. l 963-1 f03s) Data Systems .•...•.•• ·l ., 963-4,953s) Information Science " • ..... I lc963-.5111s> Puzzles .......... David H. Williams'f(9637'Il03s) Special Research • ..•. Vera R. Filby;! C968'-7119s) Traffic Analysis •. Robert J. Hanyo!<f! (968-3888s) For subscript ions .. , send name and organizat~on to: I w14I i P.L.