12 citations found. Retrieving documents...
M. Crispin. Internet message access protocol - version 4rev1. RFC 3501, March 2003.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Fighting Spam by Encapsulating Policy in Email Addresses - Ioannidis   (Correct)

....check the email against the policy rules encoded in the address, and deliver it, bounce it, or discard it accordingly. This, of course, is a very simplified view of the mail delivery process; it does not take into account the possibility that a remote mail access protocol such as POP3[13] or IMAP4[8] is used. We shall discuss these cases in Section 4. spain user user s mbox correspondent spagen procmail Figure 1. Give address get mail. The core idea is that whenever an email address is handed out, rules about its use are encoded in the address itself. The correspondent cannot, of ....

....are some more obvious policies that we could encode with a single bit, such as requiring encrypted authenticated mail to the SPA. In the limit, fullfledged policies can be expressed in some policy definition language such as the one described in [6] Finally, when systems such as POP3[13] or IMAP4[8] are used, the user can have the option of letting all mail, including spam, accumulate on the server, and then use spain like processing as each piece of mail is retrieved. Naturally, usually only the headers will need to be retrieved before a decision is made to discard the mail as spam. If the ....

M. Crispin. Internet Message Access Protocol --- Version 4rev1. RFC 2060.


RMS: A Robust Mail Store and Retrieval System - Thiemann (2002)   (Correct)

....present it in this way. The following selection criteria are supported by RMS (ordered from cheap to expensive) member of a collection ( collection MC name ) this may be narrowed to a subset of the members by specifying an ascending list of indexes in square brackets ( collection MC name [1,5,7]) date ( earlier than datespec , later than datespec ) A personal mail store only admits a single user. 9 . presence of an attribute (attribute ) regular expressions on header fields (e.g. header to: regexp ) regular expressions on message body ( contains regexp ) These ....

....next file name) In contrast, we are using globally unique message names and our objectives for using them are to support merging of replicated mail stores via standard file synchronization tools in the presence of arbitrary reorganization. IMAP is a network protocol for accessing a mail store [7]. Existing IMAP servers include an MH style implementation of the mail store. In contrast to our approach, IMAP relies on a single centralized mail store which also serves as a mail drop. Disconnected operation, in particular reorganization of the store, is not directly supported. However, there ....

[Article contains additional citation context not shown here]

Mark R. Crispin. Internet message access protocol - version 4rev1. http: //www.faqs.org/rfcs/rfc2060.


Self-Securing Network Interfaces: What, Why and How - Ganger, Economou, Bielski (2002)   (Correct)

....fewer than 100 messages in a day. Discussion: Implementing an e mail scanner for POP and SMTP was straightforward using the scanner API; the scanner simply watches for the beginning of an e mail message and then examines that message. For more interactive mail exchange protocols, such as IMAP [12], additional effort will be required. In particular, IMAP transfers e mail messages in pieces rather than as a whole, and those pieces are not self identifying. An IMAP scanner will have to track the exchanges to identify when an attachment is being transferred so that it can invoke the virus ....

M. Crispin. Internet message access protocol -- version 4rev1, RFC--2060.


Mixminion: Design of a Type III Anonymous Remailer.. - Danezis, Dingledine.. (2002)   (18 citations)  (Correct)

....how many new reply blocks to send; indeed, under this approach, an attacker can deny service by ooding the mailbox to exhaust the available reply blocks and block further messages from getting delivered. A more robust design uses a protocol inspired by e mail retrieval protocols such as IMAP [11] or POP [33] messages arrive and queue at the nymserver, and the user periodically checks the status of his mail and sends a sucient batch of reply blocks so the nymserver can deliver that mail. In this case, the nymserver doesn t need to store any reply blocks. The above ooding attack still ....

M. Crispin. Internet Message Access Protocol | Version 4rev1. IETF RFC 2060, December 1996. <http://www.rfc-editor.org/rfc/rfc2060.txt>.


Meta - a freely available scalable MTA - Westerlund..   (Correct)

....is appended to the end of this file. The mails are read from these files and eventually deleted by the pop daemon when the users fetch them to their mail clients with POP. But some users and mail clients instead access the spool files directly on the mail hub or through NFS [13] Or they use IMAP [14] or some other (and new) means of getting the mail. This means that the mails have to be stored in the common mbox format so that all the programs that can access them will understand the format. With Meta we decided early that the only way of accessing the mail would be with POP. This simplifies ....

M. Crispin, Internet Message Access Protocol - Version 4rev1, University of Washington (1996)


Internet Roaming - Rothkugel, Sturm   (Correct)

....machines in this context are required to provide an Internet connection, a card terminal, and a Java virtual machine. Like in the roaming X windows application, JavaCards are employed. A standard mail reader such as Netscape Messenger is statically configured to contact a roaming aware IMAP [6] server via the card, making manual configuration when arriving at a remote site obsolete. Any configuration as well as authentication and message encryption are responsibilities of the JavaCard. Among the additional capabilities of the roaming aware mail service are for example its ability to ....

Crispin, M.: Internet Message Access Protocol - Version 4rev1. RFC 2060. ftp://ftp.isi.edu/in-notes/rfc2060.txt


Beyond Identity: Addressing Problems that Persist in an.. - Watson (2004)   (Correct)

No context found.

M. Crispin. Internet message access protocol - version 4rev1. RFC 3501, March 2003.


DiffMail: A Differentiated Message Delivery Architecture to .. - Duan, Dong, Gopalan (2004)   (Correct)

No context found.

M. Crispin. Internet message access protocol - version 4rev1. IETF RFC3501, March 2003.


Dynamic Replica Management in Distributed Hash Tables - Waldvogel, Hurley, Bauer (2003)   (Correct)

No context found.

Mark R. Crispin. Internet message access protocol - version 4rev1. RFC 3501, Internet Engineering Task Force, March 2003.


The Design and Implementation of Datagram TLS - Nagendra Modadugu Eric (2004)   (1 citation)  (Correct)

No context found.

M. Crispin. Internet Message Access Protocol - Version 4rev1 (IMAP). RFC 3501, March 2003.


Network Event Recognition for Packet-Mode Surveillance - Bhargavan, Gunter (2002)   (Correct)

No context found.

M. Crispin. Internet Message Access Protocol - Version 4rev1. Technical Report RFC 2060.


Network Event Recognition - Karthikeyan Bhargavan University   (Correct)

No context found.

M. Crispin. Internet Message Access Protocol - Version 4rev1. Technical Report RFC 2060, IETF, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC