From raasdnil at gmail.com Thu Oct 1 19:45:27 2009 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Fri, 2 Oct 2009 09:45:27 +1000 Subject: [Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby) In-Reply-To: References: <3449FF04-692F-4D67-A5B5-17BC7AFFA790@segment7.net> Message-ID: <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> On Thu, Oct 1, 2009 at 12:11 PM, Eric Hodel wrote: eric, sorry for the late reply. The state of the TMail repo has gone into a bit of disrepair as I have been focusing on my new mail gem to hopefully replace out tmail soonish. But I still want to keep tmail in maintain, just not new features as it is getting unwieldy > On Sep 30, 2009, at 12:41, Eric Hodel wrote: > I started looking into this last test first and determined that there are > two scanners, one written in ruby and one in C. ?(Maybe one of them is out > of date and I'm using the out-of-date one?) We were thinking about ditching the C scanner in TMail.. lot of work for not a lot of gain. > Unfortunately it looks like the Rakefile is broken and `rake test` doesn't > build extensions before starting. ?From setup.rb: Yes... the tool set on TMail is in a bit of a shambles. Someone tried to put a whole new toolset in, and it has never really worked 100%, but they didn't finish, so... guess that's where it is at. > I think, setup.rb should be replaced with Hoe + rake-compiler which are > state-of-the-art. > But I can also give you a toolset that will actually work like your > contribution page says it should. Awesome! Go for it. If you can fork the github repo (http://github.com/mikel/tmail/) and patch to your hearts content, then we'll release a new gem and then backupload it to rubyforge. It's been a long while waiting. Regards Mikel -- http://lindsaar.net/ Rails, RSpec and Life blog.... From maarten at solovirtuoso.com Fri Oct 2 03:47:56 2009 From: maarten at solovirtuoso.com (Maarten Oelering) Date: Fri, 2 Oct 2009 09:47:56 +0200 Subject: [Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby) In-Reply-To: <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> References: <3449FF04-692F-4D67-A5B5-17BC7AFFA790@segment7.net> <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> Message-ID: Hi Mikel, Sorry to hear that maintenance of TMail is on second place now. However, as a developer of email software I am using TMail, but I'm not quite happy with it. Due to the legacy code it is difficult to maintain and extend. RubyMail is a bit cleaner, but it has a low of flaws. For specific purposes, such as parsing received headers, I have written my own parser code. If you plan to develop a completely new gem, think twice about what you are getting into. It is a daunting task to fully understand the RFCs, and also be able to parse the mails that are not fully compliant with RFCs. Did you also think about re-using a proven existing C/C++ library using FFI, such as VMime or GMime? The developer of the Nokogiri HTML/XML parser gem choose to use libxml2 under the hood, and his gem is a big hit! Maarten O. On 2-okt-2009, at 1:45, Mikel Lindsaar wrote: > On Thu, Oct 1, 2009 at 12:11 PM, Eric Hodel > wrote: > > eric, sorry for the late reply. The state of the TMail repo has gone > into a bit of disrepair as I have been focusing on my new mail gem to > hopefully replace out tmail soonish. But I still want to keep tmail in > maintain, just not new features as it is getting unwieldy > >> On Sep 30, 2009, at 12:41, Eric Hodel wrote: >> I started looking into this last test first and determined that >> there are >> two scanners, one written in ruby and one in C. (Maybe one of >> them is out >> of date and I'm using the out-of-date one?) > > We were thinking about ditching the C scanner in TMail.. lot of work > for not a lot of gain. > >> Unfortunately it looks like the Rakefile is broken and `rake test` >> doesn't >> build extensions before starting. From setup.rb: > > Yes... the tool set on TMail is in a bit of a shambles. Someone tried > to put a whole new toolset in, and it has never really worked 100%, > but they didn't finish, so... guess that's where it is at. > >> I think, setup.rb should be replaced with Hoe + rake-compiler >> which are >> state-of-the-art. >> But I can also give you a toolset that will actually work like your >> contribution page says it should. > > Awesome! Go for it. If you can fork the github repo > (http://github.com/mikel/tmail/) and patch to your hearts content, > then we'll release a new gem and then backupload it to rubyforge. > It's been a long while waiting. > > Regards > > Mikel > > -- > http://lindsaar.net/ > Rails, RSpec and Life blog.... > _______________________________________________ > Tmail-talk mailing list > Tmail-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/tmail-talk From raasdnil at gmail.com Fri Oct 2 04:41:29 2009 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Fri, 2 Oct 2009 18:41:29 +1000 Subject: [Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby) In-Reply-To: References: <3449FF04-692F-4D67-A5B5-17BC7AFFA790@segment7.net> <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> Message-ID: <57a815bf0910020141i57194052y6d1af8eb2ef01f25@mail.gmail.com> On Fri, Oct 2, 2009 at 5:47 PM, Maarten Oelering wrote: > Sorry to hear that maintenance of TMail is on second place now. However, as > a developer of email software I am using TMail, but I'm not quite happy with > it. Due to the legacy code it is difficult to maintain and extend. RubyMail > is a bit cleaner, but it has a low of flaws. For specific purposes, such as > parsing received headers, I have written my own parser code. Dear Maarten, Understood on your concerns, the new mail library has been designed with the viewpoint of handling at least everything TMail can and more. I have designed it from the ground up with the RFCs. It is very resilient to error messages, in fact, handles every email in the current TMail test suite without crashing. You can take a look at it and run the specs for it by grabbing http://github.com/mikel/mail In fact... I would really like it if you could run some of your more problematic emails against it and tell me what works and what breaks. Mail works for all RFC 2822 and almost everything in 822 (there are three "out there" obsolete test cases that I don't handle yet). Mail works in 1.8.6, 1.8.7 and 1.9 equally well and runs multiruby -S rake spec on all three versions without an error The only thing I have remaining is auto encode / decode of quoted pair and base64 header fields. Otherwise, it is pretty much ready for a gem release. Plus, it is nice to use, mail can do this right now: Mail.defaults do smtp '127.0.0.1' end Mail.deliver do to 'nicolas at test.lindsaar.net.au' from 'Mikel Lindsaar ' subject 'First multipart email sent with Mail' text_part do body 'Here is the attachment you wanted' end html_part do content_type 'text/html; charset=UTF-8' body '

Funky Title

Here it is

' end add_file :filename => '/path/to/myfile.pdf' end That gets you a multipart alternate email, html and text with a pdf file attached with the correct mime types specified. Oh... and it sends it as well. Anyway, please check it out. if you would like to help maintain TMail, please let me know, would appreciate the help. Regards Mikel From maarten at solovirtuoso.com Fri Oct 2 05:45:58 2009 From: maarten at solovirtuoso.com (Maarten Oelering) Date: Fri, 2 Oct 2009 11:45:58 +0200 Subject: [Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby) In-Reply-To: <57a815bf0910020141i57194052y6d1af8eb2ef01f25@mail.gmail.com> References: <3449FF04-692F-4D67-A5B5-17BC7AFFA790@segment7.net> <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> <57a815bf0910020141i57194052y6d1af8eb2ef01f25@mail.gmail.com> Message-ID: Hi Mikel, Thanks for sharing your new development. I did not realize you were that far. It all sounds very cool. I noticed that you are also using treetop. I have been testing with treetop to parse received headers (RFC 2821 section 4.4). Regards, Maarten On 2-okt-2009, at 10:41, Mikel Lindsaar wrote: > I have designed it from the ground up with the RFCs. It is very > resilient to error messages, in fact, handles every email in the > current TMail test suite without crashing. > > You can take a look at it and run the specs for it by grabbing > http://github.com/mikel/mail > > In fact... I would really like it if you could run some of your more > problematic emails against it and tell me what works and what breaks. > > Mail works for all RFC 2822 and almost everything in 822 (there are > three "out there" obsolete test cases that I don't handle yet). Mail > works in 1.8.6, 1.8.7 and 1.9 equally well and runs multiruby -S rake > spec on all three versions without an error > > The only thing I have remaining is auto encode / decode of quoted pair > and base64 header fields. Otherwise, it is pretty much ready for a > gem release. > > Plus, it is nice to use, mail can do this right now: > > Mail.defaults do > smtp '127.0.0.1' > end > > Mail.deliver do > to 'nicolas at test.lindsaar.net.au' > from 'Mikel Lindsaar ' > subject 'First multipart email sent with Mail' > text_part do > body 'Here is the attachment you wanted' > end > html_part do > content_type 'text/html; charset=UTF-8' > body '

Funky Title

Here it is

Funky Title

Here it is

' > end > add_file :filename => '/path/to/myfile.pdf' > end > > That gets you a multipart alternate email, html and text with a pdf > file attached with the correct mime types specified. > > Oh... and it sends it as well. This is gorgeous. > Anyway, please check it out. > > if you would like to help maintain TMail, please let me know, would > appreciate the help. If you've got this pile of total awesome waiting for release, I'd rather jump on it. I've been thinking about writing a replacement for ActionMailer since it seems largely unmaintaned. Basing it on top of your library would make it only require the templating portion of ActionMailer. (And maybe support for ar_sendmail.) From raasdnil at gmail.com Wed Oct 7 02:56:57 2009 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Wed, 7 Oct 2009 17:56:57 +1100 Subject: [Tmail-talk] `rake test`, `rake setup` are broken (Was: 6 tests fail using OS X 10.5's apple ruby) In-Reply-To: <5AC76CF0-5FAC-4696-8B39-4830089A9DD4@segment7.net> References: <3449FF04-692F-4D67-A5B5-17BC7AFFA790@segment7.net> <57a815bf0910011645y446ebfe6sb26cb8f980d18afd@mail.gmail.com> <57a815bf0910020141i57194052y6d1af8eb2ef01f25@mail.gmail.com> <5AC76CF0-5FAC-4696-8B39-4830089A9DD4@segment7.net> Message-ID: <57a815bf0910062356k188ab892jecbaf9cfefd6fb3f@mail.gmail.com> > If you've got this pile of total awesome waiting for release, I'd rather > jump on it. > > I've been thinking about writing a replacement for ActionMailer since it > seems largely unmaintaned. ?Basing it on top of your library would make it > only require the templating portion of ActionMailer. ?(And maybe support for > ar_sendmail.) Yeah... I want to swap out tmail out of actionmailer and replace it with Mail. it would just abstract SO much out of actionmailer... actionmailer basically tries to "rubyize" tmail if you like. Anyway, probably over the next couple of weeks I'll be wrapping up what I need to do for a 0.1 release of mail. There are some parts of it that need some cleanup and wrap up... The last feature waiting to be handled, as I said, is multilingual header field handling. It's not a lot of work, maybe a couple to three hours of programming... but time time time... I'll see what I can wrap up tonight. Mikel From kollarlaszlo at t-online.hu Tue Oct 20 04:08:06 2009 From: kollarlaszlo at t-online.hu (=?ISO-8859-1?Q?Koll=E1r_L=E1szl=F3?=) Date: Tue, 20 Oct 2009 10:08:06 +0200 Subject: [Tmail-talk] write_back weirdness Message-ID: <1256026086.27039.11.camel@localhost> Hi, When I want to write_back the changes into the raw mail, it insert extra lines ('+ ""' or '+ " "') closed by '\n' ,after every header fields: >>>>> . . Message-Id:+ "" <62B771364F1B524BA81EEFBC51D44ACF0D214F605D at NOK-EUMSG-03.mgdnok.nokia.com> Subject:+ "" =?iso-8859-2?Q?FW:_Az_=E9v_sz=FCl=F5i?= Mime-Version:+ "" 1.0 Content-Type:+ " " multipart/mixed;+ "" boundary=mimepart_4add6c58d0f98_e11..fdb99b9b0426d X-Originalarrivaltime:+ " " 20+ " " Oct+ " " 2009+ " " 07:57:05.0277+ " " (UTC)+ "" FILETIME=[EA44E2D0:01CA515A] Accept-Language:+ "" en-US . . What should I do to remedy this problem? Any advice are wellcome. Thank you Laci From raasdnil at gmail.com Sat Oct 24 22:43:26 2009 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Sun, 25 Oct 2009 13:43:26 +1100 Subject: [Tmail-talk] Mail gem released Message-ID: <57a815bf0910241943v2db7b61mc52a62e9a5ef44ef@mail.gmail.com> Hi all, I just released version 1.0.0 of the new Mail gem. # gem sources -a http://gemcutter.org # gem install mail That will only work if you have gemcutter installed, or : Please check it out. I intend this to replace tmail for ruby 1.9... unless someone else wants to maintain tmail in ruby 1.9. Mikel -- http://lindsaar.net/ Rails, RSpec and Life blog.... From raasdnil at gmail.com Sat Oct 31 07:15:26 2009 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Sat, 31 Oct 2009 22:15:26 +1100 Subject: [Tmail-talk] 1.9 Compat and merging mail gem into ActionMailer Message-ID: <57a815bf0910310415m4370536av315fbc9226e413c9@mail.gmail.com> Hi all of both RoR Core and TMail. You may know me better as the maintainer of TMail. However, TMail has been a bit difficult to get working with Ruby 1.9, so in the light of that, I sat down over the past few months and wrote myself an all encompasing mail gem. Mail passes all of its hundreds of specs equally well in Ruby 1.8.6, 1.8.7 and 1.9.1. Mail reads every email in the TMail test suite without crashing, and is designed to never crash on parsing input (I know, can't really say that, but it is very resilient to crap). The point is that TMail is _not_ 1.9 compatible and is _hard_ to get compatible. Mail is compatible, however needs some more work to make it a TMail replacement. I announced it on Ruby-Talk on the 25th of you are interested, "[ANN] mail 1.0.0" You can get mail from gemcutter, or from http://github.com/mikel/mail But this email is to solicit help and testing of a rewrite of ActionMailer to use the installed mail gem instead of the bundled tmail lib/vendor. I have forked ActionMailer at: http://github.com/mikel/rails/tree/master/actionmailer/ and I welcome help / testing / code on getting this done. Mail is "very" ruby. And we can abstract a LOT of code out of ActionMailer that is already written (or should be written) into Mail. Part handling for example, attachments, nesting multipart/report handling, all is in Mail itself... no need for actionmailer to duplicate it. With very little code changes to ActionMailer, I am down to about 79 errors / failures, most of these are highlighting areas I need to improve mail itself, which is fantastic. But with a bit of help, we can knock this over very fast. Mail is doing fairly well. It needs some refactoring, but I am expecting several .x releases over the next weeks as we refactor and get it working with ActionMailer. Any comments / suggestions, all welcome. -- http://lindsaar.net/ Rails, RSpec and Life blog....