PostalOne!® Mail.dat Technical Guide
Version 19.0.0

March 2009

PREFACE

This document is a comprehensive technical guide that outlines steps for exchanging electronic data with the PostalOne!® system using the Mail.dat® file format. The intended audience is business mailers who create/use mailing data in the preparation and/or production of business mail and who also want to send that electronic mailing data to the PostalOne! system for the purpose of conducting business electronically in lieu of the hardcopy forms and processes that were traditionally used in business mail acceptance. Although this guide provides an overview of the PostalOne! system, the intended recipient of this document is the person or team that will make necessary technical infrastructure preparations/alterations and conduct testing to ensure Mail.dat electronic data is consistently and reliably sent to the PostalOne! system. This document only discusses this form of electronic data exchange.
This guide is organized as follows: Chapters 1 and 2 provide an overview of the PostalOne! program benefits, the basic requirements for participation in the program, and how to apply for participation. Chapters 3 through 4 provide detailed technical information about the PostalOne! application. Chapter 5 provides information on who to contact for help. Appendices A, B, C, and D contain technical information about the electronic data used by or returned by the system. Appendix E contains error messages that you may need to reference.
On behalf of the PostalOne! team, we would like to welcome you into the program. You will be joining many other business mailers who are successfully using the PostalOne! system to improve the collaboration with the U.S. Postal Service®. We welcome your feedback and look forward to working with you.	

PostalOne!, USPS, U.S. Postal Service, United States Postal Service, First-Class Mail, Standard Mail, and Priority Mail are registered trademarks, and Postal Service is a trademark of the United States Postal Service. IDEAlliance and Mail.dat are registered trademarks of the International Digital Enterprise Alliance, Inc. (IDEAlliance). Sun, Sun Microsystems, and Java are trademarks or registered trademarks of Sun Microsystems, Inc. Microsoft, Microsoft Windows, and Microsoft Internet Explorer are registered trademarks of Microsoft Corporation. All other trademarks used are the property of their respective owners.

TABLE OF CONTENTS
1	Program Overview	1
2	Applying for Participation	1
3	Sending Properly Configured Mailing Files	1
3.1	Key Technical Requirements	2
3.1.1	Internet Connection	2
3.1.2	Formatted Mailing Files	2
3.1.3	Methods of Transferring Files (Manual and Batch)	3
3.2	Technical/Operational Prerequisites	3
3.2.1	Hardware	4
3.2.2	Software	4
3.2.3	Network	5
3.2.4	Infrastructure	5
3.2.5	Information/Manuals	5
3.2.6	User License Code	5
3.2.7	Security Certificates	5
3.2.8	Collaboration	5
3.3	Configuring Mailing Files for Processing	6
3.3.1	Required Files and Fields	6
3.3.2	Postage Statement Generation, Rejection, and Conflict Resolution	6
3.3.2.1	Key Fields	6
3.3.2.2	Segment Rejection	8
3.3.2.3	Issue Date Validation	9
3.3.2.4	Periodicals Rate Calculations	9
3.3.2.5	Bound Printed Matter Validation Issues	9
3.3.2.6	Unsupported Mailing Cases	9
3.3.3	Postage Payment	10
3.3.3.1	Permit Roles	10
3.3.3.2	Additional Postage	11
3.3.4	Typical File Formatting Problems	12
3.3.5	Sending Job Updates	13
3.3.5.1	File/Record Level Status	14
3.3.5.2	Rules for Sending Updates	15
3.3.5.3	Commands	16
3.3.6	File Processing Overview	16
3.4	Transferring Files	17
3.4.1	Validating Files	18
3.4.1.1	Validation Constraints	19
3.4.1.2	MLOCR Validation Constraints	23
3.4.1.3	Relationship Constraints Description	24
3.4.1.4	Validation Log Errors	28
3.4.2	Performing the File Transfer	28
3.4.3	Adjusting Memory Limits for Manual Transfers	30
3.4.3.1	Verifying Java Installation	30
3.4.3.2	Verifying Memory	30
3.4.3.3	Increasing Memory Limits for Java 1.4.2_x	30
3.4.3.4	Increasing JAVA Memory Limits for Java 1.5.x or 1.6	31
4	Batch Processing	31
4.1	Prerequisites for Batch Processing	32
4.1.1	Hardware	32
4.1.2	Software	32
4.1.3	Network	33
4.1.4	Downloading and Configuring the Windows Batch Processor	33
4.1.5	Downloading and Configuring the UNIX Batch Processor	35
4.1.6	Digital Certificates/Security	38
4.1.6.1	Creating a Keystore	38
4.1.6.2	Creating Certificate Signing Requests	39
4.1.6.3	Submitting Your Certificate Signing Request	40
4.1.6.4	Adding a Signed Certificate to a Keystore	40
4.1.6.5	Enabling Encryption on the Batch Processor Client	41
4.1.6.6	Testing Your Signed Certificate	41
4.1.6.7	Testing Batch Processor Setup	41
4.1.7	Scheduling Batch Jobs (Running the Batch Processor)	42
4.1.8	Adjusting Memory Limits for Batch Transfers	42
4.2	File Transfer Error Codes and Messages	42
5	Customer Support	42
Appendix A. Mail.dat File Definitions	44
Appendix B. Mail.dat Field Validation	47
Header Record	47
Segment Record	49
Mail Piece Unit	51
Mail Piece Unit – Class Values	52
Flats Machinability Values for Periodicals Mailings	52
MPU/C Relationship Record	53
Mailer Postage Account Record	53
Component Record	54
Issue Date Values	55
Container Summary Record	56
Container Type Values	59
Container Level Values	60
Entry Point for Entry Discount – Container Entry Values	60
International Container Label Record	61
Container Quantity Record	62
Package Quantity Record	63
Package Level Values	64
Walk Sequence Record	64
Seed Name Record	65
Package Label Record	65
IJ/C Relationship Record	66
Piece Detail Record	66
Special Fees/Charges Record	66
Manifest Individual Record	67
Manifest Summary Record	68
Postage Adjustment Record	69
Actual Tray File Record	70
Actual Pallet File Record	70
Information Access Key File Record	71
Piece Detail Record (XML version)	71
Appendix C. Status Receipt File Layout	73
C-1  Status Receipt File Content	73
C-2  Record Types and Record Format	73
Appendix D. Postage Statement Receipt File Layout	77
Appendix E. Error Messages	78
Issue Resolution	78
Processing Order	78
Mail.dat Client	79
Upload Server	86
Mail.dat Package	95
Wizard Web Service	101

LIST OF FIGURES
Figure 3‑1. The PostalOne! System - Electronic collaboration via the Internet
Figure 3‑2. Postage Payment Roles
Figure 3‑3. Sending Job Updates to the PostalOne! System
Figure 3‑4. Mail.dat File Transfer Process

LIST OF TABLES
Table 3‑1. RAM Requirements Based on Net Job Size
Table 3‑2. Key Postage Statement Generation Fields
Table 3‑3. Key Consolidation Fields
Table 3‑4. Presort and MLOCR Regular ID Requirements
Table 3‑5. MLOCR One-Pass ID Requirements
Table 3‑6. Files Included in Original and Update Transfers
Table 3‑7. File and Record Level Status Values
Table 3‑8. Allowable Container Status Values
Table 3‑9. RAM Requirements Based on Net Job Size
Table 3‑10. Presentation Category Values Required to Pass Validation
Table 3‑11. Enclosure Payment Settings
Table 4-1. RAM Requirements Based on Net Job Size
Table 4-2. Postal1.ini Parameters for Windows
Table 4-3. Postal1.ini Parameters for UNIX
Table A-1. Mail.dat Files and Definitions
Table B-1. Header Record - .HDR
Table B-2. Segment Record - .SEG
Table B-3. Mail Piece Unit Record - .MPU
Table B-4. Supported Mail Piece Unit – Class Values
Table B-5. Flats Machinability Values for Periodicals
Table B-6. MPU/C-Relationship Record - .MCR
Table B-7. Mailer Postage Account Record - .MPA
Table B-8. Component Record - .CPT
Table B-9. Suggested Issue Date Values by Frequency
Table B-10. Container Summary Record - .CSM
Table B-11. Container Type Values
Table B-12. Container Level Values
Table B-13. Entry Point for Entry Discount - Facility Type Values
Table B-14. International Container Label Record - .ICL
Table B-15. Container Quantity Record - .CQT
Table B-16. Package Quantity Record - .PQT
Table B-17. Package Level Values
Table B-18. Walk Sequence Record - .WSR
Table B-19. Seed Name Record - .SNR
Table B-20. Package Label Record - .PLR
Table B-21. IJ/C Relationship Record - .ICR
Table B-22. Piece Detail Record - .PDR
Table B-23. Special Fees / Charges Record - .SFR
Table B-24. Manifest Individual Record - .MIR
Table B-25. Manifest Summary Record - .MSR
Table B-26. Postage Adjustment Record - .PAR
Table B-27. Actual Tray File Record - .ATF
Table B-28. Actual Pallet File Record - .APF
Table B-28. Information Access Key File Record - .IAK
Table E-1. Mail.dat Client Error Messages
Table E-2. Upload Server Error Messages
Table E-3. Mail.dat Package Error Messages
Table E-4. Wizard Web Service Error Messages

1	Program Overview
The PostalOne!® system is an electronic suite of services being developed for business mailers by the United States Postal Service® to dramatically improve the mailing process. The system takes advantage of the advances in technology and leverages them to significantly improve and simplify the mailing experience.
One of the ways the system enables customers to electronically send detailed information is using the mailing industry's standardized Mail.dat® format. Customers using the system no longer have to complete manual postage statements because they can be automatically generated by the PostalOne! system. In fact, much of the acceptance and verification process has been automated, enabling a faster and more accurate method of accepting, assessing, and finalizing postage statements. The electronic documentation provided through the system means you no longer have to physically bring hardcopy presort documentation to the acceptance unit or retain it for storage.
Customers can download the estimated postage, view individual postage statements within a mailing, see a running total of postage statement activity, and view the reconciliation of the information at the end of a mailing information exchange process (mailing job). By automating and incorporating payment processing into the PostalOne! system, payments for mailing jobs can be electronically processed.
As an added benefit, the Transportation Management function of the PostalOne! system provides select users with the ability to make surface and air transportation assignments and route mail in the mailer's own plant. This capability is a great benefit to many of the larger First-Class Mail® customers because they can track mailings more accurately by knowing the detailed routing. This capability includes, but is not limited to, information found in Mail.dat files. 
2	Applying for Participation
Applying for and obtaining access to the PostalOne! system is quick and easy. We have made the application process available online through our website at http://www.usps.com/postalone. On the right, near the top of the page under New Customers, click the Learn More button. Then click the Apply Online link at the bottom of the Business Customer section. There, you can complete your online application. Following completion, our Customer Care Center reviews the application to ensure that we have accurately established your account. After completing your online application, you will receive the PostalOne! Welcome Kit. The kit contains additional information about the many features of the PostalOne! system as well as the program's Data Exchange Agreement.
NOTE: All companies participating in the PostalOne! program are required to sign an agreement, which details the participant's rights and responsibilities in this electronic arena.
3	Sending Properly Configured Mailing Files
To successfully conduct business electronically in the PostalOne! system, you will send mailing files via the Internet. These mailing files must be in the mailing industry format called Mail.dat. Without this exchange of information, electronic collaboration is not possible.
Mail.dat files are processed and stored in the PostalOne! system. Postal Service™ personnel access these files over the Internet to conduct business. For example, Postal Service acceptance clerks use these detailed mailing data files in the mail verification and acceptance process. The PostalOne! system uses the mailing files to generate postage statements for customers who have presented mailings to the Postal Service.
The figure below illustrates the relationship between the system and its users. It shows how business mailers submit mailing data to the PostalOne! system and how that data is retrieved by Postal Service business mail entry units.

Figure 3‑1. The PostalOne! System - Electronic collaboration via the Internet
NOTE: Mail.dat is a registered trademark of International Digital Enterprise Alliance, Inc. (IDEAlliance®) 2001-2007. IDEAlliance (http://www.idealliance.org/) is a not-for-profit membership organization, whose mission is to advance user-driven, cross-industry solutions for all publishing and content-related processes by developing standards, fostering business alliances, and identifying best practices.
3.1	Key Technical Requirements
3.1.1	Internet Connection
The minimum required speed for connectivity is 56kps. For optimal performance, we suggest that users with file sizes greater than one megabyte (MB) use some form of high-speed Internet access, such as T1 lines, DSL, cable modem, etc.
3.1.2	Formatted Mailing Files
To participate in the PostalOne! program, the files and fields you send must comply with PostalOne! implementation of the Mail.dat File Specification. Additional technical details concerning Mail.dat file format and content, as used by the PostalOne! system, are provided in Section 3.3, Configuring Mailing Files for Processing. As a participant, you must successfully transfer Mail.dat files to the PostalOne! system.
3.1.3	
Methods of Transferring Files (Manual and Batch)
The PostalOne! system provides you with a choice of transfer methods for your mailing data files (Mail.dat files). You can transfer mailing data files manually (Manual mode) or unattended (Batch mode).
1.	Manual mode. In Manual mode, customers log on, select the files they want to send, and then upload them. This mode is called Manual because a person must actively use the PostalOne! system and be present while the file is transferred. The information presented in this chapter assumes you will make Manual mode file transfers to the system.
2.	Batch mode. Batch mode allows customers to schedule file transfers to take place automatically, for example at 2 a.m. Once Batch mode is set up, no one needs to be present when the file transfer takes place. This capability requires additional infrastructure and configuration work. If you plan to send files in Batch mode, see Chapter 4, Batch Processing.
When using Batch mode, the PostalOne! servers return file transfer status feedback to the sender's workstation automatically. The feedback information (receipt file) is written to the client's workstation in either XML or character delimited ASCII text formats. You can load receipt files into a spreadsheet or your own database for storage and viewing. Status receipt files are the only receipt files currently available. For more information on the receipt file format and its contents, see Appendix C. Status Receipt File Layout and Appendix D. Postage Statement Receipt File Layout. 
3.2	Technical/Operational Prerequisites
As previously discussed, the system is Internet-based and the basis for conducting business electronically is the successful exchange of mailing data information between business mailers and the Postal Service. As a result, an Internet-based infrastructure must exist that is compatible with the PostalOne! system.
This section provides details on all of the technical and operational prerequisites necessary to successfully send mailing data files to the system. Topical areas include:
1.	Hardware prerequisites. The base requirements for the hardware elements of the computer system that will access and send mailing data files to the PostalOne! system such as the recommended physical memory amounts. For more information on hardware prerequisites, see Section 3.2.1, Hardware.
2.	Software prerequisites. The base requirements for the software elements of the computer system that will access and send mailing data files to the PostalOne! system, such as browser software versions. For more information on software prerequisites, see Section 3.2.2, Software.
3.	Networking prerequisites. The base requirements for the networking elements of the computer system that will access and send mailing data files to the system, such as firewall settings. For more information on network prerequisites, see Section 3.2.3, Network.
4.	Mail.dat prerequisites. The base requirements for the actual files sent. The PostalOne! system complies with the Mail.dat File Specification. As a result, mailing files must comply with this specification and the exceptions noted in this guide. This document notes any instances where the PostalOne! system differs from the Mail.dat specification, and supersedes the specification in all such instances.. We strongly recommend that you obtain and read the specification. For more information, see Section 3.2.5, Information/Manuals.
5.	User License Code (ULC) prerequisites. To use Mail.dat, your company must have a ULC, also called a Provider Code. Business mailers using Mail.dat should already have a ULC; if not, they need to get one before continuing. For more information, see Section 3.2.6, User License Code.
6.	Optional digital certificate prerequisites. To send mailing files in Batch mode, your company must obtain and install a digital security certificate. For digital certificate requirements, see Section 3.2.7, Security Certificates and Chapter 4, Batch Processing.
3.2.1	Hardware
The minimum workstation requirements to send data files are a PC with a Pentium IV 1 GHz processor, Microsoft® Windows® 95/98/2000/XP operating system, and 256 MB RAM. Depending on the size of the Mail.dat job, RAM requirements vary. The table below details the RAM requirements: 
Table 3‑1. RAM Requirements Based on Net Job Size
Net Size of Mail.dat Job (MB) *	Recommended Physical RAM	
0 - 10	64 MB	
11 - 25	128 MB	
26 - 50	256 MB	
> 50	>1024 MB	
* The net size of a Mail.dat job is calculated as the "total size of all files" associated with a job, minus the size of the PQT, SNR, and PDR files.
For Mail.dat jobs with a large total file size, file transmission may result in an “Out of Memory” error. To resolve this issue, modify the Java™ Virtual Machine (JVM) memory arguments, then retry the transmission. For more information on how to modify the JVM memory settings, see Section 3.4.3 for manual mode, or Section 4.1.8 for batch mode.
NOTE: UNIX workstations can also be used to send mailing data files in Batch processing mode. For more details, see Chapter 4, Batch Processing.
3.2.2	Software
Windows workstations used for transferring files should be configured using the following software:
•	A text editor or third-party Mail.dat viewer. This software is necessary to analyze the contents of your Mail.dat files and resolve any file format or content problems reported by the PostalOne! system.
•	Microsoft Internet Explorer® 5.0 or later with the Java Virtual Machine (JVM) plug-in or Netscape® Communicator 6.0 or later with JVM plug-in. The JVM should be version 1.4.2 (see the next bullet). In the Internet Options dialog box, the Use Java x.x for <applet> check box must be selected on the Advanced tab.
•	Because newer Microsoft operating systems (such as Windows® XP) no longer support some Java software, users with new installations of Microsoft operating systems must now install Sun Microsystems® Java Virtual Machine 1.4.2 or greater on their browsers. If you do not do this, the PostalOne! functions for file validation and manual file transfer will not work. The Batch Processor has a different requirement. 
To install the JVM, ensure you have administrator rights on your computer, then click the links on the Sun Microsystems site at: http://www.java.com/. If a security warning dialog box opens, click Yes to install, and follow any directions. If you do not have administrator rights, contact your system administrator. Once installed, the JVM automatically runs whenever necessary.
For information about batch mode requirements, see Chapter 4, Batch Processing.
3.2.3	Network
The File Transfer software (Manual mode) uses http/https protocol to communicate through port 443. If firewall settings prevent http/https communication through port 443, reconfigure the firewall to allow this traffic. Port 443 is the standard port for https communication.
The Batch Processor software uses the http/https protocol to communicate through port 444. If firewall settings prevent http/https communication through port 444, reconfigure the firewall to allow this traffic. See Chapter 4, Batch Processing.
3.2.4	Infrastructure
Because the PostalOne! system is Web-based, no infrastructure requirements exist other than the hardware and software previously discussed.
3.2.5	Information/Manuals
To ensure that you accurately configure your Mail.dat files, use this guide and the Mail.dat File Specification, Version 08-2. While the PostalOne! system also supports version 07-1 (history files only) and 08-1, the latest version is recommended. The Mail.dat File Specification is a key document from IDEAlliance. As a nonprofit organization, IDEAlliance charges a nominal fee for the file specification. The fee covers the costs of changes, updates, printing, and notifications to customers. If you do not have a current copy of the specification, contact IDEAlliance at (703) 837-1088 or download it online at http://www.idealliance.org/maildat/. 
IDEAlliance
100 Daingerfield Rd., Fourth Floor
Alexandria, VA 22314
For technical support, contact the PostalOne! Customer Support team. See Section 5, Customer Support, for contact information.
3.2.6	User License Code
To participate in the PostalOne! program, obtain a valid User License Code (ULC) from IDEAlliance, who assigns a ULC to each Mail.dat user. The ULC uniquely identifies you to the Postal Service. Customers who generate, update, or pass along Mail.dat files for subsequent use must have a ULC.
3.2.7	Security Certificates 
The PostalOne! system uses Secure Sockets Layer (SSL) Version 3.0 to transfer files safely over the Internet. SSL is a secure enhancement to the standard Transmission Control Protocol/Internet Protocol (TCP/IP). It uses a combination of cryptographic processes to authenticate the host computers, and to encrypt and decrypt data transferred between them.
If you use the Manual mode file transfer process, the pre-installed VeriSign® client SSL certificate (included with the web browser) secures the file transmissions. No user setup is required for this process other than using the required web browser.
If you use the Batch mode file transfer process, your company must have a SSL certificate installed and set up. For information about security certificates, see Section 4.1.6, Digital Certificates/Security.
3.2.8	Collaboration
For unresolved issues with Mail.dat files, the IDEAlliance Mail.dat Work Group collaborates with the Postal Service to find solutions for future releases. All Mail.dat licensees may participate in the Mail.dat Discussion Forum on the IDEAlliance collaborative Web site (http://pmstage.freecom.at/pmstage/). Topics of interest include:
•	Handling for Periodical container charges
•	Firm bundles and non-incidental enclosures
•	Virtual bundles – from USPS
•	Mail Piece Unit ID – Definition in Segments
•	Files, Fields, values to be deleted (applies to all mail classes)
•	Mail.dat specification 09-1 (work in progress)
3.3	Configuring Mailing Files for Processing
This section provides details about the Mail.dat File Specification as they relate to data elements used by the PostalOne! system. Specifically, it covers required files and fields, typical problems, sending job updates, and file processing. We strongly recommend that you acquire the Mail.dat File Specification from IDEAlliance. For more information about obtaining the specification, see Section 3.2.5, Information/Manuals.
3.3.1	Required Files and Fields
 A Mail.dat job sent to the PostalOne! system consists of, at most, twenty-one files. Each file in the set sent for a job consists of a different record type. Key fields within the records provide linkage from one file to another, thus creating a hierarchical relationship between the files. The PostalOne! system uses the Mail.dat standards as specified within the Mail.dat specification, with a few exceptions. This guide includes any exceptions and rules specific to USPS and/or the PostalOne! system. In any instance where this guide differs from the Mail.dat specification, this guide’s rules take precedence.
For a listing of the files available in Mail.dat, see Appendix A. Mail.dat File Definitions. To review the validation performed by the PostalOne! system, see Appendix B. Mail.dat Field Validation. Appendix B also notes any fields required by the PostalOne! system, but not marked in the Mail.dat specification.
3.3.2	Postage Statement Generation, Rejection, and Conflict Resolution
This section discusses the key fields used to indicate a new postage statement within a job, the issues that can cause rejection of a segment of a Mail.dat job, and conflict resolution for redundant values in Periodicals mailings. 
3.3.2.1	Key Fields
This section discusses the key fields used to indicate a new postage statement within a job, based on the Mail.dat 08-2 specification and the PostalOne! system. One job may contain multiple postage statements. The PostalOne! system generates a new postage statement each time a unique set of information is found in the following fields: 
Table 3‑2. Key Postage Statement Generation Fields
Field	Record(s)	Position(s)	Notes	
Job ID	(Multiple files)		Must be identical for all files in the job.	
Mailing Facility	(Multiple files)		Must be identical for all files in the job.	
Provider Code	(Multiple files)		Must be identical for all files in the job.	
Periodicals Issue Number	Component (CPT)	157-162	Periodicals only.	
Periodicals Volume Number	Component (CPT)	152-156	Periodicals only.	
Container Ship Date	Container Summary (CSM)	101-108		
Container Status	Container Summary (CSM)	198		
Entry Point for Entry Discount Postal Code	Container Summary (CSM)	43-48	Periodicals only.	
Postage Grouping ID	Container Summary (CSM)	233-240		
CAPS Reference Number	Mailer Postage Account (MPA)	100-139		
Federal Agency Cost Code	Mailer Postage Account (MPA)	171-175	Non-Periodicals only.	
Permit Number	Mailer Postage Account (MPA)	58-65	Pending Periodicals and non-Periodicals, including enclosures	
Permit ZIP Code + 4	Mailer Postage Account (MPA)	81-89		
Postage Payment Method	Mailer Postage Account (MPA)	140		
Publication Number	Mailer Postage Account (MPA)	49-57	Periodicals only.	
Rate Type	Mailpiece Unit (MPU)	94		
Mail Piece Unit (MPU) ID	Mailpiece Unit (MPU)	13-17	Periodicals only.	
Mail Piece Unit Weight	Mailpiece Unit (MPU)	60-65	Periodicals only.	
Mail Piece Unit Name	Mailpiece Unit (MPU)	18-29	Periodicals only.	
Periodicals Advertising Percentage	Mailpiece Unit (MPU) or
Component (CPT)*	87-91
74-78	Periodicals only.	
Periodicals Frequency	Component (CPT)	171-173	Periodicals only.	
Periodicals Issue Date	Component (CPT)	163-170	Periodicals only.	
Processing Category	Mailpiece Unit (MPU) or Component (CPT)*	95-96
82-83		
Mail Piece Unit - Class
Component Class	Mailpiece Unit (MPU) or
Component (CPT)*	93
80		
Automation Coding Date	Segment (SEG)	167-174	Periodicals only.	
Carrier Route Coding Date	Segment (SEG)	175-182	Periodicals only.	
Carrier Route Sequencing Date	Segment (SEG)	183-190	Periodicals only.	
<Mail Class> Sacking Criteria	Segment (SEG)	76-81	Non-Periodicals only.	
Packaging Services Packaging Criteria	Segment (SEG)	165-166	Non-Periodicals only.	
Container and Bundle Charge Method	Segment (SEG)	249	Periodicals only.	
MPA ID for Container and Bundle Charge Method	Segment (SEG)	250-259	Periodicals only.	
* When both MPU and CPT values are listed, the CPT values are used for enclosures.
** Only used if the same MPU ID appears multiple times within 
Once postage statements have been created, the PostalOne! system reviews the new statements to see if consolidation is necessary. A new consolidated statement is generated for each unique set of the listed fields within a job. 
Table 3‑3. Key Consolidation Fields
Field	Record(s)	Position(s)	
Job ID	(Multiple files)		
Mailing Facility	(Multiple files)		
Periodicals Issue Date	Component (CPT)	163-170	
Periodicals Issue Number	Component (CPT)	157-162	
Periodicals Volume Number	Component (CPT)	152-156	
Container Status	Container Summary (CSM)	198	
CAPS Reference Number	Mailer Postage Account (MPA)	100-139	
Federal Agency Cost Code	Mailer Postage Account (MPA)	171-175	
Mail Owner’s Lcl Permit Ref Num / Int’l Bill Num	Mailer Postage Account (MPA)	90-97	
Mail Owner’s Lcl Permit Ref Num / Int’l Bill Num - Type	Mailer Postage Account (MPA)	98	
Permit ZIP Code + 4	Mailer Postage Account (MPA)	81-89	
Postage Payment Method	Mailer Postage Account (MPA)	140	
USPS Publication Number	Mailer Postage Account (MPA)	49-57	
Rate Type	Mailpiece Unit (MPU)	94	
Mail Piece Unit Class
Component Class	Mailpiece Unit (MPU) or
Component (CPT)	93
80	
Processing Category	Mailpiece Unit (MPU) or Component (CPT)	95-96
82-83	
Container and Bundle Charge Method	Segment (SEG)	249	
3.3.2.2	Segment Rejection
Segment rejection occurs when a particular segment of a Mail.dat job fails validation. The PostalOne! system processes the entire Mail.dat job, and generates qualification reports, postage statements, etc. based on the information in the file, but skips any rejected segments and data specifically associated with those segments. Data associated with rejected segments include MPU and MPU/C Relationship Records associated only with the segment ID, as well as container IDs associated with the segment ID. Additionally, all CQT Database IDs associated only with the rejected container IDS and their records in the Package Quantity Record are also ignored during file generation. The segment rejection error message includes a description of the error(s) and the segment ID(s) of the rejected segment(s) so errors can be resolved. 
The following conditions can cause segment rejection: 
•	In a Periodicals mailing, the weight of a single ride-along piece exceeds 3.3 ounces (0.20625 lbs) and/or the weight per copy for the issue, as declared in the Component Weight field of the Component (CPT) record. 
•	A Periodicals mailing or an enclosure in a Periodicals mailing claims an unauthorized rate category, such as Nonprofit, Classroom, or Science of Agriculture. Special rates only apply to Outside County postage. The Mailing ZIP Code in the MPA record must be the finance unit granting an active permit authorization for the rate. The authorized permit must be used in the mailing. 
•	The Class Defining Preparation field in the SEG file does not match values 1 (First-Class Mail), 2 (Periodicals), 3 (Standard Mail®), or 4 (Package Services). 
When segment rejection occurs, other segments in the Mail.dat file are not affected. However, if all segments in a Mail.dat file fail, the entire job fails validation. Segment validation occurs during processing of "Ready to Pay" Mail.dat jobs. Any subsequent updates must be sent without the segment or with the segment still rejected and the associated containers removed. To resend the rejected segments, first correct the validation issues, then send a new or updated job with those segments. To prevent additional validation errors, do not include any segments that previously passed validation in the new or updated job. 
3.3.2.3	Issue Date Validation
If the required field Issue Date is missing from the CPT record for a Periodicals mailing, the file is rejected with the following error message: “For Periodical Statement # [#] Issue Date is required for 3541.” If Issue Frequency is missing, the PostalOne! system treats the field as blank and continues processing.
3.3.2.4	Periodicals Rate Calculations
The following items impact rate calculations: 
1.	Flats Machinability. The Flat Machinability field (position 118) in the MPU file accepts the value “Y” for flats machinable under DMM 301.1.3 and the value “U” for flats machinable under 707.26. The MPU Flats Machinability field (position 118) cannot be blank if Mail Piece Unit – Processing Category (positions 95-96) is “FL”.
2.	Outside County for bundles and containers. 
•	The rates for the Outside County Bundles depend on the Package Level (.pqt position 33) and the Container Level (.csm position 41-42). 
•	The rates for the Outside County Containers depend on the Container Type (.csm position 13), the Entry Point for Entry Discount – Facility Type (.csm position 49), and the Container Level (.csm position 41-42). 
For specific mappings, see Appendix B.
3.	Outside County payment method. In the required field Container and Bundle Charge Method (.seg position 249):
•	If the mailing does not include any Periodicals, this required field must be filled with a “0” (zero). 
•	If this field is set to the value “1” or “2”, the Segment field MPA ID for Container and Bundle Charge Method (positions 250-259) becomes required. 
•	If the value is set to  “3”, the MPA ID for Container and Bundle Charge Method field is not required.
•	Validation uses the first Container and Bundle Charge Method for the entire job. This differs from the Mail.dat specification.
4.	Unsupported mail preparations. 
3.3.2.5	Bound Printed Matter Validation Issues
The following list includes Bound Printed Matter (BPM) mailing combinations that result in file failure or incorrect postage statements when submitted using Mail.dat files. Incorrect validation issues affect the following BPM mailing combinations: 
•	Mailings that include bundles with a piece weight of less than one pound. These mailings fail validation with the error message "ORA-20001: EXITING WWS Data Submission Package - Invalid MPU weight." This file failure is due to a weight validation defect that will be corrected in a future release. 
•	Mailings that include bundles with the number of copies higher than the number of pieces result in an incorrect postage statement. To submit a BPM mailing that includes bundles, the Number of Pieces field (positions 58-61) must match the Number of Copies in the .pqt file. 
3.3.2.6	Unsupported Mailing Cases
The following mailing cases are not currently supported using Mail.dat files: 
•	Mailings with multiple mail classes.
•	Co-palletized mailings where a segment contains only mother containers. 
•	International mail.
•	Pending Periodicals in combined mailings, with parcel rates, or that include firm bundles. 
•	Mailings with firm bundles that include non-incidental enclosures 
•	Move Update method updates.
•	Per the DMM 707 section, Periodicals with:
•	Exception to Sacking (DMM section 23.4.2). Sacking is not required for bundles prepared for and entered at a DDU when the mailer unloads bundles under (DMM section) 28.4.6. Mail presented under this exception is not subject to the container charge (but is still subject to the bundle charges).
•	Bundle rates do not apply to barcoded letter-size mail prepared in full letter trays or to flat-size mail prepared in flat trays under the optional tray preparation in DMM sections 22.7 and 25.5. 
•	Periodicals parcels that are not bundled. If Periodicals parcels are not bundled, even irregular parcels, validation rejects the Mail.dat file. To submit Periodicals parcels that are not bundled per DMM section 23.4, submit the mailing with the alternative standardized documentation and postage statements.  
•	For MLOCR mailings, postage statements cannot claim the “Single Piece” rate category. 
•	Combined Periodicals mailings submitted using Mail.dat 07-1 files that include a Limited Circulation Discount (LCD). A mailing may either be a combined mailing or claim the LCD discount, not both.
The above list is not exhaustive; the Mail.dat specification may support additional cases that are not supported by the PostalOne! system. 
3.3.3	Postage Payment
This section discusses how to list the parties involved in a postage statement, including designating the permit(s) to be used for payment. 
3.3.3.1	Permit Roles
Postage statement permits can fill one or more of three primary roles: 
1.	Permit Holder.  This is the permit charged for the postage statement. This is represented in the MPA file as Permit Number (positions 58-65) or USPS Publication Number (positions 49-57).  The Postage Payment Method (positions 140), identifies the permit type of the listed Permit Number in the Mail.dat file.
2.	Mailing Agent (Preparer). This identifies the organization that prepared the mailing and/or delivered it to the postal service for mailing. This information is linked to the preparers login account, and is not represented in the Mail.dat file.
3.	Org for Mailing is Prepared (Owner):  This identifies the organization who owns the mail being sent. This is represented in the Mail Owner’s Lcl Permit Num (position 90-97). If this field is left blank, then the default in the postage statement is the same as the permit holder. The permit type for this permit number is Mail Owner’s Lcl Permit Ref Type (field 98) in the Mail.dat file. For example, if a ghost permit is listed in Mail Owner’s Lcl Permit Num, then position 98 will be listed as “V” = Virtual.
For an example of these fields on a postage statement, see Figure 3‑2. Postage Payment Roles. 

Figure 3‑2. Postage Payment Roles
3.3.3.2	Additional Postage
When postage affixed (precanceled stamp or meter) is used, the file must include a separate MPA record. This separate MPA record MUST be linked to a Permit Imprint account; Postage Payment Method (position 140) must be a “P”.
NOTE:  An MLOCR mailing with Postage Payment Method (.mpa position 140) values “G” (Government), “S” (Precanceled stamps), “C” (Metered - Correct), “L” (Metered – Lowest), or “M” (Metered – Neither) must have one Additional Postage MPA ID (positions 37-46) in the MPU / C Relationship (.mcr) record. Only one account is currently allowed for additional postage payment for this type of mailing, even if the mailing includes multiple statements. The first record must be a Metered or Precanceled Stamp permit, and is used to authorize the mailing. All subsequent MPA records must be Permit Imprint or ADDPOS (Additional Postage) permits, and are used to charge any additional postage due.
Presort & MLOCR Regular (2-pass) Files:
The MCR file links to the MPA record. The Primary MPA ID (positions 27-36) of the MCR record maps to the MPA Unique Sequence ID (positions 9-18) of the primary permit(s) in the MPA record.  When there is additional postage, then the Additional Postage MPA ID (positions 37-46) of the MCR record maps to the MPA Unique Sequence ID/Grouping ID (field 9-18) of the Permit Imprint in the MPA record set for additional postage in the Mail.dat file. 
NOTE:  An MLOCR mailing with Postage Payment Method (.mpa position 140) values “G” (Government), “S” (Precanceled stamps), “C” (Metered - Correct), “L” (Metered – Lowest), or “M” (Metered – Neither) must have one Additional Postage MPA ID (positions 37-46) in the MPU / C Relationship (.mcr) record. Only one account is currently allowed for additional postage payment for this type of mailing, even if the mailing includes multiple statements. The first record must be a Metered or Precanceled Stamp permit, and is used to authorize the mailing. All subsequent MPA records must be Permit Imprint or ADDPOS (Additional Postage) permits, and are used to charge any additional postage due.
Table 3‑4. Presort and MLOCR Regular ID Requirements
To Pay	MCR Record 1	MPA Record 1	MPA Record 2	
Postage Statement Charges	Primary MPA ID
(positions 27-34)	MPA Unique Sequence/Grouping ID
(positions 9-18)		
Additional Postage Charges	Additional Postage MPA ID
(positions 37-46)		MPA Unique Sequence/Grouping ID
(positions 9-18)	

MLOCR One-Pass Files: 
The Primary MPA ID (positions 27-36) maps to the MPA Unique Sequence ID (positions 9-18) of the primary permit(s) in the MPA record.  When there is additional postage, then the Additional Postage MPA ID (positions 37-46) maps to the MPA Unique Sequence ID (positions 9-18) of the Permit Imprint in the MPA record set for additional postage in the Mail.dat file.  In addition, the Postage Adjustment MPA ID (positions 56-65) must be the same as the Additional Postage MPA ID (positions 37-46).
Table 3‑5. MLOCR One-Pass ID Requirements
To Pay	MCR Record 1	MPA Record 1	MPA Record 2	
Postage Statement Charges	Primary MPA ID
(positions 27-34)	MPA Unique Sequence/Grouping ID
(positions 9-18)		
Additional Postage Charges	Additional Postage MPA ID
(positions 37-46)
Postage Adjustment MPA ID
(positions 56-65)		MPA Unique Sequence/Grouping ID
(positions 9-18)	
3.3.4	Typical File Formatting Problems
As more customers begin to utilize the PostalOne! system, we have been able to identify several common errors made in formatting fields. For details on field validation, see Appendix B. Mail.dat Field Validation. The more common errors are:
1.	The optional date fields defined in the Mail.dat File Specification are often filled with zeros. The system validates all optional fields containing information and does not consider zeros to be acceptable date values.
2.	The file/record level status flags are not used consistently. The system requires that all file/record level flags be consistent and does not allow any mixed Mail.dat transactions. For example, for an original Mail.dat transaction, all file level status flags should be set to "O".
3.	You attempt to transfer a file but it fails because of an "Invalid Facility ZIP+4" in the segment (.seg) record. When looking at the actual data, the file shows all of the data in the correct positions according to the Mail.dat File Specification. However, the software being used has written a blank record in the CR/LF pair causing the data in the Segment file to be off by two characters. 

Solution: Delete the blank record and resave the file; the data will be in the proper positions in the file.
4.	I/O Errors "Unable to connect to server." You can access the Internet and validate files, but when trying to transfer a file, you receive an I/O exception error.

There are a few situations that could cause this. Your inter-company network may allow read-only access to files. If you have your Mail.dat files saved on a network drive, the Transfer Applet is not being permitted to get the files and transmit those due to company firewall settings, inter-company network access, etc.

Solution: Create a folder on your local machine's hard drive, called "Mail.dat" for example, and save in that folder any Mail.dat files to be transferred to the PostalOne! system. Use the Transfer Applet and get the files from the new folder. This way, the Applet does not contend with the network firewall.
5.	I/O Errors "Unable to connect to server." You are transferring Mail.dat files from a folder on the local machine's hard drive (i.e., no network involvement, as described in the previous item) and still get an I/O exception error. Reasons:
a.	You may have lost connectivity to the Internet during the process.
b.	The PostalOne! database could be temporarily offline.
c.	It may be software related (an old browser or the user answered "No" to the security warning when trying to use the Transfer Applet).
6.	"Trying to Reinsert an Original File." You have sent a specific Mail.dat job and it transferred successfully; however, when you try to resend the file, the PostalOne! database fails the transfer because the file has already been transmitted under that specific Job ID.
When transferring Mail.dat files to the PostalOne! database, remember that once an original Mail.dat was transferred successfully, you can only send subsequent updates to that job, unless the job is deleted, then resent. For details about updates, see Section 3.3.5, Sending Job Updates.
To send an update to an existing Job in the system, make sure that all File Status flags in each file being transmitted reflect a "U" for update. All subsequent files included in the transfer of an update should include a “U” in the File Status flag field. For example:
a.	The Segment File SEG Record Status Flag (position 164) should contain a “U” for an update. 
b.	The Mail Piece Unit File MPU Record Status Flag (position 117) should contain a “U” for an update.
Alternately, to resend an original file, first delete the job, then resend the job. The same Job ID can be used if the first attempt to submit the file is deleted prior to the second attempt. For more information on deleting files, see Section 3.3.5.3, Commands. 
7.	If the files were validated and transferred, but not accepted by the database and you receive "Internal System Error," a file may have null characters. The database will not accept a file with null characters. To spot the null characters, open the Mail.dat files using the Textpad utility. The null characters appear as black squares. Delete the black squares, then resubmit the files.
8.	If files cannot be transferred due to an issue with the ZIP Code +4 or a permit, verify that you have a permit, even a ghost permit, at the same finance number (ZIP Code) as the permit(s) used to pay for the postage statements in the job. The finance number ZIP Code is available in the Mailer Postage Account record. 
3.3.5	Sending Job Updates
Large mailing jobs are often split into smaller production units, then produced and presented for acceptance incrementally (along with supporting documentation) over several days or even weeks. Specific details of a mailing job may change. For example, a piece weight may have changed or an initial estimated weight becomes finalized when the mail is produced. Also, in-process mailing jobs may be canceled in whole or in part for a variety of reasons. The PostalOne! system, via the Mail.dat File Specification, accommodates these and other tasks and provides business mailers the means to communicate them to the Postal Service.
The scenarios such as those described above are handled as updates to the original Mail.dat file initially sent to the system. The list below includes the general guidelines for sending updated Mail.dat files:
•	The system must receive an original Mail.dat file before any update can be received and processed.
•	Mailers can send multiple updates to a mailing job, as long as they observe the rules established by the Mail.dat File Specification and those of the system.
•	For mailers with an Optional Procedure (OP) mailing system, 100% of the containers in a mailing job must eventually be accounted for when a job is updated.
The table below lists the files a mailer would commonly include in original and update transfers.
Table 3‑6. Files Included in Original and Update Transfers
Original Mail.dat File	Update	
*Header	*Header	
*Segment	*Segment	
*Mailpiece Unit	Mailpiece Unit	
*MPU/C Relationship	Component	
*Mailer Postage Account	Container Summary	
*Component	Container Quantity	
*Container Summary		
*Container Quantity		
*Package Quantity		
*Required files
Following is a common update scenario to an original Mail.dat file: The mailer creates an ORIGINAL Mail.dat mailing data file after presort processing a large job and sends that file to the PostalOne! system. For each portion of the job, the mailer produces the incremental portion, presents it for acceptance, and sends an UPDATE to the Mail.dat file. For the portion of the mail that is presented for acceptance that it is “ready to pay,” a postage statement is created. This scenario is illustrated in Figure 3-2 below.
	Presort done on ENTIRE job		Mail.dat files sent to PostalOne!	
				
1	Mailing Job		Original Mail.dat file sent to PostalOne!	
				
First portion of Mailing Job	Mail produced day X, presented for acceptance. 		Updated Mail.dat file sent to PostalOne! for first portion	
				
Mail produced day Y, presented for acceptance.	Second portion of Mailing Job		UPDATED Mail.dat file sent to PostalOne! for second portion	
				
	Mail produced day Z, presented for acceptance.	Last portion of Mailing Job	UPDATED Mail.dat file sent to PostalOne! for final portion	
Figure 3‑3. Sending Job Updates to the PostalOne! System
NOTE: Mailers can indicate that a portion or entire mailing job is ready for payment in an Original mailing file. If an entire job or portion of a job is ready to pay and will be presented for acceptance, an Update is not necessary.
3.3.5.1	File/Record Level Status
To use the PostalOne! system, mailers must use file/record level status flags for all Mail.dat files. The table below lists the file/record level status flags allowed by the system.
Table 3‑7. File and Record Level Status Values
Mail.dat Transaction Type	File Level Status	Record Level Status	Required Files (Minimum)	
“O”riginal	All flags must be set to “O”.	All flags must be set to “O”.	HDR, SEG, MPU, MCR, MPA, CPT, CSM, CQT, PQT	
“D”elete	All flags must be set to “D”.	All flags must be set to “D”.	HDR, SEG	
“R”eplace	Not supported by the PostalOne! system.	Not supported by the PostalOne! system.	Not supported by the PostalOne! system.	
“C”hange	All flags must be set to “C”.	All flags must be set to either “I” or “U”.	HDR, SEG	
“U”pdate	All flags must be set to “U”.	All flags must be set to “U”.	HDR, SEG	
3.3.5.2	Rules for Sending Updates
When sending an update transmission, mailers participating in the PostalOne! program must follow these rules and requirements:
1.	The Header file must contain a "U" in the appropriate status field.
2.	The PostalOne! system validates all container status updates and fails transactions that violate the rules in the following table, which contains the valid container status values to which a given container can be changed. If updating the Container Summary Record, position 198 must reflect the appropriate status and have one of the following allowable values: 
Table 3‑8. Allowable Container Status Values
Container Status	Allowable Changes	Notes	
C	D, P, R, or X		
D		No changes allowed.	
O	D, P, R, X, or C		
P	D, P, R or C		
R	D, X, T, or C		
T	D, X, T, or C		
X	T		
3.	File transfers that include one or more containers with status “D” result in the cancellation of the entire postage statement and impact the reconciliation report accordingly. 
4.	Original file transfers can have a "P" value. A preliminary or estimated postage statement will be generated with the Qualification Report. This postage statement will have the stage “EST” displayed on the Dashboard. 
5.	File transfers with the container status “R” generate postage statements with a stage “UPD” (USPS Processing Due) displayed on the Dashboard. Postal clerks can only finalize (bill) UPD postage statements.
6.	The "R" value can only be resent if a container is cancelled (set to "C") prior to the second "R" being sent. The file fails if a second "R" is sent without canceling the container first.
7.	To update transportation information, use the "T" value to update the reservation number and container barcode information in a file set to “R” or “X”. The only way to update a file marked “X” is with a “T”. A "T" value is accepted only after an "R" or “X” has been sent because no transportation update is necessary until the indication of payment. You can update transportation information only after it has been marked Ready to pay ("R") or Paid and Closed (“X”). Original file transfers fail if a "T" is sent.
8.	Updates to weight are reflected only in a postage statement with a "P" or an "R" value. If an update to weight is received within any other update, it is logged, but no recalculation of the postage statement occurs until a "P" or an "R" value is received.
9.	Only one estimate of postage is generated for an entire mailing job, unless more than one actual postage statement is required for the mailing or the same containers are sent multiple times with status “P”. Original job files generate preliminary statements, and group containers by date; to perform these functions, the container status associated with the original submission must be “P”. A separate update is not required.
10.	Individual postage statements are generated for each unique Permit/USPS Pub number and each distinct Mailing Date populated in the Ship Date column in the .CSM file. The PostalOne! system consolidates postage statements across segments for an entire Mail.dat file. This applies to all files within a job that contain the same values for a postage statement: class, payment method, rate type, processing category, CAPS reference number, container ship date, sacking basis, packaging basis, entry point, and permit holder. Additionally, the PostalOne! system generates a new postage statement for each unique occurrence of the CAPS Customer Reference ID for the subset of the mailing identified by that ID. See Section 3.3.2 for key fields used in postage statement generation. 
3.3.5.3	Commands
The Delete Transaction
You can close a mailing job (i.e., containers canceled) by sending a "delete" file. This signals that the product, for whatever reason, is no longer going to mail.
A delete file is composed of a header file and a segment file. The segment file specifies the individual facilities (using the Verification Facility ZIP+4 field) affected. When the Verification Facility ZIP+4 is available, the job can be closed at a specific facility (if this job spans more than one facility). Verification Facility ZIP+4 is contained in the segment file.
The Change Transaction
If the File Status fields in the header file for a Mail.dat job are set to "C", the job is considered a "Change" job. Per the Mail.dat File Specification, available change actions are “I”nsert and “U”pdate, based on the values contained in the record level status flags. Although the specification includes support for the “D”elete flag, the PostalOne! system supports only the "I", "O" and "U" flags. Support for the "D" flag at the record level is pending.
Replace Transactions
A Mail.dat job may be replaced by sending a “delete” transaction (see above) then resubmitting the same job. 
3.3.6	File Processing Overview
When users select and send files manually, the PostalOne! system processes the files in the order the user selected them. When selecting multiple update files for transfer, users must select only those update files for which an original file has already been sent.
The batch file transfer module processes jobs in first-in-first-out (FIFO) order based on the date-time stamp on the Mail.dat files. However, this does not guarantee that the system completes jobs with different Job IDs in the original transfer order. For example, when a large job is transferred first and then followed by a smaller job with a different Job ID, the smaller job usually finishes first. This is because the file transfer module can process several jobs at a time, and the larger job takes longer to process.
The PostalOne! system Electronic Data Exchange process is detailed and illustrated in Figure 3-3 below.
1.	The customer transfers Mail.dat files to the PostalOne! system in one of two ways:
•	The Transfer Applet client, available on the PostalOne! website, manually transfers Mail.dat files to the PostalOne! File Upload Server.
•	The Batch Processor application, when scheduled, automatically transfers Mail.dat files to the PostalOne! File Upload Server using password protection and Secure Socket Layer (SSL) encryption. The File Upload Server then returns a Receipt file to the client machine.
2.	The File Upload Server inserts the Mail.dat files into the PostalOne! database.
3.	Various reports (including the postage statements) are made available from the PostalOne! web server. 
NOTE: Postage statements for Mail.dat files larger than 30MB may not be immediately available as those files take longer to process.

Figure 3‑4. Mail.dat File Transfer Process
3.4	Transferring Files
When mailers send files to the PostalOne! system, the file transfer software performs high-level file structure verification (called file validation) by checking the record counts for Mail.dat files provided in the Header record against the actual records present in the attached files. It also checks that all required fields exist. File Transfer fails the job if a required field is missing. It validates key field relationships between one or more records of files and verifies the structural and hierarchical integrity of the entire job by validating the proper existence of all predefined parent-child relationships.
To increase the likelihood of files transferring successfully, use File Validator to verify Mail.dat files before transferring them. The tool checks the validity of the data elements in the file and records error messages and warnings to the user's hard drive. To use the File Validator, under Tools, click File Validator. This is discussed in detail in Section 3.4.1, Validating Files.
After the mailing passes validation, you are ready to transfer it. For information on this, see Section 3.4.2, Performing the File Transfer.
3.4.1	Validating Files
The File Validator checks your Mail.dat files to ensure that all required fields are populated and contain the correct character format. This section explains how to use the File Validator feature.
Before using the File Validator, verify that the Physical Memory (RAM) available on your machine meets the recommendations listed in the table below:
Table 3‑9. RAM Requirements Based on Net Job Size
Net Size of Mail.dat Job (MB) *	Recommended Physical RAM	
0 - 10	64 MB	
11 - 25	128 MB	
26 - 50	256 MB	
>50	>1024 MB	
* The net size of a Mail.dat job is calculated as the "total size of all files" associated with a job, minus the size of the PQT, SNR, and PDR files.
For Mail.dat jobs with a large total file size, file transmission may result in an “Out of Memory” error. To resolve this issue, modify JVM memory limits, then retry the transmission. For more information on modifying memory limits for manual jobs, see Section 3.4.3.
NOTE: These memory requirements are for a single thread; when sending multiple simultaneous jobs, use the sum of all net sizes to estimate memory requirements.
To validate your Mail.dat files:
1.	Log on the test system. A special test system has been set up for new participants. It is located at https://cat.uspspostalone.com/postal1. This tool was created to provide a safe environment for testing files and to help you learn about the PostalOne! system.
2.	To open the File Validator page, on the left menu bar of the logon page, click File Validator. If you see a Security Warning pop-up box, click Yes to load the File Validator on your system as a temporary file. If you click No you will not load it or be able to use the File Validator.
3.	The "All Folders" pane displays your computer's local drives (usually A, C, and D). From the list, click the plus sign (+) next to the drive on which your job is saved.
4.	Scroll up or down to locate the folder in which your job is saved.
5.	Select the proper folder by clicking the folder name. The "File Contents of" pane displays the job header files.
NOTE: If the folder containing your job is in a subfolder, click the plus sign (+) next to the main folder to display the subfolders. From the subfolders, locate and select the appropriate folder.
6.	In the "File Contents of" pane, select the job header file you want to validate.
NOTE: To validate multiple job header files simultaneously, hold down the CTRL key while you select the job files.
7.	Before you validate the files, you may wish to change the validation.log file's name and location by clicking Validation Log File. By default, the File Validator writes the results to C:\Validation.log.
8.	Click Validate File(s) to begin the validation process.
9.	If your job passes the file validation process, a message indicating that the validation was successful appears. If your job fails the validation process, an error message appears. For more information about examining the validation log file, see Section 3.4.1.4, Validation Log Errors.
10.	Click OK to close the message.
3.4.1.1	Validation Constraints
The following relationship constraints are validated:
1.	To successfully pass the Mail.dat validation, the Mail.dat Presentation Category field in the Header record must be populated with one of the data values listed in the following table:
Table 3‑10. Presentation Category Values Required to Pass Validation
Data Value	Value Definition	Rules of Validation	
P	Conventional Presort	If Mail.dat Presentation Category is P, the following files must be present to successfully pass validation.
•	Header
•	Segment
•	MPU
•	MPU/C Relationship
•	Mailer Postage Account
•	Component
•	Container Summary 
•	Container Quantity
•	Package Quantity 
Optional files: 
•	Piece Detail Record	
M	MLOCR	If Mail.dat Presentation Category is M, the following files must be present to successfully pass validation.
•	Header
•	Segment
•	MPU
•	MPU/C Relationship
•	Component
•	Container Summary
•	Container Quantity
•	Mailer Postage Account
•	Package Quantity	
I	Manifest Individual	If Mail.dat Presentation Category is I, the following files must be present to successfully pass validation.
•	Header
•	Segment
•	Component
•	Container Summary
•	Manifest Individual
Optional Files:
•	Special Fees	
S	Manifest Summary	If Mail.dat Presentation Category is S, the following files must be present to successfully pass validation.
•	Header
•	Segment
•	Component
•	Mailer Postage Account
•	Manifest Summary	
N	Single-Piece	If Mail.dat Presentation Category is N, the following files must be present to pass validation:
Set A:
•	Header
•	Segment
•	Component
•	Manifest Summary
•	Manifest Individual
•	Container Summary
 - OR -
Set B:
•	Header
•	Segment
•	MPU
•	MPU/C Relationship
•	Mailer Postage Account
•	Component
•	Container Summary
•	Piece Detail Record	
2.	The Mail.dat file structure is validated for the different Mail.dat transaction types, as follows:
•	The file level status flags must be consistent for a given Mail.dat transaction. For example, for an "original" transaction, all file level status flags in the header record must be set to "O". If some optional files are not included in the "original" transaction, the record count for those files must be 0 (zero). Similarly, for "update" or "change" or "delete" transactions, all file level status flags must be set to "U" or "C" or "D" respectively.
•	"Original" transactions – For original Mail.dat transactions, the Mail.dat file structure is verified based on the presentation category, as described above.
•	"Update" transactions – For all update transactions, the Header and the Segment files are required. All other files are optional.
•	"Change" transactions – For change transactions, the Header and the Segment files are required. All other files are optional.
•	"Delete" transactions – Two types of delete transactions are supported by the PostalOne! system. To delete a complete job (including all segments of the job), a Header and a Segment file must be sent, referencing all Verification Facility ZIP+4s within the job. To delete specific segments in a job, a Header and a Segment file must be sent identifying the specific Verification Facility ZIP+4s to be deleted.
3.	All key field relationships between the different records of the Mail.dat file are validated, based on the Presentation Category.
4.	All Mail.dat records are validated to ensure that no duplicate records exist based on the key field combinations.
5.	Mail.dat records are validated to ensure that all required children are present, for any given parent record of a Mail.dat job.
6.	If the Sibling Container field in the CSM record is set to “Y”, the following fields must have values:
•	Job ID
•	Segment ID
•	Container ID
•	Container Type
•	Sibling Container Indicator
•	Sibling Container Reference ID
NOTE: 
•	All other fields, except for the optional label fields, in this CSM record MUST be left blank.
•	Validation rejects Ready-to-Pay Periodicals mailings with Sibling Container set to “Y”. 
•	For MLOCR mailings, mailers should take extra care when using sibling containers to define logical pallet to physical handling unit relationships. For more information on handling this scenario, see the Mail.dat Specification. 
7.	The Parent/Sibling Container relationship is validated. If a Sibling Container record exists, its parent must be present.
8.	If the Walk Sequence Record (WSR) file is used in the Mail.dat transmission, the Co-Palletization Code field in the MPU record must be present.
9.	If the Rate Category field in the PQT record is set to “A” (Saturation–ECR), the corresponding WSR record must be present.
10.	All Mailer Postage Account (MPA) records must have a value in the Permit ZIP+4/Postal Code field. The Permit ZIP+4 value must be the ZIP Code associated with the Post Office location where the permit is held or the original or additional entry office where the USPS Publication Number is held.
11.	Permit ZIP+4 – The PostalOne! application requires the Permit ZIP+4 field as part of the information necessary to uniquely identify a Permit number or USPS Publication Number at a Post Office location. For the PostalOne! system to complete an end-to-end transaction, it is necessary to have the Permit ZIP+4 information with all postage transactions.
12.	For the non-co-palletized portion of a co-palletized job, the co-palletized portion must not be included in the original file segment submitted for presort verification purposes. Packages in a co-palletized mailing must not be reported on a postage statement associated with the original presort. Mailings that are co-palletized cannot be reported unless a new file or file segment has been built that correctly identifies the package makeup of the new containers.
13.	If the Primary MPA ID in the MPU/Component Relationship (MCR) file of an update job is different from the original MPA ID, the new MPA ID must match the MPU – Unique Sequence/Grouping ID (positions 9-18) in the Mailer Postage Account (MPA) file of the first submission (original or preliminary).
14.	Individual container counts and the total container count cannot exceed the total number of pieces in a submitted postage statement.
15.	For Bound Printed Matter or Periodicals mailings that include First-Class Mail or Standard Mail enclosures, the permit used to pay for the enclosure must be a valid Permit Imprint, Metered, Precanceled Stamp, OMAS Imprint, or OMAS Metered permit. To designate a permit as the enclosure permit, in addition to standard required fields, mailers must set:
Table 3‑11. Enclosure Payment Settings
File	Field	Position(s)	Description	
MPA	MPA – Unique Sequence/Grouping ID	9-18	Unique identifier for enclosure	
MPA	Permit Number (if applicable)*	58-65	Permit used to pay for the enclosure	
MPA	USPS Publication Number (if applicable)*	49-57	USPS Publication Number used to pay for the enclosure	
MCR	Component ID	18-25	Component that is the enclosure	
MCR	Primary MPA ID	27-36	Points to the MPA file	
CPT	Component – Class**	80	For Periodicals with enclosures only.	
CPT 	Component – Rate Type**	81	For Periodicals with enclosures only. 	
*  Use either a Permit Number or a USPS Publication Number to pay for an enclosure, not both. If the enclosure does not have the correct parameters set in the Mail.dat file, the file fails with the error: ORA-20001: EXITING WWS Data Submission Package – Multiple qualified MPA_UIDs found for JOB_SEQ_NUM=[#],SEGMENT_ID=[ID],MPU_ID=[ID],CLASS=[class].
**  For information on completing these fields, see the “Periodical with First-Class or Standard Mail Enclosure” section in the appendix of the Mail.dat Specification. 
16.	For postage statements paying the Standard Mail rate using Pending Periodicals permits, the field Class Defining Preparation in the .seg file (position 73) must be “2” (Periodicals) and Class must be “5” (Periodicals Pending) as applicable in the .cpt file (position 80), .mpu file (position 93), and/or the Manifest Individual Record (.mir position 72). Pending Periodicals number must be in the Permit field (positions 58-65) of the .mpa file. 
17.	Pending Periodicals are partially supported. Pending Periodicals are not available at all for parcel rates or mailings that include firm bundles (rate category “FB”). However: 
•	Pending Periodicals with Preliminary container status can include First-Class Mail incidental enclosures, non-incidental enclosures, combined statements, or special authorizations (nonprofit, science of agriculture, or classroom rates), but the PostalOne! system will not generate a postage statement for the mailing. 
•	Pending Periodicals with Ready-to-Pay container status with such enclosures or special authorizations are rejected. 
18.	Validation accepts firm bundles, provided non-incidental enclosures are not included. For all mailings claiming firm bundles, Package Level in position 33 of the .pqt must be set to “A”. Additionally, firm bundles are considered a single piece and restricted to the Standard Mail limit of one pound. Pieces must be greater than zero if firm bundles are claimed, but copy number must exceed the piece count. A future release will allow  non-incidental enclosures of First-Class Mail and Standard Mail so long as the Rate Category (.cqt position 35-36) is not “FB”.  For non-incidental enclosures, firm bundles must be designated only by the .pqt Package Level equal to “A”. 
19.	For metered or precanceled stamp postage, PostalOne! validation requires an .mpa file detailing the permit to be charged for additional postage. The additional postage .mpa ID must be used in the Additional Postage MPA ID (positions 27-36) field of the .mcr file. Additional postage may only be charged to a permit imprint account.
3.4.1.2	MLOCR Validation Constraints
In addition to the standard file validations, the PostalOne! system validates Multi-Line Optical Character Reader/Barcode Sorter (MLOCR/BCS) mailings and fails jobs that do not comply with the following: 
•	The Barcode Verifier Indicator field in the Segment record (.seg position 163) is required.
•	Class can be First-Class Mail or Standard Mail, but not both.
•	Processing Category must be correct. For First-Class Mail, Processing Category must be Letter (“LT”), Card (“CD”), or Flat (“LT”). For Standard Mail, Processing Category must be Letter (“LT”).
•	Piece-weight must be correct for the class of mail and category. For example, the PostalOne! system verifies weights of 3.3 ounces for First-Class Mail Letters, 13 ounces for First-Class Mail Flats, and 3.3 ounces for Standard Mail Letters for postage meter affixed mailings. 
•	Precanceled Stamps can only be used for 1 ounce First-Class Mail letter pieces and Standard Mail letters. 
•	Container types must be trays on First-Class Mail Mixed ADC pallets.
•	The postage statement cannot claim a “Single Piece” Rate Category. For example, a Standard Mail postage statement cannot claim First-Class Mail single pieces.
•	All MPA files must pass validation. All jobs are rejected if one file fails.
•	Updates to MLOCR mailings must limit changes to piece counts, rate categories, container status, presentation category, and number of copies. If the mailing includes changes in any other fields, validation rejects the file. 
•	Updates to MLOCR mailings must not result in a greater discount due to a rate category change. 
•	Containers cannot have Container Status “P” (Preliminary) in an update file. 
•	Containers with fewer than 150 pieces must also have a change in rate category that decreases the discount claimed from the original file. 
•	An MLOCR mailing with Postage Payment Method (.mpa position 140) values “G” (Government), “S” (Precanceled stamps), “C” (Metered - Correct), “L” (Metered – Lowest), or “M” (Metered – Neither) must have one Additional Postage MPA ID (positions 37-46) in the MPU / C Relationship (.mcr) record. Only one account is currently allowed for additional postage payment for this type of mailing, even if the mailing includes multiple statements.
•	When sibling containers are used to identify a logical/physical container relationship in an MLOCR mailing, mailers should comply with the information in the Physical/Logical Trays and Pallets section of the Mail.dat Specification.
•	An MLOCR mailing cannot include a postage adjustment record (.par) file.
•	For MLOCR Standard Mail, heavy letters are not accepted. 
3.4.1.3	Relationship Constraints Description
This section describes the relationship constraints validated by the validation module, based on the different Mail.dat presentation categories. To determine which files are required for the various Mail.dat “Conventional Presort” transactions, see Section 3.3.5, Sending Job Updates.
NOTE: Only the “Conventional Presort” Mail.dat presentation category is currently implemented and tested in the PostalOne! system. All other presentation categories are currently supported by the file transfer module, but have not been tested as part of the complete PostalOne! system.
HDR: (required for all presentation categories)
•	All header records present in a HDR file must belong to a single job.
•	There must be only one “current” header record present for a job, in a HDR file.
•	The PostalOne! system does not load or validate any “history” records present in a HDR file.
SEG: (required for all presentation categories)
•	There must be at least one or more segment record(s) present in the SEG file for the unique Job ID present in the header file.
•	No duplicate segment records should be present in the SEG file considering the key fields of this record.
MPA: (required for all presentation categories)
•	The number of mailer postage account record(s) present must match the number in the header file.
•	No duplicate mailer postage account records should be present in the MPA file considering the key fields of this record.
CPT: (required for all presentation categories)
•	There must be at least one or more component record(s) present in the CPT file for the unique Job ID present in the header file.
•	No duplicate component records should be present in the CPT file considering the key fields of this record.
MPU: (required only for “Conventional Presort” and “MLOCR” presentation categories)
•	There must be at least one or more mailpiece unit record(s) present in the MPU file for each segment record present in the segment file.
•	No duplicate mailpiece unit records should be present in the MPU file considering the key fields of this record.
MCR: (required only for “Conventional Presort” and “MLOCR” presentation categories)
•	There must be at least one or more mpu/component relationship record(s) present in the MCR file for each mailpiece unit record present in the MPU file.
•	There must be at least one or more mpu/component relationship record(s) present in the MCR file for each component record present in the CPT file.
•	No duplicate mpu/component relationship records should be present in the MCR file considering the key fields of this record.
•	The Primary MPA ID must match an MPA ID submitted in the MPA file. 
PAR: (optional for all presentation categories)
•	Because the PAR records are optional, there can be one or more postage adjustment record(s) present in the PAR file for each mailpiece unit record present in the MPU file.
•	Because the PAR records are optional, there can be exactly one postage adjustment record present in the PAR file for each component record present in the CPT file.
•	A single postage statement may have no more than one adjustment; however, multiple PAR records can apply to the same postage statement. Adjustments can only be applied to postage statements with “UPD” (USPS Processing Due) status. 
•	For each PAR file submitted with Ready to Pay Adjustment Status (“R” in position 77), there must be at least one container in the CSM file with Container Status (position 98) set to “R” (Ready to Pay). 
•	The MPA – Unique Sequence/Grouping ID (positions 78-87) in a PAR record must refer to a permit in an MPA file with Postage Payment Method (position 140) set to “P” (Permit Imprint) or “G” (OMAS Imprint). 
•	A PAR file can be submitted as part of an O (Original) job; however, a PAR not have record status “U” (Update) or be included as part of an Update job. Alternately, a PAR file can be submitted with a “C” (Change) job that includes a PAR file with Insert (“I”) Record Status (position 76). 
•	No duplicate postage adjustment records should be present in the PAR file considering the key fields of this record.
MSR: (required only for “Manifest Summary” presentation category)
•	For the Manifest Summary presentation category, there must be one or more manifest summary record(s) present in the MSR file for each segment record present in the SEG file.
•	For all other presentation categories, there can be one or more manifest summary record(s) present in the MSR file for each segment record present in the SEG file.
•	No duplicate manifest summary records should be present in the MSR file considering the key fields of this record.
WSR: (optional for all presentation categories)
•	Because the WSR records are optional, there can be one or more walk sequence record(s) present in the WSR file for each segment record present in the SEG file.
•	Because the WSR records are optional, there can be exactly one walk sequence record present in the WSR file for each package quantity record present in the PQT file.
•	No duplicate walk sequence records should be present in the WSR file considering the key fields of this record.
CSM: (only optional for Manifest Summary presentation category)
•	For the Manifest Summary presentation category, there can be one or more container summary record(s) present in the CSM file for the unique Job ID present in the header file.
•	For all other presentation categories, there must be at least one or more container summary record(s) present in the CSM file for the unique Job ID present in the header file.
•	No duplicate container summary records should be present in the CSM file considering the key fields of this record.
MIR: (required only for “Manifest Individual” presentation category)
•	For the “Manifest Individual” presentation category, there must be one or more manifest individual record(s) present in the MIR file for each container summary record present in the CSM file.
•	For all other presentation categories, there can be one or more manifest individual record(s) present in the MIR file for each container summary record present in the CSM file.
•	If the MIR records are used, there can be exactly one manifest individual record present in the MIR file for each special fees/charge record present in the SFR file.
•	No duplicate manifest individual records should be present in the MIR file considering the key fields of this record.
ICL: (optional for all presentation categories)
•	Because the ICL records are optional, there can be exactly one international container label record present in the ICL file for each container summary record present in the CSM file.
•	No duplicate international container label records should be present in the ICL file considering the key fields of this record.
CQT: (required only for “Conventional Presort” and “MLOCR” presentation categories)
•	There must be at least one or more container quantity record(s) present in the CQT file for each container summary record present in the CSM file.
•	No duplicate container quantity records should be present in the CQT file considering the key fields of this record.
PLR: (optional for all presentation categories)
•	Because the PLR records are optional, there can be one or more package label record(s) present in the PLR file for each container summary record present in the CSM file.
•	No duplicate package label records should be present in the PLR file considering the key fields of this record.
PQT: (required for “Conventional Presort” if no PDR records are used or if mail class is Periodicals, and required for “MLOCR” presentation category)
•	If a piece detail record is available for every container quantity record in a job, the package quantity records are optional. There can be one or more package quantity record(s) present in the PQT file for each container quantity record present in the CQT file.
•	For Periodicals, the package quantity records are required to determine applicable bundle charges, and to produce the qualification and bundle reports. 
•	If a piece detail record is not available for every container quantity record in a job, the package quantity records are required. There must be one or more package quantity record(s) present in the PQT file for each container quantity record present in the CQT file.
•	If the package label records are used, there can be one or more package quantity record(s) present in the PQT file for each package label record present in the PLR file.
•	No duplicate package quantity records should be present in the PQT file considering the key fields of this record.
•	All PQT records with the Saturation – ECR Rate Category (A) require one or more associated Walk Sequence (WSR) records or the job will fail validation.
PDR: (required only if Seamless Indicator on the segment record is set to “Y”)
•	PDR files are required and validated only when the Seamless Acceptance Indicator in the segment record (position 261) value is “Y”. Otherwise, this file is not processed.
•	If this optional file is included, the header file must have the correct record count and file status. 
•	No duplicate piece detail records should be present in the PDR file considering the key fields of this record.
SNR: (optional for all presentation categories)
•	Because the SNR records are optional, there can be one or more seed name record(s) present in the SNR file for each package quantity record present in the PQT file.
•	No duplicate seed name records should be present in the SNR file considering the key fields of this record.
SFR: (optional for all presentation categories)
•	Because the SFR records are optional, there can be exactly one special fees/charge record present in the SFR file for each piece detail record present in the PDR file.
•	No duplicate special fees/charge records should be present in the SFR file considering the key fields of this record.
ATF: (optional for all presentation categories)
•	This file type is only supported for Mail.dat version 07-1; these files are obsolete in version 08-1 and 08-2. 
•	If this optional file is included, the header file must have the correct record count and file status. 
APF: (optional for all presentation categories)
•	This file type is only supported for Mail.dat version 07-1; these files are obsolete in version 08-1 and 08-2. 
•	Every APF record must be associated with a valid ATF record. 
•	If this optional file is included, the header file must have the correct record count and file status. 
IAK (optional)
•	If this optional file is included, the header file must have the correct record count and file status. 
3.4.1.4	Validation Log Errors
If your job fails the validation process, an error message appears. To determine why the validation failed, write down the error message, and then inspect the log file written by File Validator. If you have not changed the name and location of the Validation Log file (see Section 3.4.1, Validating Files), its default is C:\Validation.log.
Use a text editor or other tool to view the log file.
NOTE: The Validation Log file is a simple (flat) ASCII file. To view it, use a text editor, such as Microsoft® WordPad, available with most versions of Microsoft Windows® operating system. For example, if you use WordPad to view the Validation Log file, use these steps:
1.	Click Start and select Run. The Run dialog box opens.
2.	In the Open box, type wordpad and click OK to open the WordPad window.
3.	From the File menu, select Open to open the Open dialog box.
4.	Ensure that “C:” appears in the Look in box. If it does not, select it from the list.
5.	In the File name box, type validation.log, then click Open. WordPad opens the file and displays error messages from the oldest to the most recent.
Scroll through the list of error messages and write down the error message you received for your job. If the File Validation Log entry(s) indicates that your mailing job (Mail.dat file) did not pass validation, you will need to analyze the Mail.dat file. If you produced your mailing file using a third-party vendor’s software product, you will probably need to contact them for help in resolving the problem. If you produced the mailing file using “in-house” software, you will probably need to analyze the file or contact technical resources to help you resolve the problem. Some customers use a third-party Mail.dat viewer to analyze their Mail.dat files to resolve problems. Other customers analyze the Mail.dat file using a text editor capable of counting lines and character positions.
For a complete listing of error messages that appear in the Validation.log file, see Appendix E. Error Messages.
3.4.2	Performing the File Transfer
Before transferring your jobs to the Postal Service, you should first validate your files. For more information, see Section 3.4.1, Validating Files.
To transfer Mail.dat job files manually:
1.	On the left menu bar, click File Transfer. You will probably see a Security Warning message. If you do not see it, minimize or move the browser window—it may be hiding the message. Click Yes. If you do not click Yes, or if you click No, you cannot transfer files to the PostalOne! system. The File Transfer page displays the “All Folders” and “File Contents of” panes.
2.	The “All Folders” pane on the left displays your computer's local hard drives (usually A, C and D). Click the plus sign (+) next to the drive on which your jobs are saved.
3.	In the “All Folders” pane, scroll up or down to locate the folder in which your job is saved.
4.	Select the proper folder by clicking the folder name. The “File Contents of” pane on the right displays the job header files.
NOTE: If the folder containing your job is in a subfolder, click the plus sign (+) next to the main folder to display the subfolders. From the subfolders, locate and select the appropriate folder.
5.	In the “File Contents of” pane, select the header file of the job you want to transfer.
NOTE: All files associated with a mailing job are transferred as a result of selecting the header file. To transfer multiple jobs simultaneously, hold down the CTRL key and click the header files of the jobs one at a time to select them.
6.	Once you have selected the job header file(s), you can determine the location and name of the log file, just as you did when using the File Validator. To do this, click Validation Log File. By default, the File Validator writes the results to C:\Validation.log.
7.	Click Transfer file(s) to begin the transfer. While the file is transferring, you see a blue status bar beneath the “File Contents of” pane indicating transfer progress.
8.	After your job has transferred, a message indicating the transfer status appears. Click OK to close the message and continue working. If you are transferring multiple jobs, the transfer message appears after each job is transferred. When each message appears, click OK to continue working. NOTE: If you do not click OK to close the message, the remaining jobs will continue to transfer in the background.
9.	To check the status of your transferred jobs, click Transfer Summary.
Check File Transfer and Upload Status
To check transferred job and file upload status:
1.	On the File Transfer page, click Transfer Summary. The Job Status page opens. It does not initially display recently transferred jobs. To display recently transferred jobs, click the Refresh button at the top-right of the table.
NOTE: In the Job Status column, jobs are reported as "successful,” "In progress," or "failed." If your job is "failed," see Section 3.4.1.4, Validation Log Errors.
2.	By default, the Job Status page displays the first eight jobs. To view the next eight jobs, click Next 8 at the bottom of the page.
NOTE: To view more or fewer records per page, select a number from the Show records drop-down list.
3.	To check file upload status, click a Job ID in the Jobs column or enter the Job ID in the Search Job ID box, then click Search.
The Job Detail page displays all files associated with the selected job, file upload date and time, and upload status.
NOTE: The Completed Job column will either list the date and time at which a file was successfully uploaded, or report the file upload as "Failed" or "In progress."
4.	To view the status of a file's progress, click the file name in the File (Click F for Errors) column. A message box displays error details.
5.	To close the message and continue working, click Close.
6.	If your mailing job was not transferred successfully, you should check the Transfer Summary and the Validation Log file.
7.	If the Transfer Summary or Validation Log file entry(s) indicates that your mailing job (Mail.dat file) was not transferred successfully, you will need to analyze your Mail.dat file. If you produced the mailing file using a third-party vendor’s software product, you will probably need to contact them for help in resolving the problem. If you produced the mailing file using “in-house” software, you will probably need to analyze the file or contact technical resources to help you resolve the problem. Some customers use a third-party Mail.dat viewer to analyze their Mail.dat files to resolve problems. Other customers analyze the Mail.dat file using a text editor capable of counting lines and character positions.
3.4.3	Adjusting Memory Limits for Manual Transfers
NOTE: It is only necessary to adjust memory limits if attempts to transfer large files result in an “Out of Memory” error. Do not increase memory size unless necessary. 
In manual transfers, customers use the File Transfer applet in the PostalOne! system to upload Mail.dat files. Java plug-in technology extends browser functionality to allow applets to run under Sun Microsystem’s Java Runtime Environment (JRE) rather than the default browser JRE. The default memory limit for Java plug-ins is usually around 60-90MB. When the users upload Mail.dat jobs with large file sizes, the Java plug-in runs out of memory, causing the upload process to fail with an “Out of Memory” error. To resolve the issue, modify the memory settings used by the Java plug-in to a higher number. This does modify the limits for the plug-in for all applications, not just the PostalOne! system.
The steps to adjust memory limits are: 
1.	Verify the version of Java plug-in currently installed. The steps to follow vary based on your Java version. 
2.	Verify your machine has sufficient memory to increase the memory limits. Do not modify memory limits if your machine lacks sufficient memory. 
3.	Increase memory limits. For Java plug-in versions 1.4.2_x, follow the steps in Section 3.4.3.3. For all later Java plug-in versions, follow the steps in Section 3.4.3.4. 
3.4.3.1	Verifying Java Installation 
Visit the Java web site (http://www.java.com/en/download/installed.jsp) to verify/update the version of java installed on the computer. Accordingly, refer to section 3.4.3.3 for the steps to increase the memory limit, if the java version installed is 1.4.2_x (where x is any number). If the java version installed is 1.5.x or 1.6, refer to section 3.4.3.4.
3.4.3.2	Verifying Memory
You must know how much RAM the transfer computer has before increasing memory limits. To check the amount of RAM on a Windows machine, left-click My Computer on the your desktop, then click Properties. The computer must have at least 512 MB RAM before you increase memory limits. 
3.4.3.3	Increasing Memory Limits for Java 1.4.2_x
To increase the memory limit for Java version 1.4.2_x:
1.	Close any open browser windows, including any PostalOne! windows. 
2.	On the Windows taskbar, click the Start button, then click Control Panel.  
3.	Double-click the Java Plug-in icon. 
NOTE: Dependent on your Control Panel settings, you may need to click Other Control Panel Options to display the Java Plug-in icon. 
4.	Click the Advanced tab. 
5.	Click the Java Runtime Parameters box, then enter: -Xmx512m 
6.	Click the Browser tab. If the check box is not selected, select the check box for the browser used to access the PostalOne! Web site.
7.	Click Apply, then close the Java Plug-in dialog box. 
8.	Retry the transfer. 
9.	If the “Out of Memory” error reoccurs, repeat this process to increase the memory value further, but use a memory limit other than 512 in step 5. For example, set the runtime parameter to –Xmx768m to use 768 MB, then retry the upload process. 
NOTE: Ensure that any memory limit entered is less than the amount of physical memory (RAM) on the client machine. 
3.4.3.4	Increasing JAVA Memory Limits for Java 1.5.x or 1.6
To increase the memory limit for Java versions 1.5.x and 1.6:
1.	Close any open browser windows, including any PostalOne! windows. 
2.	On the Windows taskbar, click the Start button, then click Control Panel.  
3.	Double-click the Java Plug-in icon.
NOTE: Dependent on your Control Panel settings, you may need to click Other Control Panel Options to display the Java Plug-in icon. 
4.	Click the Java tab, then under Java Applet Runtime Settings, click View. A dialog box appears listing all Java Runtime Versions.
5.	Click the most recent JRE version, then double-click the Java Runtime Parameters box for the selected line. Enter: -Xmx512m
6.	Click OK.
7.	Click OK again to close the Java dialog box.
8.	Retry the transfer. 
9.	If the “Out of Memory” error reoccurs, repeat this process to increase the memory value further, but use a memory limit other than 512 in step 5. For example, set the runtime parameter to –Xmx768m to use 768 MB, then retry the upload process. 
NOTE: Ensure that any memory limit entered is less than the amount of physical memory (RAM) on the client machine.
4	Batch Processing
Batch processing allows you to schedule file transfers to take place automatically. Once batch processing is set up, you do not need to be present for the file transfer to take place. This capability requires additional infrastructure and configuration work.
When using the Batch Processor, the PostalOne! servers return file transfer/upload status feedback to the sender’s workstation automatically. The feedback information (receipt file) is written to the sender’s workstation in either a delimited ASCII text or XML format file. You can load the receipt file into a spreadsheet or a database for storage and viewing. A receipt file is saved in the same directory that contains your mailing jobs. For a detailed explanation of the contents of a receipt file and associated record types and format, see Appendix C. Status Receipt File Layout and Appendix D. Postage Statement Receipt File Layout. Status receipt files are currently the only supported receipt file. 
4.1	Prerequisites for Batch Processing
4.1.1	Hardware
For batch file transfers using UNIX, the minimum workspace requirements are a workstation with a 1 GHz processor and 256 MB RAM. For batch file transfers using Windows XP, the minimum workstation requirements are a Personal Computer (PC) with a Pentium IV 1 GHz processor and 256 MB RAM. The exact RAM requirements vary depending on the size of the Mail.dat job. Table 4-1 details the RAM requirements.
NOTE: The Batch Processor can also be run on machines with HPUX operating systems.
Table 4-1. RAM Requirements Based on Net Job Size
Net Size of Mail.dat Job (MB) *	Recommended Physical RAM	
0 – 10	64 MB	
11 – 25	128 MB	
26 – 50	256 MB	
>50	>1024 MB	
* The net size of a Mail.dat job is calculated as the "total size of all files" associated with a job, minus the size of the PQT, SNR, and PDR files.
For Mail.dat jobs with a large total file size, file transmission may result in an “Out of Memory” error. To resolve this issue, modify the JVM memory arguments, then retry the transmission. For more information on how to modify the memory settings for batch processing, see Section 4.1.8.
NOTE: These memory requirements are for a single thread; when sending multiple simultaneous jobs, use the sum of all net sizes to estimate memory requirements.
4.1.2	Software
The following software is required to use the Batch Processing functionality:
•	Operating System – Microsoft Windows XP for PCs or Sun Solaris 2.6 for UNIX Workstations.
•	Java Software – Sun Microsystems Java Runtime Environment (JRE) or SDK, latest revision of Version 1.4.2 or greater.
This is available from Sun Microsystems, Inc. at http://java.sun.com/products/archive/index.html. Select Java 2 JRE or SDK, Version 1.4.2 or greater. Review and accept the download terms and conditions. Next, select the JRE or SDK that corresponds to your operating system configuration. Then select a “Typical” installation, and note the directory to which the Java software is installed (e.g., C:\program files\java\j2re1.4.1\bin).
•	Scheduling software – software that lets you schedule batch processing of your mailing files to run on the dates and at the times you require. The default scheduling utility for the operating system on the machine you use to send mailing files (e.g., cron/UNIX or “AT” task scheduler/Windows XP) may work.
•	Digital Certificate – get and install a digital certificate for each server that is used to send mail files. For more information, see Section 4.1.6, Digital Certificates/Security.
4.1.3	Network 
The Batch Processor software uses the http/https protocol to communicate through port 444. If firewall settings prevent http/https communication through port 444, reconfigure the firewall to allow this traffic.
4.1.4	Downloading and Configuring the Windows Batch Processor
To download and configure the Windows Batch Processor:
1.	Launch Windows Explorer and in your root directory, create a PostalOne! Batch Processor installation directory. This is where you will place the batch processor software.
NOTE: Give the folder a name that you will readily remember, such as: C:\MAILDAT.
2.	Log on to the PostalOne! system, http://www.uspspostalone.com/.
3.	On the left menu bar, click Download Batch Processor and download the following files into the installation directory:
•	WinZip file – Java archives that perform the batch processing
•	Parameters Files – Local host parameter for the batch processor
4.	Extract the files from daemon.zip, using WinZip, into the PostalOne! Batch Processor installation directory (double-click the zip file and extract the contents). Once extracted, the directory should contain:
•	daemon.jar – Java archive file
•	jsse.jar – Java Secure Socket Extension (JSSE) Java archive file
•	jcert.jar – JSSE Java archive file
•	jnet.jar – JSSE Java archive file
•	xercesImpl.jar – JSSE Java archive file
•	client.config – Client configuration file that specifies parameters to connect to the PostalOne! system
•	postal1.ini – Daemon initialization file that specifies local host parameters
5.	Copy the three JSSE archive files to the extension library ( …\lib\ext ) directory created when the Java JRE / SDK software was downloaded and installed:
For example: 
•	Java Runtime Environment - C:\Program Files\JavaSoft\JRE\1.4\lib\ext 
•	Java 2 SDK - C:\jdk1.4\jre\lib\ext
6.	Create a “Repository” subfolder in the PostalOne! batch processor installation directory. 
This folder is a repository for your Mail.dat files. For example: C:\MAILDAT\Repository.
7.	Create two subfolders in the new repository folder—one for successful transmissions and one for unsuccessful transmissions. For example: C:\MAILDAT\Repository\Successful and C:\MAILDAT\Repository\Unsuccessful. The batch processor deposits transmission files in these folders as each job is processed.
8.	Edit the hostName parameter of the client.config file to connect to the desired server. Use your preferred text editor, such as Notepad, to edit the client.config file.  
•	To connect to the Customer Acceptance Test (CAT) environment, set: 
hostName = upload9.uspspostalone.com
•	To connect to the Production environment, set: 
hostName = upload1.uspspostalone.com 
The default hostName connects to the Production environment. 
9.	After you have created all three subfolders, edit the Postal1.ini file using Notepad, for example, and make the following modifications to the [Repository] section to reflect the directory structure you created above.
[Repository]
RepositoryLocation=C:\MAILDAT\REPOSITORY
SuccessfulRepositoryLocation= C:\MAILDAT\REPOSITORY\SUCCESSFUL
UnSuccessfulRepositoryLocation= C:\MAILDAT\REPOSITORY\UNSUCCESSFUL
NOTE: Postal1.ini is located in your batch processor installation directory (i.e. C:\MAILDAT).
The parameters required to efficiently use the PostalOne! system are provided in the table below.
Table 4-2. Postal1.ini Parameters for Windows
Parameter Name	Valid Values	Default	Description	
MaximumOpenThreads	1-50	4	Maximum threads that can be open at one time.	
RepositoryLocation	Any valid directory path.	C:\postal1\data	Location of Mail.dat files waiting to be processed.	
SuccessfulRepositoryLocation	Any valid directory path.	C:\postal1
\SUCCESSFUL	Location where the Mail.dat files are moved after they are successfully processed.	
UnSuccessfulRepositoryLocation	Any valid directory path.	C:\postal1
\UNSUCCESSFUL	Location where the Mail.dat files are moved if the processing fails.	
ReceiptFileRepositoryLocation	Any valid directory path.	C:\postal1
\ReceiptFile	Location where the receipt files are written by the application. This is the default for both status and postage statement receipts. However, status receipts use it only if PSReceiptFileRepositoryLocation is set.	
ReceiptFileName	Any valid file name.	Report	The name of the receipt files. Note that a unique three-digit sequence number is used to define the extension of the receipt files.	
Delimiter	Any printable ASCII character.	,	This character delimits all receipt file fields.	
NumberOfValidationLogFiles	Any Numeric value. *	5	Number of validation log files that are written by the application before the first file is overwritten.	
NumberOfServerLogFiles	Any Numeric value. *	5	Number of server log files that are written by the application before the first file is overwritten.	
MaximumValidationLogLength	Any Numeric value. *	100000	The maximum size (in bytes) of a single validation log file.	
MaximumServerLogLength	Any Numeric value. *	1000000	The maximum size (in bytes) of a single server log file.	
SystemUsername	A valid PostalOne! account User Name.	Jdoe	A valid PostalOne! user name belonging to an active account that allows the account holder to transfer files.	
SystemPassword	A valid PostalOne! account password.	Password	A valid PostalOne! password belonging to an active account that allows the account holder to transfer files.	
FileType	MAILDAT or DELCON	MAILDAT	Specifies the type of file that is processed by the application. MAILDAT for transferring Mail.dat files, and DELCON for transferring e-VS manifest files.	
StatusReceiptFilename	Any valid file name.	receipt	Determines the name of status receipt file. The PostalOne! system appends a three-digit number to the name, which is incremented with each new receipt.	
PostageStatementReceiptFilename	Any valid file name.	psreceipt 	Determines the name of the postage statement receipt file. The PostalOne! system appends a three-digit number to the name, which is incremented with each new receipt.	
PSReceiptFileRepositoryLocation	Any valid directory path.		Location where the postage statement receipt files (if set) are written by the application. 	
PSReceiptType	XML or DEL		Determines the format of the postage statement receipt file, either XML or character delimited (DEL).	
StatusReceiptType	XML or DEL		Determines the format of the status receipt file, either XML or character delimited (DEL).	
* NOTE: Sufficient disk space should be available to store the number of specified files.
The parameter MaximumSystemErrors is no longer required in the postal1.ini file. If it is still there, you should remove it.
4.1.5	Downloading and Configuring the UNIX Batch Processor
To download and configure the UNIX Batch Processor:
1.	Create a PostalOne! Batch Processor installation directory. The batch processor will be located in this directory. For example: /postal1/.
2.	Log on to the PostalOne! system, http://www.uspspostalone.com/.
3.	On the left menu bar, click Download Batch Processor and download the required files to your batch processor installation directory:
•	Archive file (daemon.tar) – Java archives that perform the batch processing 
•	Parameter File (postal1.ini) – Local host parameters for the batch processor
4.	Use tar to extract the files into the installation directory. Once extracted, the directory should contain:
•	daemon.jar – Java archive file
•	jsse.jar – Java Secure Socket Extension (JSSE) Java archive file
•	jcert.jar – JSSE Java archive file
•	jnet.jar – JSSE Java archive file
•	xercesImpl.jar – JSSE Java archive file
•	client.config – Client configuration file that specifies parameters for connecting to the PostalOne! system
•	postal1.ini – Daemon initialization file that specifies local host parameters
5.	Copy the three JSSE archive files to the extension library directory ( …\lib\ext ) created when the Java software was downloaded and installed.
For example:
•	Java Runtime environment - j2re1_4_2/lib/ext
•	Java 2 SDK - j2se/jre/lib/ext 
6.	Once the files are successfully copied or downloaded, create a “repository” subfolder in the installation directory. This folder is a repository for your Mail.dat files, for example: /postal1/data.
7.	Create additional two subfolders—one for successful transmissions and one for unsuccessful transmissions. The batch processor deposits transmission files in these folders as each job is processed, for example: /postal1/successful and /postal1/unsuccessful.
8.	Edit the hostName parameter of the client.config file to connect to the desired server. Use your preferred text editor, such as Notepad, to edit the client.config file.  
•	To connect to the Customer Acceptance Test (CAT) environment, set: 
hostName = upload9.uspspostalone.com
•	To connect to the Production environment, set: 
hostName = upload1.uspspostalone.com 
The default hostName connects to the Production environment.
9.	After you have created all three subfolders, edit the postal1.ini file and make the following modifications to the [Repository] section to reflect the directories you created:
[Repository]
RepositoryLocation=/postal1/data
SuccessfulRepositoryLocation=/postal1/successful
UnSuccessfulRepositoryLocation=/postal1/unsuccessful
NOTE: For UNIX servers, file paths in the postal1.ini file must be all lowercase.
The postal1.ini file is located in your initial installation directory. The parameters required to efficiently use the PostalOne! system are provided in the table below.
Table 4-3. Postal1.ini Parameters for UNIX
Parameter Name	Valid Values	Default	Description	
MaximumOpenThreads	1-50	4	Maximum threads that can be open at one time.	
RepositoryLocation	Any valid directory path.	C:\postal1\data	Location of Mail.dat files waiting to be processed.	
SuccessfulRepositoryLocation	Any valid directory path.	C:\postal1
\successful	Location where the Mail.dat files are moved after they are successfully processed.	
UnSuccessfulRepositoryLocation	Any valid directory path.	C:\postal1
\unsuccessful	Location where the Mail.dat files are moved if the processing fails.	
ReceiptFileRepositoryLocation	Any valid directory path.	C:\postal1
\receiptfile	Location where the receipt files are written by the application.	
ReceiptFileName	Any valid file name.	report	The name of the receipt files. Note that a unique three-digit sequence number is used to define the extension of the receipt files.	
Delimiter	Any printable ASCII character.	,	This character delimits all receipt file fields.	
NumberOfValidationLogFiles	Any Numeric value. *	5	Number of validation log files that are written by the application before the first file is overwritten.	
NumberOfServerLogFiles	Any Numeric value. *	5	Number of server log files that are written by the application before the first file is overwritten.	
MaximumValidationLogLength	Any Numeric value. *	100000	The maximum size (in bytes) of a single validation log file.	
MaximumServerLogLength	Any Numeric value. *	1000000	The maximum size (in bytes) of a single server log file.	
SystemUsername	A valid PostalOne! account User Name.	Jdoe	A valid PostalOne! user name belonging to an active account that allows the account holder to transfer files.	
SystemPassword	A valid PostalOne! account password.	password	A valid PostalOne! password belonging to an active account that allows the account holder to transfer files.	
FileType	MAILDAT or DELCON	MAILDAT	Specifies the type of file that is processed by the application. MAILDAT for transferring Mail.dat files, and DELCON for transferring e-VS manifest files.	
StatusReceiptFilename	Any valid file name.	receipt	Determines the name of the status receipt file. The PostalOne! system appends a three-digit number to the name, which is incremented with each new receipt.	
PostageStatementReceiptFilename	Any valid file name.	psreceipt 	Determines the name of the postage statement receipt file. The PostalOne! system appends a three-digit number to the name, which is incremented with each new receipt.	
PSReceiptFileRepositoryLocation	Any valid directory path.		Location where the postage statement receipt files (if set) are written by the application.	
PSReceiptType	XML or DEL		Determines the format of the postage statement receipt file, either XML or character delimited (DEL). 	
StatusReceiptType	XML or DEL		Determines the format of the status receipt file, either XML or character delimited (DEL). 	
* NOTE: Sufficient disk space should be available to store the number of specified files.
The parameter MaximumSystemErrors is no longer required in the postal1.ini file. If it is still there, you should remove it.
4.1.6	Digital Certificates/Security
The PostalOne! system uses the Secure Sockets Layer (SSL) version 3.0 to transfer files securely over the Internet. SSL is a secure enhancement to the standard Transmission Control Protocol/Internet Protocol (TCP/IP). It uses a combination of cryptographic processes to authenticate the host computers and to encrypt and decrypt data transferred between them. To transfer files securely (Batch only) with the PostalOne! system, complete the following tasks to permit SSL to operate on your host system:
1.	Create a Keystore
2.	Create a Certificate Signing Request
3.	Submit your CSR and procure a Digital Certificate
4.	Add the Signed Certificate to your Keystore
5.	Enable Encryption on the Batch Processor Client
6.	Test your Signed Certificate
7.	Test the Batch Processor Setup
Each of these steps is discussed in detail below.
4.1.6.1	Creating a Keystore
A keystore is a file that contains a digitally signed certificate. The Batch Processor file transfer system uses this certificate to verify the name of your host computer before accepting files from it.
To create a keystore, use the keytool utility that is part of the Java JRE/SDK software you downloaded earlier. You will need to know the following information to create a keystore:
•	The fully-qualified domain name of your file transfer computer (i.e., ARLNVAUX002.usps.gov) 
NOTE: The common name must match the domain name. 
•	The name of your organizational unit (i.e., Marketing)
•	The name of your organization (i.e., United States Postal Service)
NOTE: The formal name must be alphanumeric characters (no @ or &, for example).
•	The city, state or province, and two-character country code of your location. 
An example of creating a keystore follows:
C:\(directory of keytool Java software utility)> keytool -genkey -alias postalone -keystore p1keys -keyalg rsa
NOTE: You must specify -keyalg rsa when creating a keystore for use with the PostalOne! system. The PostalOne! system uses the RSA signature algorithm for signing certificates.
Enter keystore password: postal1 (for example)
What is your first and last name?
 [Unknown]: ARLNVAUX002.usps.gov
What is the name of your organizational unit?
 [Unknown]: Marketing 
What is the name of your organization?
 [Unknown]: United States Postal Service
What is the name of your city or locality?
 [Unknown]: Arlington
What is the name of your state or province?
 [Unknown]: Virginia
What is the two-letter country code for this unit?
 [Unknown]: US
Is <CN=ARLNVAUX002.usps.gov, OU=PostalOne, O=United States Postal Service, L=Arlington, ST=Virginia,C=US> correct?[no]:
 [Unknown]:	y
Enter key password for <postalone>
 (RETURN if same as keystore password):
NOTE: Record your keystore password in a safe place. You will need it in subsequent steps.
4.1.6.2	Creating Certificate Signing Requests
Use keytool to create your certificate signing request (CSR). 
NOTE: Use the directory where the keytool software utility resides.
C:\(directory of keytool java software)>Keytool –certreq –alias postalone – keystore p1keys –file p1req.txt
Enter keystore password: postal1 (for example)
Your CSR is contained in the file p1req.txt.
4.1.6.3	Submitting Your Certificate Signing Request
You must now submit your CSR for digital signing, i.e., procure a digital certificate. Currently, the PostalOne! system uses digital certificates issued by VeriSign. To obtain a certificate, go to http://www.verisign.com/products/site, and obtain a basic 40-bit SSL Secure Server ID for each machine that will send batch files to the PostalOne! system.
NOTE: Your digital certificate generally expires after one (1) year. You need to renew it after that.
4.1.6.4	Adding a Signed Certificate to a Keystore
After you submit a CSR to VeriSign, you will receive a digitally signed certificate. You must then add this signed certificate to your keystore. The file transfer system uses this signed certificate to verify the identity of your host computer before accepting any files from it.
Begin by getting the reply certificate from VeriSign and copying it into a text editor. It should look similar to the following example:
-----BEGIN CERTIFICATE-----
MIICdjCCAiACEBKVRKjE/nsXwEii3fN6k9AwDQYJKoZIhvcNAQEEBQAwgakxFjAU BgNVBAoTDVZlcmlTaWduLCBJbmMxRzBFBgNVBAsTPnd3dy52ZXJpc2lnbi5jb20v cmVwb3NpdG9yeS9UZXN0Q1BTIEluY29ycC4gQnkgUmVmLiBMaWFiLiBMVEQuMUYw RAYDVQQLEz1Gb3IgVmVyaVNpZ24gYXV0aG9yaXplZCB0ZXN0aW5nIG9ubHkuIE5v IGFzc3VyYW5jZXMgKEMpVlMxOTk3MB4XDTAyMDMwNDAwMDAwMFoXDTAyMDMxODIz NTk1OVowgY4xCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhWaXJnaW5pYTESMBAGA1UE BxQJQXJsaW5ndG9uMSUwIwYDVQQKFBxVbml0ZWQgU3RhdGVzIFBvc3RhbCBTZXJ2 aWNlMRIwEAYDVQQLFAlQb3N0YWxPbmUxHTAbBgNVBAMUFEFSTE5WQVdaMTg0LlVT UFMuR09WMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGzthcIrSzSHFHl3x1 ojzhPjacRUSH1vAuk8SZN1VVRrwi76dl4VqtsGpMD/YjmmMbN1fwgTFm6rfpmRXF rWbQaMe9aB6EPZPwOhpEYdTY3Z9QpOwyKdu6amCwyQzUKkNV7sOeycSe+e9cW4JK 0Koxey14YvLkEu03DHGi0zQ0BwIDAQABMA0GCSqGSIb3DQEBBAUAA0EAv5bA+oCG AzzhZsMiclS2O3liuVN3ppLrRU+DdCvi6otcpC0xUYVYjXFi83POzgjmdr0RJt2g 
QSWT9fCoL28lgA==
-----END CERTIFICATE-----
Ensure the certificate context (the text between the BEGIN CERTIFICATE line and the END CERTIFICATE line) has no spaces or return characters when copying and pasting. If there are any spaces or return characters, delete them. Put one and only one new line (i.e. carriage return) without any space after the END CERTIFICATE line. Then save the file (e.g., p1cert.txt).
After you have saved the signed certificate, use keytool to import your certificate into your keystore.
C:\(directory of keytool java software utility)>keytool -import -trustcacerts -file p1cert.txt -alias 
postalone -keystore p1keys
Enter keystore password: postal1 (for example)
Certificate was added to keystore
Now use keytool to verify that your signed certificate is in your keystore:
C:\postalone>keytool -list -keystore p1keys -alias postalone -v
Enter keystore password: postal1 (for example)
Alias name: postalone
Creation date: Wed Oct 29 11:41:01 EDT 2003
Entry type: trustedCertEntry
Owner: CN=ARLNVAUX002.usps.gov, OU= Marketing, O=United States Postal Service, L=Arlington, OID.2.5.4.17=94497, ST=VA, C=US
Issuer: CN=USPS CA, OU=www.usps.com/CPS, O=United States Postal Service, C=US
Serial number: 2895
Valid from: Tue Oct 28 14:08:07 EDT 2003 until: Wed Oct 27 14:08:07 EDT 2004
Certificate fingerprints:
MD5: 69:2C:04:E3:B7:F1:A9:1F:DE:FD:0E:36:A2:1B:FF:12
SHA1:E5:91:36:25:76:2B:CA:E0:DF:DD:3C:2B:91:E8:3B:97:B3:E6:8D:CE
NOTE: In the example, the certificate is valid for one year, then it expires.
4.1.6.5	Enabling Encryption on the Batch Processor Client
To enable the batch processor client secure file transfer feature, you must copy your keystore file to the directory in which you have installed the batch processor client software. You must also edit the client.config file. The client.config is already located in the directory in which you have previously installed the batch processor client software.
After copying your keystore file (for example, p1keys) to the directory containing the batch processor client, edit the client.config file. To enable encryption, you must set the encryption parameter to true. You must also supply the name of your keystore file and its corresponding password. When you are finished, these entries should look similar to the following example:
encryption = true
keystore = p1keys
password = postal1 (for example)
4.1.6.6	Testing Your Signed Certificate
Your batch processor client software gives you the ability to test the installation of your certificate. This test is performed from the command prompt on your local file transfer host.
To test the installation of your signed certificate, make sure the encryption parameter of your client.config file is set to true. Then execute the following command. 
NOTE: Use the batch processor installation directory.
C:\(batch processor installation directory)>java –cp Daemon.jar Daemon -testlocal
If your certificate is valid and is installed properly, you will see the following: 
Local Server Listening for Client Connection
Response Code is : 200
Response Message is : OK
This (Certificated) Local Connection test is SUCCESSFULL!
4.1.6.7	Testing Batch Processor Setup
The batch processor client software also lets you test that the batch processor has been set up correctly and can communicate with the PostalOne! system. This test is run from the command prompt on your local file transfer host. 
NOTE: Use the batch processor installation directory.
C:\(batch processor installation directory)>java –cp Daemon.jar Daemon -testremote
4.1.7	Scheduling Batch Jobs (Running the Batch Processor)
To have your jobs run automatically, use a scheduling utility/program that allows you to set the date and time the batch file transfer processor runs. Copy or move the mailing files into the repository directory before the batch job executes. To run the batch processor application, you invoke it at the command prompt. For example:
java –cp C:\<dir>\daemon.jar Daemon
Where <dir> is the directory containing the Java archive file (daemon.jar), the Daemon initialization file (postal1.ini), and client configuration file (client.config).
4.1.8	Adjusting Memory Limits for Batch Transfers
NOTE: It is only necessary to adjust memory limits if attempts to transfer large files result in an “Out of Memory” error. Do not increase memory size unless necessary. 
When the users upload Mail.dat jobs with large file sizes, the computer sending the files (the client) may run out of memory, causing the upload process to fail with an “Out of Memory” error. 
To resolve the issue, first verify the amount of memory available on the client computer is sufficient. Next, edit the client.config file to use a larger value for maximumHeapSize, such as 512 (512 MB). The client.config file is located in the batch processor installation directory. For example: 
maximumHeapSize=512
Save and exit the client.config file, then retry the transfer. If the Out of Memory error reoccurs, increase maximumHeapSize to a higher number. For example, set maximumHeapSize=768 to use 768 MB, then retry the upload process. 
NOTE: Ensure that any memory limit entered is less than the amount of physical memory (RAM) on the client machine.
4.2	File Transfer Error Codes and Messages
When you transfer mailings, the system records error codes and descriptive messages. If you transferred the mailing using the manual process or the batch process, you can retrieve the error messages using the File Transfer page and selecting the Transfer Summary option.
Additionally, if you transferred the mailing using the batch process, error messages are stored in the folder/directory used as the installation folder/directory for batch file transfers.
The list of file error messages is in Appendix E. Error Messages.
5	Customer Support
The PostalOne! program has a staffed Customer Care Center (help desk) to assist customers who may have questions or need assistance with a problem or technical issue with the PostalOne! system. The PostalOne! Customer Care Center is available Monday through Friday from 8:00 a.m. to 5:00 p.m., CST, and can be contacted via e-mail or telephone. You can also call the telephone number below for after-hours assistance with some issues. Our after-hours staff will forward unresolved issues to the Customer Care Center at the beginning of the next workday.
Customer Care Center Telephone	(800) 522-9085
Customer Care Center e-mail		postalone@email.usps.gov
If you experience any difficulties when using the PostalOne! system, have questions, or need more information about the PostalOne! system, contact the Customer Care Center. Your calls will be answered by the Customer Care Center in a priority order, with preference given to fully enrolled customers having a signed PostalOne! user agreement on file.
If you have comments or suggestions regarding this guide, e-mail the Customer Care Center.

Appendix A. Mail.dat File Definitions
This appendix contains the names and definitions of each file used in Mail.dat. (Source: IDEAlliance Users’ Guide for Mail.dat, Version 08-2) 
Table A-1. Mail.dat Files and Definitions
File	Definition	
Header file (.HDR)	The Header file is an introduction to the entire Mail.dat. It identifies who created the file, what version of the IDEALLIANCE standard was used (ensuring compatibility with other users), and when the file was created. Most importantly, it identifies the total file record count for each file type. If the quantity fields in the Header record say there are a differing number of records than received, it is the first indication that the file is incomplete and, therefore, invalid. The presort software used, history of who has touched this Mail.dat, and other information is also in the Header.	
Segment file (.SEG)	The Segment file is used to identify all of those addresses that are considered as a group within a presort. It separates parts of a mailing that require different processing. The specification notes:
In general, the fewer the segments in a Mail.dat, the better. It is only appropriate to create a unique segment when it is needed to separate part of a mailing for different processing. Segmenting should not be used to differentiate among entry points unless they will need to be processed in some fundamentally different fashion. Similarly, segmentation should not be used to create reporting categories from information that is otherwise available in the Mail.dat.
The Segment file identifies the class and characteristics of the mail preparation for each Segment.	
Mailpiece Unit file (.MPU)	The Mailpiece Unit file contains the physical description of the whole mailpiece in terms of physical attributes, such as dimensions and ad percentages. Often, there is a single MPU within a Segment. A Mailpiece Unit ID cannot cross Segment; however, co-mingled mail, selectively inserted letters, and selectively bound catalogs/periodicals can have multiple Mailpiece Units associated with one segment. Another example of where there might be multiple Mailpiece Units in one segment is if multiple editions are produced in separate processes, but staged onto the same pallets on the backend in order to be presented as part of one mailing.	
Mailer Postage Account (.MPA)	The Mailer Postage Account file describes the mailer's permit and account information, including the payment method to be used and any special authorizations. 	
Component file (.CPT)	The Component ID file is used to define those parts of a Mailpiece Unit by the mail class for which they qualify. For example, a magazine is in the mail class of Periodicals. However, the publisher may decide to have a mailpiece that is ineligible for Periodicals rates to be attached to the front of the magazine. The ineligible mailpiece might be a Standard Mail™ piece. Each of these parts would be identified with a separate Component record that is linked to the appropriate MPU.	
MPU/Component Relationship file (.MCR)	The MPU/Component Relationship file is a table relating the two variables. Like the MPU and Segments relationships, often there is a one-to-one relationship with an MPU and a Component. However, as described in the above file definition, there are exceptions. Periodicals with First-Class Mail attachments and Periodicals with Standard Mail enclosures are two examples.	
Container Summary file (.CSM)	The Container Summary file identifies each container, its level, its destination, the point of entry and the contents in terms of rates, copies, pieces, and weight. Pallets, sacks, and trays are containers. There will be one Container Summary per container.	
International Container Label file (optional) (.ICL)	The International Container Label file contains label information for each USPS international mail container. This file also has unique subsections applicable only to USPS international mail. 	
Container Quantity file (.CQT)	The Container Quantity file supplies quantitative details about the content of each container. It summarizes the contents of each container in terms of MPUs, zones, and rate categories. It also supplies copy and piece counts at this level of detail. Unlike the usually limited relationship of MPU/Segment, and Component/MPU, it is expected that there will be a great number of Container Quantity records linked to the same Container Summary.	
Package Quantity file (optional) (.PQT)	The Package Quantity file presents a finer level of detail defining the quantity, rate, weight, and package destination for every package in a container. Although optional, this file is required for MLOCR mailings, or if the application is to produce a standard USPS Qualification report and/or provide input to the USPS PostalOne! system. For Periodicals mailings, this file is required for production of the PS Form 3541 postage statement, qualification report, and bundle report. 	
Walk Sequence file (optional) (.WSR)	The Walk Sequence file provides detail for carrier route packages in a Walk Sequence mailing: package ZIP Code, carrier route number, walk sequence type, total stops made, and total possible stops.	
Seed Name file (optional) (.SNR)	The Seed Name file provides the precise container, package, entry, version, etc. that applies to the respective Seed Names within the mailing. For those mailers who use seed addresses such as subscriber reporters or mail monitors, this file can be supplied by the presort provider to support communications regarding the total tracking program.	
Package Label file (optional, Canadian only) (.PLR)	The Package Label file, like the Container Label file, is information to be used to print Canadian package labels (facing slips).	
Ink Jet/Container Relationship file (optional) (.ICR)	The Ink Jet/Container Relationship file defines the specific location of each container on the associated ink jet tapes or transmitted files.	
Piece Detail file (optional) (.PDR)	The Piece Detail file is used by “manifest” mailing procedures and is processed only if the Seamless Indicator (position 261 of the .seg) is “Y”.	
Special Fees and Charges file (optional) (.SFR)	The Special Fees and Charges file can represent various fixed and weight-variable special fees and charges for any or all of the respective piece details within the mailing. Examples are Insured, Delivery Confirmation, and Signature Service.	
Manifest Individual file (optional) (.MIR)	The Manifest Individual file is used for “manifest” mailings, especially suitable for parcels.	
Manifest Summary file (optional) (.MSR)	The Manifest Summary file is used for “manifest” mailings, where there is repetition of item characteristics, which lends itself to “summarized” presentation, rather than an individual PDR record for every piece.	
Postage Adjustment file (optional) (.PAR)	The Postage Adjustment file defines any postage adjustments required to be made, as compared to the anticipated production specifics as supplied within the Mail.dat. An example would be a penalty for too many unreadable barcodes.	
Actual Tray File (optional) (.ATF)	The Actual Tray File distinguishes between logical and physical containers. 07-1 files only. Deleted in 08-1 and 08-2.	
Actual Pallet File (optional) (.APF)	The Actual Pallet File creates associations with pallets in the ATF record. Requires at least one ATF record. 07-1 files only. Deleted in 08-1 and 08-2. 	
Information Access Key (optional) (.IAK)	Identifies the mailing agents assigned to each business role for each unique MPU and CPT record set. New with 08-1. 	

Appendix B. Mail.dat Field Validation
This appendix contains the field validations the PostalOne! system enforces for Mail.dat, separated by the record containing the field(s). Although very close, these are not identical validations to the Mail.dat version 08-2 specification; rather, this is how the PostalOne! system validates the fields. 
The following conventions will apply for each data type in the respective fields as indicated, except as noted in specific record layouts.
•	Alphanumeric = Left-justify these fields, and fill the right with spaces. For example, KC123ID should be “KC123ID  ”.
•	Numeric – Right-justify these fields, and fill the left with zeroes. For example, 123 should be “00123”.
•	Numeric Decimal – For some fields, a decimal place is automatically added to the field. Fill smaller numbers with zeroes if necessary to place the decimal in the correct location. For these fields, this guide uses the letter “v” to indicate where the decimal appears. For example, to fit in a field marked as 99v9999, the value 1.23 should be “012300”. 
If a field does not require the use of conventional values and is not used in the mailing, then use a space-filled field.
NOTE: Fields marked with a single asterisk (*) are required by the PostalOne! system, in addition to the fields required by the Mail.dat specification. Fields marked with multiple asterisks indicate a special note at the end of the table.
Header Record
Table B-1. Header Record - .HDR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
IDEAlliance Version	07-1, 08-1, or 08-2		
Header History Sequence Number	Numeric		
Header History Status	C, H		
Historical Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Licensed User’s Job Number*	Alphanumeric		
Job Name/Title & Issue	Alphanumeric		
File Source	Alphanumeric		
User License Code*	Alphanumeric	Case sensitive. Ensure that all updates to a job uses the same case as the original file or a new statement is created. This differs from the Mail.dat specification. 	
Contact Name	Alphanumeric		
Contact Telephone Number	Telephone Number	No “000” area codes. Example: 9999999999	
Date Prepared	Date	YYYYMMDD - Example: 20061225	
Time Prepared	Time	HH:MM – Example: 13:30	
Segmenting Criteria	Alphanumeric		
Segment Record Count	Numeric		
Segment File Status	O,C,D,U,N		
Mail Piece Unit Record Count	Numeric		
Mail Piece Unit File Status	O,C,D,U,N		
MPU / C Relationship Record Count	Numeric		
MPU / C Relationship File Status	O,C,D,U,N		
Mailer Postage Account Record Count	Numeric		
Mailer Postage Account File Status	O,C,D,U,N		
Component Record Count	Numeric		
Component File Status	O,C,D,U,N		
Container Summary Record Count	Numeric		
Container Summary File Status	O,C,D,U,N		
International Container Label Count	Numeric		
International Container Label Status	O,C,D,U,N		
Container Quantity Record Count	Numeric		
Container Quantity File Status	O,C,D,U,N		
Package Quantity Record Count	Numeric		
Package Quantity File Status	O,C,D,U,N		
Walk Sequence Record Count	Numeric		
Walk Sequence File Status	O,C,D,U,N		
Seed Name Record Count	Numeric		
Seed Name File Status	O,C,D,U,N		
Package Label Record Count	Numeric		
Package Label File Status	O,C,D,U,N		
IJ / C Relationship Record Count	Numeric		
IJ / C Relationship File Status	O,C,D,U,N		
Piece Detail Record Count	Numeric		
Piece Detail File Status	O,C,D,U,N		
Special Fee/Charge Record Count	Numeric		
Special Fee/Charge File Status	O,C,D,U,N		
Manifest Individual Record Count	Numeric		
Manifest Individual File Status	O,C,D,U,N		
Manifest Summary Record Count	Numeric		
Manifest Summary File Status	O,C,D,U,N		
Postage Adjustment Record Count	Numeric		
Postage Adjustment File Status	O,C,D,U,N		
Actual Tray File Record Count	Numeric	Only for 07-1. Deleted in 08-1.	
Actual Tray File Status	O,C,D,U,N	Only for 07-1. Deleted in 08-1.	
Actual Pallet File Record Count	Numeric	Only for 07-1. Deleted in 08-1. 	
Actual Pallet File Status	O,C,D,U,N	Only for 07-1. Deleted in 08-1.	
Information Access Key Record Count	Numeric	New for 08-1.	
Information Access Key File Count	O,C,D,U,N	New for 08-1.	
XML PDR File	Y,N		
Mail.dat Presentation Category	P,M,I,S,N		
Mail.dat Software Vendor Name	Alphanumeric		
Mail.dat Software Product’s Name	Alphanumeric		
Mail.dat Software Version	Alphanumeric		
Mail.dat Software Vendor’s Email	Alphanumeric		
Licensed User’s Email	Alphanumeric		
Zone Matrix Date	Date	YYYYMMDD - Example: 20061225	
Event Manager Audit Code	Alphanumeric		
Software Vendor’s ZAP Option	Numeric	Required for Periodicals with original or preliminary container status. This differs from the Mail.dat specification. 	
User Option	Alphanumeric		
Closing Character	#		

Segment Record
Table B-2. Segment Record - .SEG
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes. Each segment record must have all segment-keyed records required by the original or update transmission (CSM, MPU, and MCR).	
Segment Description	Alphanumeric		
Class Defining Preparation	1,2,3,4,9,X,V,T,P	If Principal Processing Category is one of {LT,FL,CD,CM,MM,MP,IR,OS,PF}, then acceptable values are {1,2,3,4,9,X,V,T,P}. Validation fails the associated segments if the following values are used in this field: 5,6,9,X,V,T,P,A,B,C,D.	
Principal Processing Category	LT,FL,CD,CM,IR,MM,MP,NA,NB,NP,OS,PF,UA,UL,UM,UR	If Class Defining Preparation is one of {1,2,3,4,9,X,V,T,P}, acceptable values are {LT,FL,CD,CM,MM,MP,IR,OS,PF}. 	
Mail Sacking Criteria – CR/ECR	CO,CF,CB,PC,TP,PT		
Mail Sacking Criteria – 3 or 5 digit	CO,CF,CB,PC,TP,PT		
Mail Sacking Criteria – Basic	CO,CF,CB,PC,TP,PT		
Substituted Container Prep	S,T		
Periodicals Newspaper Treatment	Y,N		
Logical/Physical Container
Indicator	L,P		
Log/Phy Package Indicator	L,P		
Reserve		Only for 07-1 files. Deleted in 08-1. 	
Production Set-up Code	Alphanumeric		
LOT Database Date	Date	YYYYMMDD - Example: 20061225. Fill with 00010101 if no date available; lack of valid date may impact rate eligibility. 	
Sibling Container Mailing	‘Y’, ‘ ‘ (space)		
Verification Facility Name*	Alphanumeric		
Verification Facility ZIP+4*	Numeric	Required field for all file versions. Fill with the ZIP Code + 4 without a hyphen. Example: 123451234. Must be identical for all segments in a job. For owner updates to jobs previously submitted by a preparer, this field must be the same as the Verification Facility ZIP + 4 claimed in the original job.	
Confirm Indicator	N,P,R,S,’ ‘ (space)		
Static Planet Code	Alphanumeric	Rejected if the Confirm Indicator is “S” and this Code is less than 11 digits long.	
L.O.T. Direction Indicator	F,R		
Barcode Verifier Indicator	Y,N		
SEG Record Status	O,I,U	Acceptable values dependent on file type.	
User Option	Alphanumeric	Only for 07-1 files. Moved in 08-1 to the end of the segment file.	
Package Services Packaging Criteria	PC,PD,CB		
Automation Coding Date	Date	YYYYMMDD - Example: 20061225. Fill with 00010101 if no date available; lack of valid date may impact rate eligibility.	
Carrier Route Coding Date	Date	YYYYMMDD - Example: 20061225	
Carrier Route Sequencing Date	Date	YYYYMMDD - Example: 20061225	
EMD Barcode Indicator	M,S,P		
EMD Mailing-Generic Package Barcode	Alphanumeric		
Move Update Date	Date	YYYYMMDD - Example: 20061225	
PDR Population Status	P,F		
Detached Address Label Indicator	Y,’ ‘ (space)		
Requested Presort Verification Completion Date	Date	YYYYMMDD – Example: 20061225. Do not fill with all zeroes.**	
Requested Piece Weight Verification Completion Date	Date	YYYYMMDD – Example: 20061225. **	
Mailing Agreement Type	A,B,C,D,E,F		
Mail Facility ID*	Alphanumeric	 	
Container and Bundle Charge Method	1,2,3,0	For non-Periodicals jobs, this value must be 0 or file rejection occurs. Validation reads only the first value for this field in a job and applies it to the entire job. This differs from the Mail.dat specification.	
MPA ID for Container and Bundle Charge Method	Alphanumeric	Only enter if Container and Bundle Charge Method is 1 or 2. This ID should match the MPA - Unique Sequence/Grouping ID in the MPA file.	
Presentation Category	P,A		
Seamless Acceptance Indicator	Y,N,1,2,’ ‘ (space)	New for 08-1. New for 08-2: Y, N are deleted. 1, 2, and ‘ ‘ are added. 	
Less Than a Presort Segment Presentation	Y,N	New for 08-1. 	
User Option	Alphanumeric	Only for 08-1 and 08-2. For 07-1 files, this field is earlier in the segment record.	
SASP Preparation Option	B,F,’ ‘ (space)	New for 08-2. 	
Reserve	Alphanumeric		
Closing Character	#		
**  Field designated for future use. The PostalOne! system will not process this data for any functional need until a future release.
Mail Piece Unit
Table B-3. Mail Piece Unit Record - .MPU
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Mail Piece Unit ID	Alphanumeric	Must be unique within a job. If numeric only, fill left with zeroes.	
Mail Piece Unit Name	Alphanumeric	Must be unique within a segment.	
Mail Piece Unit Description	Alphanumeric		
Mail Piece Unit – Weight	Numeric Decimal	99v9999	
MPU - Weight: Source*	A,P,C,L		
MPU - Weight: Status	M,P,F,N		
Mail Piece Unit - Length	Numeric Decimal	999v9999. If MPU Surcharge is D, then this field must contain a valid non-zero value.	
Mail Piece Unit - Width	Numeric Decimal	99v9999. If MPU Surcharge is D, then this field must contain a valid non-zero value.	
Mail Piece Unit - Thickness	Numeric Decimal	99v9999. If MPU Surcharge is D, then this field must contain a valid non-zero value.	
Mail Piece Unit - Periodical Ad %	Numeric Decimal	999v99. Must be equal to or less than 100.00.	
MPU - Periodical Ad %: Status*	N,P,F		
Mail Piece Unit - Class	1,2,3,4,5,9,X,V,T,P	If MPU - Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T}, then acceptable values are {1,2,3,4,9,X,V,T,P,5}. Validation fails the associated segments if the following values are used in this field: 6,A,B,C,D.	
Mail Piece Unit - Rate Type	R,C,P,L,S,B,F,N, T,1,2,3,4,D,G,W,Y	If MPU - Class is one of {1,2,3,4,,9,X,V,T,P,5}, then acceptable values are {R,C,P,L,S,B,F,N,T}.
New for 16.1.0: W,Y
New for 08-1 and 08-2: J, K	
Mail Piece Unit - Processing
Category	LT,FL,CD,MP,IR,OS,AA,AB,AC,AD,AE,AF,AG,AH,AI,AJ,AK,AL,AM,LA,LB,LC,LD,LE,LF,LG,LH,LL,LM,SF,SG,SH,PF,CM,NA,NB,NP	If MPU – Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T}, then acceptable values are {LT,FL,CD,MP,IR,OS,PF,CM}. 	
Country	Numeric or the two-character ISO 3166 code element.	For a list of ISO 3166 code elements, see the ISO 3166 website (http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html). 	
MPU Surcharge	N,O,P,Q,R,S,1,2,D	If MPU Surcharge is D, then MPU Length, MPU Width, and MPU Thickness must contain valid non-zero values. 	
Co-Palletization Code	Alphanumeric		
Five Digit Scheme Database Date	Date	YYYYMMDD - Example: 20061225	
Reserve	Numeric	For 07-1 files only. Deleted in 08-1.	
Sibling Container Mailing	Y,’ ‘ (space/blank)		
Confirm Subscriber ID	Numeric		
MPU Record Status	O,I,U	Acceptable values dependent on file type.	
Flat Machinability	Y,U,N,’ ‘ (space/blank)	For Periodicals, if Mail Piece Unit – Processing Category is FL, this field is required and impacts rates. For more information, see the Flats Machinability Values table. 	
Pre-Denominated Amount	Numeric		
Postage Affixed Type	S,M		
Prose XML Edition Code	Alphanumeric		
Bulk Insurance	Y,N,O		
Reserve	Alphanumeric		
Closing Character	#		
Mail Piece Unit – Class Values
The PostalOne! system currently supports the following mail classes (Mail Piece Unit - Class, position 93 in the .mpu file) for electronic data submission: 
Table B-4. Supported Mail Piece Unit – Class Values
Value	Class	
1	First-Class Mail	
2	Periodicals	
3	Standard Mail	
4	Package Services. Parcel Post, Parcel Select, Library Mail, and Media Mail are not supported. 	
5	Pending Periodicals. 	
Flats Machinability Values for Periodicals Mailings
For Periodicals mailings, Flats Machinability (.mpu position 118) values map to the following presort levels and piece rates. 
NOTE: 
•	For Periodicals, UFSM 1000 Compatible mailings get a Machinable rate (line C15) for 5-Digit Barcoded. Otherwise, follow the Nonmachinable and Parcel lines.
•	For Periodicals, parcel lines are the Nonbarcoded under Nonmachinable and Parcel section: Lines C10, C12, C14, and C16.  See changes in table below.
Table B-5. Flats Machinability Values for Periodicals
Value	Presort Level	Piece Rates	
Y	All	Machinable Flats	
U	3-Digit, ADC, Mixed ADC	Nonmachinable Flats	
U	5-Digit Barcoded	Machinable Flats	
N	All	Parcels	
Blank	All	None. Error message occurs if blank in a Periodicals mailing with Processing Category “FL”. 	
MPU/C Relationship Record
Table B-6. MPU/C-Relationship Record - .MCR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Mail Piece Unit ID	Alphanumeric	If numeric only, fill left with zeroes.	
Component ID	Alphanumeric	If numeric only, fill left with zeroes.	
MCR Record Status	O,I,U	Acceptable values dependent on file type.	
Primary MPA ID	Alphanumeric		
Additional Postage MPA ID	Alphanumeric	Must match the MPA ID containing the permit imprint account used to pay for additional postage in metered or precanceled stamp mailings. 	
Host Statement Component ID	Alphanumeric	Required if more than one Component ID in the Mail Piece Unit ID. If numeric only, fill left with zeroes.	
Host Indicator of Ad Computation	Y,N		
Postage Adjustment MPA ID	Alphanumeric	If numeric only, fill left with zeroes. 	
Reserve	Alphanumeric		
Closing Character	#		
Mailer Postage Account Record
Table B-7. Mailer Postage Account Record - .MPA
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
MPA - Unique Sequence/Grouping ID	Alphanumeric	If numeric only, fill left with zeroes.	
MPA - Description	Alphanumeric		
USPS Publication Number*	Alphanumeric	Mutually exclusive with Permit Number field. Use only for Periodicals mailings. Do not use for Pending Periodicals. 	
Permit Number*	Alphanumeric	Mutually exclusive with Publication Number field. Use for all non-Periodicals, including Pending Periodicals. 	
Permit City	Alphabetic		
Permit State	Alphabetic		
Permit ZIP+4*	Alphanumeric		
Mail Owner’s Lcl Permit Ref Num / Int.l Bill Num	Numeric	Required field for PostalOne! postage payment with a mail owner that is different from the permit holder or the mail preparer – this differs from the Mail.dat specification. Determines nonprofit status.	
Mail Owner’s Lcl Permit Ref Num/ Int.l Bill Num - Type	S,M,P,G,V,H	Required field for PostalOne! postage payment with a mail owner that is different from the permit holder or the mail preparer – this differs from the Mail.dat specification. Determines nonprofit status.	
Postage Payment Option*	C,D,V,O,T,B		
CAPS Reference Number	Alphanumeric		
Postage Payment Method	S,M,P,A,C,L,H,I,G,T	Only required if Permit Number is present.	
Mailing Facility Identifier*	Alphanumeric	Use DUNS number or USPS-assigned Customer Reference ID. 	
Permit Holder Identifier	Alphanumeric	Use DUNS number or USPS-assigned Customer Reference ID.	
Federal Agency Cost Code	Alphanumeric		
Non-Profit Authorization Number	Alphanumeric		
Title	Alphanumeric	Exists for mailer convenience. 	
MPA Record Status	O,I,U		
Reserve	Alphanumeric		
Closing Character	#		
Component Record
Table B-8. Component Record - .CPT
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Component ID	Alphanumeric	If numeric only, fill left with zeroes.	
Component Description	Alphanumeric		
Component - Weight	Numeric Decimal	99v9999	
Component - Weight: Source*	A,P,C,L		
Component - Weight: Status	M,P,F,N		
Component - Length	Numeric		
Component - Width	Numeric		
Component - Thickness	Numeric		
Component - Periodical Ad Percentage*	Numeric Decimal	999v99. Must be equal to or less than 100.00.	
Component - Periodical Ad
Percentage: Status	N,P,F		
Component - Class	1,2,3,4,5,9,X,V,T,P	If Component – Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T,H,M,E,Z}, then acceptable values are {1,2,3,4,9,X,V,T,P,5}. Validation fails the associated components if the following values are used in this field: 6,A,B,C,D.	
Component - Rate Type	R,C,P,L,S,B,F,N,T,1,2,3,4,H,M,E,Z,D, G,I,W,Y,J,K	If Component – Class is one of {1,2,3,4,9,X,V,T,P,5}, then acceptable values are {R,C,P,L,S,B,F,N,T,H,M,E,Z}. New for 08-1: I New for 16.1.0: W,Y. New for 08-2: J,K	
Component -Processing Category	LT,FL,CD,MP,IR,OS,AA,AB,AC,AD,AE,AF,AG,AH,AI,AJ,AK,AL,AM,LA,LB,LC,LD,LE,LF,LG,LH,LL,LM,SF,SG,SH,PF,CM,NA,NB,NP	If Component – Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T,H,M,E,Z}, then acceptable values are {LT,FL,CD,MP,IR,OS,PF,CM}. 	
Mail Owner Identifier	Alphanumeric	Provide the 12-digit FAST Scheduler ID if participating in the FAST system, or fill with blanks. Any other value fails FAST validation. 	
Sibling Container Mailing	Y,’ ‘ (space/blank)		
Mail Owner’s Mailing Reference ID	Alphanumeric		
CPT Record Status	O,I,U	Acceptable values dependent on file type.	
Periodical Ad% Treatment	B,S,N		
Periodical Volume Number	Alphanumeric	If this field has a value, Periodical Issue Number is required or the job will be rejected.	
Periodical Issue Number	Alphanumeric	Required if Volume Number is populated. The job will be rejected if Volume Number is filled, but Issue Number is empty. 	
Periodical Issue Date*	Date	YYYYMMDD - Example: 20061225. See Issue Date Values below for suggested values. Only required for Periodicals mailings. 	
Periodical Frequency	Numeric		
Weight Version ID	Alphanumeric	**	
Weight Equivalent User License Code	Alphanumeric	Use with Weight Equivalent Mail.dat Job ID and Weight Equivalent Component ID.**	
Weight Equivalent Mail.dat Job ID	Alphanumeric	Use with Weight Equivalent User License Code and Weight Equivalent Component ID.**	
Weight Equivalent Component ID	Alphanumeric	Use with Weight Equivalent User License Code  and Weight Equivalent Mail.dat Job ID.**	
Component Title	Alphanumeric	Exists for mailer convenience. 	
Reserve	Alphanumeric		
Closing Character	#		
**  Field designated for future use. The PostalOne! system will not process this data for any functional need until a future release. 
Issue Date Values
For the Issue Date field in the Component record, use the date the publisher provides in the issue if it is a month, day and year format. In all cases, if there is a cover/issue date on a publication, use that date as the issue date.
If no date has been provided, use the table below. This is an optional method to standardize the usage of the issue date. The Pricing and Classification Service Center (PCSC) provided these suggested dates. Any method to standardize the issue date is acceptable if it meets the requirement that all postage statements for the same issue have the same issue date. Look up the frequency of the issue and then use the month, day and year provided. If two issues occur on the same date, use the Volume Number and Issue Number to differentiate the issues.
Table B-9. Suggested Issue Date Values by Frequency
Frequency	Issue	Use Date	
Quarterly 
(if not dated, or no month & year)	First Quarter	1/1/2004	
	Second Quarter	4/1/2006	
	Third Quarter	7/1/2006	
	Fourth Quarter	10/1/2006	
Seasonal 
(if not dated, or no month & year)	Spring	3/21/2006	
	Summer	6/21/2006	
	Fall	9/21/2006	
	Winter	12/21/2006	
Monthly 
(if not dated) 
or any other frequency using only a Month & Year as issue date	Month & Year	1/1/2006	
		2/1/2006	
		3/1/2006	
		etc.	
Semimonthly 
(if not dated)	 First Issue of Month	1/1/2006	
	 Second Issue of Month	1/15/2006	
	 First Issue of Month	2/1/2006	
	 Second Issue of Month	2/15/2006	
		etc.	
Bimonthly
(if not dated)	First Month of Issue		
	e.g. Jun-Jul 2006 	6/1/2006	
	       Dec '05/Jan '06	12/1/2005	
		etc.	
NOTE: All "Special/Extra" issues or other frequencies should have an issue date.  
Container Summary Record
Table B-10. Container Summary Record - .CSM
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container Type	P,S,O,T,E,F,B,W,Z,U,L,1,2,3,4,5,M,H,A,G,D,R,C	This field impacts rates for Periodicals mailings. See the Container Type Values table. New for 08-1: M,H,A,G,D,R,C	
Container ID	Numeric	If numeric only, fill left with zeroes.	
Display Container ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container Grouping Description	Alphanumeric		
Container Destination Zip	Alphanumeric		
Container Level	A,B,C,D, G,H,I,J,K, M,N,P,Q,R,S,T,U,V,X,Y,Z,AA,AB,AC,AD,AE,AF,AG,AH,AI,AJ,BA,BB,BC,BD,BE,BF,BG,BH,BI,BJ,BK,BL,BM	Validation fails files with E, F, or L in this field for all mail classes. This field impacts rates for Periodicals mailings. For more information, see the Container Level Values table. New for 08-1: AJ	
Entry Point for Entry Discount -
Postal Code	Alphanumeric		
Entry Point for Entry Discount -
Facility Type	B,A,S,D,H,R,O,X,V,U,T,N,G,P,F,C**,E,J,K,L,M,Q,I	For all mail classes, validation fails files with Y or Z in this field. This field impacts rates for Periodicals mailings. For more information, see the Entry Point for Entry Discount – Facility Type Values table. 	
Entry Point - Actual / Delivery -
Locale Key	Alphanumeric	•	If Entry Point for Entry Discount - Facility Type is one of {A,B,C,D,E,J,K,L,M,Q,R,T}, then this field is required and must start with “LOC” preceding the locale key. 
•	If Entry Point for Entry Discount - Facility Type is one of {O,H}, then this field is required and must contain “ORIGIN”.
•	If Entry Point for Entry Discount - Facility Type is one of {F,G,I,P,N,U,V,X}, then this field is optional and must contain a six-digit Canadian or international code.	
Entry Point - Actual / Physical -
Facility Type	B,A,S,D,H,R,O,X,V,U,T,N,G,P,F,C,E,J,K,L,M,Q,I	Only for 07-1; deleted in 08-1 and 08-2. Validation fails files with Y,Z in this field. 	
Entry Point – Actual / Delivery Postal Code	Alphanumeric	New for 08-1. ZIP Code + 4	
Parent Container Reference ID	Numeric		
Truck or Dispatch Number	Alphanumeric		
Stop Designator	Alphanumeric		
Reservation Number	Alphanumeric	For FAST recurring appointments, the sixth character should be an “R” and Scheduled Induction Date, Scheduled Induction Time, and a FAST Content ID are required. All other appointments should be numeric. 	
Container Ship Date*	Date	YYYYMMDD - Example: 20061225. This is the mailing date on the postage statement. 	
Container Ship Time	Alphanumeric	New for 08-1. HH:MM – Example: 18:12	
Container Pick Up Date	Numeric	New for 08-1. YYYYMMDD - Example: 20081225	
Container Pick Up Time	Alphanumeric	New for 08-1. HH:MM – Example: 18:12	
Container Acceptance Date	Date	YYYYMMDD - Example: 20061225	
Scheduled In-Home Date	Date	YYYYMMDD - Example: 20061225	
Additional In-Home Range	Numeric		
Scheduled Induction Date	Date	YYYYMMDD - Example: 20061225. Required for recurring reservation numbers. 	
Scheduled Induction Time	Time	HH:MM – Example: 13:30. Required for recurring reservation numbers.	
Internal Date	Date	YYYYMMDD - Example: 20061225	
Number of Copies	Numeric		
Number of Pieces	Numeric		
Total Weight (product only)	Numeric	9999v9	
Unique Container ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container Status	R,C,X,P,T,O,D,’ ‘ (space/blank)	Validation rejects any files with containers claiming status “A”. New for 08-1: D	
Machinable Mail Piece	Y,N,U,A		
Tray Preparation Type	O,T,E,F,S		
Protected Container Status	P,N		
Container Presort Content	A,B,C,D,E,F,G		
Geographic Scheme Level	A,B,C		
Trans-Ship Bill of Lading Number	Alphanumeric		
Production Machine ID	Alphanumeric		
Sibling Container Indicator	Y,’ ‘ (space/blank)		
Sibling Container Reference ID	Numeric		
Postage Grouping ID	Alphanumeric		
Container Gross Weight	Numeric		
Container Gross Weight - Source	A,E		
Container Height	Numeric		
Container Height - Source	A,E		
EMD - 8125 ASN Barcode	Alphanumeric		
Transportation DUNS Number	Alphanumeric		
Entry Point for Entry Discount - Physical Address Postal Code	Alphanumeric	Only for 07-1. Deleted in 08-1. Origin facilities can have any value allowed by the Mail.dat specification. Validation requires a Locale Key with “LOC” filled on the left for locations that are not origin facilities.  For example, LOCV99999.	
Container Level Attempted	Alphanumeric		
Reserve	Alphanumeric	Only for 07-1. Deleted in 08-1. 	
Special Condition On Limit	OV,UF,SM,SN,OM		
DMM Section Defining Container Preparation	Alphanumeric	Allows up to 12 characters. 	
Alternate Method Defining Preparation	Alphanumeric		
"Zebra Stripe" Indicator	Z,N		
Label: IM Container or IM Tray Barcode*	Alphanumeric	Usually 24 characters. For pallets, use 21 characters; populate the leftmost 21 characters. Required only if the mailing uses e8125 and the container is a pallet. 	
Label: 10-Character Container Barcode	Alphanumeric		
Label: Destination Line 1	Alphanumeric		
Label: Destination Line 2	Alphanumeric		
Label: Contents - Line 1	Alphanumeric		
Label: Contents - Line 2	Alphanumeric		
Label: Entry (Origin) Point Line	Alphanumeric		
Label: User Information Line 1	Alphanumeric		
Label: User Information Line 2	Alphanumeric		
Container Label CIN Code	Alphanumeric		
Container Label Type	1,2,3,4,01,02,03,04		
CSM Record Status	O,I,U	Acceptable values dependent on file type.	
Container Contains Overflow Indicator	Y,N		
FAST Content ID	Alphanumeric	Required for recurring reservation numbers.	
FAST Scheduler ID	Numeric	New for 08-1. 	
IM Barcode Upper Serialization	Alphanumeric	New for 08-2.	
IM Barcode Lower Serialization	Alphanumeric	New for 08-2.	
USPS Pick Up	Y,N,’ ‘ (blank)	New for 08-2. Required for Start the Clock performance metrics to determine if USPS transportation was used for delivery to USPS plants. 	
Reserve	Alphanumeric		
Closing Character	#		
** The Postage Statement Register does not display facility name for mailings that claim “C” for Entry Point for Entry Discount - Facility Type. Instead, only “SCF” and the three-digit code display.
Container Type Values
For Periodicals mailings, Container Type Mail.dat values (.csm position 13) values map to the following chargeable container types.
Table B-11. Container Type Values
Mail.dat Value	Container Type	
1 = #1 Sack	Sack	
2 = #2 Sack	Sack	
3 = #3 Sack	Sack	
4 = 01 V Sack	Sack	
5 = 03 V Sack	Sack	
A = Hamper, Large Plastic	Pallet	
B = Bedload	Not mapped for Periodicals 	
C = Collapsible Wire Container	Pallet	
D = Eastern Region Mail Container w/ Web Door	Pallet	
E = EMM Tray	Tray	
F = Flat Tub	Tray	
G = General Purpose Mail Container with Gate	Pallet	
H = Hamper, Large Canvas	Pallet	
L = Logical Tray	Not mapped for Periodicals	
M = Logical Pallet (MLOCR)	Pallet	
O = 1’ Tray	Tray	
P = Pallet	Pallet	
R = Wire Container Rigid	Pallet	
S = Sack	Sack	
T =  2’ Tray	Tray	
U = Unit Load Device	Not mapped for Periodicals	
V – Sack (Virtual)	Not supported currently. Submit mailings with these containers using hard copy postage statements.	
W = Walled Unit	Not mapped for Periodicals	
Z = User Pallet	Pallet	

Container Level Values
For Periodicals mailings, Container Level  (.csm position 41-42) values map to the following chargeable container levels. 
Table B-12. Container Level Values
Mail.dat Value	Container Level Rate	
A = CR-Direct	5-Digit	
B = Mixed CR in 5 Digit	5-Digit	
C = Mixed CR in 3 Digit	SCF/3-Digit	
D = CR – 5 D Scheme	5-Digit	
G = 5 Digit (Auto/Presort)	5-Digit	
H = 5 Digit (Merged)	5-Digit	
I = 5 Digit (Presort only)	5-Digit	
J = 5 Digit (Barcode only)	5-Digit	
K = Metro Scheme	SCF/3-Digit 	
M = 5D Scheme (Presort)	5-Digit	
N = 5D Scheme (Auto, Presort)	5-Digit	
P = 5D Scheme (Barcode)	5-Digit	
Q = 5D Scheme (Merged	5-Digit	
R = 3 Digit (Auto, Presort)	SCF/3-Digit	
S = 3 Digit (Barcode)	SCF/3-Digit	
T = 3 Digit (Presort)	SCF/3-Digit	
U = 3 Digit (CR, Auto, Presort)	SCF/3-Digit	
V = 3 Digit Scheme	SCF/3-Digit	
X = SCF	SCF/3-Digit	
Y = Protected SCF	SCF/3-Digit	
Z = ADC	ADC/AADC	
AA = AADC	ADC/AADC	
AB = Mixed ADC	Mixed ADC/AADC	
AC = Mixed AADC	Mixed ADC/AADC	
AD = ASF	Mixed ADC/AADC	
AE = BMC	Mixed ADC/AADC	
AF = Protected BMC	Mixed ADC/AADC	
AG = Mixed BMC	Mixed ADC/AADC	
AH = Origin Mixed ADC	Mixed ADC/AADC	
AI = Protected ADC	ADC/AADC	
AJ = Single Piece Container	Mixed ADC/AADC	
Entry Point for Entry Discount – Container Entry Values
For Periodicals mailings, Entry Point for Entry Discount – Facility Type (.csm position 49) values map to the following chargeable Container Entry values.
Table B-13. Entry Point for Entry Discount - Facility Type Values
Mail.dat Value	Container Entry	
A = ASF	Destination BMC	
B = DBMC	Destination BMC	
D = DDU	DDU	
S = DSCF	Destination SCF	
H = Tran Hub	Not mapped for Periodicals	
R = ADC	Destination ADC	
O = Origin	Origin Post Office/DMU	
X = Alt Delivery	Not mapped for Periodicals	
V = Int’l Gateway	Not mapped for Periodicals	
U = USPS Int'l	Not mapped for Periodicals	
T = Orig(T-Hub Sq)	Not mapped for Periodicals	
N = Not-determined	Origin Post Office/DMU	
G = Can (Gatwy)	Not mapped for Periodicals	
P = Can (in Can)	Not mapped for Periodicals	
F = Forgn Mail Consol.	Not mapped for Periodicals	
C = Origin SCF**	Origin SCF	
E = Origin DDU	Origin Post Office/DMU	
J = Origin ADC	Origin ADC	
K = Origin BMC	Origin BMC	
L = Origin ASF	Origin BMC	
M = Dest AMF	Destination BMC 	
Q = Origin AMF	Origin BMC	
I = IBMC (Int'l BMC, NJ)	Origin BMC	
Y = RDC (Regional Distribution Center)	Not mapped for Periodicals	
Z = DPC (Destination Processing Center)	Not mapped for Periodicals	
**  The Postage Statement Register does not display facility name for mailings that claim “C” for Entry Point for Entry Discount - Facility Type. Instead, only “SCF” and the three-digit code display.
International Container Label Record
Table B-14. International Container Label Record - .ICL
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric	If numeric only, fill left with zeroes.	
Destination Line 1	(below)		
Destination Line 1: Int.l: Dest Location	Alphabetic		
Destination Line 1: Int.l: Dest OE Qualifier	Alphabetic		
Destination Line 1: Int.l: Final Dest City Name	Alphabetic		
Destination Line 2	Alphanumeric		
Contents Line 1	Alphanumeric		
Contents Line 2	Alphanumeric		
Entry (Origin) Point Line	(below)		
Entry (Origin) Point Line : Int.l: Origin Country Code	Alphabetic		
Entry (Origin) Point Line : Int.l: Origin Location	Alphabetic		
Entry (Origin) Point Line : Int.l: Origin OE Qualifier	Alphabetic		
Entry (Origin) Point Line : Int.l: Internal Date	Date	DDMMYYYY - Example: 25122006	
Entry (Origin) Point Line : Int.l: spare	Alphanumeric		
User Information	Alphanumeric		
Container Label Bar Code	Alphanumeric		
Alt Del - Line 1: 	(below)		
Alt Del - Line 1: Int.l: Int.l Mail Category	Alphanumeric		
Alt Del - Line 1: Int.l Mail Class/ Sub-Class	Alphanumeric		
Alt Del - Line 1: Int.l: Dispatch Year	Numeric		
Alt Del - Line 1: Int.l: Dispatch Number	Numeric		
Alt Del - Line 1: Int.l: Receptacle Number	Numeric		
Alt Del - Line 1: Int.l: Highest Recpt # Indicator	Numeric		
Alt Del - Line 1: Int.l: Registrd/ Insured Indicator	Numeric		
Alt Del - Line 1: Int.l: Weight	Numeric		
Alt Del - Line 1: Int.l: spare	Alphanumeric		
Alt Del - Line 2	Alphanumeric		
Alt Del - Line 3	Alphanumeric		
Alt Del - Line 4	Alphanumeric		
Alt Del - Line 5	Alphanumeric		
ICL Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Container Quantity Record
Table B-15. Container Quantity Record - .CQT
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
CQT Database ID	Numeric		
Container ID	Numeric		
3 Digit / 5 Digit Container Division	Alphanumeric		
Mail Piece Unit ID	Alphanumeric	If numeric only, fill left with zeroes.	
Zone	S,D, L,1,3,4,5,6,7,8, N,A,E,P,F,C,M,V	If Periodicals: Not County/In County is “I”, this value must be “D” or “N”. 
Foreign and Canadian values Q, R, X, T, U and G are not supported. 	
Destination Entry	B,S,D,N,A,O,P,Q		
Rate Category	A,B,D,DE,FB,G,H,K,L,N,O,S,X,Y,L1,L2,L3,L4,L5,NF,AF,BF,Z1,Z2,KF,GF,PI,PM,NG,NK,N5,N6,L6,L7,L8,PE,PQ,PR,PG,PK,P5,P6, P7,P8	Canadian and foreign rates are not supported. This differs from the Mail.dat specification. 	
Barcode Discount or Surcharge Indicator	O,B,D,S,I		
Periodicals: Sub/ Non-Sub/ Requester Indicator	S,N,R,O		
Periodicals: Not County/In County	N,I,O		
Number of Copies	Numeric		
Number of Pieces	Numeric		
CQT Record Status	O,U	Acceptable values dependent on file type.	
Periodicals Co-Palletization Discount Indicator	Y,N		
Exp Per HE,HW, SC Pub - Origin Delivery Zone	Numeric		
Exp Per HE,HW, SC Pub - Origin 3-Digit Zip	Numeric		
ZAP Agent Code	Numeric	Not validated.	
Container Charge Allocation	Numeric	9v999999. Exists for mailer convenience. 	
Reserve	Alphanumeric		
Closing Character	#		
Package Quantity Record
Table B-16. Package Quantity Record - .PQT
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
CQT Database ID	Numeric	See this field in the CQT file for usage. The PostalOne! system does not support the CQT Database ID for the PQT file described in the Mail.dat specification. 	
Package ID	Alphanumeric	For Periodicals bundle charges, validation creates a bundle for each unique combination of Container ID, Package ID, Package ZIP Code, and Package Carrier Route. If numeric only, fill left with zeroes.	
Package Zip Code	Alphanumeric	For Periodicals bundle charges, validation creates a bundle for each unique combination of Container ID, Package ID, Package ZIP Code, and Package Carrier Route.	
Package Carrier Route	Alphanumeric	For Periodicals bundle charges, validation creates a bundle for each unique combination of Container ID, Package ID, Package ZIP Code, and Package Carrier Route.	
Package Level	1,2,3,4,5,6,7,8,A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W	This field impacts rates for Periodicals. For more information, see the Package Level Values table. Validation rejections Periodicals with Package Level “A” and Ready-to-Pay status. 	
Package Barcode	Alphanumeric		
Number of Copies	Numeric		
Number of Pieces	Numeric		
Package Status	C		
PQT Record Status	O,I,U	Acceptable values dependent on file type.	
Bundle Charge Allocation	Numeric	9v999999. Exists for mailer convenience. 	
Reserve	Alphanumeric		
Closing Character	#		
Package Level Values
For Periodicals mailings, Package Level (.pqt position 33) maps to the following chargeable bundle levels: 
Table B-17. Package Level Values
Mail.dat Value	Bundle Level	
A = Firm	Firm at Container Level	
B = Carrier Route	Carrier Route	
C = 5 Digit	5-Digit	
D = Unique 3-Digit	3-Digit/SCF	
F = 3 Digit	3-Digit/SCF	
H = ADC	ADC/AADC	
I = AADC	ADC/AADC	
K = Origin MxADC	Mixed ADC/AADC	
L = MxADC	Mixed ADC/AADC	
M = MxAADC	Mixed ADC/AADC	
O = Working	Not mapped for Periodicals	
R = Parcel	Not mapped for Periodicals	
S = Multi-pc Parcel	Not mapped for Periodicals	
T = 3-D Scheme	3-Digit/SCF	
U = 5-D Scheme + L007	5-Digit	
V = BMC	Mixed ADC/AADC	
W = 5-Digit Super Scheme	5-Digit	
Walk Sequence Record
Table B-18. Walk Sequence Record - .WSR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Package Zip Code	Alphanumeric		
Package CR Number	Alphanumeric		
Co-Palletization Code	Alphanumeric		
Walk Sequence Type	T,R		
Walk Sequence Stops	Numeric		
Walk Sequence Denominator	Numeric		
Walk Sequence Database Date	Date	YYYYMMDD - Example: 20061225	
WSR Record Status	O,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Seed Name Record
Table B-19. Seed Name Record - .SNR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric	If numeric only, fill left with zeroes.	
Package ID	Alphanumeric	If numeric only, fill left with zeroes.	
Mail Piece Unit ID	Alphanumeric	If numeric only, fill left with zeroes.	
Seed Name ID	Alphanumeric	If numeric only, fill left with zeroes.	
Version Key Code	Alphanumeric		
Seed Name Received Date	Date	YYYYMMDD - Example: 20061225	
Seed Type	C,S,R,B		
Piece Barcode	Numeric		
SNR Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reported Seed Condition	M,G,F,P		
Piece 4-State Barcode / Planet Code	Numeric	Deleted in 08-2. 	
IM Barcode	Alphanumeric	New for 08-2.	
Planet Code	Alphanumeric	New for 08-2.	
Reserve	Alphanumeric		
Closing Character	#		
Package Label Record
Table B-20. Package Label Record - .PLR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Alphanumeric	If numeric only, fill left with zeroes.	
Package ID	Alphanumeric	If numeric only, fill left with zeroes.	
City Name	Alphanumeric		
Province Code	Alphanumeric		
Postal Code	Alphanumeric		
PDR Record Status	O,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
IJ/C Relationship Record
Table B-21. IJ/C Relationship Record - .ICR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
File Name	Alphanumeric	Special characters (such as _ or # ) result in file rejection.	
Tape ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric		
Beginning Record	Numeric		
Ending Record	Numeric		
ICR Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Piece Detail Record
See the end of this appendix for a sample of an XML PDR file. Use a .PDR file to submit data to the PostalOne! system; PDR.XML files are validated, but not loaded.  
Table B-22. Piece Detail Record - .PDR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
CQT Database ID	Numeric	Fill left with zeroes. 	
Package ID	Alphanumeric	If numeric only, fill left with zeroes.	
Piece ID	Alphanumeric	If numeric only, fill left with zeroes.	
Piece Barcode	Numeric		
Line-Of-Travel Sequence Number	Numeric		
Line-Of-Travel Seq. Direction Code	Alphanumeric		
Walk Sequence Number	Numeric		
"Wasted Piece" Indicator	Y,’ ‘ (space/blank)		
Delivery Signature Confirmation ID	Alphanumeric		
Piece 4-State Barcode / Planet Code	Numeric	Deleted in 08-2. 	
IM Barcode	Alphanumeric		
Planet Code	Alphanumeric		
PDR Record Status	O,D,I,U	Acceptable values dependent on file type.	
MLOCR Rate and Postage Marking	Alphanumeric		
Machine ID	Alphanumeric	New for 08-1.	
Mailer ID of Mail Owner	Numeric	New for 08-1.	
Mailer ID of Barcode Applicator	Numeric	New for 08-1.	
Move Update Method*	0,1,2,3,4,5		
Reserve	Alphanumeric		
Closing Character	#		
Special Fees/Charges Record
Table B-23. Special Fees / Charges Record - .SFR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric	Fill left with zeroes. Only for 07-1 and 08-1 files. Deleted in 08-2. 	
CQT Database ID	Numeric	New for 08-2. Fill left with zeroes. 	
Piece ID	Alphanumeric	If numeric only, fill left with zeroes.	
Service Type	Alphanumeric		
Service "Stated Value"	Numeric		
Service Fee	Numeric		
Special Fees/Charges Services ID	Alphanumeric	If numeric only, fill left with zeroes.	
SFR Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Manifest Individual Record
Table B-24. Manifest Individual Record - .MIR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric		
Piece ID	Alphanumeric	If numeric only, fill left with zeroes.	
MPU ID	Alphanumeric	If numeric only, fill left with zeroes.	
Piece Barcode	Numeric		
Piece Zone	Alphanumeric		
Piece Destination Entry	Alphanumeric		
Package Level	Alphanumeric		
Package Zip Code	Alphanumeric		
Piece Carrier Route Code	Alphanumeric		
Piece Weight	Numeric		
Postage Class	1,2,3,4,9,X,V,T,P,A,B,C,D,5	If Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T,H,M,E,Z}, then
acceptable values are {1,2,3,4,9,X,V,T,P,5}.	
Processing Category	{LT,FL,CD,MP,IR,OS,AA,AB,AC,AD,AE,AF,AG,AH,AI,AJ,AK,AL,AM,LA,LB,LC,LD,LE,LF,LG,LH,LL,LM,SF,SG,SH,PF,CM}	If Rate Type is one of {R,C,P,A,L,S,B,F,N,X,T,H,M,E,Z}, then acceptable values are {LT,FL,CD,MP,IR,OS,PF,CM}.	
Rate Type	R,C,P,A,L,S,B,F,N,X,T,1,2,3,4,H,M,E,Z, D	If Postage Class is one of {1,2,3,4,9,X,V,T,P,5}, then acceptable values are {R,C,P,A,L,S,B,F,N,X,T,H,M,E,Z}.	
Rate Category	A,B,D,DE,FB,G,H,K,L,N,O,S,X,Y,L1,L2,L3,L4,L5,NF,AF,BF,Z1,Z2,KF,GF,PI,PM,NG,NK,N5,N6,L6,L7,L8,PE,PQ,PR,PG,PK,P5,P6, P7,P8	Canadian and foreign rates are not supported. This differs from the Mail.dat specification. 	
Piece Postage*	Numeric	9999v111. Required field – this differs from the Mail.dat specification. 	
Barcode Discount or Surcharge Indicator	Y,N,O,C		
Parcel Rate Adjustment	Y,N,O		
"Wasted Piece" Indicator	Y,’ ‘ (blank/space)		
Delivery Signature Confirmation ID	Alphanumeric		
Line-Of-Travel Sequence Number	Numeric		
Line-Of-Travel Seq. Direction Code	Alphanumeric		
Walk Sequence Number	Numeric		
Piece Length	Numeric		
Piece Width	Numeric		
Piece Thickness	Numeric		
Piece 4-State Barcode / Planet Code	Numeric	Deleted in 08-2.	
IM Barcode	Alphanumeric		
Planet Code	Alphanumeric		
Primary Payer MPA ID	Alphanumeric		
Secondary Payer MPA ID	Alphanumeric		
Surcharge	Alphanumeric		
Pre-denominated Amount	Numeric		
Postage Affixed Type	S,M		
Weight Source	A,P,C,L		
Weight Status	M,P,F,N		
Package ID	Alphanumeric		
MIR Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Manifest Summary Record
Table B-25. Manifest Summary Record - .MSR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Pallet/Cage Type	P,C,N		
Pallet/Cage ID	Alphanumeric	If numeric only, fill left with zeroes. To indicate no Pallet or Cage ID, use “XXXXX”. 	
Pallet/Cage CIN Code	Numeric		
Tray/Sack Type	O,T,E,F,S		
Tray/Sack ID	Alphanumeric	If numeric only, fill left with zeroes.	
Tray/Sack CIN Code	Numeric		
Piece Range-Set CIN Code	Numeric		
Piece Range-Set Zip Code	Alphanumeric		
Piece Range-Set CR	Alphanumeric		
Piece Range-Set Zone	Alphanumeric		
Piece Range-Set Postage	Numeric		
Piece Range-Set Weight	Numeric		
Piece Range-Set Physical Space	Numeric		
Piece Range-Set First Sequence Number	Numeric		
Piece Range-Set Count	Numeric		
Piece Range-Set One Ounce Qty	Numeric		
Piece Range-Set Two Ounce Qty	Numeric		
Piece Range-Set Three Ounce Qty	Numeric		
Piece Range-Set Four Ounce Qty	Numeric		
Piece Range-Set Five Ounce Qty	Numeric		
Piece Range-Set Six Ounce Qty	Numeric		
Piece Range-Set Seven Ounce Qty	Numeric		
Piece Range-Set Eight Ounce Qty	Numeric		
Piece Range-Set Nine Ounce Qty	Numeric		
Piece Range-Set Ten Ounce Qty	Numeric		
Piece Range-Set Eleven Ounce Qty	Numeric		
Piece Range-Set Twelve Ounce Qty	Numeric		
Piece Range-Set Thirteen Ounce Qty	Numeric		
Waste Quantity	Numeric		
MPA - Unique Sequence/Grouping ID	Alphanumeric		
MSR Record Status	O,D,I,U	Acceptable values dependent on file type.	
Reserve	Alphanumeric		
Closing Character	#		
Postage Adjustment Record
Do not include .par files for Periodicals or MLOCR mailings. 
Table B-26. Postage Adjustment Record - .PAR
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes.	
Mail Piece Unit ID	Alphanumeric	If numeric only, fill left with zeroes.	
Component ID	Alphanumeric	If numeric only, fill left with zeroes.	
Sequence Number	Numeric		
Date	Date	YYYYMMDD - Example: 20061225	
Adjustment Type	1,2,3,4,01,02,03,04		
Adjustment Amount	Numeric	Cannot be zero. 	
Credit/Debit Indicator	D		
Total Pieces Affected	Numeric		
User Comments	Alphanumeric		
PAR Record Status	O,I,U		
Adjustment Status	R		
MPA - Unique Sequence/Grouping ID	Alphanumeric		
Reserve	Alphanumeric		
Closing Character	#		
Actual Tray File Record
This record type is only available for Mail.dat files version 07-1. Version 08-1 and 08-2 files do not accept this record type.
Table B-27. Actual Tray File Record - .ATF
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric	If numeric only, fill left with zeroes.	
Tray Record Number	Alphanumeric		
ATF Record Status	O,D,I,U		
Label: 24-Character Container Barcode	Alphanumeric	Fill with blanks if necessary. Data must be populated in this field if the mailing uses an e8125 and container is a pallet. 	
Tray Weight	Numeric	999v9999 (in pounds)	
Tray Type	P,E		
Reserve	Alphanumeric		
Closing Character	#		
Actual Pallet File Record
This record type is only available for Mail.dat files version 07-1. Version 08-1 and 08-2 files do not accept this record type.
Table B-28. Actual Pallet File Record - .APF
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Container ID	Numeric	If numeric only, fill left with zeroes. 	
Tray Record Number	Alphanumeric		
Pallet Record Number	Alphanumeric		
Container Level	A,B,C,D,E,F,G,H,I,J,K,L,M,N,P,Q,R,S,T,U,V,W,X,Y,Z,AA,AB,AC,AD,AE,AF,AG,AH,AI,BA,BB,BC,BD,BE,BF,BG,BH,BI,BJ,BK,BL,BM		
APF Record Status	O,D,I,U		
Label: 24-Character Container Barcode Def	Alphanumeric	Fill left with blanks.	
Pallet Weight	Numeric	9999v9 (in pounds)	
Pallet Type	P,E		
Container ZIP	Alphanumeric	999991234	
Reserve	Alphanumeric		
Closing Character	#		

Information Access Key File Record
This record type identifies different business roles when mail is handled by multiple mailing agents, with each agent responsible for different business tasks, and identified using unique MPU and CPT records within a mail piece. This record type is new with Mail.dat version 08-1.  
Table B-28. Information Access Key File Record - .IAK
Field	Acceptable Values	Notes	
Job ID	Alphanumeric	If numeric only, fill left with zeroes.	
Segment ID	Alphanumeric	If numeric only, fill left with zeroes. 	
Mail Piece Unit ID	Alphanumeric	If numeric only, fill left with zeroes.	
Component ID	Alphanumeric	If numeric only, fill left with zeroes.	
Information Access ID	Alphanumeric	If numeric only, fill left with zeroes.	
Mail Owner	Numeric	USPS-assigned CRID	
Mail Preparer	Numeric	USPS-assigned CRID	
Mail Scheduler	Numeric	USPS-assigned CRID	
Mail Consolidator	Numeric	USPS-assigned CRID	
Mail Logistics	Numeric	USPS-assigned CRID	
IAK Record Status	O,D,I,U		
Reserve	Alphanumeric		
Closing Character	#		
Piece Detail Record (XML version) 
A sample XML piece detail record is below. The .pdrxml file is validated against the XSD schema file available on the IDEAlliance site: http://www.maildat.org. Use a .PDR file to submit data to the PostalOne! system; XML PDR files are validated, but not loaded.
<?xml version="1.0" encoding="UTF-8"?>
<PDRXml>
	<UserLicenseCode>123456</UserLicenseCode>
	<MaildatJobID>12345678</MaildatJobID>
	<PieceCount>1</PieceCount>
	<PDRInfoBlock>
		<PackageID>123456</PackageID>
		<CQTDatabaseID>12345678</CQTDatabaseID>
		<!--Choice<LOTSequenceDirectionCode>S</LOTSequenceDirectionCode><LOTSequenceNumber>1234</LOTSequenceNumber>-->
		<WalkSequenceNumber>12345</WalkSequenceNumber>
		<IMB>
			<BarcodeID>12</BarcodeID>
			<ServiceTypeCode>123</ServiceTypeCode>
			<MailerID6>123456</MailerID6>
			<SerialNumber9>123456789</SerialNumber9>
			<!--<MailerID9>123456789</MailerID9><SerialNumber9>123456</MailerID9>		-->
			<DeliveryPointZIP>werwe243</DeliveryPointZIP>
		</IMB>
		<!--<PlanetCode>1111111111111</PlanetCode><DeliveryPointZIP>11111111111</DeliveryPointZIP>-->
		<!--<DeliveryContainerID>1111111111111111111111</DeliveryContainerID><DeliveryPointZIP>11111111111</DeliveryPointZIP>-->
		<PieceID>1111111111111111111111</PieceID>
		<WastedPieceIndicator>Yes</WastedPieceIndicator>
		<MLOCRrateANDpostageMarking>S123456</MLOCRrateANDpostageMarking>
		<MoveComplianceUpdateMethod>4</MoveComplianceUpdateMethod>
		<MailOwner>
			<MailerID6>123456</MailerID6>
			<!--<MailerID9>123456789</MailerID9><CRID>1</CRID><SchedulerID>S11111111111</SchedulerID>-->
		</MailOwner>
		<BarCodeApplicator>
			<MailerID6>123456</MailerID6>
			<!--<MailerID9>123456789</MailerID9><CRID>1</CRID><SchedulerID>S11111111111</SchedulerID>-->
		</BarCodeApplicator>
		<MachineID>S123</MachineID>
		<PDRRecordStatus>D</PDRRecordStatus>
	</PDRInfoBlock>
</PDRXml>

Appendix C. Status Receipt File Layout
This appendix contains details about the contents of a Status Receipt file and associated record types and format. 
NOTE: Status receipt files are the only receipt files currently available; postage statement receipts are unavailable. 
C-1  Status Receipt File Content
The receipt file conforms to these specifications:
1.	A receipt file shall contain one or more records represented by ASCII text. The text shall be in the subset of ASCII characters indicated by the decimal values 33 to 126.
2.	A new line character or sequence of characters (this is platform dependent) shall terminate each record.
3.	The records of a receipt file shall contain a predefined character that shall serve to distinguish its fields. The default character shall be a comma “,”.
NOTE: You can customize the “delimiter” character by changing the Delimiter parameter in the postal1.ini file. For more information, see Section 4.1.4, Downloading and Configuring the Windows Batch Processor or Section 4.1.5, Downloading and Configuring the UNIX Batch Processor.
4.	The receipt file record may have various types. Only one record type has been specified at this point.
5.	A record in a receipt file shall commence with a “record-type” field that shall serve in the record’s identification. Following the record-type field shall be various character-delimited fields following a predefined sequence.
C-2  Record Types and Record Format
This section provides details about the receipt file's record types and formats. For additional information about postal1.ini parameters, see the table in Sections 4.1.4, Downloading and Configuring the Windows Batch Processor or 4.1.5, Downloading and Configuring the UNIX Batch Processor.
Record Type: status receipts
The PostalOne! system allows Batch Processor users to receive Mail.dat transaction confirmations in the form of Status Receipt files. The Status Receipt file indicates the successive stages of a Mail.dat transaction being processed and can be transmitted in two formats: XML and character delimited.
The following is the XML schema for Status Receipts:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:element name="receipts">
		<xs:complexType>
			<xs:all>
				<xs:element name="record-type">
					<xs:annotation>
						<xs:documentation>The current record type for PostalOne! receipt files is: transfer-status. The transfer-status record shall serve to indicate the progress of the processing of a Mail.dat file transferred to the PostalOne! Java upload server. The record shall trace, through its fields, the validation, the loading, and the processing of postage statements for a Mail.dat file transfer.</xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:all>
							<xs:element name="version">
								<xs:annotation>
									<xs:documentation>the version of this receipt file. (e.g. 1.0)</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="job-id">
								<xs:annotation>
									<xs:documentation>Mail.dat Job ID as presented in the header file specification of Mail.dat.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="filename">
								<xs:annotation>
									<xs:documentation>the part of the name of a Mail.dat file without the extension. For example, if the files sent are foo.hdr, foo.csm and foo.cqt, the filename is foo. If the receipt record is for a finalized, a canceled or a reversed postage statement, this record will contain the container ID of one of the containers that was finalized, canceled, or reversed.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="verification-facility-zip-4">
								<xs:annotation>
									<xs:documentation>The zip plus 4 code of the mailing facility where verification occurred.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="date-time">
								<xs:annotation>
									<xs:documentation>a time stamp, represented in the 24 hour time system, that indicates the creation or the receipt of a file. The Java upload server provides the time that is used.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="validation">
								<xs:annotation>
									<xs:documentation>a binary value of P or F indicating successful validation or failed validation, respectively, of a Mail.dat file.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="job-acceptance">
								<xs:annotation>
									<xs:documentation>a binary value of P or F indicating whether a file has been successfully loaded to the Java upload server's data repository for loading to a database.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="insert">
								<xs:annotation>
									<xs:documentation>a binary value of P or F indicating the successful loading of a job from the Java upload server's data repository to the database.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="PS-generated">
								<xs:annotation>
									<xs:documentation>a Boolean value of T or F indicating whether a postage statement has been generated or has not been generated.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="PS-canceled">
								<xs:annotation>
									<xs:documentation>a value of C or null indicating whether a postage statement has been canceled or no action has been taken, respectively.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="PS-finalized">
								<xs:annotation>
									<xs:documentation>a value of F, R or null indicating whether a postage statement has been finalized, reversed or no action has been taken, respectively.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="mpu-edit">
								<xs:annotation>
									<xs:documentation>a value of T or null indicating whether an mpu edit has occurred on the front-end or not.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="error-code">
								<xs:annotation>
									<xs:documentation>a numeric error code generated by the PostalOne! Java upload server that represents the occurrence or absence of an error. A zero in the field indicates the absence of error.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="error-message">
								<xs:annotation>
									<xs:documentation>a message generated by the PostalOne! Java upload server that describes, with brevity, an error or warning that has occurred. If there is no error or warning, this field will be null.</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:all>
					</xs:complexType>
				</xs:element>
			</xs:all>
		</xs:complexType>
	</xs:element>
</xs:schema>
Record Type: transfer-status
The current record type for PostalOne! receipt files is: transfer-status.
The transfer-status record shall serve to indicate the progress of the processing of a Mail.dat file transferred to the PostalOne! Java upload server. The record shall trace, through its fields, the validation, the loading, and the processing of postage statements for a Mail.dat file transfer. The format for job status records is as follows:
transfer-status<char-del>version<char-del>jobid<char-del>filename<char-del>verification-facility-zip+4<char-del>date-time<char-del>validation<char-del>job-acceptance<char-del>insert<char-del>PS-gen<char-del>PS-canceled<char-del>PS-fin<char-del>mpu-edit<char-del> error-code<char-del>error-msg<new-line>
where
transfer-status : represents the literal text that will be placed at the beginning of a transfer-status record.
<char-del>: represents the ASCII character used as the field delimiter.
version: the version of this receipt file. (e.g. 1.0)
jobid: the Mail.dat Job ID as presented in the header file specification of Mail.dat.
filename: the part of the name of a Mail.dat file without the extension. For example, if the files sent are foo.hdr, foo.csm and foo.cqt, the “filename” is foo. If the receipt record is for a finalized, a canceled or a reversed postage statement, this record will contain the container ID of one of the containers that was finalized, canceled, or reversed.
verification-facility-zip+4: The ZIP+4 Code of the mailing facility where verification occurred.
date-time: a time stamp, represented in the 24 hour time system, which indicates the creation or the receipt of a file. The Java upload server provides the time that is used.
validation: a binary value of “P” or “F” indicating successful validation or failed validation, respectively, of a Mail.dat file.
job-acceptance: a binary value of “P” or “F” indicating whether a file has been successfully loaded to the Java upload server’s data repository for loading to a database.
insert: a binary value of “P” or “F” indicating the successful loading of a job from the Java upload server’s data repository to the database.
PS-gen: a Boolean value of “T” or “F” indicating whether a postage statement has been generated or has not been generated.
PS-canceled: a value of “C” or <empty> indicating whether a postage statement has been canceled or no action has been taken, respectively.
PS-fin: a value of “F”, “R” or <empty> indicating whether a postage statement has been finalized, reversed or no action has been taken, respectively.
mpu-edit: a value of “T” or <empty> indicating whether an mpu edit has occurred on the front-end or not.
error-code: a numeric error code generated by the PostalOne! Java upload server that represents the occurrence or absence of an error. A zero in the field indicates the absence of error.
error-msg: a message generated by the PostalOne! Java upload server that describes, with brevity, an error or warning that has occurred. If there is no error or warning, this field will be empty.
<new-line>: the platform-specific new line character sequence. 

Appendix D. Postage Statement Receipt File Layout
Postage statement receipt files are not currently supported. See the Mail.XML Specification on the IDEAlliance Mail.XML site (http://www.mailxml.org) for the Postage Statement Query and Periodical Statement Query messages that will be supported in a future release.

Appendix E. Error Messages
This appendix contains a list of error messages generated during manual or batch file processing. Error messages may appear in one or more of the following places: 
•	In the Validation.log file. By default, the file is on your machine in C:\Validation.log. This option is only available to manual file processing users. 
•	In the Transfer Summary Report.  On the left menu bar, click File Transfer, then click Transfer Summary. The Summary Report shows the status of all jobs. Click a failed job, and then click the name of the file with errors to see the error message. These messages are usually also in the Validation.log file. This option is available to all manual file transfer users with access to Preparer or Owner features in the PostalOne! system.
•	In the batch processor logs. See Server#.log (# = 1 to n) for general status information, and User#.log (#1 = 1 to n) for transfer error messages containing the error codes and messages as shown in this section. This option is only available to batch processing users. 
•	In the Metrics Search. To view error messages, on the left menu bar, click Metrics Search. Search for the job if necessary. Click the F link for the failed job. The error report displays. This option is available to all users with access to Preparer or Owner features in the PostalOne! system. 
NOTE: Errors produced by the database are not included in this appendix. Generally, a database error begins with “ORA-“ followed by a number. If you should receive one of these errors, confirm your data is formatted correctly (numeric fields do not contain letters, etc.). If your data appears to be correct, contact the Customer Care Center with the error message. 
Issue Resolution
Some error messages will suggest a specific step to resolve the error, such as checking the client.config file, resubmitting the job, or correcting data (if a data issue is involved) and then resubmitting. 
If no resolution is suggested, you may want to: 
•	Verify your machine has the correct software and versions of the software.
•	Verify any settings in your client.config file are correct. (Batch processing users only)
•	Verify your Internet connection is available. 
•	Check the PostalOne! site to see if an outage has been posted. 
•	Verify your machine has sufficient memory for the size of the files you were trying to send. 
•	Verify the all of the data being sent is in the correct format, and does not conflict with other sections of the files and/or postal regulations for the claimed mail classes and rates. Generally, you must correct the error(s) before you will be able to successfully resubmit the file if you have a data issue. 
Processing Order
Mail.dat submissions are processed in the following order: 
1.	Mail.dat Client
2.	Upload Server
3.	Mail.dat Package
4.	Wizard Web Service (WWS) Server
5.	Database
Mail.dat Client
Words in brackets and italics, such as [number], indicate a value automatically added to the error message by the PostalOne! system. For example, the maximum size of a specific field might be inserted if that maximum was exceeded. 
Table E-1. Mail.dat Client Error Messages
Error Message	Notes	
Authentication failure Error: [server user verification error]		
DataRepository Class Internal Error!, Enumeration error: [message]		
DataRepository Class Internal Error!, Get Parent Table error: [message]		
DataRepository Class Internal Error!, Get Parent Table error: Table did not match any types.		
DataRepository Class Internal Error!, Get Second Partial Table error: Table did not match any types.		
DataRepository Class Internal Error!, No Such Element Exception error: [message]		
DataRepository Class Internal Error!, Table Contains Data error: File did not match any types.		
DataRepository Class Internal Error!, validate Csm Parent Child Relation error: [message]		
DataRepository Class Internal Error!, validate Csm Sibling Relation error: [message]		
DDataRepository Class Internal Error!, StringTokenizer error: [message]		
Error: [file name] has an Error. [extended client error]		
Error: All file-level status flags are not identical in the Header file: [file name].	The file status claimed in the HDR record does not match the file status claimed in supporting files such as the MPU file.	
Error: All of file-level status flag in Header file are None Transmitted in the Header file: [file name].		
Error: An unknown file type was sent to the PostalOne! server. Please check your data files and retry this transaction. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: At least one file-level status flag was not accepted in the Header file: [file name].		
Error: Can't delete file [file name]		
Error: Encoding error. Error details: [exception]		
ERROR: File [file name] file contains an Invalid history status.		
ERROR: File [file name] file contains an Invalid Mail.dat Presentation Category.		
ERROR: File [file name] file contains job ID [job ID] from history records can't found from current records.		
ERROR: File [file name] file contains Non-zero record counts that are not allowed in the header record of a delete job (except Segment record count).		
ERROR: In [file name] either the [field name] (Row [record number] :position [start position] [stop position] field or the [field] (Row # [record number] :position [value] [token] field should be filled, but both fields are blank.		
ERROR: In [file name] GCA Version Identifier of Record # [rec_num] is invalid.		
ERROR: In [file name] length of Record # [number] is incorrect.		
ERROR: In [file name] mandatory field \ field name \ (Row # [record number] :position [start position] [stop position] is blank.		
ERROR: In [file name] optional field [field name] Row # [record number] :position [start position] [stop position] contains invalid data.		
ERROR: In [file name] the [field name] (Row # [record number] :position [start position] [stop position] and the [field] Row # [record number] :position [token] [next token] fields contain incompatible data.		
ERROR: In [path] Invalid file name.	Verify file names do not include special characters, such as “-“ or “/”.	
ERROR: In directory [Path] [FILE NOT FOUND]		
Error: In file [file name.par] for the “ADJUSTMENT_STATUS” field (in Record #: position 77_77), the currently supported value is R (Ready To Pay).		
ERROR: In File [file name], History SEQ Number is either missing or not valid.		
ERROR: In File [file name], Job ID is either missing or not valid.		
ERROR: In File [file name], one or more Record Closing Characters are either missing or not valid.		
ERROR: In File [file name], one or more Record Counts are either missing or not valid.		
ERROR: In File [file name], one or more Record Lengths are incorrect.		
ERROR: In File [file name], Provider Code is either missing or not valid.		
Error: Input file 'Client.config' can not be found!		
Error: NewLineCheck error: [exception]		
Error: No update files found for the transmittal of JOBID [job ID].		
Error: PAR file is not supported for MLOCR mailings.		
Error: PAR file is not supported for Periodicals.		
Error: PAR file is not supported for the MPA UIDs associated with Postage Payment Method (in MPA file) values other than P (Permit type is PI) or G (Permit type is OI).		
Error: PAR file should be submitted along with at least one container with status of Ready to Pay (R) in the .csm file.		
Error: PAR_RECORD_STATUS("Record #: position 76_76), with value of 'U' is not supported. Please modify the PAR_RECORD_STATUS value and re-submit the job.	PAR files cannot have PAR Record Status (position 76) set to “U” or as part of an update job. 	
Error: PostalOne! Connect to the Server has a error.		
Error: Reading file error. Error details: [exception]		
Error: Record count for the required file [file name] cannot be set to '0' in the header record.		
Error: Run Out of memory: Please shutdown and modify Xms  Xmx parameter to expand java runtime memory (example -Xms756m -Xmx1024m)		
Error: 'Temp User' is either missing or not valid in selected file.		
ERROR: The [file name] file contains duplicate history sequence numbers.		
ERROR: The [file name] file contains duplicate keys		
Error: The 'Checksum' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Client-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Customer-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
ERROR: The File [file name] file contains a mail facility which is either missing or not valid.		
Error: The 'File-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'File Name' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'File-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
ERROR: The header file contains multiple current status lines in the History Status field.		
ERROR: The header file contains multiple version in the GCA field of current records.		
ERROR: The header file contains no current status lines in the History Status field.		
Error: The 'Job-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Job-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
ERROR: The last record in file [file name] does not end with a newline character.		
ERROR: The length of record # [error rec num] in file [path] is incorrect.		
Error: The 'Location-Seq' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Mailing-facility' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Password' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The PostalOne! Batch Processor application		
Error: The PostalOne! server failed to receive the complete mail.dat files in this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Provider-code' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Request-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Service Date' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Service Name' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Username' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: Unable to find one of the files for the submitted process.		
EVS File Transfer Error: Unable to download the e-VS hand held application software.		
File: [File name] can't connect to [host] :[port]. [NO REPONSE FROM SERVER]. Application exit		
Internal System Error:  [ErrorNum] Please call the PostalOne! Customer Care Center and report this error.		
Internal System Error: A fatal error occurred while receiving CMP file (*.cmp).  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Internal System Error: A fatal error occurred while receiving IMP file (*.imp).  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: A communication error occurred (a request other than 'POST' was used), while processing this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: A communication error occurred (unable to determine the content type values), while processing this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: A system error occurred in the PostalOne! application while locating a system resource. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: A system error occurred in the PostalOne! application while requesting a system resource. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An attempt was made to re-insert a mail.dat job that already exists in the PostalOne! database. Such transactions are not allowed by the PostalOne! application.		
System Error: An error occurred while processing a database (SQL) transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error: An error occurred while reading one of the files in this mail.dat job. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while re-assembling the mail.dat job on the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the CLR file (*.clr) for this transaction. Please resubmit the job. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the CONFIRM file (*.csv) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the CPT file (*.cpt) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the CQT file (*.cqt) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the CSM file (*.csm) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the EVS file (*.evs) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the HDR file (*.hdr) for this transaction. Please resubmit the job. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the ICL file (*.icl) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the ICR file (*.icr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the MCR file (*.mcr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the MIR file (*.mir) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the MPU file (*.mpu) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the MSR file (*.msr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the PAR file (*.par) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the PLR file (*.plr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the PQT file (*.pqt) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the SEG file (*.seg) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the SFR file (*.sfr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the SNR file (*.snr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the SPR file (*.spr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An error occurred while receiving the WSR file (*.wsr) for this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: An unknown protocol (other than HTTP/HTTPS) was used to initiate communication with the PostalOne! server. If using the batch processor application, please check your client.config file and resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Client connection timed out. Please retry this transaction. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Could not add new job to database. Please call the PostalOne! Customer Care Center and report this error.		
System Error: Could not delete existing job to insert new job. Please call the PostalOne! Customer Care Center and report this error.		
System Error: Could not delete job status from DB. Please call the PostalOne! Customer Care Center and report this error.		
System Error: Error occurred while assembling split file on server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Error on server while creating directories for file storage. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Error on server while reading in HTTP input. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Error on server writing file from input steam to file. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: None or partial received from input stream. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Server could not validate data from this application.  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Server is currently busy.		
System Error: The PostalOne! Database is temporarily unavailable (server can not connect to the database). Your transaction will be automatically processed when the PostalOne! Database is back online.		
System Error: The PostalOne! server is temporarily unavailable. If using the File Transfer Applet, please retry this transaction in ten minutes; if using the Batch Processor Application, this transaction will be automatically resent. If the problem persis		
System Error: The PostalOne! server is temporarily unavailable. Please retry this transaction in ten minutes. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: The PostalOne! server is temporarily unavailable. This transaction will be automatically resent. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error: Unable to update the file status details in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
System Error: Unable to update the transaction status details in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
System Error: Unable to update the transaction status in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
Unable to download the e-VS hand held application software.		
Unable to transfer an error message to the PostalOne! server while processing file: [path] [extended client error]		
User Error(3109) A Mail.dat job is already in process in the PostalOne! server. Please wait until the job complete processing and resubmit the job.	Wait until the current job has completed processing before sending an update / delete job.	
User Error: All file-level status flags in Header file are not identical. Please correct the data of the mail.dat job and resubmit the job.		
User Error: All of file-level status flag in Header file are None Transmitted. Please correct the data of the mail.dat job and resubmit the job.		
User Error: An attempt was made to connect to the PostalOne! server using an outdated batch process application. Please download the current version of the batch processor application from the PostalOne! web site, and then retry this transaction.		
User Error: At least one file-level status flag in Header file was not accepted. Please correct the data of the mail.dat job and resubmit the job.		
User Error: File failed - validation on the client. Please refer to the validation.log file for details. Please resubmit the job after correcting the validation errors.		
User Error: in .pdrxml file. PieceCount element not found or it has zero value		
User Error: in .pdrxml file. Total No. of pieces included in XML document is not matching PieceCount element value		
User Error: No update files found for the update job. Please correct the data of the mail.dat job and resubmit the job.		
User Error: Record count for a required file is set to '0' in the Header file. Please correct the data of the mail.dat job and resubmit the job.		
User Error: The  [file] record count indicated in the header record for job id  [job ID], does not match the actual record count.  Please correct the data of the mail.dat job and resubmit the job.		
User Error: The file name used by this mail.dat job is not allowed by the PostalOne! application. Please correct the file name and resubmit the job. For more information, please check the online documentation, or call the PostalOne! Customer Care Center.	File names must be alphanumeric and cannot include any special characters.	
User Error: The header record for this delete transaction contains non-zero counts for one or more mail.dat files (except the segment file) in this transaction. Please correct the data of the mail.dat job and resubmit the job.		
User Error: The optional [file] xxx file indicated in the header record for job id  [job ID], was not found in this mail.dat job.  Please correct the data of the mail.dat job and resubmit the job.		
User Error: This mail.dat transaction (Job ID) [Job  ID] does not contain the required [file] or the required file type is NONE TRANSMITTED. Please correct the mail.dat data and resubmit the job.		
Upload Server
Words in brackets and italics, such as [number], indicate a value automatically added to the error message by the PostalOne! system. For example, the maximum size of a specific field might be inserted if that maximum was exceeded. 
Table E-2. Upload Server Error Messages
Error Message	Notes	
Error: container ID in CQT is not in CSM [line].		
Error: Encoding error. Error details: [details]		
Error: Get Connection not found.		
ERROR: In [path] failed validation.		
ERROR: In [path] File contains no data. 		
ERROR: In [path] Invalid file name.	Verify file names do not include special characters, such as “-“ or “/”.	
Error: International mail is not supported for Pending Periodicals at this time - Job ID [ID]		
Error: International mail is not supported for Pending Periodicals at this time - Job ID [ID] Container [container ID] has foreign zone [container zone].		
Error: International mail is not supported for Periodicals at this time - Job ID [ID] Container [container ID] has container status 'R' and foreign zone [zone].	Files are rejected if foreign pieces are included.	
Error: No directory found here!		
Error: The 'Checksum' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Client-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center. 		
Error: The 'Customer-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'File-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Filename' information is missing or invalid due to a transmission error.  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'File-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Job-ID' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Job-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Location-Seq' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Mailing-facility' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Password' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Provider-code' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Request-type' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Service Date' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Service Name' information is missing or invalid due to a transmission error.  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: The 'Username' information is missing or invalid due to a transmission error. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
Error: unable to send out notification email. (Context: send out an email notifying admins of this Job which keeps crashing.)		
HTTP BAD REQUEST = 400 (Bad Request)		
HTTP MOVED TEMP = 302 (Moved Temporarily)		
HTTP OK = 200 (Ok)		
HTTP SERVER ERROR = 500 (Internal server error)		
HTTP UNAUTHORIZED = 401 (Unauthorized)		
HTTP UNAVAILABLE = 503 (Service Unavilable)		
HTTP WRONG VERSION = 402 (Daemon Version Error)		
IMBLowerSerializatio/IMBUpperSerialization error in CSM file. STC and MID don't match for container id [ID]		
IMBLowerSerializatio/IMBUpperSerialization limits error in CSM file. Upper limit for container id [ID] is less than the Lower limit.		
Loader Process was terminated with signal value of [value].		
Malformed IMBLowerSerializatio/IMBUpperSerialization in CSM file for container id [ID]		
PAR DATA is invalid. No Postage statements were found to post the adjustment. Please correct the PAR data and resubmit the job.	PAR data did not seem to match any postage statement pending finalization. Update the PAR data and resubmit the job. 	
Postage Reduction WWS call returned with ERRORS. The reduction does not find the statement with sufficient postage.	The PAR adjustment amount was greater than the Postage Statement total. Update the PAR data and resubmit the job.	
System Error [1000]: Unable to write the HDR file (*.hdr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1001]: Unable to write the SEG file (*.seg) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1002]: Unable to write the MPU file (*.mpu) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1003]: Unable to write the MCR file (*.mcr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1004]: Unable to write the CPT file (*.cpt) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1005]: Unable to write the CSM file (*.csm) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1006]: Unable to write the CLR file (*.clr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1007]: Unable to write the ICL file (*.icl) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1008]: Unable to write the CQT file (*.cqt) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1009]: Unable to write the PQT file (*.pqt) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1010]: Unable to write the WSR file (*.wsr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1011]: Unable to write the SNR file (*.snr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1012]: Unable to write the PLR file (*.plr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1013]: Unable to write the ICR file (*.icr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1014]: Unable to write the PAR file (*.par) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1015]: Unable to write the MSR file (*.msr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1016]: Unable to write the MIR file (*.mir) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1017]: Unable to write the SPR file (*.spr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1018]: Unable to write the SFR file (*.sfr) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1021]: Unable to write the EVS file (*.evs) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1022]: Unable to write the CONFIRM file (*.csv) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1023]: Unable to create a file on the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1025]: Unable to write the ATF file (*.atf) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1026]: Unable to write the APF file (*.apf) to the PostalOne! server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1100]: A system error occurred (error on server while reading in HTTP input) while processing this transaction. Please resubmit the job. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1105]: Error on server while creating directories for file storage. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.  		
System Error [1106]: None or partial received from input stream. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1107]: Error on server writing file from input steam to file. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1108]: Error occurred while validating file list. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1303]: Error occurred while assembling split file on server. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1304]: Error occurred while retrieving assembled file list. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1305]: Error occurred while validating files in files.txt. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1308]: A complete maildat transmission was not received.  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1309]: Incomplete file received. Server timed out. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1312]: Error reading header file (*.hdr). Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [1324] occurred while splitting multiple job id files. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [2000]: uncompressing file  Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [2001]: An System Error occurred while processing this transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [2002]: An System Error occurred while loading this Mail.dat transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [3003]: Unable to update the transaction status in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
System Error [3004]: Unable to update the transaction status details in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
System Error [3005]: Unable to update the file status details in the PostalOne! database.  Please call the PostalOne! Customer Care Center and report this error.		
System Error [3101]: An error occurred while processing a database (SQL) transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [3103]: A system error occurred while allocating a data buffer in the PostalOne! application. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System error [3104]: The Mail.dat version of this update does not match that of the original file		
System Error [3108]: A System Error occurred while loading the PDR data. Please call the PostalOne! Customer Care Center and report this error.		
System Error [4000]: An unknown protocol (other than HTTP/HTTPS) attempted to initiate communication with the PostalOne! server. If using the Batch Processor, please check your client.config file and resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [4001]: A communication error occurred (a request other than 'POST' was used), while processing this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [4002]: A communication error occurred (unable to determine the content type values), while processing this transaction. Please resubmit the job. If the problem persists, please call the PostalOne! Customer Care Center.		
System Error [5000]: One or more duplicate records were found while processing this job. Please correct the data of the mail.dat job and resubmit the job. 		
System Error [5001]: No record found for the update.		
System Error [5004]: A system error occurred while running an internal database stored procedure for this original job. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5005]: A system error occurred while running an internal database stored procedure for this update job. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5007]: A system error occurred while running an internal database stored procedure (container quantity procedure). Please call the PostalOne! Customer Care Center and report this error.		
System Error [5008]: ): A system error occurred while inserting the LEVEL IDs in the PostalOne! database. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5010]: A system error occurred while running an internal database stored procedure (total weight procedure). Please call the PostalOne! Customer Care Center and report this error.		
System Error [5011 or 5012]: Nonvalid zero for value. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5013]: Postage statement is not available for this mail.dat transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5017]: An error occurred (too many rows) while generating the postage statement for this transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5018]: An error occurred (PS exception) while generating the postage statement for this transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5020]: An error occurred while canceling containers in this transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [5024] One or more segments in this job could not be deleted. Please call the PostalOne! Customer Care Center for more information.		
System Error [5025]: A system error occurred while running an internal database stored procedure for sibling containers job. Please call the PostalOne! Customer Care Center and report this error.  		
System Error [5030] All segments rejected for the job. Please call the PostalOne! Customer Care Center for more information.		
System Error [5031]: The Mail.dat submission failed MLOCR rejection criteria. Please correct the data of the mail.dat job and resubmit the job.		
System Error [6000]: The PostalOne! Database is temporarily unavailable (server can not connect to the database). Your transaction will be automatically processed when the PostalOne! Database is back online.		
System Error [6003]: This mail.dat transaction type is currently not supported by PostalOne!. Please call the PostalOne! Customer Care Center and report this error.		
System Error [7000]: User logon failed. Please check your user name and password and resubmit the job.		
System Error [8000]: A database error occurred (unique limitation error), while processing this transaction. Please call the PostalOne! Customer Care Center and report this error.		
System Error [8001]: A database configuration error has occurred. Please call the PostalOne! Customer Care Center and report this error.		
System Error [9000]: The PostalOne! server was unable to forward this manifest file to PTS. Please call the PostalOne! Customer Care Center and report this error.	Only affects eVS customers. 	
System Error: An attempt was made to re-insert a Mail.dat job that already exists in the PostalOne! database. Such transactions are not allowed by the PostalOne! application.		
Upload Server Error: Cannot obtain Container count to verify for update job.		
Upload Server Error: Cannot obtain Destination Zip count to verify for update job.		
Upload Server Error: Cannot obtain job preparers permit no and permit type.		
Upload Server Error: Cannot obtain job presentation category.		
Upload Server Error: Cannot obtain job transmission type.		
Upload Server Error: Cannot obtain Original Qualification report ID.		
Upload Server Error: Problem getting mailing data id mapping (Orig to Upd) MLOCR onepass [Get Job Info].		
Upload Server Error: Problem running M_WWS_DATA_SUBMISSION_PKG.chk_onepass_rate_catg_dwn_f [job ID].		
Upload Server Error: Problem running M_WWS_DATA_SUBMISSION_PKG.chk_onepass_ratecatg_upward_f [job ID].		
User Error [1310]: File name for transmitted file is not allowed. Please correct the file name and resubmit the job.		
User Error [1311]: PostalOne! does not currently support this Mail.dat version. Please check the online documentation or call the PostalOne! Customer Care Center for the supported mail.dat version(s).		
User Error [1325]: Invalid history status from history and current records. Please correct the data of the mail.dat job and resubmit the job.		
User Error [3105]: Transmission of a job after a delete transmission cannot occur on the same date as the original job transmission.  Wait one day before transmitting the job.		
User Error [5002]: Either the Permit Number, or the USPS Pub Number must be populated in all mail.dat jobs. Both fields were blank in this transaction. Please populate the missing information and resubmit the job.		
User Error [5003 or 5006]: No original Mail.dat job was found for this update transaction. Please submit the original Mail.dat job first, and then resubmit this transaction.		
User Error [5009]: This job is closed. Please contact your local Detached Mail Unit (DMU).		
User Error [5014]: One or more containers in this shipment have previously been identified as having paid postage or ready to pay. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5015]: Preliminary Postage Statements cannot be created using a container that has already generated a Postage Statement. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5016]: Invalid new value for the status of a cancelled or paid container. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5021]: One or more containers not marked as ready to pay have been flagged for a transportation update. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5022]: The status of a container cannot be marked as 'paid' if not already marked as 'ready-to-pay'. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5023]: One or more containers in this shipment have been identified as canceled, marked ready to pay, or having paid postage. A delete transaction is not allowed for this job.		
User Error [5027]: The only containers that may be canceled are those marked Ready To Pay. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5028]: Only containers marked Original or Preliminary may be updated to Ready to Pay. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5029]: Jobs with estimated or cancelled postage statements only can be deleted. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5032]: Invalid Primary MPA ID in MCR record. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5033]: Invalid Additional Postage MPA ID in MCR record. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5034]: Invalid Postage Adjustment MPA ID in MCR record. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5035]: International mail is not supported for Periodicals at this time - Foreign Periodical Zone in CQT record.  Please correct the data of the mail.dat job and resubmit the job.	Files have been rejected due to foreign zone in the Zone field of the CQT file.	
User Error [-5036]: International mail is not supported for Pending Periodicals at this time - Foreign Periodical Zone in CQT record.  Please correct the data of the mail.dat job and resubmit the job.		
User Error [5037]: Invalid Ship date with R-2006 Rate case implementation date. Please correct the data of the mail.dat job and resubmit the job.	The Container Ship Date (positions 101-108) of the .csm file is not a valid ship date.	
User Error [5038]: Pending Periodical or Periodical Enclosure rates are not supported at this time. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5039]: Pending Periodicals are not supported at this time. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5040]: Invalid MPA ID for Periodical Container Charge Method in SEG record. Please correct the data of the mail.dat job and resubmit the job.	Multiple segments cannot use the same MPA ID.	
User Error [5041]: Missing MPA ID for Periodical Container Charge Method in SEG record. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5042]: MPA ID for Periodical Container Charge Method 2 in SEG record needs to have a USPS publication number. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5043]: For Rate Category 'FB', package level must be 'A'. Please correct the data of the mail.dat job and resubmit the job.	If .pqt Rate Category is “FB”, Package Level in position 33 of the .pqt must be set to “A”.	
User Error [5044]: Mail.dat Periodicals ready-to-pay for non-incidental enclosures is not supported at this time.” Please correct the data of the mail.dat job and resubmit the job.		
User Error [5054]: Invalid new value for the status of a deleted container. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5069]: Transportation update is allowed only for container with previous container status R, T or X. Please correct the data of the mail.dat job and resubmit the job.		
User Error [5070]:  All the job permit/publication # in MPA file must belong to the owner for owner job. Please correct the data of the mail.dat job and resubmit the job.	Only occurs for Owner users. Verify all permits claimed and Verification Facility ZIP + 4 are correct and visible using the Owner Manage Permits feature. Change the values or contact the Customer Care Center to associate the permit with the owner’s corporation.  	
User Error [5071]:  All the job permit/publication # in database must belong to the owner for owner job.	Only occurs for Owner users. Verify all permits claimed and Verification Facility ZIP + 4 are correct and visible using the Owner Manage Permits feature. Change the values or contact the Customer Care Center to associate the permit with the owner’s corporation.  	
Mail.dat Package
Words in brackets and italics, such as [number], indicate a value automatically added to the error message by the PostalOne! system. For example, the maximum size of a specific field might be inserted if that maximum was exceeded. 
Table E-3. Mail.dat Package Error Messages
Error Message	Notes	
A permit number is required for all classes of mail except periodical.		
Additional Postage permit info not found.		
Apportionment total= [total], but should be 0 total chargeable bundles for JOB_SEQ_NUM= [number]		
Apportionment total= [total], but should be 0 total chargeable containers for JOB_SEQ_NUM= [number]		
Automation coding date has passed 180 day limit => [value]	This is only a warning message and will not cause a job to fail.	
Both permit no and usps pub no are NULL.		
Bundles (excluding firm-bundles) must have copies=pieces.  Check the following CQT_DB_ID/PACKAGE_ID: [CQT ID/Package ID]		
Carrier route coding date has passed 90 day limit => [value]		
Carrier route sequencing date has passed 180 day limit => [value]		
Container/Bundle Deviation Exceeded for [number](Bundle Deviation value). The round-off error [percent] for the bundles is unacceptable.		
Container/Bundle Deviation Exceeded for [number](Bundle Deviation value). The round-off error [percent] for the total containers is unacceptable.		
Container level values E, F, and L are not allowed.		
Dim Weight calculation can not be used for non-parcel items. Invalid combination of MPU processing category and MPU Surcharge.		
Enclosures are not supported in Pending periodicals.		
Entry Point Discount Facility Type values Y and Z are not allowed.		
Error occurred in [file] with error message: no rate level exists for rate category [category].		
Error validating Mailer Owner Non-Profit eligibility.		
EXITING WWS Data Submission Package - [error message]		
FB Rate category is only allowed for Outside-County Periodicals.		
FB Rate category provided but no Outside-County Periodicals with firm-bundles found.		
Finance number is NULL		
Firm Bundles cannot have zero total pieces. Check the following CQT_DB_ID/PACKAGE_ID: [CQT ID/Package ID]		
Firm Bundles must have copies greater than pieces.  The following CQT_DB_ID/PACKAGE_ID combinations are in error: [CQT ID/Package ID]		
Firm Bundles must have package_level ''A''.  The following CQT_DB_ID/PACKAGE_ID combinations are in error: [CQT ID/Package ID]	If .pqt Rate Category is “FB”, Package Level in position 33 of the .pqt must be set to “A”.	
First Class letters can not exceed 3.5 oz.		
For firm bundles with nonincidental enclosures ready-to-pay is not supported at this time, check Container ID.		
FORM TYPE IS NOT VALID	This is only a warning message and will not cause a job to fail.	
Found Firm Bundle not less than one pound. Parcel rates for Pending Periodicals are not supported at this time.	A firm bundle is considered a single piece and restricted to the Standard Mail limit of one pound.	
Government permits do not qualify for Nonprofit rates.		
Incorrect component class is used for Pending periodical with  incidental mail. The only Component classes allowed are 1, 2, or 3 for incidental mail.		
In-County Periodicals with rate category FB are not supported at this time		
Invalid Additional Postage payment method		
Invalid advertisement percentage	This is only a warning message and will not cause a job to fail. The advertising percentage exceeds 100%. Check the CPT and MPU records to ensure advertising percentage is less than 100. Original file submissions may generate qualification reports, but Update submissions will fail to generate postage statements.	
Invalid class. Valid class inputs: 3, 5		
Invalid Container Level(s): [file - levels]		
Invalid Container Type(s): [file - types]		
Invalid destination zone		
Invalid Enclosure weight.		
Invalid Entry Level(s): [file - levels]		
Invalid input on job. Please validate the combination of input values for in/out county indicator and container type.		
Invalid input on job. Please validate the combination of input values for in/out county indicator and zone.		
Invalid input on job. Please validate the combination of input values for in/out county indicator, container level and package  level.		
Invalid input on job. Please validate the combination of input values for in/out county indicator, container type, container level and entry level.		
Invalid input on job. Please validate the combination of input values for in/out county indicator, container type, container level, package level and entry level.		
Invalid MPU Rate Type		
Invalid MPU weight	Weight does not meet minimums or exceeds maximums for the class of mail.	
Invalid MPU/CQT Rate Type		
Invalid or null finance number		
Invalid Package Level(s): [file - level]		
Invalid payment method		
Invalid PP account, periodical rate code not found.		
Invalid PP account, permit not found.		
Invalid process category		
Invalid Rate Categories: [file - categories]		
Invalid rate category		
Invalid rate category, foreign rates not supported for pending periodicals.	For Periodicals mailings, foreign rates are not applicable for mailing dates after 5/14/2007.	
Invalid Sub/Non-Sub/Requester Indicator		
Invalid Zone(s): [zones]		
Mail Owner is not authorized to claim non-profit rates for this mailing.		
Mail Owner permit number is required for validating Mailer Owner Non-Profit eligibility.		
Mail Owner permit type is required for validating Mailer Owner Non-Profit eligibility.		
Mail piece version info differs across segments for MPU [version id].		
Mail.dat for Pending Periodicals with enclosures is not yet supported.		
Mail.dat for Pending Periodicals with rate type Z for First Class Mail in component is not yet supported.		
Mail.dat is not yet supporting Pending Periodicals at parcel rates.		
MPU process category LT is not allowed for CQT rate categories AF,BF,JF,NF,KF,GF		
Multiple qualified MPA_UIDs found for JOB_SEQ_NUM= [job number] ,SEGMENT_ID= [ID] ,MPU_ID= [ID] ,CLASS= [class]		
No apportioned records in M_BUNDLE_DETAIL for JOB_SEQ_NUM= [job number]		
No apportioned records in M_CONTAINER_BUNDLE_DETAIL for JOB_SEQ_NUM= [job number]		
No BUNDLE records found in M_BUNDLE_DETAIL (Qual Report).		
No BUNDLE records found in M_BUNDLE_DETAIL.		
No container or bundle data found for periodical job.		
No CONTAINER records found in M_CONTAINER_BUNDLE_DETAIL (Qual Report).		
No CONTAINER records found in M_CONTAINER_BUNDLE_DETAIL.		
No data found - no mapping records found for non-incidental enclosures [CLASS=[class], RATE_CATG=[category], PROCESS_CAT=[category], WEIGHT=[weight], DEST_ENTRY=[destination entry]] - M_WWS_ENCLOSURE_RATES		
No data found in the is_mlocronepass_f		
No data found in the is_mlocronepass_original_f		
No data found in the is_mlocronepass_update_f		
No job sequence number found in M_JOB_INFO_SEQ_LOOKUP table (Qual Report).		
No job sequence number found in M_JOB_INFO_SEQ_LOOKUP table.		
No job_seq_num found for Postage Statement Seq No [number]		
No M_BUNDLE_DETAIL records for JOB_SEQ_NUM= [job number]		
No M_CONTAINER_BUNDLE_DETAIL records for JOB_SEQ_NUM= [job number]		
No mapping found for container_level for bundles [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],CONTAINER-LEVEL=[level],PACKAGE-LEVEL=[package level]] - M_RATES_CONTAINER_LEVEL_MAP		
No mapping found for container_level for sacks/trays/pallets [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],CONTAINER-TYPE=[type],CONTAINER-LEVEL=[level],ENTRY-LEVEL=[facility type]] - M_RATES_CONTAINER_LEVEL_MAP		
No mapping found for container_type [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],CONTAINER-TYPE=[type]] - M_RATES_CONTAINER_TYPE_MAP		
No mapping found for SEG process category [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],SEG-PROCESS-CAT=[category],MPU-SURCHARGE=[surcharge]] - M_RATES_PROCESS_CATEGORY_MAP		
No mapping records found for CPT process category [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],CPT-PROCESS-CAT=[category],MPU-SURCHARGE=[surcharge]] - M_RATES_PROCESS_CATEGORY_MAP		
No mapping records found for dest zone [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],ZONE=[zone]] - M_RATES_ENTRY_LEVEL_MAP		
No mapping records found for flats machinability [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],MPU-PROCESS-CAT=[category],FL-MACHINABLE=[machinability], RATE-CAT=[cqt category]] - M_RATES_MACHINABLE_MAP		
No mapping records found for MPU process category [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator],MPU-PROCESS-CAT=[category],MPU-SURCHARGE=[surcharge]] - M_RATES_PROCESS_CATEGORY_MAP		
No mapping records found for non-incidental enclosures [CLASS=[class], RATE_CATG=[category], PROCESS_CAT=[category], WEIGHT=[weight], DEST_ENTRY=[entry]] - M_WWS_ENCLOSURE_RATES		
No mapping records found for rate category [SEG-CLASS=[class],ICNTY-OCNTY=[in county indicator], RATE_CAT=[cqt category]] - M_RATES_RATE_CATEGORY_MAP		
No mapping records found for rate category [SEG-CLASS=[class],MPU-CLASS=[class],ICNTY-OCNTY=[indicator],RATE_CAT=[cqt category]] - M_RATES_RATE_CATEGORY_SPCL_MAP		
No qualified primary MPA_UID found for JOB_SEQ_NUM= [number],SEGMENT_ID= [ID],MPU_ID= [ID],CLASS= [class]		
NO_DATA_FOUND in M_WWS_ENCLOSURE_RATES when converting rate category and destination entry (CLASS: [class], RATE_CATG: [category], DEST_ENTRY: [entry], PROCESS_CAT: [category], WEIGHT: [weight] )		
Null finance number for Qualification Report Preparer.		
Null or Invalid File Number	This is only a warning message and will not cause a job to fail. Original file submissions may generate qualification reports, but Update submissions will fail to generate postage statements.	
Null permit no or permit type for Qualification Report Preparer		
Only Mail.dat version 07-1, 08-1, and 08-2 are currently supported.		
Only one Post Office of Mailing can exist in a single segment.		
Pending Periodical jobs must have a permit number.		
Pending periodical jobs must have a permit number.		
Pending periodical jobs must use the class value of ''5'' in the MPU and CPT files.		
Pending periodical must use the postage payment method value of ''T'' in the MPA file.		
Pending Periodicals with Nonprofit Status are not supported.		
Periodical jobs must have a USPS publication number.		
Periodical with non-incidental jobs must have a permit number.		
Periodicals for Mail.dat 07-1 are currently not supported.		
Periodicals non-incidental enclosures with rate category FB are not supported at this time		
Permit [number] is not associated with an active debit-pay CAPS account. A permit must be associated with an active debit-pay CAPS account to use the Ready-to-Accept container status. Please contact the Help Desk for further assistance.		
Permit holder or Publisher address is NULL for permit [permit number] [publication number].	The permit holder or publisher information in the Mail.dat file does not match the information on file. If all permit data in the Mail.dat file is correct, see USPS acceptance personnel about updating the permit information in the database.	
PERMIT TYPE IS NULL	This is only a warning message and will not cause a job to fail. Original file submissions may generate qualification reports, but Update submissions will fail to generate postage statements.	
Piece count in PQT must be more than zero for Pending Periodicals with firm bundles.		
Piece count in PQT must be more than zero for Periodicals with firm bundles.		
Piece Counts in the Qualification Report and the Postage Statement Are Not Equal.		
Preparer information is NULL		
Presort First Class letters can not exceed 3.3 oz.		
Rate Category ''FB'' is not supported for Pending Periodicals.		
Rate Category FB not supported for Periodicals Non-Incidental Enclosures		
Rate level is not found the RATES.VIEW_WWS_RATE_MAP table.		
Requester publications with preferred rates (exception In-county) are not supported on Mail.dat submitted postage statements. Have BMEU or DMU enter this postage statement.		
The mail piece weight equals to or exceeds 16 ounces. Mail.dat is not yet supporting Pending Periodicals at parcel rates.		
The round-off error ([bundle deviation] * 100) || % for the bundles is unacceptable.		
The round-off error ([container deviation] * 100) % for the total containers is unacceptable.		
The sum of the piece count and copy count should match the firm bundle for pending periodicals.		
The sum of the piece count and copy count should match the firm bundle for periodicals.		
The total number of containers [[count]] must be less than the total number of mailing pieces [[piece count]].		
The updated piece count exceeds total in initial file.		
There is more than one original entry office associated with permit [number]. Please contact one of the original entry offices associated with your permit and request to have the permit record changed from an original entry office to an additional entry o		
There is not a valid CPP indicator associated with permit [number]. Please contact the original entry office for your permit and request that the CPP Indicator on your permit record be changed to allow consolidated payment.		
There is not an original entry office associated with permit [number]. Please contact one of the additional offices associated with your permit and request that the status be changed from an additional entry office to an original entry office on your perm		
Too many CAPS reference numbers (limit 30).	Too many CAPS Reference IDs were included in the mailing. 	
Too many mapping records found for dest zone [SEG-CLASS=[class],ICNTY-OCNTY=[indicator],ZONE=[cqt destination zone]] - M_RATES_ENTRY_LEVEL_MAP		
Too many mapping records found for flats machinability [SEG-CLASS=[class],ICNTY-OCNTY=[indicator],MPU-PROCESS-CAT=[category],FL-MACHINABLE=[machinability],RATE-CAT=[cqt category]] - M_RATES_MACHINABLE_MAP		
Too many mapping records found for rate category [SEG-CLASS=[class],ICNTY-OCNTY=[indicator],RATE_CAT=[cqt category]] - M_RATES_RATE_CATEGORY_MAP		
Too many mapping records found for rate category [SEG-CLASS=[class],MPU-CLASS=[class],ICNTY-OCNTY=[indicator],RATE_CAT=[cqt category]] - M_RATES_RATE_CATEGORY_SPCL_MAP		
Total piece count must be more than zero for pending periodicals with firm bundles.		
Total piece count must be more than zero for periodicals with firm bundles.		
Value [value] in Segment record for Class is not yet supported. The segment [ID] is rejected.	In the SEG record, Class Defining Preparation (position 73) is set to an unsupported value.	
Zero piece count not allowed for pending periodicals with firm bundles.		
Zero piece count not allowed for periodicals with firm bundles.		

Wizard Web Service
Words in brackets and italics, such as [number], indicate a value automatically added to the error message by the PostalOne! system. For example, the maximum size of a specific field might be inserted if that maximum was exceeded. 
Table E-4. Wizard Web Service Error Messages
Error Message	Notes	
A null line item is not valid#		
A null line item summary entry is not valid.		
A Volume Number was provided, but an Issue Number was not found. If you provide a Volume Number, then you must also provide an Issue Number.		
Actual pieces can't be zero or less		
Actual Qualification Report should contain valid Combined Mailing ID [combined mailing ID]		
Actual Qualification Report should contain valid qualification Report ID [qualification report ID]		
Actual Rate Category is required for MLOCR One Pass Finalization line items.		
Advertising percentage must be a positive number.		
Advertising percentage must be between 0% and 100%.		
Advertising percentage must not be more precise than 2 decimal places.		
Affixed Metered Method is not correct		
Affixed Postage Statement came without Permit Info for adjustments.		
Affixed rate value [rate] is not a published rate.		
Affixed rate value [rate] is not a one-ounce published rate.		
All versions must be requester/nonrequester or all versions must be subscriber/nonsubscriber		
All versions must have the same  customer group id		
All versions must have the same  mailing agent permit.		
All versions must have the same  mailing group id.		
All versions must have the same  post office of mailing zip		
All versions must have the same  postage payment method		
All versions must have the same Agency Code		
All versions must have the same Agency Cost Code		
All versions must have the same CAPS id		
All versions must have the same job ID		
All versions must have the same mailing owner permit		
All versions must have the same over 10		
All versions must have the same processing category		
All versions must have the same publication title		
All versions must have the same publisher permit		
All versions must have the same rate type		
barcode contains illegal meta-characters.		
barcode must be 20 characters.		
Barcode Rate is required for each line item.		
[Entry discount value] is an invalid Entry Discount.		
CMM ( CUSTOM_MARKETMAIL ) does not support special services.	The mailing claims both customized mailing rates and special services. Remove one.	
CMM does not support special services.	The mailing claims both customized mailing rates and special services. Remove one. 	
Combined Id is not positive number		
comments contains illegal meta-characters.		
comments must be 200 or less characters.		
Conflicting summary lines for line number [number]		
Congressional cost code [cost code] not found.  Congressional postage statements must use a valid cost code.		
Congressional OMAS Account is not correct : [account]		
contactAtMDSA contains illegal meta-characters.		
contactAtMDSA is required.		
contactAtMDSA must be 60 or less characters.		
contactName contains illegal meta-characters.		
contactName is required.		
contactName must be 60 or less characters.		
contactPhone must be 3 digit or characters.		
contactPhoneAtMDSA must be 3 digit or characters.		
Container Type is required.		
containerDisplayName contains illegal meta-characters.		
containerDisplayName is required.		
containerDisplayName must be 50 or less characters.		
containerSubType contains illegal meta-characters.		
containerSubType is required.		
containerSubType must be 1 character.		
containerType must be 1 character.		
contype is an invalid Container Type.		
Copies in the line item must not be less than 0.		
Could not validate service code		
Cumulative Postage is improperly set on one or more container detail items.  It must be equal to the running total of postage.		
Cumulative Postage should be a number greater than 0, when submitting a batch manifest.		
Cumulative Postage should be blank or 0 when not submitting a batch manifest.		
Customer Container ID is required.		
Customer Group ID contains illegal meta characters		
Customer Group ID is invalid for the specified Mailing Group		
Customer qualification report ID must have length <= 66		
customerContainerID is required.		
customerContainerID must be 50 or less characters.		
DAL pieces must not exceed total pieces for the mailing		
DAL Pieces should be zero or more than zero		
Destination ZIP code is required.		
Destination ZIP code must be 3, 5 or 6 characters.		
Detail Line Item with balloon surcharge cannot have  piece-weight over 20 lbs		
Discount quantity must be a positive number.		
Discount quantity should be number of pieces (Integer) for discount type [type].		
dropShipmentAppointmentNo contains illegal meta-characters.		
dropShipmentAppointmentNo is required.		
dropShipmentAppointmentNo must be 12 or less characters.		
Duplicate statements specified. ID= [IDs]		
Duplicate Version Id		
[Value] is an invalid Enclosing Class.		
Entry Discount is required for each line item.		
Entry Discount Type is required.		
Entry Facility Type must be ORIGIN when Register of Mailing is not submitted.		
Entry Facility Type value of [type] is an invalid value.		
Entry Point Facility Type is required.		
Entry Point ZIP code is required.		
Entry Point ZIP must be 3, 5 or 6 characters.		
Entry ZIP code is required for Register of Mailing.		
Entry ZIP code must be 3, 5 or 6 characters.		
Entry ZIP code must be empty when Register of Mailing is not submitted.		
Failed to get publication title for permit [type] (permit type) [number] (permit).		
Finance Number was not found.		
First Class's First Class Parcels and Flats less than 1oz need equal number of non machinable surcharge pieces.		
First Issue Date is for 3541-M only.		
First Issue Date is required for 3541-M.		
First userStatementSequenceNumber may not exceed length [length]		
First-class 1 oz Parcel or Flats must have equal number of nonmachinable surcharge pieces.		
For In-County, the number of pieces eligible for the Delivery Unit discount must be <= the number of copies going to the Delivery Unit.		
For In-County, the number of pieces with DDU discounts must be <= total number of addressed pieces.		
For In-County, the number of pound-rate copies must equal the number of piece-rate copies.		
For MLOCR First-Class mailing of flats, precancelled stamps are not allowed.		
For Outside-County, the number of piece-rate pieces must equal the number of piece-rate copies.		
For Outside-County, the number of pound-rate copies must equal the number of piece-rate copies.		
For permit rate code [value] Limited Circulation Discount cannot be claimed.		
For Postage Statement #[ID] Machinable Flats with rate category of L4, L6, L3, L5, H, or K are not allowed if copy-weight is over 1.25 pounds		
Form type is required.		
Found non cards line item in the cards container.		
getPhoneAreaCode contains illegal meta-characters.		
getPhoneAreaCodeAtMDSA contains illegal meta-characters.		
Heavy Letter should be set to false for each line item.		
Illegal Permit State		
In a qualification report submission for form type other than periodical, the in-out county indicator must OTHER not [value]. Please check the in-out county indicator and zone values.		
In a qualification report submission for form type periodical, the in-out county indicator must be one of IN_COUNTY or OUT_COUNTY or FOREIGN not [value].		
In a qualification report submission, the in-out county indicator must be populated.		
Inout county indicator is required for each line item.		
Invalid average piece weight for a line must be between 0.00001 and 15.0000		
Invalid average piece weight for a line with weight break of ([value]). it must be between 0.2063 and 0.9999	Average piece weight is above the maximum. 	
Invalid average piece weight for a line with weight break of ([value]). it must be between 0.00001 and 0.2063	Average piece weight is below the minimum. 	
Invalid average piece weight for a line with weight break of ([value]). it must be between 0.2063 and 0.2188	Average piece weight is not in heavy letter weight range.	
Invalid Bundle Level ([value])		
Invalid bundle line item, you must specify container level.		
Invalid bundle or container line item, it only has container level ( [value])		
Invalid Carrier-Route Number crn Check the first character to make sure it is valid.		
Invalid Carrier-Route Number crn The last number except first one should be  digits must be numbers		
Invalid combined mailing id [ID] for mailing group [ID].		
Invalid Container Charge Entry Facility Type ([type])		
Invalid Container Level  ([type])		
Invalid container line item, it has invalid container type ([type]), container level ([level]) and entry level ([entry level]) combination.		
Invalid Container Type ([value])		
Invalid Container Type.		
Invalid Data Exception with message		
Invalid discount type ([value]) for In-County.		
Invalid discount type ([value]) for Outside-County		
Invalid Entry Discount Type		
Invalid Entry Point Facility Type: [type]		
Invalid Form type		
Invalid form type for Certified Mail		
Invalid form type for COD		
Invalid form type for PAL		
Invalid form type for Registered Mail		
Invalid form type for Restricted Delivery		
Invalid form type for Return Receipt		
Invalid form type for Return Receipt electronic		
Invalid form type for Return Receipt Merchandise		
Invalid form type for Signature Confirmation		
Invalid form type for Special Handling		
Invalid Form Type.		
Invalid In/Out County Indicator ([value]).In-County rates are not allowed for government publications.		
Invalid Limited Circulation Discount Claimed indicator value [value], must be one of: I, N, or Y		
Invalid line item, if the publisher permit type is PI then the only valid line types are bundle or container line.		
Invalid Mailing Group cannot be submitted.		
Invalid Mailing Group ID		
Invalid Origin.		
Invalid PaperElectronicInd.		
Invalid payment method for Delivery Confirmation		
Invalid payment method for Signature Confirmation		
Invalid Pending Periodical Statement Type		
Invalid Periodical Statement Type ([type])		
Invalid periodical statements cannot be submitted.		
Invalid Permit data.		
Invalid permit number or type for the [role] (role type )		
Invalid Permit Type.		
Invalid PlantVerifiedDropShipment cannot be submitted.		
Invalid Postage Payment Method [value].		
Invalid postage statements cannot be submitted.		
Invalid precancelled stamp value [value].		
Invalid processing category for form type and service of Signature Confirmation		
Invalid Processing Category [value]		
Invalid Processing Category.		
Invalid qualification reports - Stored procedure can't be called.		
Invalid qualification reports cannot be submitted.		
Invalid Rate Category ([value])		
Invalid Rate Level Indicator.		
Invalid Rate Type [value].		
Invalid Recipient Typ [value]		
Invalid service code		
Invalid service code ([value]) provided for special services		
Invalid service sub code for service code ssc		
Invalid special service summary information		
Invalid special service summary information		
Invalid Surcharge/Discount Type		
Invalid Surcharge/Discount Type ([value])		
Invalid Zone ([zone] ).		
Invalid Zone ([zone]) for In-County		
Issue Date is for 3541 only.		
Issue Date is required for 3541.		
Last Issue Date is for 3541-M only.		
Last Issue Date is required for 3541-M.		
Last userStatementSequenceNumber may not exceed length [maximum size]		
[value] is an invalid Entry Discount.		
[value] is an invalid Entry Facility Type.		
Limited Circulation Discount cannot be claimed because the number of outside county copies ([value])exceeds the circulation limit of lcd		
Limited Circulation Discount Claimed indicator is not set, must be one of: I, N, or Y		
Line item (index: [value]) is a duplicate.		
Line item copies must not be less than pieces.		
Line item single piece weight is required for Register of Mailing.		
Line item total piece postage of [total] is greater than the maximum of [value]		
Line item total piece postage of [total]is less than the minimum of [value]		
Line item total pound  postage of pamt is less than the minimum of [value]		
Line item total pound postage of pamt is greater than the maximum of [value]		
Line Item with balloon surcharge cannot have average piece-weight over 20 lbs		
[value] is an invalid Actual Rate Category.		
[value] is an invalid Weight Break Type.		
Mailing cannot be accepted for the Permit supplied - please contact PostalOne!		
Mailing Date is required.		
Mailing Group [ID] is not One Pass Mailing Group.		
Mailing Group is closed		
Mailing section could not be validated due to incomplete form.		
MailingInfo is required to validate Mailing Group.		
Metered Affixed Method should be null		
Metered Affixed Method should be null for pre-canceled stamp.		
MLOCR must be tray based preparation only		
MLOCR One Pass Indicator cannot be  checked  when presentation category is not MLOCR		
MLOCR standard mail letter maximum weight is 3.5 oz		
name contains illegal meta-characters.		
name is required.		
name must be 60 or less characters.		
NON USPS OMAS  Agency Cost Code length is not correct		
Nonmachinable surcharge line item's piece count is not correct.		
Non-requester copies do NOT apply to recipient type Requester .		
Non-subscriber copies do NOT apply to recipient type Subscriber.		
Non-subscriber/Non-requester copies in the line item must not be less than 0.		
OMAS Agency Cost Code is not interger:::: [value]		
OMAS Agency Cost Code is not positive interger ::: [value]		
OMAS Agency Cost Code length is not six		
One of more DMM sections are larger than 12 characters.		
One of more DMM sections contain illegal meta-characters.		
one Pass Flag [value] contains illegal meta characters OR does not contain valid values.		
One Statement can't be first and last statement of combined Mailing. Combined Mailing must have at least two  statements		
Only one of Rate Category,Discount Type or Zone should be filled out.		
Origin is required.		
originPlantLocation contains illegal meta-characters.		
originPlantLocation is required.		
originPlantLocation must be 80 or less characters.		
PaperElectronicInd is required.		
Parcel Surcharge is only applicable to rate categories 3-Digit and ADC		
[value] Is an invalid Processing Category.		
Pending Periodical Postage is required.		
Pending Periodical Statement Type is required.		
Periodical statement ([value]), was not found in group([ID])		
Periodical Statement Type is required.		
Periodical versions can't come with null version id.		
Periodicals can't have more than one version per statement.		
Permit holder's permit type [type] is invalid for form type [number].		
Permit Number is provided with version [value] but Permit Type is not provided		
Permit Number is required		
Permit Number/Type is invalid for Mailing Group		
Permit Number/Type/Zip is invalid for Mailing Group		
Permit type for permit holder must be set.		
Permit Type is provided with version [value]  but Permit Number is not provided		
Permit Type is required.		
Permit was not found.		
phoneAreaCode is required.		
phoneAreaCodeAtMDSA is required.		
PhoneLast4 contains illegal meta-characters.		
phoneLast4 is required.		
phoneLast4 must be 4 digit or characters.		
phoneLast4AtMDSA contains illegal meta-characters.		
phoneLast4AtMDSA is required.		
phoneLast4AtMDSA must be 4 digit or characters.		
phonePrefix contains illegal meta-characters.		
phonePrefix must be 3 digit or characters.		
phonePrefixAtMDSA contains illegal meta-characters.		
phonePrefixAtMDSA must be 3 digit or characters.		
phonePrefixis required.		
phonePrefixisAtMDSA required.		
Piece Postage must be greater than zero.		
Piece Postage must be set to zero.		
Piece Rate must be set to zero.		
Pieces in the line item must not be less than 0		
Please check Combined Mailing Total Statements. Total Statement should be more than 0		
Please check CombinedId. Combined Id is already exist. Can't used again for new combined mailing		
Please check CombinedId. Combined Id is not correct.		
Post Office of Mailing ZIP code is required.		
Post Office of Mailing ZIP code must be a 5 digit number.		
Post Office of Mailing ZIP code must be numeric.		
Post Office of Mailing ZIP code [value] must be a 5 digit number.		
Post Office of Mailing ZIP code [value] must be numeric.		
Post Office Of Mailing Zip is required.		
Post Office Of Mailing Zip must not contain non-numeric characters.		
Postage affixed amount for the mailing is required when payment method is postage affixed.		
Postage affixed amount for the mailing must be 0 when payment method is permit imprint.		
Postage affixed amount for the mailing must not be less than 0		
Postage Amount must be set to zero.		
Postage cannot be calculated for invalid postage statements.		
Postage Payment Method is required.		
Postage should be a number greater than 0, when submitting a batch manifest.		
Postage should be blank or 0 when not submitting a batch manifest.		
Postage statement ([ID]), was not found in group ([ID]).		
Postage statement claims nonprofit rates, but system was unable to find record of nonprofit authorization or application for mail owner permit for permittype and permitNumber.		
Postage Statement is required to validate Mailing Group.		
postageStatementSeqNo = [value] and customerGroupID = [value] combination does not exist.		
postageStatementSeqNo [value] cannot be used twice in one container.		
Pound Postage must be greater than or equal to zero.		
Pound Postage must be set to zero.		
Pound Rate must be set to zero.		
[value] is an invalid Packaging Basis.		
Preparation Date is required.		
Preparer is required to validate Mailing Group.		
Preparer permit number is required.		
Preparer permit type contains illegal meta characters		
Processing Category is required.		
Publisher must be specified		
Qualifiaction Reports can't be submitted without containers		
Qualification Report is required to validate Mailing Group.		
qualification reports with Invalid QualReportid - Stored procedure can't be called.		
Rate Category is required for each line item.		
Rate Level is required.		
Rate Type is required.		
[value] is an invalid Rate Category.		
Recipient Type is required.		
Register of Mailing can only be included with an extended form.		
Repositionable Notes are not allowed with Irregular Parcels.		
Requester/Non-requester copies shouldn't be all 0 for recipient type Requester/Nonrequester.		
Required data for postage rate calculation was missing.		
Restricted Delivery Pieces can't be more than the total pieces of Insured, certified and registered  collect on delivery pieces.		
Return Receipt Electronics Pieces can't be more than the total pieces of Insured, certified, registered and collect on delivery pieces.		
Return Receipt Pieces can't be more than the total pieces of Insured, certified, registered and collect on delivery pieces.		
Ride Along Weight is for 3541 only.		
[value] is an invalid Rate Type.		
Single copy weight must be a positive number.		
Single copy weight must be between  0 and 6 pounds.		
Single copy weight must not be more precise than 4 decimal places.		
Single piece Dimensional weight must be a positive number.		
Single piece weight Dimensional must not be more precise then 4  decimal places.		
Single piece weight for  [process category] [rate category] line items must be between  0  and  .2063  pounds.		
Single piece weight for [process category] [rate category] line items must be between 0 and .8125 pounds.		
Single piece weight for [process category] [rate category] line items must be between 0 and .2188 pounds.		
Single Piece weight for the line item is not same as it's specified version's weight.		
Single piece weight must be a positive number.		
Single piece weight must be between [minimum] and [maximum] pounds.		
Single piece weight must not be more precise then 4 decimal places.		
Single ride along weight must be a positive number.		
Single ride along weight must be between 0 and 0.2063 pound.		
Single ride along weight must be less than or equal to copy weight.		
Single ride along weight must not be more precise than 4 decimal places.		
Single sheet weight must be between 0 and .9999 pounds.		
Single sheet weight must not be more precise than 4 decimal places.		
Sortation Level is required.		
Special service amount, for service  service is greater than the calculated max of [total]		
Special service amount, for service service is less than the calculated minimum of: [total]		
Special Service summary ([value]) is a duplicate.		
Special service total amount must be greater than zero.		
Special service total amount must be set to zero.		
Special service total pieces must be a positive number.		
Special service value must be zero or a positive number.		
Special service value must not be more precise then 4 decimal places.		
[value] is an invalid Sacking Basis.		
Statement cannot be submitted with Total Affixed Postage and Affixed Piece Rate.		
Statements marked for consolidation must not contain bundle or container charges.		
Statements marked for consolidation must not contain bundle or container charges.		
status contains illegal meta-characters.		
status is required.		
status must be 10 or less characters.		
Subscriber/Non-subscriber copies shouldn't be all 0 for recipient type Subscriber/Nonsubscriber.		
Subscriber/Request copies in the line item must not be less than 0.		
Subscriber/Requester copies do NOT apply to recipient type Nonsubscriber/Nonrequester.		
Summary Line item total piece postage of [value] is greater than the maximum of [maximum]		
Summary Line item total piece postage of [value] is less than the minimum of [minimum]		
Summary Line item total pound  postage of [value] is less than the minimum of [minimum]		
Summary Line item total pound postage of [value] is greater than the maximum of [maximum]		
Summary Line with balloon surcharge cannot have  piece-weight over [maximum]		
Summary Line with balloon surcharge cannot have  piece-weight over 20 lbs		
[value] is an invalid Surcharge		
[value] is an invalid Zone.		
Surcharge is required for each line item.		
The name must be [maximum] characters or less.		
The [role] (role type)  name is required.	A permit is missing a name.	
The [role] (role type)  phone number is required.	A permit is missing a phone number. 	
The agency code contains illegal meta-characters.		
The agency code must be 3 characters or less.		
The agency cost code must be  5 characters or less.		
The application fee for permit PermitHolder' permit type [type] PermitHolder [number] in finance number [value] has not been paid.This permit may not be used to pay for a mailing until the application fee is paid."		
The application fee for permit [value] in finance number [value] has not been paid. This permit may not be used to pay for a mailing until the application fee is paid.		
The CAPS ID contains illegal meta-characters.		
The CAPS ID must be  40 characters or less.		
The Carrier-Route Number contains illegal meta-characters.		
The Carrier-Route Number must be 4 characters in length.		
The Certification section is required.		
The Container Barcode contains illegal meta-characters.		
The Container Barcode must be 50 or less characters.		
The container display name (s) contains illegal meta-characters.		
The Container Display Name contains illegal meta-characters.		
The Container section is required!		
The Customer Container ID ([ID]) contains illegal meta-characters.		
The Customer Container ID contains illegal meta-characters.		
The Customer Container ID must be 50 or less characters.		
The Customer Container ID must be unique for each container.		
The Customer Description must be [maximum] or less characters		
The Customer Group ID is required.		
The Customer Group ID must be [maximum] or less characters.		
The Document versions section should not be included.		
The edition code [value] contains illegal meta-characters.		
The edition code [value] must be 60 characters or less.		
The issue frequency value contains illegal meta-characters.		
The issue frequency value must be 8 characters or less.		
The Job ID contains illegal meta-characters.		
The Job ID [value] contains illegal meta-characters.		
The Job ID [value] must be 8 characters or less.		
The Job ID must be 8 characters or less.		
The last 4 digits of the signer phone number are invalid. It must be a 4 digit number.		
The Line item section is required.		
The Line item section should not be included.		
The Line item summary section is required.		
The Line item summary section should not be included.		
The Mail End Seq No contains illegal meta characters.		
The Mail End Seq No is required when submitting a batch manifest.		
The Mail End Seq No must be 50 or less characters.		
The Mail End Seq No should be blank when not submitting a batch manifest.		
The Mail Start Seq No contains illegal meta characters.		
The Mail Start Seq No is required when submitting a batch manifest		
The Mail Start Seq No must be 50 or less characters.		
The Mail Start Seq No should be blank when not submitting a batch manifest.		
The mailer role is invalid.		
The mailer role is required.		
The Mailing Information section is required.		
The MailingAgent/Preparer section is required.		
The number of 1mm tray containers specified cannot be negative.		
The number of 2emm tray containers specified cannot be negative.		
The number of 2mm tray containers specified cannot be negative.		
The number of flat containers specified cannot be negative.		
The number of issues this month is for 3541-M only.		
The number of other containers specified cannot be negative.		
The number of pallet containers specified cannot be negative.		
The number of sack containers specified cannot be negative.		
The Parent Container ID contains illegal meta-characters.		
The Parent Container ID must be 50 or less characters.		
The Permit Holder section is required.		
The permit number/type/zipcode specified for the [value] (role type) needs technical assistance, please contact PostalOne!		
The Post Office Of Mailing Zip must be 5 characters.		
The Prepared as Standard Mail indicator should be set to false.		
The Prepared as Standard Mail indicator should be set to true.		
The Presort SW Company contains illegal meta-characters.		
The Presort SW Company must be 50 or less characters		
The Presort SW Product contains illegal meta-characters.		
The Presort SW Product must be 50 or less characters.		
The Presort SW Version contains illegal meta-characters.		
The Presort SW Version must be 10 or less characters.		
The publication title [title]  must be 60 characters or less.		
The publication title [title] contains illegal meta-characters.		
The Publisher section is required.		
The [value] (role type )  permit type is required.		
The [value] (role type ) permit number is required		
The [value] (role type ) permit type is invalid.		
The [value] (role type ) permit number and type is not an active permit for the zip code specified.		
The Sibling Container ID must be 6 characters or less.		
The signer name contains illegal meta-characters.		
The signer name must be [maximum size] characters or less		
The signer phone number area code is invalid. It must be a 3 digit number.		
The signer phone number area code is invalid. It must be numeric.		
The signer phone number is required in the Certification section.		
The single piece dimensional weight for the line item is required …		
The single piece weight for the line item is not the same as the single piece weight specified for the postage statement		
The single piece weight for the line item is required…		
The Special Service detail section should not be included.		
The Special Service summary section should not be included.		
The statement sequence number [value] contains illegal meta-characters.		
The statement sequence number [value] must be  20 characters or less.		
The total pieces for a special service should not exceed total pieces for the postage statement.		
The Version ID must be 10 characters or less.		
There must be at least one container specified.		
This Flat Rate Indicator is not supported for this processing of this form type:: [value]		
To submit a First-Class statement with cards and letters, the processing category of each line must be either card or letter.		
Total Copies should be positive number.		
Total Pieces in the line item are required.		
Total pieces of total copies should be positive number		
Total Pieces should be a number greater than 0.		
Total Weight for the line item must equal the single piece weight * total pieces.		
Total Weight in the line item is required.		
Total Weight in the line item must not be less than 0.		
Total Weight must not be more precise then 4 decimal places.		
Unknown postage affixed payment method.		
User does not have right to view this Postage Statements. If you think this is incorrect please contact PostalOne!.		
User does not have rights to view this Periodical Statements. If you think this is incorrect please contact PostalOne!.		
Version [ID] has form type [number] Form type must be  PERIODICAL		
version id for Container line [value] is null.		
Version Id for the line item is not found in the versions specified for the postage statement.		
version id for Version line [value] has null version id		
Version is required for line [value] for versioned statement.		
Version [value] has invalid pending periodical statement type		
Version [value] has no entry facility type. Entry facility type is required.		
Version [value] has no entry zip. Entry zip is required.		
Version [value] has no pending periodical statement type		
Version [value] has stage [value]. Stage must be [value].		
Version [value] has statement type [value]. Consolidated statements may not include other consolidated statements.		
Version [value] is already consolidated under statement [ID].		
Version [value] is in group [ID]. Target group number is [ID].		
Version [version] has PeriodicalMailingInfo=NULL!		
Version [version] is NULL!		
Versions are not used for line items.		
Versions must have at least weights or affixed postage.		
Versions were declared for the Qualification Report but not used in the containers.		
Weight Break Type is required for each line item.		
Weight for Version line [value] has zero Weight.		
Weight of One Sheet is for 3541-M only.		
Weight of One Sheet is required for 3541-M.		
You do not have access to a permit to open a mailing group.  If you feel this is incorrect, please contact PostalOne! with details.		
You must specify at least 2 versions to consolidate.		
You must specify one of Rate Category, Discount Type or Zone.		
Zone is required for each line item.		
Zone is required.		

Index

A
Actual Tray file	70
ASCII	35, 38
B
batch processor	3, 17
error logs	78
memory	42
prerequisites	31
scheduling	42
testing setup	42
UNIX	35
updating	42
Windows	33
Bound Printed Matter (BPM) issues	9
Business Mail Entry (USPS)	2
business mailer	2
C
canceling jobs	See deleting jobs
certificate signing request	39
change job transaction	16
client.config memory	42
collaboration opportunities	5
Component file	54
Component ID file	44
configuring Mail.dat files, overview	6
Container Quantity file	45, 62
Container Summary file	45, 56
containers
levels	60
status	15
types	59
Customer Care Center	1, 5, 42
D
deleting jobs	16
delimiter
in receipt file	73
parameter	76
digital certificate
adding to keystore	40
obtaining	40
testing	41
DMM 707	9
duplicate field resolution	9
E
edit
batch memory	42
manual memory	30
electronic collaboration	1
encryption	41
entry point facility	60
errors
common file formatting	12
errors, cont. 
data	79
database	78
Mail.dat client	79
Mail.dat package	95
processing order	78
resolution	78
transfer	42
upload server	86
validation	28
viewing	78
WWS	101
F
fields
conventions	47
duplicate Periodicals	9
key	6
key consolidation	7
MLOCR validation	23
validation	47
file transfer	See also, Mail.dat file
applet	See manual file transfer
memory	30, 42
overview	17
processing order	78
file validator	18
files
definitions	44
processing order	78
relationships	24
status	14
firewall	5, 12, 33
flats machinability	52
H
hardware, required	4
Header file	44, 47
help desk	See Customer Care Center
I
IDEAlliance	2, 5
IDEAlliance collaborative Web site	5
IJ/C Relationship file	66
Information Access Key file	71
Ink Jet/Container Relationship file	45
International Container Label file	45, 61
Internet connection	2
issue date, suggested	55
J
Java
1.4.2 memory	30
1.5 memory	31
1.6 memory	31
installed version	30
Java, cont. 
upload server	17, 73
version	32
job
change transaction	16
deleting	16
updating	13
Job Status page	29
JRE	32
JVM	4, 30
K
key fields
bundles	63
conflict resolution	9
consolidation	7
postage statements	6
keystore	38
M
Mail Piece Unit file	51
Mail.dat
client errors	79
package errors	95
Mail.dat file
configuring, overview	6
definitions	44
field validations	47
formatting errors	12
processing overview	16
required files	6
specification	3, 5
transferring
in batch	31
manually	28
update, sending	13
upload status	29
validating	18
validation	19
Mailer Postage Account file	44, 53
Mailpiece Unit file	44
Manifest Individual file	45, 67
Manifest Summary file	45, 68
manual file transfer	28
maximumHeapSize	42
memory
batch	42
manual	30
verify	30
Metrics Search	78
MLOCR	23
MPU/C Relationship file	44, 53
Multi-Line Optical Character Reader	23
P
Package Label file	45, 65
package levels	64
Package Quantity file	45, 63
parameters	See postal1.ini file
Periodicals
conflict resolution	9
consolidation key fields	7
rate calculations	9
Piece Detail file	45, 66
Piece Detail XML	71
Pmstage	5
port numbers	5, 33
Postage Adjustment file	45, 69
postage statements
key consolidation fields	7
key fields	6
postal1.ini file	73
parameters, UNIX	37
parameters, Windows	34
PostalOne! system
applying to	1
overview	1
prerequisites	3
problem resolution	12, 42
processing files	16
Provider Code	See ULC
R
RAM	30
receipt file
content	73
layout	73
record types	73
transfer status	75
record status	14
relationship constraint	24
replacing jobs	16
S
scheduling software	32
Seed Name file	45, 65
Segment file	44, 49
segment rejection	8
software, required	4
Special Fees and Charges file	45
Special Fees/Charges file	66
SSL	5, 17, 38
T
transfer applet	See manual file transfer
Transfer Summary	29
Transfer Summary Report	78
transferred job, checking	29
transferring methods, introduction	3
troubleshooting	12
U
ULC	5
UNIX	32
update
batch processor	42
update, cont. 
commands	16
rules	15
sending	13
upload server errors	86
upload status	29
V
validation
BPM	9
field	47
log file	28

validation, cont. 
MLOCR	23
overview	18
Periodicals	9
rules	19
validation log errors	78
W
Walk Sequence file	45, 64
Wizard Web Service errors	101
X
XML	35, 38, 71, 73