Security Best Practices: Out-of-Office Replies
draft-aeble-ooo-replies-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Axel Eble | ||
| Last updated | 2003-09-29 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Email has come to be the single most important application of modern Information Technology. It is often considered business critical. Most current email systems have means for automated replies to incoming messages. These are mostly used for so-called out-of-office replies or OoO-replies for short. This document discusses problems of out-of-office replies and suggests best practices and controls that should be put in place.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)