| Word | Description |
| raw archives | Mailing list email archives that live on the server's file system, as opposed to the web-viewable archives presented online as part of mailing lists and groups' email repositories. Raw archives can often be retrieved using ezmlm commands sent by email to the mailing list. See also: mailing list, MHonArc |
| regular subscriber | Regular subscribers receive every email sent to the list singly, as opposed to digest subscribers who receive email in batches. Users have the ability to select from these two options when managing their subscriptions. See also: digest subscriber |
| Reply-To | A field in an email header that provides the address to which replies to the message will go. It is similar to the return address on an envelope you'd send through the postal service. Like the return address, this field can be set by the sender and is not necessarily valid; if it isn't valid, email returned to the sender will be undeliverable. Mailing lists set the 'Reply-To' field to the address of an automated bounce handler so that when an email sent to a subscriber bounces, it won't be returned to the list and distributed to all the other list subscribers. See also: envelope header, mail transfer agent, Return-Path |
| Return-Path | A field in an email envelope header that stores the fully qualified domain name or IP address of the MUA from which the email originated and frequently includes the sender's username. Since Return-Path is added automatically by receiving mail hosts, it more reliably identifies the actual originating sender (the From and Reply-To fields can be set by the user). It also shows the path that the email took from host-to-host, including a timestamp for each transfer; this information is useful in troubleshooting email delivery issues. See also: envelope header, envelope sender, Reply-To, mail user agent |
| role | Underlying mechanism governing user access to Workspace and other applications. The default role for a user is 'authenticated', meaning the user has basic access permissions that allow the user to login and gain access to some tools. Other default and custom roles exist to grant users the ability to access the tools and information they need to participate in the organization. See also: role cache |
| role cache | All roles assigned to a user are stored in this cache, which cumulatively represents this user's level of site access. See also: role |
| rolling year | Rolling year memberships have a fixed duration of one year; the start date of the membership term is whatever date the membership became current, and the end date is one year from the start date. Membership terms in an organization with rolling year memberships can start on any date, as opposed to an organization with annual fixed term or fixed dates memberships, where all full-term memberships start and end on the same date each year. New rolling year memberships don't have to be pro-rated. Rolling year memberships lend themselves well to auto-renewal. See Also: auto-renewal, duration, term, membership term |