[sup-devel] new branch: maildir

2010-03-25 Thread Rich Lane
This branch makes some drastic changes to how mbox and maildir sources work. There's no longer any state associated with a source between Sup runs - no cur_offset or mtimes in sources.yaml. Instead, the source queries the index to find out which messages it's already seen and which messages are new

Re: [sup-devel] Accept ASCII_8BIT in String.check

2010-03-25 Thread Johann Klähn
Ah, now it's perfectly clean to me, I guess I just shouldn't do any debugging when I'm too tired. The problem is that the call to Iconv.iconv(target, ..., ...) in Iconv.easy_decode expects target to be typed as "UTF-8", and my environment has $encoding = "utf8". Iconv can't handle this and thus ret

Re: [sup-devel] new branch: maildir

2010-03-25 Thread Mark Alexander
Excerpts from Rich Lane's message of Thu Mar 25 03:12:57 -0400 2010: > This branch makes some drastic changes to how mbox and maildir sources > work. Thanks for attacking this problem! I just took a quick look at the diffs, and I have some concern about this line in maildir.rb: Dir[File.join(s

Re: [sup-devel] new branch: maildir

2010-03-25 Thread Ben Walton
Excerpts from Mark Alexander's message of Thu Mar 25 07:24:59 -0400 2010: > I'm worried about the memory usage with some of my maildirs that > have tens of thousands of files. Would it be more memory-efficient > to use Dir.open and Dir.each? You'd have to filter out "." and > "..", of course. A

Re: [sup-devel] new branch: maildir

2010-03-25 Thread Rich Lane
Excerpts from Mark Alexander's message of 2010-03-25 07:24:59 -0400: > Excerpts from Rich Lane's message of Thu Mar 25 03:12:57 -0400 2010: > > This branch makes some drastic changes to how mbox and maildir sources > > work. > > Thanks for attacking this problem! > > I just took a quick look at t

[sup-devel] [PATCH] Bugfix: for encrypted and signed messages, run verification and decryption separately

2010-03-25 Thread Michael Stapelberg
Hi, attached to this email you can find a patch which runs verification and decryption of signed + encrypted messages separately. This is necessary because GPG will stop decrypting a message when the signature cannot be verified for any reason (like the public key not being in your keyring). Best