Hello all,
I''m happy to report that Sup version 2 is well underway!
Sup version 2 features:
- a client/server model that works over HTTP, allowing
a) development of other clients, e.g. web-based and phone-based
b) simultaneous access from multiple clients
c) IMAP emulation, aka no more lock-in!
- an improved console-based client
Heliotrope, the server component, is close to ready for a version 1 release.
You can find it at https://github.com/wmorgan/heliotrope/.
The client, which I''m calling Turnsole, is coming along swimmingly. I
hope to
release a pre-alpha some-stuff-actually-works version within the next few days.
Much of the UI code has been borrowed from Sup, but the internals are quite
different:
- it''s event-based, rather than thread-based, which streamlines a lot
of the
code and avoids a whole big class of bugs.
- all the index and email threading code is ripped out
- most of the email parsing code is gone
- it handles Ruby 1.9 string encoding stuff correctly, rather than having
random checks scattered around
I think you''re going to like it, since:
- the threads are pre-computed on the server side, so it''s much, much
faster
- you can finally view attachments locally!
Stay tuned for more. We''re still a ways off before it''s a
drop-in replacement,
but I''m excited about how everything is coming together.
--
William <wmorgan-sup at masanjin.net>
Thank you very much. I''ve been using sup for quite a few months now, and I must say that the labels-centric point of view really is an improvement over the other mail management systems. I''ve been following sup news very closely, and I''m really excited about heliotrope/turnsole. I have tried the new system a little bit, and I have a few things to say : - you must have ''html2text'' (not specified) installed on your system, as long as you have any html mail. I think this is the case for too many of us, unfortunately. - I didn''t find rubymail with gem, but found it under the name rmail - I still had some problem with the encoding stuff. I was using ruby v1.9.2 (or so I thought), but got the "ArgumentError - invalid byte sequence in UTF-8" error. Strange thing, the log showed me evidence that I was using ruby v1.9.1 (problems came from files in "/usr/lib/ruby/gems/1.9.1"). So I switched back to v1.8.7 from AUR (I''m using archlinux), and the problem just went away. In the light of what you wrote, I have two questions : - Is sup development bound to be stopped, at least when heliotrope/turnsole will be ready ? - Is there any mailing-list for this new project, or should we keep using those related with sup ? - Do you have any address where I can find and test turnsole ? Again, thank you very much for your work and your help, and I''m talking to everyone on these lists. Regards, -- Matthieu RAKOTOJAONA
On Sun, 27 Mar 2011 20:41:59 +0000, William Morgan <wmorgan-sup at masanjin.net> wrote:> Hello all, > > I''m happy to report that Sup version 2 is well underway! > > Sup version 2 features: > - a client/server model that works over HTTP, allowing > a) development of other clients, e.g. web-based and phone-based > b) simultaneous access from multiple clients > c) IMAP emulation, aka no more lock-in! > - an improved console-based client > > Heliotrope, the server component, is close to ready for a version 1 release. > You can find it at https://github.com/wmorgan/heliotrope/. > > The client, which I''m calling Turnsole, is coming along swimmingly. I hope to > release a pre-alpha some-stuff-actually-works version within the next few days. > Much of the UI code has been borrowed from Sup, but the internals are quite > different: > - it''s event-based, rather than thread-based, which streamlines a lot of the > code and avoids a whole big class of bugs. > - all the index and email threading code is ripped out > - most of the email parsing code is gone > - it handles Ruby 1.9 string encoding stuff correctly, rather than having > random checks scattered around > > I think you''re going to like it, since: > - the threads are pre-computed on the server side, so it''s much, much faster > - you can finally view attachments locally! > > Stay tuned for more. We''re still a ways off before it''s a drop-in replacement, > but I''m excited about how everything is coming together.While mass importing an mbox I got this: $ ... heliotrope-add ... ; forced to decode html. running html2text on 868b mime part... end offset is 237534473 .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub'': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError) from .../heliotrope/lib/heliotrope/decoder.rb:109:in `decode_rfc2047'' from .../heliotrope/lib/heliotrope/message.rb:208:in `decode_header'' from .../heliotrope/lib/heliotrope/message.rb:30:in `parse!'' from bin/heliotrope-add:105:in `<main>'' Best regards, -- Nicolas Pouillard http://nicolaspouillard.fr
On Sun, Mar 27, 2011 at 08:41:59PM +0000, William Morgan wrote:> Hello all, > > I''m happy to report that Sup version 2 is well underway!Hehe, believe me, you''re not the only one happy with this news :)> Sup version 2 features: > - a client/server model that works over HTTP, allowing > a) development of other clients, e.g. web-based and phone-based > b) simultaneous access from multiple clients > c) IMAP emulation, aka no more lock-in! > - an improved console-based client > > Heliotrope, the server component, is close to ready for a version 1 release. > You can find it at https://github.com/wmorgan/heliotrope/.This is something that makes me think that this sup server could be used as an MDA receiving mails directly from the MTA. What currently have is the following env: MTA -> MDA (courier for me) -> MDA Maildir (offlineimap in my case) -> sup (heliotrope) -> Mail reader Why not doing something like this?!: MTA -> sup (heliotrope) -> Mail reader I''ve started to write a web app to read my mails and I''m not using an IMAP, POP or any other of these protocols, it''s based on a python library I''m writting to be generict enough to connect with anything. But I''d love to abandon this abstraction layer in favor of sup :D Cheers, -- Lincoln de Sousa <lincoln at comum.org> xmpp:lincoln at comum.org http://comum.org http://culturadigital.br -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20110328/4b8ad61b/attachment.bin>
Excerpts from Matthieu Rakotojaona''s message of Sun Mar 27 21:14:24 -0700 2011:> Thank you very much....> I''ve been following sup news very closely, and I''m really excited > about heliotrope/turnsole.+1 on encouragement. I switched to sup a few months back and I love it. I''m also very excited about supv2 as it seems you''re working on exactly the sort of things that are, at present, insufficiently awesome about sup. In particular, local viewing of attachments would be very nice.> I have tried the new system a little bit, and I have a few things to say : > - you must have ''html2text'' (not specified) installed on your system, > as long as you have any html mail. I think this is the case for too > many of us, unfortunately.+1 on this for sure. I''m not actually sure why I keep getting HTML only mail from some people, but I presume there''s some tragically popular and not very nice mail client that does this. -- med v?nlig h?lsning David J. Hamilton
Reformatted excerpts from Matthieu Rakotojaona''s message of 2011-03-28:> I have tried the new system a little bit, and I have a few things to say : > - you must have ''html2text'' (not specified) installed on your system, > as long as you have any html mail. I think this is the case for too > many of us, unfortunately. > - I didn''t find rubymail with gem, but found it under the name rmailThanks, I will update the README.> - I still had some problem with the encoding stuff. I was using ruby > v1.9.2 (or so I thought), but got the "ArgumentError - invalid byte > sequence in UTF-8" error.Ok, I''m still working on tracking this down. If you have a backtrace handy, that would be useful.> - Is sup development bound to be stopped, at least when > heliotrope/turnsole will be ready ?I''m planning on moving my efforts entirely over to heliotrope + turnsole. Which isn''t that big of a deal, really, since I haven''t done much on Sup for years.> - Is there any mailing-list for this new project, or should we keep > using those related with sup ?I''ll keep talking about it here until people complain.> - Do you have any address where I can find and test turnsole ?Check back in a few days. -- William <wmorgan-sup at masanjin.net>
Reformatted excerpts from Nicolas Pouillard''s message of 2011-03-28:> .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub'': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError)Hm. I think I know what the problem is. Stay tuned. -- William <wmorgan-sup at masanjin.net>
Reformatted excerpts from Lincoln de Sousa''s message of 2011-03-28:> This is something that makes me think that this sup server could be used as > an MDA receiving mails directly from the MTA.Yeah, this is not so far-fetched. Heliotrope is pretty close to this point altready (e.g. it can take a single raw email on stdin). -- William <wmorgan-sup at masanjin.net>
Reformatted excerpts from Nicolas Pouillard''s message of 2011-03-28:> .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub'': incompatible > character encodings: UTF-8 and ASCII-8BIT > (Encoding::CompatibilityError)Can you try with the latest master? If it still doesn''t work, are you able to narrow down the string encodings of from and word? This 1.9 string encoding stuff is tricky business, especially combined with the messy world of email. I think I''m getting close. -- William <wmorgan-sup at masanjin.net>
On Tue, 29 Mar 2011 04:00:36 +0000, William Morgan <wmorgan-sup at masanjin.net> wrote:> Reformatted excerpts from Nicolas Pouillard''s message of 2011-03-28: > > .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub'': incompatible > > character encodings: UTF-8 and ASCII-8BIT > > (Encoding::CompatibilityError) > > Can you try with the latest master? If it still doesn''t work, are you > able to narrow down the string encodings of from and word? > > This 1.9 string encoding stuff is tricky business, especially combined > with the messy world of email. I think I''m getting close.Nice, it seems to go a lot further. However there seems to be some strange blocking behavior, like using CPU and producing nothing in hours. -- Nicolas Pouillard http://nicolaspouillard.fr
Reformatted excerpts from Nicolas Pouillard''s message of 2011-03-29:> Nice, it seems to go a lot further. However there seems to be some strange > blocking behavior, like using CPU and producing nothing in hours.Weird. I wonder if it''s triggering some regex worst case like we''ve seen before in Sup. Are you able to narrow down what message or text is causing this? I will add a --verbose option, which might make this easier. -- William <wmorgan-sup at masanjin.net>
* On Sun Mar 27 22:41:59 +0200 2011, William Morgan wrote:> Heliotrope, the server component, is close to ready for a version 1 release. > You can find it at https://github.com/wmorgan/heliotrope/.Heliotrope (Actually Time.parse()) crashes on some illegaly formatted dates: /usr/lib/ruby/1.9.1/time.rb:137:in `apply_offset'': undefined method `<'' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.9.1/time.rb:197:in `make_time'' from /usr/lib/ruby/1.9.1/time.rb:261:in `parse'' from /home/ico/external/heliotrope/lib/heliotrope/message.rb:27:in `parse!'' from bin/heliotrope-add:108:in `<main>'' The date of the message was "Wed, 7 2005 22:55: 1 -0180". Fixed by adding a NoMethodError catch: diff --git a/lib/heliotrope/message.rb b/lib/heliotrope/message.rb index 1682062..d63e411 100644 --- a/lib/heliotrope/message.rb +++ b/lib/heliotrope/message.rb @@ -23,7 +23,7 @@ class Message @from = Person.from_string decode_header(validate_field(:from, @m.header["from"])) @date = begin Time.parse(validate_field(:date, @m.header["date"])).to_i - rescue ArgumentError + rescue ArgumentError, NoMethodError #puts "warning: invalid date field #{@m.header[''date'']}" Time.at 0 end -- :wq ^X^Cy^K^X^C^C^C^C
* On Sun Mar 27 22:41:59 +0200 2011, William Morgan wrote:> Heliotrope, the server component, is close to ready for a version 1 release. > You can find it at https://github.com/wmorgan/heliotrope/.Here''s another crash, but I''ve not been able yet to find out what exactly is happening. The problem seems to be caused by a mismatch of multipart mime boundary strings. /home/ico/external/heliotrope/lib/heliotrope/message.rb:151:in `decode_mime_parts'': undefined method `multipart?'' for nil:NilClass (NoMethodError) from /home/ico/external/heliotrope/lib/heliotrope/message.rb:154:in `decode_mime_parts'' from /home/ico/external/heliotrope/lib/heliotrope/message.rb:130:in `mime_parts'' from /home/ico/external/heliotrope/lib/heliotrope/message.rb:116:in `has_attachment?'' from /home/ico/external/heliotrope/lib/heliotrope/index.rb:77:in `add_message'' from bin/heliotrope-add:113:in `<main>'' You have new mail in /home/ico/Maildir I''ve stripped the offending mail down to the following minimal mbox which causes the crash:>From foo at bar.com Tue May 9 11:22:38 2006Date: Tue, 09 May 2006 02:22:18 -0800 From: foo at bar.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="one" Message-Id: <1> --two Part --three -- :wq ^X^Cy^K^X^C^C^C^C