- return false if broken?
- return true if @imap
- Redwood::log "connecting to #{@parsed_uri.host} port #{ssl? ? 993 : 143}, ssl=#{ssl?} ..."
-
- ## ok, this is FUCKING ANNOYING.
- ##
- ## what imap.rb likes to do is, if an exception occurs, catch it
- ## and re-raise it on the calling thread. seems reasonable. but
- ## what that REALLY means is that the only way to reasonably
- ## initialize imap is in its own thread, because otherwise, you
- ## will never be able to catch the exception it raises on the
- ## calling thread, and the backtrace will not make any sense at
- ## all, and you will waste HOURS of your life on this fucking
- ## problem.
- ##
- ## FUCK!!!!!!!!!
+ return if broken? || @imap
+ safely { } # do nothing!
+ end
+ synchronized :connect
+
+ def scan_mailbox
+ return if @last_scan && (Time.now - @last_scan) < SCAN_INTERVAL
+ last_id = safely do
+ @imap.examine mailbox
+ @imap.responses["EXISTS"].last
+ end
+ @last_scan = Time.now
+
+ return if last_id == @ids.length
+
+ Redwood::log "fetching IMAP headers #{(@ids.length + 1) .. last_id}"
+ values = safely { @imap.fetch((@ids.length + 1) .. last_id, ['RFC822.SIZE', 'INTERNALDATE']) }
+ values.each do |v|
+ id = make_id v
+ @ids << id
+ @imap_ids[id] = v.seqno
+ end
+ end
+ synchronized :scan_mailbox
+
+ def each
+ ids =
+ @mutex.synchronize do
+ unsynchronized_scan_mailbox
+ @ids
+ end
+
+ start = ids.index(cur_offset || start_offset) or die_from "Unknown message id #{cur_offset || start_offset}.", :suggest_rebuild => true # couldn't find the most recent email
+
+ start.upto(ids.length - 1) do |i|
+ id = ids[i]
+ self.cur_offset = id
+ yield id, @labels.clone
+ end
+ end
+
+ def start_offset
+ unsynchronized_scan_mailbox
+ @ids.first
+ end
+ synchronized :start_offset
+
+ def end_offset
+ unsynchronized_scan_mailbox
+ @ids.last
+ end
+ synchronized :end_offset
+
+ def pct_done; 100.0 * (@ids.index(cur_offset) || 0).to_f / (@ids.length - 1).to_f; end
+
+private
+
+ def unsafe_connect
+ say "Connecting to IMAP server #{host}:#{port}..."
+
+ ## apparently imap.rb does a lot of threaded stuff internally and
+ ## if an exception occurs, it will catch it and re-raise it on the
+ ## calling thread. but i can't seem to catch that exception, so
+ ## i've resorted to initializing it in its own thread. surely
+ ## there's a better way.
+ exception = nil