2008
DOI: 10.17487/rfc5321
|View full text |Cite
|
Sign up to set email alerts
|

Simple Mail Transfer Protocol

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
210
0
5

Year Published

2008
2008
2020
2020

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 205 publications
(227 citation statements)
references
References 32 publications
1
210
0
5
Order By: Relevance
“…For this period of over sixty days 6 , at the test server, it was recorded:  6,793 distinct source IP addresses  14,282 distinct mail addresses (both sender and receiver)  23,194 connections, of which:…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…For this period of over sixty days 6 , at the test server, it was recorded:  6,793 distinct source IP addresses  14,282 distinct mail addresses (both sender and receiver)  23,194 connections, of which:…”
Section: Resultsmentioning
confidence: 99%
“…It is roughly divided into three main areas and five components, as shown in Table 2. A decision process is initiated by the MTA, and its goal is to process each SMTP [6] command and decide to either accept or reject the SMTP session or transaction based on available information. When the information is insufficient to make a reliable decision, the MTA returns a temporary fail, and that fact gets registered.…”
Section: Working Principlementioning
confidence: 99%
“…From S's view, the whole session starts and ends, by interactions with C, in this one case, if the session indeed proceeds this way at run-time: while S remains unconnected, we can consider it as "inactive" with regards to session safety and progress. At the same time, this solution reduces the gap between MPST-based descriptions and real protocols, like Internet application RFCs, by recognising that the client/server connection actions are as important to a rigorous specification as the message passing (e.g., the STARTTLS "re-connection" in SMTP [28], and FTP's active/passive modes [39]). …”
Section: Use Case: Travel Agency Web Service (Revisited)mentioning
confidence: 99%
“…The term "notification message" ([RFC5321], Section 4.5.5) is used to refer to a message with a null RFC5321.MailFrom.…”
Section: Document Conventionsmentioning
confidence: 99%