aboutsummaryrefslogtreecommitdiffstats
path: root/trio/html/group___scanf.html
blob: 0c8d9d2b23439ae3e96cc56e0bbf49a6ee967070 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
 <title>TRIO</title>
 <link href="trio.css" rel="stylesheet" type="text/css">
</head>
<body>
<!-- Generated by Doxygen 1.2.12 -->
<center>
<a class="qindex" href="index.html">Main Page</a> &nbsp; <a class="qindex" href="modules.html">Modules</a> &nbsp; </center>
<hr><h1>Formatted Scanning Functions.</h1>Variations of formatted scanning functions. 
<a href="#_details">More...</a><table border=0 cellpadding=0 cellspacing=0>
<tr><td colspan=2><br><h2>Functions</h2></td></tr>
<tr><td nowrap align=right valign=top>int&nbsp;</td><td valign=bottom><a class="el" href="group___scanf.html#a0">trio_scanf</a> (const char *format,...)</td></tr>
<tr><td>&nbsp;</td><td><font size=-1><em>Scan characters from standard input stream.</em> <a href="#a0">More...</a><em></em></font><br><br></td></tr>
</table>
<hr><a name="_details"></a><h2>Detailed Description</h2>
Variations of formatted scanning functions.
<p>
<b>SYNOPSIS</b>
<p>
<div class="fragment"><pre>
cc ... -ltrio -lm

#include &lt;trio.h&gt;
</pre></div>
<p>
<b>DESCRIPTION</b>
<p>
This documentation is incomplete. The documentation of the scanf family in [C99] and [UNIX98] also applies to the trio counterparts.
<p>
<b>SCANNING</b>
<p>
The scanning is controlled by the format string. The format string can contain normal text and conversion indicators. The normal text can be any character except the nil character (\000) and the percent character (\045 = '%'). Conversion indicators consists of an indication character (%), followed by zero or more conversion modifiers, and exactly one conversion specifier.
<p>
<b>Modifiers</b>
<p>
<em>Positional</em> ( <code>9$</code> ) [UNIX98]
<p>
See <a class="el" href="group___printf.html#a0">trio_printf</a>.
<p>
<b>Specifiers</b>
<p>
<em>Percent</em> ( <code>%</code> )
<p>
<em>Character</em> ( <code>c</code> )
<p>
<em>Decimal</em> ( <code>d</code> )
<p>
<em>Floating-point</em> ( <code>a</code>, <code>A</code>, <code>e</code>, <code>E</code>, <code>f</code>, <code>F</code>, <code>g</code>, <code>G</code> )
<p>
<em>Integer</em> ( <code>i</code> )
<p>
<em>Count</em> ( <code>n</code> )
<p>
<em>Octal</em> ( <code>o</code> )
<p>
<em>Pointer</em> ( <code>p</code> )
<p>
<em>String</em> ( <code>s</code> )
<p>
<em>Unsigned</em> ( <code>u</code> )
<p>
<em>Hex</em> ( <code>x</code>, <code>X</code> )
<p>
<em>Scanlist</em> ( <code>[]</code> )
<p>
Scanlist Exclusion (<code>^</code> )
<p>
Scanlist Range ( <code>-</code> ) [TRIO]
<p>
<ul>
<li> Only increasing ranges, i.e. <code>[a-b]</code>, but not <code>[b-a]</code>. <li> Transitive ranges, ie. <code>[a-b-c]</code> equals <code>[a-c]</code>. <li> Trailing minus, ie. <code>[a-]</code> is interpreted as an <code>a</code> and a <code>-</code>. <li> Duplicates are ignored.</ul>
Scanlist Equivalence Class Expression ( <code>[</code>= =<code>]</code> ) [TRIO]
<p>
Locale dependent (LC_COLLATE). Only one expression can appear inside the delimiters. <ul>
<li> <code>[=a=]</code> All letters in the same equivalence class as the letter <code>a</code>. <div class="fragment"><pre>
  trio_scanf("%[[=a=]b]\n", buffer);
  trio_scanf("%[[=a=][=b=]]\n", buffer);
</pre></div></ul>
Scanlist Character Class Expression ( <code>[</code>: :<code>])</code> [TRIO] Locale dependent (LC_CTYPE). Only one expression can appear inside the delimiters. <ul>
<li> <code>[:alnum:]</code> Same as <code>[:alpha:]</code> and <code>[:digit:]</code> <li> <code>[:alpha:]</code> Same as <code>[:lower:]</code> and <code>[:upper:]</code> <li> <code>[:cntrl:]</code> Control characters <li> <code>[:digit:]</code> Decimal digits <li> <code>[:graph:]</code> Printable characters except space <li> <code>[:lower:]</code> Lower case alphabetic letters <li> <code>[:print:]</code> Printable characters <li> <code>[:punct:]</code> Punctuation <li> <code>[:space:]</code> Whitespace characters <li> <code>[:upper:]</code> Upper case alphabetic letters <li> <code>[:xdigit:]</code> Hexadecimal digits <div class="fragment"><pre>
  trio_scanf("%[[:alnum:]]\n", buffer);
  trio_scanf("%[[:alpha:][:digit:]]\n", buffer);
</pre></div></ul>
<b>RETURN</b> <b>VALUES</b>
<p>
<b>SEE</b> <b>ALSO</b>
<p>
<a class="el" href="group___printf.html#a0">trio_printf</a> <hr><h2>Function Documentation</h2>
<a name="a0" doxytag="trio.c::trio_scanf"></a><p>
<table width="100%" cellpadding="2" cellspacing="0" border="0">
  <tr>
    <td class="md">
      <table cellpadding="0" cellspacing="0" border="0">
        <tr>
          <td class="md" nowrap valign="top"> int trio_scanf </td>
          <td class="md" valign="top">(&nbsp;</td>
          <td class="md" nowrap valign="top">const char *&nbsp;</td>
          <td class="mdname" nowrap>&nbsp; <em>format</em>, </td>
        </tr>
        <tr>
          <td></td>
          <td></td>
          <td class="md" nowrap>...&nbsp;</td>
          <td class="mdname" nowrap>&nbsp;</td>
        </tr>
        <tr>
          <td></td>
          <td class="md">)&nbsp;</td>
          <td class="md" colspan="2"></td>
        </tr>

      </table>
    </td>
  </tr>
</table>
<table cellspacing=5 cellpadding=0 border=0>
  <tr>
    <td>
      &nbsp;
    </td>
    <td>

<p>
Scan characters from standard input stream.
<p>
<dl compact><dt><b>
Parameters: </b><dd>
<table border=0 cellspacing=2 cellpadding=0>
<tr><td valign=top><em>format</em>&nbsp;</td><td>
Formatting string. </td></tr>
<tr><td valign=top><em>...</em>&nbsp;</td><td>
Arguments. </td></tr>
</table>
</dl><dl compact><dt><b>
Returns: </b><dd>
Number of scanned characters. </dl>    </td>
  </tr>
</table>
<HR>
<center class="copyright">Copyright (C) 2001 Bj&oslash;rn Reese and Daniel Stenberg.</center>
</body>
</html>
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-13 18:13:35 +0000
n .fetchmailrc</h2> <p>The reason there's no facility to store passwords encrypted in the .fetchmailrc file is because this doesn't actually add protection.</p> <p>Anyone who's acquired the 0600 permissions needed to read your .fetchmailrc file will be able to run fetchmail as you anyway -- and if it's your password they're after, they'd be able to rip the necessary decoder out of the fetchmail code itself to get it.</p> <p>All .fetchmailrc encryption would do is give a false sense of security to people who don't think very hard.</p> <h2>Truly concurrent queries to multiple hosts</h2> <p>Occasionally I get a request for this on "efficiency" grounds. These people aren't thinking either. True concurrency would do nothing to lessen fetchmail's total IP volume. The best it could possibly do is change the usage profile to shorten the duration of the active part of a poll cycle at the cost of increasing its demand on IP volume per unit time.</p> <p>If one could thread the protocol code so that fetchmail didn't block on waiting for a protocol response, but rather switched to trying to process another host query, one might get an efficiency gain (close to constant loading at the single-host level).</p> <p>Fortunately, I've only seldom seen a server that incurred significant wait time on an individual response. I judge the gain from this not worth the hideous complexity increase it would require in the code.</p> <h2>Multiple concurrent instances of fetchmail</h2> <p>Fetchmail locking is on a per-invoking-user because finer-grained locks would be really hard to implement in a portable way. The problem is that you don't want two fetchmails querying the same site for the same remote user at the same time.</p> <p>To handle this optimally, multiple fetchmails would have to associate a system-wide semaphore with each active pair of a remote user and host canonical address. A fetchmail would have to block until getting this semaphore at the start of a query, and release it at the end of a query.</p> <p>This would be way too complicated to do just for an "it might be nice" feature. Instead, you can run a single root fetchmail polling for multiple users in either single-drop or multidrop mode.</p> <p>The fundamental problem here is how an instance of fetchmail polling host foo can assert that it's doing so in a way visible to all other fetchmails. System V semaphores would be ideal for this purpose, but they're not portable.</p> <p>I've thought about this a lot and roughed up several designs. All are complicated and fragile, with a bunch of the standard problems (what happens if a fetchmail aborts before clearing its semaphore, and how do we recover reliably?).</p> <p>I'm just not satisfied that there's enough functional gain here to pay for the large increase in complexity that adding these semaphores would entail.</p> <h1>Multidrop and alias handling</h1> <p>I decided to add the multidrop support partly because some users were clamoring for it, but mostly because I thought it would shake bugs out of the single-drop code by forcing me to deal with addressing in full generality. And so it proved.</p> <p>There are two important aspects of the features for handling multiple-drop aliases and mailing lists which future hackers should be careful to preserve.</p> <ol> <li> <p>The logic path for single-recipient mailboxes doesn't involve header parsing or DNS lookups at all. This is important -- it means the code for the most common case can be much simpler and more robust.</p> </li> <li> <p>The multidrop handing does <em>not</em> rely on doing the equivalent of passing the message to sendmail -t. Instead, it explicitly mines members of a specified set of local usernames out of the header.</p> </li> <li> <p>We do <em>not</em> attempt delivery to multidrop mailboxes in the presence of DNS errors. Before each multidrop poll we probe DNS to see if we have a nameserver handy. If not, the poll is skipped. If DNS crashes during a poll, the error return from the next nameserver lookup aborts message delivery and ends the poll. The daemon mode will then quietly spin until DNS comes up again, at which point it will resume delivering mail.</p> </li> </ol> <p>When I designed this support, I was terrified of doing anything that could conceivably cause a mail loop (you should be too). That's why the code as written can only append <em>local</em> names (never @-addresses) to the recipients list.</p> <p>The code in mxget.c is nasty, no two ways about it. But it's utterly necessary, there are a lot of MX pointers out there. It really ought to be a (documented!) entry point in the bind library.</p> <h1>DNS error handling</h1> <p>Fetchmail's behavior on DNS errors is to suppress forwarding and deletion of the individual message that each occurs in, leaving it queued on the server for retrieval on a subsequent poll. The assumption is that DNS errors are transient, due to temporary server outages.</p> <p>Unfortunately this means that if a DNS error is permanent a message can be perpetually stuck in the server mailbox. We've had a couple bug reports of this kind due to subtle RFC822 parsing errors in the fetchmail code that resulted in impossible things getting passed to the DNS lookup routines.</p> <p>Alternative ways to handle the problem: ignore DNS errors (treating them as a non-match on the mailserver domain), or forward messages with errors to fetchmail's invoking user in addition to any other recipients. These would fit an assumption that DNS lookup errors are likely to be permanent problems associated with an address.</p> <h1>IPv6 and IPSEC</h1> <p>The IPv6 support patches are really more protocol-family independence patches. Because of this, in most places, "ports" (numbers) have been replaced with "services" (strings, that may be digits). This allows us to run with certain protocols that use strings as "service names" where we in the IP world think of port numbers. Someday we'll plumb strings all over and then, if inet6 is not enabled, do a getservbyname() down in SocketOpen. The IPv6 support patches use getaddrinfo(), which is a POSIX p1003.1g mandated function. So, in the not too distant future, we'll zap the ifdefs and just let autoconf check for getaddrinfo. IPv6 support comes pretty much automatically once you have protocol family independence.</p> <h1>Internationalization</h1> <p>Internationalization is handled using GNU gettext (see the file ABOUT_NLS in the source distribution). This places some minor constraints on the code.</p> <p>Strings that must be subject to translation should be wrapped with GT_() or N_() -- the former in function arguments, the latter in static initializers and other non-function-argument contexts.</p> <h1>Checklist for Adding Options</h1> <p>Adding a control option is not complicated in principle, but there are a lot of fiddly details in the process. You'll need to do the following minimum steps.</p> <ul> <li>Add a field to represent the control in <code>struct run</code>, <code>struct query</code>, or <code>struct hostdata</code>.</li> <li>Go to <code>rcfile_y.y</code>. Add the token to the grammar. Don't forget the <code>%token</code> declaration.</li> <li>Pick an actual string to declare the option in the .fetchmailrc file. Add the token to <code>rcfile_l</code>.</li> <li>Pick a long-form option name, and a one-letter short option if any are left. Go to <code>options.c</code>. Pick a new <code>LA_</code> value. Hack the <code>longoptions</code> table to set up the association. Hack the big switch statement to set the option. Hack the `?' message to describe it.</li> <li>If the default is nonzero, set it in <code>def_opts</code> near the top of <code>load_params</code> in <code>fetchmail.c</code>.</li> <li>Add code to dump the option value in <code>fetchmail.c:dump_params</code>.</li> <li>For a per-site or per-user option, add proper <code>FLAG_MERGE</code> actions in fetchmail.c's optmerge() function. For a global option, add an override at the end of load_params; this will involve copying a "cmd_run." field to a corresponding "run." field, see the existing code for models.</li> <li>Document the option in fetchmail.man. This will require at least two changes; one to the collected table of options, and one full text description of the option.</li> <li>Hack fetchmailconf to configure it. Bump the fetchmailconf version.</li> <li>Hack conf.c to dump the option so we won't have a version-skew problem.</li> <li>Add an entry to NEWS.</li> <li>If the option implements a new feature, add a note to the feature list.</li> </ul> <p>There may be other things you have to do in the way of logic, of course.</p> <p>Before you implement an option, though, think hard. Is there any way to make fetchmail automatically detect the circumstances under which it should change its behavior? If so, don't write an option. Just do the check!</p> <h1>Lessons learned</h1> <h3>1. Server-side state is essential</h3> <p>The person(s) responsible for removing LAST from POP3 deserve to suffer. Without it, a client has no way to know which messages in a box have been read by other means, such as an MUA running on the server.</p> <p>The POP3 UID feature described in RFC1725 to replace LAST is insufficient. The only problem it solves is tracking which messages have been read <em>by this client</em> -- and even that requires tricky, fragile implementation.</p> <p>The underlying lesson is that maintaining accessible server-side `seen' state bits associated with Status headers is indispensible in a Unix/RFC822 mail server protocol. IMAP gets this right.</p> <h3>2. Readable text protocol transactions are a Good Thing</h3> <p>A nice thing about the general class of text-based protocols that SMTP, POP2, POP3, and IMAP belongs to is that client/server transactions are easy to watch and transaction code correspondingly easy to debug. Given a decent layer of socket utility functions (which Carl provided) it's easy to write protocol engines and not hard to show that they're working correctly.</p> <p>This is an advantage not to be despised! Because of it, this project has been interesting and fun -- no serious or persistent bugs, no long hours spent looking for subtle pathologies.</p> <h3>3. IMAP is a Good Thing.</h3> <p>Now that there is a standard IMAP equivalent of the POP3 APOP validation in CRAM-MD5, POP3 is completely obsolete.</p> <h3>4. SMTP is the Right Thing</h3> <p>In retrospect it seems clear that this program (and others like it) should have been designed to forward via SMTP from the beginning. This lesson may be applicable to other Unix programs that now call the local MDA/MTA as a program.</p> <h3>5. Syntactic noise can be your friend</h3> <p>The optional `noise' keywords in the rc file syntax started out as a late-night experiment. The English-like syntax they allow is considerably more readable than the traditional terse keyword-value pairs you get when you strip them all out. I think there may be a wider lesson here.</p> <h1>Motivation and validation</h1> <p>It is truly written: the best hacks start out as personal solutions to the author's everyday problems, and spread because the problem turns out to be typical for a large class of users. So it was with Carl Harris and the ancestral popclient, and so with me and fetchmail.</p> <p>It's gratifying that fetchmail has become so popular. Until just before 1.9 I was designing strictly to my own taste. The multi-drop mailbox support and the new --limit option were the first features to go in that I didn't need myself.</p> <p>By 1.9, four months after I started hacking on popclient and a month after the first fetchmail release, there were literally a hundred people on the fetchmail-friends contact list. That's pretty powerful motivation. And they were a good crowd, too, sending fixes and intelligent bug reports in volume. A user population like that is a gift from the gods, and this is my expression of gratitude.</p> <p>The beta testers didn't know it at the time, but they were also the subjects of a sociological experiment. The results are described in my paper, <a href="//www.catb.org/~esr/writings/cathedral-bazaar/">The Cathedral And The Bazaar</a>.</p> <h1>Credits</h1> <p>Special thanks go to Carl Harris, who built a good solid code base and then tolerated me hacking it out of recognition. And to Harry Hochheiser, who gave me the idea of the SMTP-forwarding delivery mode.</p> <p>Other significant contributors to the code have included Dave Bodenstab (error.c code and --syslog), George Sipe (--monitor and --interface), Gordon Matzigkeit (netrc.c), Al Longyear (UIDL support), Chris Hanson (Kerberos V4 support), and Craig Metz (OPIE, IPv6, IPSEC).</p> <h1>Conclusion</h1> <p>At this point, the fetchmail code appears to be pretty stable. It will probably undergo substantial change only if and when support for a new retrieval protocol or authentication method is added.</p> <h1>Relevant RFCS</h1> <p>Not all of these describe standards explicitly used in fetchmail, but they all shaped the design in one way or another.</p> <dl> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc821.txt">RFC821</a></dt> <dd>SMTP protocol</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc822.txt">RFC822</a></dt> <dd>Mail header format</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc937.txt">RFC937</a></dt> <dd>Post Office Protocol - Version 2</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc974.txt">RFC974</a></dt> <dd>MX routing</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc976.txt">RFC976</a></dt> <dd>UUCP mail format</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1081.txt">RFC1081</a></dt> <dd>Post Office Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1123.txt">RFC1123</a></dt> <dd>Host requirements (modifies 821, 822, and 974)</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1176.txt">RFC1176</a></dt> <dd>Interactive Mail Access Protocol - Version 2</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1203.txt">RFC1203</a></dt> <dd>Interactive Mail Access Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1225.txt">RFC1225</a></dt> <dd>Post Office Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1344.txt">RFC1344</a></dt> <dd>Implications of MIME for Internet Mail Gateways</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1413.txt">RFC1413</a></dt> <dd>Identification server</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1428.txt">RFC1428</a></dt> <dd>Transition of Internet Mail from Just-Send-8 to 8-bit SMTP/MIME</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1460.txt">RFC1460</a></dt> <dd>Post Office Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1508.txt">RFC1508</a></dt> <dd>Generic Security Service Application Program Interface</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1521.txt">RFC1521</a></dt> <dd>MIME: Multipurpose Internet Mail Extensions</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1869.txt">RFC1869</a></dt> <dd>SMTP Service Extensions (ESMTP spec)</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1652.txt">RFC1652</a></dt> <dd>SMTP Service Extension for 8bit-MIMEtransport</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1725.txt">RFC1725</a></dt> <dd>Post Office Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1730.txt">RFC1730</a></dt> <dd>Interactive Mail Access Protocol - Version 4</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1731.txt">RFC1731</a></dt> <dd>IMAP4 Authentication Mechanisms</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1732.txt">RFC1732</a></dt> <dd>IMAP4 Compatibility With IMAP2 And IMAP2bis</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1734.txt">RFC1734</a></dt> <dd>POP3 AUTHentication command</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1870.txt">RFC1870</a></dt> <dd>SMTP Service Extension for Message Size Declaration</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1891.txt">RFC1891</a></dt> <dd>SMTP Service Extension for Delivery Status Notifications</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1892.txt">RFC1892</a></dt> <dd>The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1894.txt">RFC1894</a></dt> <dd>An Extensible Message Format for Delivery Status Notifications</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1893.txt">RFC1893</a></dt> <dd>Enhanced Mail System Status Codes</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1894.txt">RFC1894</a></dt> <dd>An Extensible Message Format for Delivery Status Notifications</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1938.txt">RFC1938</a></dt> <dd>A One-Time Password System</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1939.txt">RFC1939</a></dt> <dd>Post Office Protocol - Version 3</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1957.txt">RFC1957</a></dt> <dd>Some Observations on Implementations of the Post Office Protocol (POP3)</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc1985.txt">RFC1985</a></dt> <dd>SMTP Service Extension for Remote Message Queue Starting</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2033.txt">RFC2033</a></dt> <dd>Local Mail Transfer Protocol</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2060.txt">RFC2060</a></dt> <dd>Internet Message Access Protocol - Version 4rev1</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2061.txt">RFC2061</a></dt> <dd>IMAP4 Compatibility With IMAP2bis</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2062.txt">RFC2062</a></dt> <dd>Internet Message Access Protocol - Obsolete Syntax</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2195.txt">RFC2195</a></dt> <dd>IMAP/POP AUTHorize Extension for Simple Challenge/Response</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2177.txt">RFC2177</a></dt> <dd>IMAP IDLE command</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2449.txt">RFC2449</a></dt> <dd>POP3 Extension Mechanism</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2554.txt">RFC2554</a></dt> <dd>SMTP Service Extension for Authentication</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2595.txt">RFC2595</a></dt> <dd>Using TLS with IMAP, POP3 and ACAP</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2645.txt">RFC2645</a></dt> <dd>On-Demand Mail Relay: SMTP with Dynamic IP Addresses</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2683.txt">RFC2683</a></dt> <dd>IMAP4 Implementation Recommendations</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2821.txt">RFC2821</a></dt> <dd>Simple Mail Transfer Protocol</dd> <dt><a href="ftp://ftp.isi.edu/in-notes/rfc2822.txt">RFC2822</a></dt> <dd>Internet Message Format</dd> </dl> <!-- RFC2192 IMAP URL Scheme RFC2193 IMAP4 Mailbox Referrals RFC2221 IMAP4 Login Referrals --> <h1>Other useful documents</h1> <dl> <dt><a href="http://www.faqs.org/faqs/LANs/mail-protocols/">http://www.faqs.org/faqs/LANs/mail-protocols/</a></dt> <dd>LAN Mail Protocols Summary</dd> </dl> <hr /> <table width="100%" cellpadding="0" summary="Canned page footer"> <tr> <td width="30%">Back to <a href="index.html">Fetchmail Home Page</a></td> <td width="30%" align="right">$Date$</td> </tr> </table> <br clear="left" /> <address>Eric S. Raymond <a href="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</a></address> </body> </html>
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-13 18:13:35 +0000