/usr/share/doc/ruby-rubymail-doc/html/TODO.html is in ruby-rubymail-doc 1.1.3-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 | <!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>TODO - RubyMail Documentation (version 1.1.3)</title>
<script type="text/javascript">
var rdoc_rel_prefix = "./";
</script>
<script src="./js/jquery.js"></script>
<script src="./js/darkfish.js"></script>
<link href="./css/fonts.css" rel="stylesheet">
<link href="./css/rdoc.css" rel="stylesheet">
<body id="top" role="document" class="file">
<nav role="navigation">
<div id="project-navigation">
<div id="home-section" role="region" title="Quick navigation" class="nav-section">
<h2>
<a href="./index.html" rel="home">Home</a>
</h2>
<div id="table-of-contents-navigation">
<a href="./table_of_contents.html#pages">Pages</a>
<a href="./table_of_contents.html#classes">Classes</a>
<a href="./table_of_contents.html#methods">Methods</a>
</div>
</div>
<div id="search-section" role="search" class="project-section initially-hidden">
<form action="#" method="get" accept-charset="utf-8">
<div id="search-field-wrapper">
<input id="search-field" role="combobox" aria-label="Search"
aria-autocomplete="list" aria-controls="search-results"
type="text" name="search" placeholder="Search" spellcheck="false"
title="Type to search, Up and Down to navigate, Enter to load">
</div>
<ul id="search-results" aria-label="Search Results"
aria-busy="false" aria-expanded="false"
aria-atomic="false" class="initially-hidden"></ul>
</form>
</div>
</div>
<div class="nav-section">
<h3>Table of Contents</h3>
<ul class="link-list" role="directory">
<li><a href="#label-FIXME">FIXME</a>
<li><a href="#label-STOLEN">STOLEN</a>
<li><a href="#label-Documentation">Documentation</a>
<li><a href="#label-Features">Features</a>
<li><a href="#label-Minor+Features">Minor Features</a>
<li><a href="#label-Documentation+Tasks">Documentation Tasks</a>
</ul>
</div>
<div id="project-metadata">
<div id="fileindex-section" class="nav-section">
<h3>Pages</h3>
<ul class="link-list">
<li><a href="./ChangeLog.html">ChangeLog</a>
<li><a href="./README_md.html">README</a>
<li><a href="./THANKS.html">THANKS</a>
<li><a href="./TODO.html">TODO</a>
<li><a href="./guide/Intro_txt.html">Intro</a>
<li><a href="./guide/MIME_txt.html">MIME</a>
<li><a href="./guide/TableOfContents_txt.html">TableOfContents</a>
</ul>
</div>
</div>
</nav>
<main role="main" aria-label="Page TODO">
<p>In rough priority order…but please let me know if something you need is
missing.</p>
<h1 id="label-FIXME">FIXME<span><a href="#label-FIXME">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>StreamHandler should get preamble_begin and preamble_end callbacks. Same
for epilogue_begin, epilogue_end.</p>
</li><li>
<p>Add a Rakefile rule to run the tests in the super anal way (against
multiple versions of Ruby).</p>
</li></ul>
<h1 id="label-STOLEN">STOLEN<span><a href="#label-STOLEN">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>Header continuation issue: <a
href="https://sourceforge.net/tracker/?func=detail&atid=105470&aid=504152&group_id=5470">sourceforge.net/tracker/?func=detail&atid=105470&aid=504152&group_id=5470</a></p>
</li><li>
<p>Subject: =?ISO-8859-1?Q?=24=A3_Kills_IRB?=</p>
</li></ul>
<h1 id="label-Documentation">Documentation<span><a href="#label-Documentation">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>Make it clear that all strings the library works with are the ASCII strings
that are part of the RFC2822 message – not strings in any other charset.</p>
</li><li>
<p>Update Intro.txt, write MIME.txt and other Guides.</p>
</li></ul>
<h1 id="label-Features">Features<span><a href="#label-Features">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>RFC2231 <a
href="http://mail.python.org/pipermail/email-sig/2003-November/000032.html">mail.python.org/pipermail/email-sig/2003-November/000032.html</a></p>
</li><li>
<p>Smart handling of charset issues for text/ types.</p>
<dl class="rdoc-list label-list"><dt>Goal
<dd>
<p>allow setting the body part to a given piece of data, and <a
href="RMail.html">RMail</a> handles setting the appropriate <a
href="guide/MIME_txt.html">MIME</a> headers. This requires the data to
have a known charset.</p>
</dd></dl>
<p>Maybe this plays into the encoding solution below.</p>
</li><li>
<p>Base64 and quoted-printable encoding</p>
<dl class="rdoc-list label-list"><dt>Goal
<dd>
<p>allow setting the body part to a given piece of data, and <a
href="RMail.html">RMail</a> handles setting the appropriate <a
href="guide/MIME_txt.html">MIME</a> headers and possibly quoted-printable
or base64 transcoding it if appropriate.</p>
</dd></dl>
<p>This may be best done by introducing an RMail::TransferEncodedString class
that knows whether it is transcoded as binary, quoted-printable, base64,
etc. You would set <a
href="RMail/Message.html#method-i-body">RMail::Message#body</a> to a
TransferEncodedString and <a href="RMail/Message.html">RMail::Message</a>
would set the appropriate <a href="guide/MIME_txt.html">MIME</a> headers.
If at serialization time the message body were set to a plain String, then
<a href="RMail/Message.html">RMail::Message</a> would transcode it into
base64.</p>
</li><li>
<p>An RMail::Message#attach method that takes care of setting
content-disposition, etc.</p>
</li><li>
<p>Header folding in <a href="RMail/Header.html">RMail::Header</a>.</p>
</li><li>
<p>A small wrapper around Net::SMTP#send_mail that takes care of:</p>
<ul><li>
<p>parsing recipients out of the various message headers</p>
</li><li>
<p>deleting the Bcc: header</p>
</li><li>
<p>sending the message</p>
</li></ul>
</li><li>
<p>Provide a way to parse just the message headers, leaving the rest in the
input stream (for use by RubyFilter). This also implies a feature that
parses a message body given a <a href="RMail/Header.html">RMail::Header</a>
object and an input stream. This should be easy – read line by line until
you get an empty line or EOF, then pass that off to parse_header as a
string to be parsed. Parsing the body can just use a PushbackReader.</p>
</li><li>
<p>Handle different end of line terminators everywhere (for both parsing and
generating).</p>
</li><li>
<p>Provide some way when parsing a message to start spooling to disk for
really large messages. This would be easy to do depending on how message
body transparency is implemented.</p>
</li><li>
<p><a href="guide/MIME_txt.html">MIME</a> charset support in header fields and
message bodies. This requires m18n support in ruby, so it won't be
coming soon.</p>
</li><li>
<p>Maildir parsing.</p>
</li><li>
<p>Simplify the Parser such that the class used to hold the parse result can
be easily changed and so the memory used can be minimized.</p>
<p>The idea is to support “bogofilter” style parsing where the data of the
parse is immediately processed and thrown away but the structure and
content of the parsed message is important.</p>
<p>This may require extensions to header parsing, where things like the
important <a href="guide/MIME_txt.html">MIME</a> header fields can be
parsed without creating a whole <a
href="RMail/Header.html">RMail::Header</a> object.</p>
</li></ul>
<h1 id="label-Minor+Features">Minor Features<span><a href="#label-Minor+Features">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>Untainting of email addresses. See Perl's CGI::Untaint::email.</p>
</li><li>
<p>Parser for Received: headers. See Perl's Mail::Field::Received.</p>
</li></ul>
<h1 id="label-Documentation+Tasks">Documentation Tasks<span><a href="#label-Documentation+Tasks">¶</a> <a href="#top">↑</a></span></h1>
<ul><li>
<p>A “howto” like documentation.</p>
<ul><li>
<p>How to write out a base64 encoded <a href="guide/MIME_txt.html">MIME</a>
part to a file.</p>
</li><li>
<p>How to parse a unix MBOX file.</p>
</li><li>
<p><a href="guide/MIME_txt.html">MIME</a> operations (see RFC2047)</p>
<ul><li>
<p>Character sets in message bodies</p>
</li><li>
<p>Non-textual message bodies</p>
</li><li>
<p>Multi-part message bodies</p>
</li><li>
<p>Textual header information in character sets other than US-ASCII.</p>
</li></ul>
</li></ul>
</li><li>
<p>Go through every class and make sure the methods are sorted in a sensible
order so the RDoc output is nice.</p>
</li></ul>
</main>
<footer id="validator-badges" role="contentinfo">
<p><a href="http://validator.w3.org/check/referer">Validate</a>
<p>Generated by <a href="http://docs.seattlerb.org/rdoc/">RDoc</a> 4.2.1.
<p>Based on <a href="http://deveiate.org/projects/Darkfish-RDoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
</footer>
|