A Service Pack is the block of Registered E-Mail® units you'd like to purchase. We sell Service Packs in blocks of 100, 500, 1000, 2500 and 5000 units. If this is your first order of RPost® Registered E-mail®, you will get 2 Service Packs for the price of one. For example, if you purchase a Service Pack of 1000 units, you will get an additional 1000 units for free with your first order. The Service Pack is available for any user within the authorized domain.

One Registered E-mail® Unit is defined as one recipient address per megabyte e-mail size.

If this is your first order of the RPost® Registered E-mail® service, you will be issued a FREE matching block of e-mail units, in addition to your Service Pack, at the time of activation.

Once you purchase the service, your account needs to be activated by RPost®. Your Service Pack will be available to you within 24 hours of purchasing, if you purchase during regular business hours. RPost® will send you a confirmation e-mail once the Service Pack has been activated so you can start sending Registered E-mails.

Note: If you are ordering the RPost® service outside of regular business hours or on a weekend, your account will be activated the next business day.

Amicus Attorney has arranged 10 complimentary Registered E-mail® units for you, so that you can start using the service immediately while you are waiting for your service to be activated. However, if you have already downloaded and used your Free Trial of the Registered E-mail® service, you will have to wait until your Service Pack is activated by RPost® to send Registered E-mail® messages.

With Service Packs, all software license and activation charges are INCLUDED in the per-unit cost.

Yes. If you have different e-mail addresses at same firm you can still draw off the same Service Pack. Simply provide us with the e-mail addresses of firm members you would like to be able to use Registered E-mail®.

If everyone in your firm has the same domain name (all from "xyzlawfirm.com") - they can all draw from the same block simply by downloading the Send Registered Button.

To get the fastest response for technical questions related to the service, please send an e-mail to: amicusattorney@rpost.com

No. Most common installations of Registered E-mail® work by adding the light Send (R)egistered™ software add-in into your mail client (desktop e-mail program) that routes only e-mail that you want to be sent "Registered" through the RPost Registration Networks. The RPost System™ does not store e-mail. There are separate server side solutions that provide an organization or its individuals the ability to send Registered E-mail® based upon the preference of the sender's organization.

No. RPost does not store any e-mail or components of any e-mail. RPost encrypts, compresses and attaches to the Delivery Receipt all of the data needed to authenticate the Delivery Receipt, transmission information, and re-present an authenticated original.

Yes. Receivers of Registered E-mail® are able to view the message and attachments using any e-mail service including web based e-mail service such as AOL, MSN, Hotmail, Yahoo Mail and Lycos Mail. Registered E-mail® proves legal delivery to any Internet e-mail address. This is done with no uploads, downloads, links or passwords for the recipient. All a receiver needs is a valid e-mail address.

Yes. Registered E-mail® supports any and all attachments that your e-mail program normally allows and requires no extra steps to upload or download the attachment.

Yes. Typical limitations are the sender or receiver's mail server limits. RPost allows e-mail attachments as large as 10 MB unless the sender subscribes to a higher message megabyte plan.

There are subtle cosmetic and functional differences when using Outlook Editor versus Word Editor. These subtleties differ by version of Outlook 2000 or XP and do NOT impact core service functionality.

Yes. Registered E-mail® can be sent to many recipients in the To, Cc and Bcc field as your e-mail program normally allows. The sender will receive only one Delivery Receipt for all recipients that are associated with that e-mail message and each recipient's delivery status will have a row in the Delivery Status section. Note, RPost does limit the number of recipients in an e-mail to 100, to protect against abuse. For special volume mailing installations, contact RPost.

Yes. Registered E-mail® can be sent to any valid e-mail address, regardless of location of receiver.

Registered E-mail® permits a sender of e-mail to prove *what* was sent, *when* it was sent, *whether* it was delivered, and *when* it was delivered and *accepted*. The RPost System™ can do this without retaining a copy of the original e-mail -- all data necessary for such proof is in a receipt, returned to the sender or sender's organization, which is authentication-ready at any time. RPost can prove content by the special methods it uses to package the Registered Receipt™.

As soon as the RPost Registration Systems induct an e-mail message for processing, the sender receives an Acknowledgment returned to their inbox. The Acknowledgement has an official time seal, which provides proof of sending, until the Delivery Receipt arrives. It also serves to alert the sender that the e-mail has made it out of their internal mail system, and is on its way to the intended recipient. The Acknowledgement is similar to the receipt that the FedEx carrier gives after taking a package.

The Acknowledgements arrive in the sender's inbox as soon as the e-mail has been inducted into the RPost Registration System for processing. If the Acknowledgement does not arrive within several minutes of sending the Registered E-mail®, contact your IT director. In general, if you do not get an Acknowledgement, your Registered E-mail® has not reached the RPost Registration System and therefore will not be delivered. Note that in some installations, the sender can turn off the Acknowledgement receipt.

RPost allows the use of a company's client code accounting system to allocate costs of the Registered E-mail® to their clients or vendors. Insert the optional Client Code field in the dialog box that pops up after you press Send (R)egistered™ to have a specific tag associated with that Registered E-mail. The client code is transparent to the receiver of the Registered E-mail®. On your monthly report, you will see how many Registered E-mail messages you have sent with that specific code and can bill accordingly.

To be clear, RPost® Registered E-mail® service is **completely different** from various e-mail authentication systems that have been proposed by a number of e-mail providers in an effort to produce an Internet standard for e-mail "sender authentication". The goal with these sender authentication plans have been to increase trust in e-mail and reduce the threat of spoofing and phishing. DKIM is an example of a proposed solution. DKIM stores public keys in DNS and digitally signs e-mails on a domain basis. In general, these e-mail authentication systems provide value in allowing message recipients to view e-mail with a greater degree of trust and hold sending domains more accountable.

BY CONTRAST, the core value of the RPost® Registered E-mail® service is in protecting the sender by providing them LEGAL PROOF of the content, attachments, and time the sender's e-mail was legally sent and received by each recipient. The Registered E-mail® system provides the sender of an e-mail with legally valid evidence of the transmission for any Internet address. The RPost® system does not require the recipient to have any special software or take any compliant action to prove delivery. RPost® services provide the sender with a (R)egistered Receipt™ e-mail, a tamper-detectable e-mail receipt that contains all the information required to prove delivery and content; RPost® does not retain a copy of the message.

IN SUM, Registered E-mail® services provide a record of the e-mail delivery and the content for the sender. Sender authentication systems do not offer such protection to the sender. In fact, the two systems complement each other rather than compete.