Common Mail.dat File Errors

If you submit Mail.dat® files to PostalOne!®, you already know how frustrating it can be when you get error messages, indicating that there is a problem with the data in your Mail.dat files. Identifying just what those errors are, and then pinpointing where in the Mail.dat file those errors are located, and knowing how to fix the errors can be complicated. This week, we share some of the more common errors we see when assisting clients.

read more: http://www.windowbook.com/Learning/Postal-Concierge-E-tips

Correcting By/For Errors in eDoc

As more mailers are now starting to pay closer attention to their Mailer Scorecard on PostalOne!®, a common issue that shows up on their scorecards is By/For errors. So, you ask, what the heck is “By/For” and how do mailers get these errors to go away?

By/For
For Full-Service mailings, the United States Postal Service® (USPS®) requires that electronic documentation (eDoc) includes identification of the Mail Owner, the Mail Preparer, and the eDoc Submitter. This is often referred to as the “By/For” data: the Mail Preparer is the company who is preparing the mail (the “By” part) and the Mail Owner is the company responsible for the content of the mailpiece and receives the benefit of the mailing (the “For” part). Likewise, the eDoc Submitter is the company submitting the electronic documentation (“By”) for the Mail Owner (“For”). All of these entities are identified in the eDoc using their Mailer ID numbers (MIDs) or Customer Registration ID Numbers (CRIDs). For companies preparing and submitting their own mailings, all of these entities may be the same company. For companies that use Mail Service Providers, these three entities may be three different companies.

Where is the data?
The MID and CRID data used to identify the Mail Owner and Mail Preparer in the mailing is located in the Mailer Postage Account (MPA) file of the Mail.dat® file. The CRID data to identify the eDoc Submitter is located in the Header (HDR) file of the Mail.dat file. The eDoc Submitter data is also located in the Segment (SEG) file, but that is for mailing industry use; PostalOne! uses the data in the Header file.

Read more.

 

International and Domestic Market Dominant Federal Register Notices

Today the proposed International and Domestic Market Dominant Federal Register Notices for the January 2014 price change were posted on pe.usps.com under the Federal Register Notices tab of the left-hand side. The official 30 day comment period will start once the Federal Register Office reopens and posts these notices on the federalregister.gov web site. We look forward to feedback from the mailing industry.

Via USPS RIBBS

New Intelligent Mail Package Barcode (IMpb) Requirement Effective January 26, 2014

The Postal Service is revising Mailing Standards of the United States Postal Service, Domestic Mail Manual (DMM®) to require the use of Intelligent Mail® package barcodes (IMpb) on all commercial parcels, and to require the transmission of supporting electronic documentation including piece-level address or ZIP+4® Code information. Included in these new requirements is a per-piece price adjustment for mailpieces not complying with the IMpb standards.

The Postal Service is also adding DMM reference to a future requirement to use a complete destination delivery address or an 11-digit delivery point validated ZIP CodeTM in the mailer’s electronic documentation.

Read more:  Federal Register (Vol. 78, No. 243).

Visit USPS RIBBS website for information on Shipping Services File (SSP Version 1.6).

January 2014 Price Change and PostalOne! Release Webinars

Webinars will be held on January 8, 10 and 15th which will cover Price Changes and changes to the PostalOne! system that will be implemented January 26, 2014. Topics will include the new requirements for Intelligent Mail parcel barcodes, the new Metered price and Flat Sequencing System mail preparation.

Read more

Via USPS RIBBS

Promotions & Incentive Programs for First-Class™ & Standard Mail®

Registration for promotions and incentives can be made through http://gateway.usps.com. Once logged into the Business Customer Gateway, select “Incentive Programs”. From this link, programs open to registration will display. Each incentive or promotion requires separate registration.

Via USPS

Labeling List Changes for January 2014

The United States Postal Service® (USPS®) announced changes to the Labeling List data, effective January 1, 2014, with a mandatory use date of January 31, 2014. The Labeling Lists affected are L001, L002, L006, L007, L008, L012, L602, L605, and L606.  Read more.

New Mailing Standards for Domestic Mailing Services Products

December 18, 2013

New Mailing Standards for Domestic Mailing Services Products

Today the final rule New Mailing Standards for Domestic Mailing Services Products Federal Register Notice for the January 2014 price change was published. It is on the Federal Register site and on Postal Explorer® pe.usps.com under the Federal Register Notices link on the left-hand side.

This final rule contains revisions to the Domestic Mail Manual (DMM®) to accompany the price adjustments filed with the PRC on September 26, including new pricing eligibility for retail and commercial nonpresorted First-Class Mail® letters, several mail classification changes, and some condensing of current standards for Periodicals publications.

The effective date is January 26, 2014.

The Domestic Mail Manual (DMM®) and DMM Advisories are available on Postal Explorer® (pe.usps.com)

Via USPS DMM Advisory

Mail.XML vs Mail.Dat The Present and Future Tools By Monica Lundquist, Postal Affairs WindowBook

                           Mail.XML vs. Mail.dat

Most of us in the mailing industry have become accustomed to the word “mail.dat” and have a good understanding of what it is and the benefits of using it. For those of you still not familiar with the term mail.dat, it is a mailing industry standard specification (established and maintained by IDEAlliance) for a set of relational database files. These files are generated at the time that the mailing list is sorted through postal presort software, or when the mailpieces are sorted on Multi-Line Optical Character Reader (MLOCR) sorters. The set of files together represent just about all the specifics about a mailing with the exception of the mailing names and addresses. These files are used by the mailing industry and the United States Postal Service® (USPS) to share information and facilitate electronic transactions.

Just when we thought we had become pretty smart about mail.dat, along comes Mail.XML. Unless you are a real techie, mail.xml probably seems like a word from a foreign language. Actually, mail.xml is fairly simple, and it represents a really cool method to transmit mailing information. But what does it mean for the average mailer?

As background, Mail.XML is a newer mailing industry standard specification (again established and maintained by IDEAlliance) for informational transmissions. Mail.dat is quite robust and can contain huge amounts of information. This is very beneficial, except when you only need portions of the information that resides in mail.dat files. In these cases, it can be time consuming and a strain on transmission and storage resources to send entire Mail.dat files back and forth between the involved participants in the mailings.

To help understand the difference between Mail.dat and Mail.XML, think of it in terms of the Mail.dat file being the encyclopedia of a Mail.XML given mailing. Then think of Mail.XML being the telegram that you send to someone describing a portion of the encyclopedia. If your recipient only needs a small segment of information, it is much easier (for both of you!) to send them a short telegram than to send them an entire encyclopedia. That is essentially how Mail.XML works in relationship to mail.dat.

One of the ways that Mail.XML will be used is during transactions with the USPS. For example, if you use PostalOne! to transact business with the USPS, you will first upload a mail.dat file for the mailing as a “planned” mailing. Once all the final attributes of the mailing have been determined and all adjustments made to the Mail.dat file, you need transmit only Mail.XML “telegrams” to the USPS to update the mail.dat file that you previously uploaded. This eliminates the need to re-upload an entire mail.dat file every time a change is made or a new transaction required. This allows you to pay postage, make drop ship appointments, and a variety of other transactions using much smaller chunks of data.

Mail.dat is not going away anytime soon, and will certainly not be replaced by mail.xml. Mail.XML is just a very useful tool for use in transmitting smaller chunks of a mail.dat file. You’ll be hearing lots more about Mail.XML, particularly as the USPS proceeds with the integration of Intelligent Mail®.

Monica Lundquist, Postal Affairs, Window Book, Inc.

Mail.XML A Present and Future Tool

Mail.XML is a mailing industry standard specification for light-weight transactions between participants in the mailing process. The Mail.XML specification, as with the mail.dat specification, was established and is maintained by IDEAlliance.

Mail.dat is the powerful foundation for communicating data regarding mailings. It is a suite of relational database files which contain virtually every piece of data about a mailing except for the actual name and address records.

Mail.XML is a communications tool which allows for participants in the mailing process to communicate changes and updates to the Mail.dat file in a fast, efficient manner which is almost real-time. There are numerous transactions that occur during the course of the mailing process which do not require transmission of the entire Mail.dat database. Using Mail.XML for these lighter-weight transactions reduces manual data entry processes and makes these transactions quicker and more efficient.

Mail.dat stores complete information about a mailing as a database.  Prior to Mail.XML, the complete dataset was interchanged between the list house, printer/manufacturer, trucking company and USPS.


Mail.dat will not be replaced by Mail.XML.  Mail.XML provides an alternative to exchanging the entire Mail.dat database.  Mail.XML adds a new light-weight transaction messaging mechanism between mail owner, list house, manufacturer/printer, logistics company and the USPS.


The United States Postal Service® (USPS) continues to move toward a forms-based transaction protocol, to which Mail.XML lends itself beautifully. For example, transmitting postage statements to the USPS for postage payment is a forms-based transaction, for which Mail.XML may be used. Making drop ship appointments through the USPS FAST system is another example.

Mail.dat is not going away and will not be replaced with Mail.XML. Rather, Mail.XML is a powerful tool to make mailing transaction communications much quicker and easier. Window Book offers numerous world-class Mail.XML solutions for communications between mail owners, mail preparers, the USPS and other suppliers. Come join us and tap into the future today!