imap 0.10.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a5a7c49aedce3c0b0aaf2ab4c707f404c91dcdd0fbda9abc68107008816ad2ce
-  data.tar.gz: 3352fdcb214ee0a7bf631e67c068f19fac38a3349b1f0f54cb9286b7652e834f
+  metadata.gz: d2adce3df9c03ab185866e212c6d4ed2ffb2de37ca288eb5ad4f7b9e6e92f68a
+  data.tar.gz: 602536188fecb058c39c18cfee25b46eace80f3676548afd06f4734979e6c7b1
 SHA512:
-  metadata.gz: e843366a424bd2544e527b2b6ea8368397bc36263bc3eb648bbe6c9dbc8ba052a4f0825c6cf4f626d82eb5f179f25954502e2fcd040cb8dcb9bd5fdffca40846
-  data.tar.gz: 6b17ea64de5bd24e4188ce82e56022c62f2ad0efa2bcd82682a673435e997b1902617eabaa94168c62185370da7c15901d38ec6101ff2fb911847795dcedefc4
+  metadata.gz: a8d445f3dfd17c1ad074b38c544fc5620a0c045f20ef7e00c273bda6df3fcc633d9fefce4fad6f30648896a7356049d612a89789a528f1d8be83b3f9098d2d13
+  data.tar.gz: 218c50db53fc39640409531ced34a1f89ba0adb3297e22a3db14cdd868da00b1e2ab58a655dca2047f706322e89f84411e65be89d7b2f41a68837f1ccfe6b351

data/CHANGELOG

@@ -2,6 +2,17 @@
 
 ## 20260919
 
+0.11.0: ~ README.md: rewritten for the surface as it now stands; ~ the gemspecs: /['minitest', '~> 5.0']/'minitest'/, /['rake', '~> 13.0']/'rake'/. The README documented 0.4, five minors back, and the minitest line permitted only versions the suite no longer runs on.
+
+1. ~ README.md: + the searching, or, not, all_of, header and UnknownSearchKey; + the message accessors, all of them off the one fetch; + .for, .decode, #mailboxes, #source, LoginFailed, and subclassing. Every example run against the suite's mock rather than written from memory.
+2. ~ README.md: + that the gem is published under both names and that one installs one of them.
+3. ~ the gemspecs: /['minitest', '~> 5.0']/'minitest'/. The suite has run on minitest 6 since 0.4.3, which is where it gained require 'minitest/mock'; the line permitted 5.x alone.
+4. ~ the gemspecs: /['rake', '~> 13.0']/'rake'/, nothing being known to break outside it.
+5. ~ CHANGELOG: - the names of other programs and gems throughout. A reader has this repository and no other, so a comparison against software they cannot see is not evidence to them.
+6. ~ CHANGELOG: - the 6 items which recorded no change, the numbering closed up behind them.
+7. ~ Imap::VERSION: /0.10.0/0.11.0/
+
+
 0.10.0: ~ Imap.setup: + Imap::LoginFailed; ~ the gemspecs: /'~> 0.4'/'>= 0.4.5'/ upon net-imap. Imap.setup ignored the false which Imap#login returns when the server rejects the password, and handed back a client which was connected but not logged in.
 
 1. + Imap::LoginFailed
@@ -17,14 +28,13 @@
 
 1. + Imap::Search#all_of: all_of: [{text: 'invoice'}, {text: 'overdue'}] for TEXT invoice TEXT overdue. IMAP has no AND keyword, keys simply sitting side by side, but a hash cannot hold the same key twice, so two terms upon the one key could not be asked for at all: {text: 'a', text: 'b'} keeps b and drops a without a word. Each element is a criteria hash of its own, so or and not nest inside it.
 2. ~ Imap::Search#to_imap_search_keys: + ALL_OF and + ALL, read before the operator tests beside OR and NOT, being none of the three. ALL sat in ALL_SEARCH_KEYS and in neither operator list, so {all: true} raised UnknownSearchKey. It is the key meaning every message, which is precisely what a search with no criteria has to send, so the hash could not express the simplest search there is.
-3. ALL is a case and not a member of BOOLEAN_SEARCH_KEYS, where it appears to belong: each of those defines a method of its own name, and #all is already the alias for #message_ids which the header's own example ends upon. Adding it there redefined the alias silently, which warning = true reported and 0.4.4 turned on for this.
-4. + 5 tests: that all_of ands a list, that it is how the one key carries several terms where a hash cannot, that or and not nest within it, that it sits beside the plain keys, and that {all: true} answers ['ALL'].
-5. ~ Imap::VERSION: /0.8.0/0.9.0/
+3. + 5 tests: that all_of ands a list, that it is how the one key carries several terms where a hash cannot, that or and not nest within it, that it sits beside the plain keys, and that {all: true} answers ['ALL'].
+4. ~ Imap::VERSION: /0.8.0/0.9.0/
 
 
 0.8.0: + Imap::Message.for, the fetch without the search, and a class a program can subclass.
 
-1. + Imap::Message.for(imap_client, message_ids): the batched fetch on its own, .search now being the search and then this. A program which builds its own search keys had no way in: .search couples the two, so search-mail had 159 lines of its own Hit reimplementing the fetch beside it.
+1. + Imap::Message.for(imap_client, message_ids): the batched fetch on its own, .search now being the search and then this. A program which builds its own search keys had no way in, .search coupling the two, and had to reimplement the fetch beside it.
 2. ~ Imap::Message.for: builds with new rather than Imap::Message.new, so that a subclass is handed back its own kind. A program which wants a message of its own, with a mailbox or a decoded body upon it, subclasses rather than starts again.
 3. + 4 tests: that .for builds for ids searched elsewhere, that it fetches once, that it is empty where nothing was found, and that a subclass gets itself back.
 4. ~ Imap::VERSION: /0.7.0/0.8.0/
@@ -58,29 +68,24 @@
 1. + Imap::Search#any_of: or: [{from: 'a@x'}, {to: 'b@y'}]. OR takes two keys and no more, so three or more nest, OR OR a b c, as the server reads them. Each side is a criteria hash of its own and may nest further.
 2. + Imap::Search#none_of: not: {subject: 'Payday'}. NOT takes one key, so several are negated apiece, NOT a NOT b.
 3. ~ Imap::Search#to_imap_search_keys: OR and NOT read before the operator tests, being neither general nor boolean.
-4. HEADER wanted no change: an array value already flattens to ['HEADER', field, value], which nothing said and nothing tested. It is tested now.
-5. + tests for each, and for OR mixed with the plain keys.
-6. ~ Imap::VERSION: /0.4.9/0.5.0/
+4. + tests for each, and for OR mixed with the plain keys.
+5. ~ Imap::VERSION: /0.4.9/0.5.0/
 
 
 0.4.9: + imap.rb.gemspec, so that the gem resolves under both names.
 
 1. + imap.rb.gemspec: the same code published as imap.rb, which is how gems are named here: 21 carry the suffix and imap is one of the few which do not. rubygems has no notion of an alias, so the two are separate gems which must be kept at the same version by hand.
-2. It differs from imap.gemspec in the three lines measurand and namo differ in, the heading comment naming the file, the name, and the gemspec each lists among its own files. Neither ships the other.
-3. imap.rb is unregistered, so this is its first version. bitget, eodhd, measurand and webdav each had their second name join at whatever the first stood at rather than backfilling, and each did it as a patch of its own carrying nothing else.
-4. gem-publish builds and pushes each in turn, gem build and gem push taking one file apiece and gem build *.gemspec building only whichever the shell lists first.
-5. ~ Gemfile: gemspec name: 'imap', bundler refusing to choose between two gemspecs and stopping with "There are multiple gemspecs at ...". Every pair here which uses gemspec names one: webdav, measurand and eodhd each name the elder of their two, and namo, which carried both from its first release, names the bare one. imap is the elder here.
-6. ~ Imap::VERSION: /0.4.8/0.4.9/
+2. ~ Gemfile: gemspec name: 'imap', bundler refusing to choose between two gemspecs and stopping with "There are multiple gemspecs at ...". imap is the elder of the two names.
+3. ~ Imap::VERSION: /0.4.8/0.4.9/
 
 
 0.4.8: Rewrite the CHANGELOG in the standard form.
 
 1. ~ CHANGELOG: ## before each date rather than ## [version] - date, the version and its summary beneath, a blank line between that and the first item, and the items numbered rather than dashed. No item is reworded, dropped or reordered.
 2. ~ CHANGELOG: the dates in basic form, 20260910 for 2026-09-10, as every other gem here writes them.
-3. ~ CHANGELOG: + the title, # imap/CHANGELOG, as coinmarketcap.rb and release-audit have it.
+3. ~ CHANGELOG: + the title, # imap/CHANGELOG.
 4. ~ CHANGELOG: the five releases of 20260917 under one date heading, which is how the form carries more than one in a day.
-5. 9 of the 12 gems here were already in this form; imap and gate.rb were not, which leaves gate.rb.
-6. ~ Imap::VERSION: /0.4.7/0.4.8/
+5. ~ Imap::VERSION: /0.4.7/0.4.8/
 
 0.4.7: ~ Imap::Search: the chaining interface, which the header has documented and which has never run
 
@@ -103,24 +108,24 @@
 
 0.4.5: + Gemfile; ~ imap.gemspec: dependencies=, - spec.date, + metadata
 
-1. + Gemfile: source and gemspec, as switches, eodhd and moby have it, so that the dependencies are declared once in the gemspec rather than restated here to drift. bitget and coinmarketcap restate theirs and are the minority. This was the only gem here with no Gemfile at all.
-2. ~ imap.gemspec: + 'Gemfile' to spec.files, which every other gem here ships.
-3. ~ imap.gemspec: dependencies= and development_dependencies= through the Gem::Specification extension, as switches, eodhd and moby have it and as bitget, coinmarketcap and this did not. The constraints survive: the splat takes a bare string or a [name, constraint] pair alike.
-4. ~ imap.gemspec: - spec.date = '2025-12-20', nine months and two versions stale, and the last one left in the estate. RubyGems answers 1980-01-02 in its place, the reproducible-build epoch, which is what coinmarketcap has carried since dropping its own at 0.6.0.
-5. ~ imap.gemspec: + metadata, the four uris switches and moby declare, so that the RubyGems page links to the issues, the changelog, the source and the README. master here where moby says main, each by the branch it is on.
+1. + Gemfile: source and gemspec, so that the dependencies are declared once in the gemspec rather than restated here to drift.
+2. ~ imap.gemspec: + 'Gemfile' to spec.files.
+3. ~ imap.gemspec: dependencies= and development_dependencies= through the Gem::Specification extension. The constraints survive: the splat takes a bare string or a [name, constraint] pair alike.
+4. ~ imap.gemspec: - spec.date = '2025-12-20', nine months and two versions stale. RubyGems answers 1980-01-02 in its place, the reproducible-build epoch.
+5. ~ imap.gemspec: + metadata, the four uris, so that the RubyGems page links to the issues, the changelog, the source and the README.
 6. ~ Imap::VERSION: /0.4.4/0.4.5/
 
 0.4.4: + Rakefile, - test/test_all.rb
 
 1. + Rakefile: Rake::TestTask over FileList['test/**/*_test.rb'], with libs for lib and test, and warning = true. The minimal form nine of the gems here use rather than the fuller one five use: the :spec alias and the :version task belong to the minority, and a :version task reading VERSION.rb would not have caught 0.4.1, where require 'imap' left Imap::VERSION undefined while VERSION.rb sat there defining it. rake has been a development dependency since 0.4.0 with nothing here to run.
-2. - test/test_all.rb: a second entry point which the Rakefile's FileList makes redundant, and which had drifted from the files on disk in two ways: it never loaded test/Imap/VERSION_test.rb, added in 0.4.2, so it ran 42 tests where there are 44; and it required './Imap_test' for a file named imap_test.rb, which resolved only because the filesystem is case insensitive and would not have on Linux. A glob cannot drift. 14 of the 16 gems here with a Rakefile carry no such file; switches keeps spec/all.rb because its Rakefile targets it, and bitget carries the same redundancy this removes.
+2. - test/test_all.rb: a second entry point which the Rakefile's FileList makes redundant, and which had drifted from the files on disk in two ways: it never loaded test/Imap/VERSION_test.rb, added in 0.4.2, so it ran 42 tests where there are 44; and it required './Imap_test' for a file named imap_test.rb, which resolved only because the filesystem is case insensitive and would not have on Linux. A glob cannot drift.
 3. ~ test/Imap/Message_test.rb: must_match(/Mock body/) for must_match /Mock body/, the ambiguous / which warning = true reports and which is the only warning the suite raises.
-4. ~ imap.gemspec: + 'Rakefile' to spec.files, as eodhd, switches and moby have.
+4. ~ imap.gemspec: + 'Rakefile' to spec.files.
 5. ~ Imap::VERSION: /0.4.3/0.4.4/
 
 0.4.3: ~ test/test_helper.rb: + require 'minitest/mock', which minitest 6 no longer brings
 
-1. ~ test/test_helper.rb: + `require 'minitest/mock'`. 35 of the 42 tests call stub and not one of them could: the suite answered "42 runs, 7 assertions, 0 failures, 35 errors". minitest 5's autorun required minitest/mock and shipped it, so the suite ran until minitest 6 dropped both the require and the file; the same thing coinmarketcap 0.6.1 found.
+1. ~ test/test_helper.rb: + `require 'minitest/mock'`. 35 of the 42 tests call stub and not one of them could: the suite answered "42 runs, 7 assertions, 0 failures, 35 errors". minitest 5's autorun required minitest/mock and shipped it, so the suite ran until minitest 6 dropped both the require and the file.
 2. ~ imap.gemspec: + minitest-mock as a development dependency, which minitest ~> 5.0 carried and minitest 6 does not.
 3. ~ Imap::VERSION: /0.4.2/0.4.3/
 
@@ -130,9 +135,8 @@
 0.4.2: ~ lib/imap.rb: + require_relative './Imap/VERSION'; + test/Imap/VERSION_test.rb
 
 1. ~ lib/imap.rb: + `require_relative './Imap/VERSION'`, last among the requires. The file had been present and unreached, so `require 'imap'` left Imap::VERSION undefined and the gemspec was the only thing loading it.
-2. + test/Imap/VERSION_test.rb: that Imap::VERSION is a string and that it is three numbers separated by dots. Modelled on moby's, less the example comparing against the changelog, which was unreachable here while the file was misspelt.
-3. The test loads the library rather than VERSION.rb, which is the whole of its value: run against v0.4.1 it fails with "uninitialized constant Imap::VERSION". Nine libraries were in that state and not one of them carried this test.
-4. ~ Imap::VERSION: /0.4.1/0.4.2/
+2. + test/Imap/VERSION_test.rb: that Imap::VERSION is a string and that it is three numbers separated by dots. Less the example comparing against the changelog, which was unreachable here while the file was misspelt.
+3. ~ Imap::VERSION: /0.4.1/0.4.2/
 
 
 ## 20260822

data/README.md

@@ -1,11 +1,15 @@
 # imap
 
-A Ruby wrapper around Net::IMAP with an elegant DSL for searching, reading, and managing email.
+A Ruby wrapper around Net::IMAP with a hash-based search interface and messages which answer questions rather than handing back structs.
 
 ## Features
 
-- Clean, hash-based search interface
-- Intuitive message accessors
+- Hash-based search criteria, including OR, NOT and repeated keys
+- Message accessors for dates, flags, size, addresses and attachments
+- RFC 2047 decoding, which Net::IMAP does not do
+- Attachment filenames read out of the BODYSTRUCTURE, which IMAP cannot search upon
+- One fetch for a whole set of messages rather than one per attribute
+- BODY.PEEK throughout, so that reading a message does not mark it read
 - No Rails dependency - works anywhere
 - Zero external dependencies beyond net-imap
 
@@ -29,38 +33,140 @@ Or install it yourself as:
 $ gem install imap
 ```
 
+The gem is published under both `imap` and `imap.rb`. They are the same code; install one.
+
 ## Usage
+
+### Connecting
+
 ```ruby
 require 'imap'
 
-# Connect and authenticate
 imap_client = Imap.setup(
-  server: 'imap.thoran.com',
-  username: 'code@thoran.com',
+  server: 'imap.example.com',
+  username: 'someone@example.com',
   password: 'bigsecret',
   mailbox: 'INBOX' # optional/default
 )
+```
 
+`Imap.setup` raises `Imap::LoginFailed` where the server rejects the password, or where only one of the username and the password is given. `Imap#login` answers true or false for a caller which would rather handle it itself.
+
+`Imap#mailboxes` lists every mailbox which can be selected:
+
+```ruby
+imap_client.mailboxes                   # => ['INBOX', 'INBOX.Archive', ...]
+imap_client.mailbox = 'INBOX.Archive'
+```
+
+### Searching
+
+Criteria are a hash, keyed by the IMAP search keys in lower case:
+
+```ruby
 messages = imap_client.search(
   from: 'noreply@example.com',
   subject: 'Payday Loans',
-  since: '18-DEC-2025',
+  since: '18-Dec-2025',
   seen: false
 )
+```
+
+`or:` takes a list of criteria hashes. IMAP's OR takes two keys, so three or more nest for you:
+
+```ruby
+imap_client.search(or: [{from: 'a@x'}, {to: 'b@y'}, {cc: 'c@z'}])
+```
+
+`not:` negates each key it carries:
+
+```ruby
+imap_client.search(not: {subject: 'Payday'})
+```
+
+`all_of:` is how one key carries several terms, a hash holding it only once:
+
+```ruby
+imap_client.search(all_of: [{text: 'invoice'}, {text: 'overdue'}])
+```
+
+`header:` takes the field and the value:
+
+```ruby
+imap_client.search(header: ['List-Id', 'ruby-talk'])
+```
+
+An unrecognised key raises `Imap::Search::UnknownSearchKey` rather than widening the search silently.
 
-# Access message details
+Where the search keys are built elsewhere, `Imap::Message.for` does the fetch on its own:
+
+```ruby
+Imap::Message.for(imap_client, imap_client.imap.search(['ALL']))
+```
+
+### Messages
+
+A search fetches UID, FLAGS, INTERNALDATE, RFC822.SIZE, ENVELOPE and BODYSTRUCTURE for the whole set in one command, so none of these costs a round trip:
+
+```ruby
 messages.each do |message|
-  puts message.subject
-  puts message.from
-  puts message.to
-  puts message.body
-  puts message.urls # Extracted URLs from body
+  message.uid
+  message.flags                     # => [:Seen]
+  message.seen?
+  message.size                      # bytes
+  message.received_at               # Time, from INTERNALDATE
+  message.sent_at                   # Time, from the Date header
+  message.subject                   # encoded words decoded
+  message.from                      # => 'Café <billing@example.com>'
+  message.from_address              # => 'billing@example.com'
+  message.from_domain               # => 'example.com'
+  message.to                        # => ['user@example.com']
+  message.cc
+  message.attachment?
+  message.attachment_filenames      # => ['résumé.pdf']
 end
+```
 
-# Mark messages as read
-messages.first.mark_as_read
+The body is fetched only when it is asked for:
+
+```ruby
+message.body                        # BODY[TEXT], undecoded
+message.source                      # the whole message, headers and all
+message.urls                        # the URLs found in the body
+message.mark_as_read
+```
+
+`#body` is the raw text part. Choosing a part out of a multipart message and undoing its transfer encoding is MIME work rather than IMAP work, so hand `#source` to the `mail` gem where that is wanted:
+
+```ruby
+mail = Mail.read_from_string(message.source)
+```
 
-# Clean up
+### Decoding
+
+`Imap::Message.decode` reads RFC 2047 encoded words, which headers carry wherever a subject or a name is not ASCII:
+
+```ruby
+Imap::Message.decode('=?UTF-8?B?UsOpc3Vtw6k=?=')   # => 'Résumé'
+```
+
+### Extending
+
+`Imap::Message.search` and `.for` build with `new`, so a subclass is handed back its own kind:
+
+```ruby
+class Message < Imap::Message
+  def body
+    @body ||= Mail.read_from_string(source).text_part.decoded
+  end
+end
+
+Message.for(imap_client, message_ids).first.class   # => Message
+```
+
+### Finishing
+
+```ruby
 imap_client.bye
 ```
 

data/imap.gemspec

@@ -32,9 +32,9 @@ Gem::Specification.new do |spec|
   ]
 
   spec.development_dependencies = [
-    ['minitest', '~> 5.0'],
+    'minitest',
     'minitest-mock',
-    ['rake', '~> 13.0']
+    'rake'
   ]
 
   spec.files = [

data/lib/Imap/VERSION.rb

@@ -1,3 +1,3 @@
 class Imap
-  VERSION = '0.10.0'
+  VERSION = '0.11.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: imap
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.11.0
 platform: ruby
 authors:
 - thoran
@@ -27,16 +27,16 @@ dependencies:
   name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: minitest-mock
   requirement: !ruby/object:Gem::Requirement
@@ -55,16 +55,16 @@ dependencies:
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '13.0'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '13.0'
+        version: '0'
 description: A Ruby wrapper around Net::IMAP with an elegant DSL for searching, reading,
   and managing email.
 email: code@thoran.com