1.10.3  Standards for Using E-mail

Manual Transmittal

July 08, 2011

Purpose

(1) This transmits revised IRM 1.10.3, Standards for Using E-mail.

Background

This IRM provides guidelines for using e-mail in the most effective and productive manner. It includes guidance on formatting messages in a way that will be easily accessible for all employees, including those using the Enterprise Remote Access System (ERAP). It also includes information on security guidelines, creation and use of distribution lists, and contacts for assistance with e-mail issues.

Material Changes

(1) Text has been revised to clarify and update information including web site references.

Effect on Other Documents

IRM 1.10.3 dated June 1, 2007 is superseded.

Audience

All IRS employees

Effective Date

(07-08-2011)

Terry Lemons
Director
Office of Communications

1.10.3.1  (06-01-2007)
Introduction

  1. E-mail is now commonly used in business as an official form of communication, often replacing memorandums, meetings or phone conversations. This technology option is often the most efficient way to handle business communications and responsibilities. But its benefits can lead to burdens if we do not use this powerful tool judiciously. This section defines the standards for e-mail use in Internal Revenue Service communications.

1.10.3.2  (07-08-2011)
Security/Privacy

  1. E-mail messages are official documents and should reflect this perspective. E-mail communications can be offered as evidence in court and can be legally binding. Before sending an e-mail, you must consider how it reflects on the Service's image and take into account privacy, records management, and security factors.

  2. The privacy of e-mail cannot be assured and is easily compromised. Messages can be forwarded to unintended recipients (sometimes outside the agency or even outside the government). The public we serve, or the Congress, who may have occasion to see an e-mail message, do not differentiate between employees as individuals and our agency. We are the IRS.

  3. More information on the Service’s e-mail security policy is available at MITS Cybersecurity's web page, http://mits.web.irs.gov/Cybersecurity/Aware_Train/email_security.htm.

1.10.3.2.1  (07-08-2011)
Secure Messaging & Encryption

  1. The Internal Revenue Service processes Sensitive But Unclassified (SBU) information. The definition of SBU information is information which, if lost, misused, accessed or modified in an unauthorized way, could adversely affect the national interest, the conduct of Federal programs, or the privacy of individuals. Refer to IRM 10.8.1.3.1.1.1 for specifics about SBU information.

  2. Personally Identifiable Information (PII) is a specific type of sensitive information. PII includes the personal data of taxpayers, and also the personal information of employees, contractors, applicants and visitors to the IRS. Refer to IRM 10.8.1.3.1.1.3 for specifics about PII information.

  3. You should never consider e-mail secure. Do not include taxpayer, SBU, or PII information in e-mail messages or attachments unless you use encryption.

  4. Use the Secure Enterprise Messaging System (SEMS, or " Secure Messaging" ) for sending Microsoft Outlook messages that contain SBU data. Secure Messaging enables you to digitally encrypt e-mail messages and attachments for transmission among IRS e-mail users including Criminal Investigation, TIGTA, and Chief Counsel employees. In order for you to send a secure message through Outlook, both you and the recipient must have Secure Messaging installed. This allows authorized employees to transmit SBU information to other authorized employees within the system once they have been enrolled and received training.

  5. Secure Messaging enrollment is an automated process for all LAN accounts with an Exchange mailbox in IRS. You can find the instructions for configuring the Outlook client to use the certificates at the Secure Enterprise Messaging Systems (SEMS) web site: http://documentation.sems.enterprise.irs.gov/.

  6. Alternatively, you may encrypt files to be e-mailed as attachments using the latest software provided by MITS. Instructions are provided at http://findit-mits.web.irs.gov/.

  7. IRS employees may never send SBU data by electronic mail to taxpayers or their representatives unless they are using a technology and methodology that has been approved by the Security Services & Privacy Executive Steering Committee and the Senior Executive Team.

  8. IRS employees may send SBU data by electronic mail to authorized non-IRS parties (other than taxpayers or their representatives), but only if the SBU data is protected by an IRS-approved encryption method which meets FIPS-140 standards.

  9. More information on the Service’s security policy is available at http://mits.web.irs.gov/Cybersecurity/Policy_Compliance/default.htm.

1.10.3.2.2  (07-08-2011)
Suspicious E-mails/"Social Engineering"

  1. Individuals seeking to commit fraud or intending harm to the IRS or employees often engage in �social engineering,� wherein they use an alias and a seemingly innocuous cover story in order to gain the victim’s confidence and gather sensitive information. Such scammers may use e-mail, and try to trick you into revealing your password, or personal information.

1.10.3.2.3  (07-08-2011)
E-mails as Possible Federal Records

  1. All Federal employees and Federal contractors are required by law to preserve records containing adequate and proper documentation of the organization, functions, policies, decisions, procedures, and essential transactions of the agency. Records must be properly stored and preserved, available for retrieval and subject to appropriate approved disposition schedules.

  2. The Federal Records Act applies to e-mail records just as it does to records you create using other media. E-mails are records when they:

    • Are created or received in the transaction of agency business

    • Are appropriate for preservation as evidence of the government’s function and activities, or

    • Are valuable because of the information they contain

  3. If you create or receive e-mail messages during the course of your daily work, you are responsible for ensuring that you manage them properly. The Department’s current e-mail policy requires e-mails and attachments that meet the definition of a Federal record be added to the organization’s files by printing them (including the essential transmission data) and filing them with related paper records. If transmission and receipt data are not printed by the e-mail system, annotate the paper copy. More information on IRS records management requirements is available at http://erc.web.irs.gov/Displayanswers/Question.asp?FolderID=4&CategoryID=5 or see the Records Management Handbook, IRM 1.15.1 ( http://publish.no.irs.gov/IRM/P01/PDF/31421A03.PDF).

  4. An e-mail determined to be a Federal Record may eventually be considered as having historical value by the National Archivist prior to disposal. Therefore, ensure that all your communications are professional in tone.

  5. Please note that maintaining a copy of an e-mail or its attachments within the IRS e-mail MS Outlook application does not meet the requirements of maintaining an official record. Therefore, print and file e-mail and its attachments if they are either permanent records or if they are related to a specific case.

1.10.3.2.4  (07-08-2011)
E-mails are Subject to FOIA

  1. The public is aware of the role e-mails play in agency internal operations and e-mails are included in a growing number of Freedom of Information Act (FOIA) requests. E-mails that are responsive to a FOIA request must be released unless the information contained in the e-mail falls into one of nine very specific categories of exemption. (See IRM 11.3.13 for more on FOIA processing). There is no category of exemption to protect the author or the Service from embarrassment.

  2. E-mails provided in response to a FOIA must include the addressee, date and time. The address list, date and time are considered part of the record for both FOIA and Record Management purposes.

  3. Do not delete a message or attachment that is the subject of a Congressional, Freedom of Information Act (FOIA), or discovery request or that is needed for litigation.

1.10.3.2.5  (07-08-2011)
Inappropriate E-mails

  1. Sending chain letters, jokes or other non-business correspondence via your IRS e-mail may seem harmless. However, this unauthorized practice affects the performance of our systems and represents wasted computer resources and staff hours. The IRS Policy on Limited Personal Use of Government IT Equipment/Resources (see http://mits.web.irs.gov/Cybersecurity/Aware_Train/personal_use.htm), prohibits employees from creating, copying, transmitting, or retransmitting chain letters or other unauthorized mass mailings regardless of the subject matter.

  2. IRM 10.8.1.4.6.3 (9), Information Technology (IT) Security, states "E-mail spamming, sending or forwarding chain letters, other junk e-mail, or inappropriate messages shall be prohibited. " In addition, IRM 10.8.1.4.6.3 (8) states "Any use of IRS IT resources, including e-mail, shall be made with the understanding that such use may not be secure, is not private, is not anonymous and may be subject to disclosure under FOIA."

  3. If you receive an inappropriate e-mail, please notify your immediate supervisor or your local Data Security Area. Do not forward it to your co-workers, friends or family, etc. You should delete the inappropriate e-mail after notifying the proper authorities.

1.10.3.3  (07-08-2011)
Message Format

  1. Most IRS employees have access to e-mail, but not everyone has the same e-mail environment. Many employees work offsite and their e-mail messages must go through the Enterprise Remote Access System (ERAP). A result is that these users often experience slower access and transmission. E-mail messages that IRS office workers download in fractions of seconds can often take longer for a field user. Additionally, graphics and stationery can’t be read by adaptive equipment and can freeze the user’s system.

  2. Unnecessary messages or excess volume of data within a message require time for the recipient to review and digest. Keep the reader’s situation and need in mind at all times.

1.10.3.3.1  (07-08-2011)
Don’t Slow Down the System

  1. To avoid slowing down transmission of information:

    • Use Arial or another simple font on a plain background.

    • Do not use animation, fancy background, "wallpapers," borders, graphics and photographs as part of your "stationery" or message format. Exceptions will only be allowed for special IRS Commissioner initiatives.

    • Refrain from sending large attachments to work groups or audiences. Remember every e-mail message and any attachments, embedded graphics and photographs require a copy for each Exchange server store where each recipient’s mailbox resides. Instead store the document on an IRS public web archive or SharePoint repository and insert a hyperlink into the message. Ensure the permissions allow access by all recipients prior to sending the message.

1.10.3.3.2  (06-01-2007)
Categorize Messages

  1. A meaningful subject line helps recipients prioritize their e-mail. Categorize all e-mail by type. Include only related information in a message. If there is another topic you wish to address, send it in a separate message. This makes it easier for the recipient to manage and respond to messages on different topics.

  2. Use the follow-up flag feature to identify items with required follow-up dates.

1.10.3.3.3  (06-01-2007)
Designate Priority

  1. Most e-mail will be normal priority. Only designate high priority if the receiver will need to act on the message immediately. If your message is truly urgent, consider trying to reach the recipient by phone or in person.

    • "!" – High. Example – Computers will be down this weekend so overtime will not be scheduled and credit hours will not be approved. Example – We need volunteers for a task force in Washington that will convene in two weeks. Nominations are due this Friday.

    • "blank" – Normal (the default)

    • "down arrow" – Low. Example – The territory office of (another operating division) in another city has moved; its new address is…

1.10.3.3.4  (06-01-2007)
Designate Sensitivity

  1. Most e-mail is of normal sensitivity. Messages designated as " private" or "confidential" should not be forwarded – but the system allows for this. Marking a message with one of these settings is advisory only. Recipients can take any actions on the message that they want to, such as forwarding the message to another person.

  2. To designate sensitivity, from the "View" menu, select "Options." Then select the appropriate designation.

    • Private – Example – Communications with Labor Relations about an issue involving a particular employee.

    • Confidential – Example – A proposal you are sharing with someone for their input, but which has not been shared with those who will approve or those who will implement the procedures.

    • Normal (default)

1.10.3.3.5  (07-08-2011)
Follow Guidelines of E-mail Common Sense and Etiquette

  1. To improve the effectiveness of e-mail, follow these rules of etiquette and common sense guidelines:

    • Consider whether e-mail is the best method for your communication. Sometimes, two-way dialogue by phone or in person may be more effective. Other times, e-mail may be best if you need to provide written documentation.

    • Choose your recipients carefully. When selecting from the global address list, watch for duplicate names. If you frequently send to the same individuals, put them in your Personal Address Book. If two or more individuals have the same names, check the employees’ properties in the Global Address List to ensure the recipient is the right person in the right location.

    • Do not use a distribution list (as a convenience to you) unless your message is appropriate for everyone on that list.

    • Use the subject line to categorize messages.

    • Forward messages only when necessary. Do not forward to people who have already received the message. Example: Do not resend Commissioner All-Employee messages.

    • Be concise.

    • Review your messages for accuracy in content, spelling, and punctuation. Hint: Set auto spell check to check all messages before sending.

    • If you say that a file is attached, attach it. Hint: attach the file before you compose the message.

    • Insert hypertext links to large documents stored on IRS document repositories.

    • Maintain your Inbox.

    • Respond promptly to messages.

    • Routinely purge your mailbox of old and unnecessary messages (but do not delete e-mail that could be Federal Records).

    • Use the "To" address line for the primary recipient.

    • Use the carbon copy "cc" and blind carbon copy "bcc" features appropriately. Avoid copying people who do not need to see your message. In an internal office environment, it is rarely appropriate to use the "bcc" feature.

    • Use "Reply to all" only if all the original recipients need to know your response. Otherwise, reply only to the sender.

    • Never use "Reply to all" when you receive an e-mail as a member of a large geographic or Servicewide distribution list.

    • Use conversational grammar.

    • Do not use all caps or all lower case. Use punctuation.

    • Use the "out of office assistant" or " auto forward" features when you will be out of the office for an extended time.

    • If you receive any messages with a known or suspected virus, delete them immediately.

    • Avoid background, stationery or graphics.

    • To accommodate those with visual impairments, select font and background colors that provide sufficient contrast and avoid unusual color combinations. For example, use the default font color (usually black or blue) rather than selecting red or green, use the default background color rather than selecting a background color and do not use the text highlighting feature.

    • Help prevent unnecessary e-mail by telling recipients when your message does not require a reply.

    • Manage your e-mail more effectively by using Outlook features such as Voting Buttons and Invitation options. It will be easier for recipients to respond and easier for you to manage and track the results.

1.10.3.3.6  (07-08-2011)
Limit Size of Attachments

  1. Since large attachments can degrade overall system efficiency, you should limit the transmission of large files as e-mail attachments where possible.

  2. Consider alternatives for attachments larger than 50KB:

    If ... Then ...
    "Attachment" has widespread impact and a shelf life
    • Have it posted to your organization’s intranet site for retrieval, and

    • Include the hyperlink in the e-mail message.

    • -or-

    • Save it to your shared directory, and

    • Include file and path name in the e-mail message.

    "Attachment" does not have widespread impact and/or a shelf life
    • Zip large files for faster transmission.

    • Eliminate official IRS seal from memos.

    • If possible, remove graphics, borders, pictures and non-standard fonts.

    "Attachment" is a large graphic presentation (i.e., PowerPoint, screen shots, scanned documents)
    • Send it only to people who need to use or see the actual file.

    • Convert the information to a text file for those who only need the information.

    • Zip the file.

    • Have it posted to your organization’s intranet site and e-mail the hyperlink.

  3. If you are responding with an attachment, use "Forward " instead of "Reply" because attachments do not stay with replies.

  4. If you want to save the e-mail message but do not need the attachment, follow these instructions:

    • Open the message,

    • Right click the attachment icon, and

    • Select remove from the menu.

    • Close file. Select "yes" at the "Do you want to Save changes?" prompt.

    This will also save disk space.

1.10.3.3.7  (06-01-2007)
Malicious Attachments

  1. Ensure attachments are safe from viruses. Open attachments only if you trust the source and are expecting the attached file. Because of the impact the spreading of various worms and viruses have had on the IRS network, the Enterprise Messaging System is now configured to block all files with a particular extension. If a file is sent via e-mail with certain extensions (such as .exe, .vbs and .lnk), the message will be deleted without delivery.

  2. A number of virus variants try to bypass the IRS virus scanning software by including their damaging payload within a .ZIP file. Be cautious with any message you receive containing an attachment with a .ZIP file extension, and only unzip the file if you trust the source.

  3. When you receive an e-mail message with an attachment, save both the e-mail and the attachment to a hard drive or network drive as soon as possible and remove the message and attachment from your mailbox. You free up space on your server by doing this.

1.10.3.4  (07-08-2011)
Using and Creating Distribution Lists

  1. Distribution groups/lists are a convenience when messages need to be sent to a large defined group. They allow users to send e-mail messages to each individual on the list without selecting each name individually. However, you should use them judiciously.

1.10.3.4.1  (07-08-2011)
Personal Distribution Lists

  1. Personal distribution lists are created by an individual user. Use your Outlook Help feature, keyword – personal distribution list, for instructions on creating and sharing personal lists.

1.10.3.4.2  (06-01-2007)
Global Distribution Lists

  1. MITS and the SEMS staff can create global distribution lists for groups of practically any size and for any situation. These distribution lists are available for use from the global address list on Outlook. The list owner determines who will have authorization to use the list.

  2. There are several different types of global distribution lists.

    Location specific Considered local in scope, these lists only contain members from a local site. An example would be functional coordinators within a service center campus.
    Special needs Cross multiple organization boundaries and are often created for temporary groups, such as task forces.
    Large lists Contain more than 100 members and require specific set up and delivery restrictions. The AWSS all employee list (&AWSS Employees) is an example.

    Note:

    The use of large global lists should be confined to those who have a business need to communicate with the list. Examples are messages sent by MITS to alert users of systems related issues or distribution of other approved Servicewide communications tools such as IRS headlines or Leaders' Alert.

    Lists created from a database Membership for these lists is determined by specifying certain criteria within a database (such as TAPS or TIMIS) and populating the list with names meeting the criteria. Changes to membership cannot be made directly to the list, but must be made to information contained in the database. The SB/SE all-employee list (&SBSE All) is an example.

1.10.3.4.3  (04-01-2003)
Using Global Lists

  1. Before using a global distribution list to send an e-mail message that requires follow-up actions or commitment of resources by recipients outside of your division, always discuss the requirement with the applicable Division Commissioner’s office.

1.10.3.4.4  (07-08-2011)
Requesting a Global Distribution List

  1. Contact OSGetServices (1-866-743-5748) or TDD/TTY: 1-866-435-7486 to request creation of a new global distribution list (DL). The following information is required:

    • Business need justification

    • Scope – to whom it applies

    • Anticipated "shelf life" of DL

    • Name and number of the individual charged with maintaining the DL

    • Proposed list of initial DL members

    • If the list is automated, the conditional criteria of the members


    Please note: Distribution group/list names must be pre-approved by the designated business unit point of contact prior to opening the ITAMS ticket.

1.10.3.4.5  (07-08-2011)
Managing a List

  1. Distribution group/list managers can find information on modifying a list in the SEMS Documentation Library online at http://documentation.sems.enterprise.irs.gov/.

1.10.3.5  (04-01-2003)
Messages Intended for All Employees

  1. The IRS has the capability to send e-mail messages to all employees; however this method of communication should be used sparingly. If you have a message you believe should be communicated Servicewide, contact your business unit communication office.

1.10.3.5.1  (06-01-2007)
IRS Headlines...and more

  1. Generally, information requiring communication to all employees is distributed via the IRS Headlines … and more electronic newsletter. The C&L Internal Communications (IC) branch distributes IRS Headlines…and more every Monday using the all employee global distribution list. Articles for IRS Headlines …and more should contain time-sensitive information (something happening last week, this week or next week) relevant to a cross-section of IRS managers and employees.

  2. If you think you have information appropriate for IRS Headlines… and more, you should take the following steps:

    • Originator discusses topic and schedule with the business unit's communication office. (If none, contact IC directly http://irweb.irs.gov/AboutIRS/bu/cl/cldir/9296.aspx.)

    • Business unit communicator discusses topic and schedule with their IC consultant.

    • IC determines whether the topic is appropriate for IRS Headlines …and more.

    • Originator and business unit communicator draft message and submit it to Internal Communications (IC) (*Assignment Desk — CL:C:IC).

    • IC will provide editorial feedback on content, length, tone, and key messages.

    • IC will schedule article for publication in the IRS Headlines…and more electronic newsletter.

    • IC will suggest ways to incorporate message into other internal communications products, if appropriate.

1.10.3.5.2  (06-01-2007)
Special All-Employee E-mails

  1. On very rare occasions, special circumstances may require the issuance of an all-employee e-mail separate from IRS Headlines … and more. Any message submitted for distribution as an all-employee e-mail will be subject to a stringent review process because of the heavy volume of e-mail traffic to employees and the resulting burden. The communications manager in your business unit is your initial point of contact for advice in deciding whether to start the process of creating an all-employee e-mail.

  2. For a message to be considered for distribution to all employees, you must provide the following information:

    • Significance to employees (Is there something they must know immediately to do their jobs correctly, to comply with the law, to prevent a systems failure, etc.?)

    • Reason for extreme time sensitivity (Why is this information so critical to employees that it cannot wait for inclusion in the next edition of Headlines?)

    • Necessity of e-mail delivery vs. Headlines or other vehicle (Why does this information have to be sent via a special e-mail? Why wouldn’t IRweb (intranet) or Headlines be appropriate vehicles?)

    • Desired outcome (What immediate action do you want employees to take?)

    • Business objective

  3. The C&L Internal Communication Branch will determine the best method of communicating the message based on the information submitted.

1.10.3.6  (07-08-2011)
Assistance with E-mail Issues

  1. Use the following table to determine where to get assistance with e-mail issues.

    Topic Resource
    Security Concerns Immediately contact the Computer Security Incident Response Center (CSIRC) at http://www.csirc.web.irs.gov/
    E-mail: csirc@csirc.irs.gov
    (866) 216-4809 (toll-free)
    (202) 283-4809 (local)
    (202) 283-0345 (FAX)
    Technical problems w/Outlook Submit OS GetServices ticket online at http://getservices.web.irs.gov/or by calling 1-866-743-5748 or TDD/TTY: 1-866-435-7486.
    Creating or changing criteria for an Automated Distribution Group/List (Requires an ITAMS ticket) Contact OS GetServices online at http://getservices.web.irs.gov/or by calling at 1-866-743-5748 or TDD/TTY: 1-866-435-7486.
    SPAM issues DO NOT open e-mail; forward questionable e-mail to *SPAM with "Possible SPAM" in subject line.
    For additional information on Anti-SPAM procedures, see: http://mits.web.irs.gov/photogallery/m_communications/announcements/spam%20march%202005.doc .

Exhibit 1.10.3-1 
Reducing the Size of Your Mailbox

The Secure Enterprise Messaging system (SEMS) establishes a standard size of 150 MB (150 megabytes) for individual mailboxes. The system mails you daily warning messages that the limit is being approached when your mailbox reaches a size of 120 MB. When it exceeds the 150 MB limit, you will receive the following warning each time you attempt to send a message:

  • "You have exceeded your storage limit on your mailbox " .

  • Delete some mail from your mailbox or contact your system administrator to adjust your storage limit. (Consider whether any of the items you want to delete may be a Federal Record. See IRM 1.10.3.3.2 above.)

It is not the practice of the SEMS staff to adjust any individual mailbox storage limits, but rather to provide guidance on how to reduce the size of the contents. Outlook help provides instructions for enabling and configuring both Auto-archiving and Rules to manage mail and mailbox folders to maintain proper storage limits.

Exhibit 1.10.3-2 
Postscript/Signature

Your e-mail signature section should include only the identifying information that would otherwise be included in any official IRS communication (i.e. business card, memorandum, letter, etc.):

  • Name

  • Title

  • Organization

  • Street/e-mail address

  • Telephone/fax numbers

Refrain from including quotes or other personal messages as part of the signature section.

Follow these steps to create an automatic signature in Outlook:

  • Select "Options" from the "Tools" menu. Choose the "mail format" tab. Use the " Signatures" section at the bottom to create your personal signature line.


More Internal Revenue Manual