From raasdnil at gmail.com Thu Apr 10 15:56:56 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Fri, 11 Apr 2008 05:56:56 +1000 Subject: [Tmail-talk] [ANN] TMail 1.2.3 - Security Update Message-ID: <57a815bf0804101256r5386a6b5nabd909bc9ff572d6@mail.gmail.com> [ANN] TMail 1.2.3 - Security Update - 11 Apr 2008 IMPORTANT NOTE: ------------------- This is a recommended upgrade for all TMail users of TMail version 1.0.0 or above (which includes all Rails 2.x users - see below) Information: ------------------- TMail is an e-mail handling library for Ruby! TMail is the Ruby Mail handler used in the Ruby on Rails and Nitro web frame works as well as many others (including, the Ruby Talk mail gateway). TMail is a gem. You can install it on any platform via: # gem install tmail Alternatively you can download the source code or view extra documentation at the website: http://tmail.rubyforge.org/ Release Summary: ------------------ This update handles a potential DOS vulnerability on any host using TMail to handle incomming email; a crafted email with carefully positioned whitespace can cause the TMail library to go into an endless loop causing denial of service attack on email services. Ruby on Rails and Nitro users need to just do a "gem update tmail" to get this security patch applied to their web framework. All other users of course, just need to "gem update tmail" as well. New release handles five tickets in the TMail tracker as well as more documentation and more work on the moving target of Ruby 1.9's character set Encoding/Decoding functionality. Additionally added 7 more test cases to the library to handle the above tickets. This should be a drop in replacement for existing TMail installations - unless you are using TMail on Ruby 1.9, in which case, you _might_ run into encoding problems if you are on Ruby 1.9.1, Ruby 1.9 still works (pre January 2008 release), YMMV, any feedback on TMail on Ruby 1.9.1 with patches is really welcome! Release Update Details: ------------------------- * Closed #18881 - TMail goes into an endless loop if sent an crafted email which puts a whitespace character at position 78 of the line to be wrapped. * Closed #19203 - TMail errors in Ruby 1.9.1 on invalid multibyte chars. * Closed #18814 - Fixed attchment.rb failing on mail part that had a nil content-type - now assumes text/plain as the missing content type and preserves the mail structure. * Closed #18516 - Fixed TMail::Mail#preamble, and added #preamble=, this allows you now to set and read the preamble text of an email (the plain text that appears before any MIME encoded attachments that you can read in any email client) (Charles Lowe) * Closed #18515 - Removed ftools from test case to clean it up (Charles Lowe) Bug Reports / Fixes: ---------------------- As always, we really welcome any bug reports or code for patches you have created. Please submit anything you find through our RubyForge tracker project which you can get to from our website: http://tmail.rubyforge.org/ We hope you enjoy this release! The TMail Team. Changes: === 1.2.2 / 2008-03-07 * Fixed install bug with gem pacakge (1.2.1 was not compiling on gem install) * A _LOT_ more documentation...! * More documentation - (Mikel) * Applied Ruby 1.9 patches to the library - All tests passing now - (Mikel) * Closed #17719 - Fixed UNIXMbox code - readonly was not working and raising an exception. Now works. * Closed #18038 - Multiple froms not being parsed correctly, added a test case to cover this and show the correct handling - (Mikel) === 1.2.1 / 2008-01-11 * More documentation (Mikel) * Added 15 test cases from the Rails ActionMailer to TMail * Changed mailscanner to tmailscanner (mailscanner is copyrighted) * Closed Bug - Handled quote boundary being gready on content-type header (M. Mondragon) * Closed #16025 - Fixed scanner.rb so it passes same tests as scanner.c * Closed #16283 - Handled incorrect decoding of attachments (M. Aoki - garyo) * Closed #16899 - HeaderField.new_from_port and added test cases to cover this code (Maarten O.) * Closed #16900 - UNIXMbox.fromaddr missing port param and does not return Envelope Sender (Maarten O.) === 1.2.0 / 2007-11-29 * 5 major enhancements: * Extensive documentation work. (mikel) * Renamed scanner_c.c to mailscanner.c. (trans) * Removed base64 c extension. It's speed benefit was negligable (only 0.2 sec over 10000 sizable encode/decode runs) (trans) * Closed 15445 - TMail::Mail#create_forward now returns a new Mail object that has the original mail as an encoded 7 bit multipart attachment. Also moved create_forward and create_reply from tmail/net into tmail/interface as it makes more sense to have it there. (mikel) * Closed 15643 - TMail::Mail#reply_addresses was returning an empty array if reply_to was set to nil (ie, the header field existed but was empty) instead of returning the from address or default. (mikel) * Closed 16025 - TMail scanner.rb would not parse ATOM chars correctly making it fail tests where the C version passed them. Fixed this by updating the Scanner.rb version to be in step with the C version (there was an extra @ symbol in the ATOM CHARS definition that was not in the C version.) (mikel) * Fixed scanner.rb so that it would pass the same tests that the C version does - had a sundry @ symbol inside of the ATOM CHARS * 3 minor enhancements: * Renamed scanner_c.c to tmailscanner.c (trans) * Changed TMail::Mail#sender to have a default "default" value of nil to be in alignment with all the other interface methods (mikel) * Made base64_decode and base64_encode into ! versions as they are destructive on the mail body (encodes the body to base64 or decodes it), made aliases for base64_decode and base64_encode to point back to the bang versions. Doing this with a view to change base64_encode to a non destructive version (returns the encoded body) in future versions. (mikel) === 1.1.1 / 2007-11-05 * 3 major enhancement: * Created unified package, for installation in any platform. * Added require_arch.rb to facilitate multi-platform support. * If compilation fails, set NORUBYEXT="true" and reinstall. * 3 minor enhancement: * Fixed line wrapping of long header fields so that they wrap at the correct whitespace points. * Fixed bug where re-assigning the mail.body to existing mail object that already had a parsed body would not re-parse the body. * Started documenting the source code... lots more to do. === 1.1.0 / 2007-10-28 * 1 minor enhancements: * Changed the quoting of paramaters in the header fields to wrap double quotes around fields that are needed to be quoted. * Removed keeping double quotes around a filename that does not need double quotes per RFC 1521 * More clean up and getting tests passing. Now standing at 2 failures out of 3366 assertions. One is the incorrect handling of "@"@test.com (returns @@test.com) and the other is a japanese encoding issue. === 1.0.0 / 2007-10-28 * 1 major enhancement: * TMail is now released as a GEM! * 2 minor enhancements: * Fixed bug 15077 - TMail now recognizes attachments as soon as they are added to the body. * Refactored handling of quotations in header fields - now cleaner From zeljko.filipin at gmail.com Fri Apr 11 03:35:39 2008 From: zeljko.filipin at gmail.com (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Fri, 11 Apr 2008 09:35:39 +0200 Subject: [Tmail-talk] Error installing tmail Message-ID: I can not install tmail-1.2.2 and tmail-1.2.3. Install works fine for tmail-1.2.1 and earlier. I could not find this problem searching the Internet (I found one page, but in Japanese) or in your bug tracker. Should I put it in bug tracker? R:\>gem install tmail Building native extensions. This could take a while... ERROR: Error installing tmail: ERROR: Failed to build gem native extension. c:/ruby/bin/ruby.exe extconf.rb install tmail creating Makefile nmake 'nmake' is not recognized as an internal or external command, operable program or batch file. Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/tmail-1.2.3 for inspection. Results logged to c:/ruby/lib/ruby/gems/1.8/gems/tmail-1.2.3/ext/tmailscanner/tmail/gem_make.out ?eljko Filipin -- ZeljkoFilipin.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/tmail-talk/attachments/20080411/5817d8e5/attachment.html From raasdnil at gmail.com Fri Apr 11 05:12:24 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Fri, 11 Apr 2008 19:12:24 +1000 Subject: [Tmail-talk] Error installing tmail In-Reply-To: References: Message-ID: <57a815bf0804110212t175acdeqb8979a842e9235e1@mail.gmail.com> > I can not install tmail-1.2.2 and tmail-1.2.3. Install works fine for > tmail-1.2.1 and earlier. I could not find this problem searching the > Internet (I found one page, but in Japanese) or in your bug tracker. Should > I put it in bug tracker? Yes, please file a ticket. You can get to the project via http://tmail.rubyforge.org/ We will get this fixed ASAP. Regards Mikel From zeljko.filipin at gmail.com Fri Apr 11 05:55:09 2008 From: zeljko.filipin at gmail.com (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Fri, 11 Apr 2008 11:55:09 +0200 Subject: [Tmail-talk] Error installing tmail In-Reply-To: <57a815bf0804110212t175acdeqb8979a842e9235e1@mail.gmail.com> References: <57a815bf0804110212t175acdeqb8979a842e9235e1@mail.gmail.com> Message-ID: On Fri, Apr 11, 2008 at 11:12 AM, Mikel Lindsaar wrote: > please file a ticket Done. http://rubyforge.org/tracker/index.php?func=detail&aid=19429&group_id=4512&atid=17370 ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/tmail-talk/attachments/20080411/f1647239/attachment.html From raasdnil at gmail.com Fri Apr 11 08:23:12 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Fri, 11 Apr 2008 22:23:12 +1000 Subject: [Tmail-talk] Error installing tmail In-Reply-To: References: <57a815bf0804110212t175acdeqb8979a842e9235e1@mail.gmail.com> Message-ID: <57a815bf0804110523o6c0c4d7sd9b053e09272f843@mail.gmail.com> On Fri, Apr 11, 2008 at 7:55 PM, ?eljko Filipin wrote: > On Fri, Apr 11, 2008 at 11:12 AM, Mikel Lindsaar wrote: > > please file a ticket > Done. > http://rubyforge.org/tracker/index.php?func=detail&aid=19429&group_id=4512&atid=17370 This is now fixed and I released TMail 1.2.3.1 Sorry about that. Mikel From zeljko.filipin at gmail.com Fri Apr 11 08:54:06 2008 From: zeljko.filipin at gmail.com (=?UTF-8?Q?=C5=BDeljko_Filipin?=) Date: Fri, 11 Apr 2008 14:54:06 +0200 Subject: [Tmail-talk] Error installing tmail In-Reply-To: <57a815bf0804110523o6c0c4d7sd9b053e09272f843@mail.gmail.com> References: <57a815bf0804110212t175acdeqb8979a842e9235e1@mail.gmail.com> <57a815bf0804110523o6c0c4d7sd9b053e09272f843@mail.gmail.com> Message-ID: On Fri, Apr 11, 2008 at 2:23 PM, Mikel Lindsaar wrote: > This is now fixed and I released TMail 1.2.3.1 Thanks. I tried it and it works. :) ?eljko -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/tmail-talk/attachments/20080411/4e058057/attachment.html From jose at stat.ucla.edu Mon Apr 14 14:41:56 2008 From: jose at stat.ucla.edu (Jose Hales-Garcia) Date: Mon, 14 Apr 2008 11:41:56 -0700 Subject: [Tmail-talk] Capturing first found headers Message-ID: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> I'm using Tmail to parse quarantined messages. Some of these messages will contain the headers that I am interested in multiple times. In these cases the last header is retained. How do I parse the headers so the first header encountered is retained. Thank you, Jose From raasdnil at gmail.com Mon Apr 14 20:13:57 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Tue, 15 Apr 2008 10:13:57 +1000 Subject: [Tmail-talk] Capturing first found headers In-Reply-To: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> References: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> Message-ID: <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> On Tue, Apr 15, 2008 at 4:41 AM, Jose Hales-Garcia wrote: > I'm using Tmail to parse quarantined messages. Some of these messages > will contain the headers that I am interested in multiple times. In > these cases the last header is retained. How do I parse the headers > so the first header encountered is retained. Which headers are you talking about? If it is any of 'orig-date', 'from', 'sender' 'reply-to' 'to' 'cc' 'bcc' 'message-id' 'in-reply-to' 'references' or 'subject', then these are only ever meant to appear once. Regards Mikel From jose at stat.ucla.edu Mon Apr 14 23:56:31 2008 From: jose at stat.ucla.edu (Jose Hales-Garcia) Date: Mon, 14 Apr 2008 20:56:31 -0700 Subject: [Tmail-talk] Capturing first found headers In-Reply-To: <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> References: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> Message-ID: On Apr 14, 2008, at 5:13 PM, Mikel Lindsaar wrote: > Which headers are you talking about? If it is any of 'orig-date', > 'from', 'sender' 'reply-to' 'to' 'cc' 'bcc' 'message-id' 'in-reply-to' > 'references' or 'subject', then these are only ever meant to appear > once. The headers are: X-Spam-Flag, X-Spam-Score, X-Spam-Level, X-Spam- Status (see example message below). These headers are being generated for my domain's emails by Amavis-new. I've consulted with the Amavis developers and found a way to strip the conflicting headers. When they're not stripped though, theTMail parse method retains the last 'X- Spam-Score' header encountered, i.e. in the example below, it retains the header with a value of '*****' instead of the one with '16.07'. In my discussions with Amavis core, the point was made that there is no definition of the headers that states that they occur only once. I haven't corroborated this but at least it's true for the spam email I''m processing, where headers are often times unconventional. I'll be doing the techniques suggested by Amavis core to strip the excess headers, but before the idea was suggested, I was considering looking at the parse method to see how I could get it to use an array instead of a hash to store the header data. Jose ....................................................... Jose Hales-Garcia UCLA Department of Statistics jose at stat.ucla.edu Return-Path: <> Delivered-To: spam-quarantine X-Envelope-From: X-Envelope-To: <********@stat.ucla.edu> X-Quarantine-ID: X-Spam-Flag: YES X-Spam-Score: 16.07 X-Spam-Level: **************** X-Spam-Status: Yes, score=16.07 tag=-1000 tag2=6.31 kill=6.31 tests=[BAYES_50=4, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=2, RCVD_NUMERIC_HELO=2.067, URIBL_RED=0.001, URIBL_SC_SURBL=4, URIBL_WS_SURBL=4] Received: from smtp.stat.ucla.edu ([127.0.0.1]) by localhost (mta.stat.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u79lpchtlym0 for <********@stat.ucla.edu>; Mon, 14 Apr 2008 11:43:15 -0700 (PDT) Received: from smtp-13.smtp.ucla.edu (smtp-13.smtp.ucla.edu [169.232.46.249]) by smtp.stat.ucla.edu (Postfix) with ESMTP id E8037C42DB2 for <********@stat.ucla.edu>; Mon, 14 Apr 2008 11:43:15 -0700 (PDT) Received: from dino.ess.ucla.edu (dino.ess.ucla.edu [128.97.31.199]) by smtp-13.smtp.ucla.edu (8.14.2/8.14.2) with ESMTP id m3EIhFZM010543 for <********@stat.ucla.edu>; Mon, 14 Apr 2008 11:43:15 -0700 X-geo_ess_ucla_edu_-MailScanner-Watermark: 1208803395.11439 at cjEzhdOLK6XsMz6gYSCtog Received: from zephyr.ess.ucla.edu (zephyr [128.97.31.1]) by dino.ess.ucla.edu (8.13.8+Sun/8.13.8) with ESMTP id m3EIhFhq010692 for <*****@dino.ess.ucla.edu>; Mon, 14 Apr 2008 11:43:15 -0700 (PDT) Received: from 79.26.30.109 (host109-30-dynamic.26-79- r.retail.telecomitalia.it [79.26.30.109]) by zephyr.ess.ucla.edu (8.12.10+Sun/8.12.10) with ESMTP id m3EIkj1l010876 for <*****@ess.ucla.edu>; Mon, 14 Apr 2008 11:46:46 -0700 (PDT) Message-ID: <000701c89e5f$04790d3c$05ddcca4 at xrdtca> From: "hobard leanne" To: <*****@ess.ucla.edu> Subject: *****'s hidden cam video Date: Mon, 14 Apr 2008 16:55:27 +0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01C89E5F.0478ED4C" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-geo_ess_ucla_edu_-MailScanner-Information: Please contact the ISP for more information X-geo_ess_ucla_edu_-MailScanner: Found to be clean X-geo_ess_ucla_edu_-MailScanner-From: nlycaznwklq at yourpcstuff.com X-Spam-Status: No X-Probable-Spam: no X-Spam-Hits: 4.702 X-Spam-Score: ***** X-Spam-Report: HTML_MESSAGE ,NORMAL_HTTP_TO_IP,RCVD_NUMERIC_HELO,URIBL_RED,URIBL_WS_SURBL X-Scanned-By: smtp.ucla.edu on 169.232.46.249 From raasdnil at gmail.com Tue Apr 15 00:09:16 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Tue, 15 Apr 2008 14:09:16 +1000 Subject: [Tmail-talk] Capturing first found headers In-Reply-To: References: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> Message-ID: <57a815bf0804142109p5c409680ja5fdf988b179a463@mail.gmail.com> On Tue, Apr 15, 2008 at 1:56 PM, Jose Hales-Garcia wrote: > On Apr 14, 2008, at 5:13 PM, Mikel Lindsaar wrote: > > Which headers are you talking about? If it is any of 'orig-date', > > 'from', 'sender' 'reply-to' 'to' 'cc' 'bcc' 'message-id' 'in-reply-to' > > 'references' or 'subject', then these are only ever meant to appear > > once. > In my discussions with Amavis core, the point was made that there is > no definition of the headers that states that they occur only once. I > haven't corroborated this but at least it's true for the spam email > I''m processing, where headers are often times unconventional. Hmm, that is a bug in tmail then. It should preserve those X headers, regardless of the number of times they occur. Could you raise a ticket at http://tmail.rubyforge.org/ ? Click on the project tab and then the tracker. Regards Mikel From jose at stat.ucla.edu Tue Apr 15 00:44:40 2008 From: jose at stat.ucla.edu (Jose Hales-Garcia) Date: Mon, 14 Apr 2008 21:44:40 -0700 Subject: [Tmail-talk] Capturing first found headers In-Reply-To: <57a815bf0804142109p5c409680ja5fdf988b179a463@mail.gmail.com> References: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> <57a815bf0804142109p5c409680ja5fdf988b179a463@mail.gmail.com> Message-ID: <342D40FA-6180-4B29-83B2-A709FE77CB4C@stat.ucla.edu> On Apr 14, 2008, at 9:09 PM, Mikel Lindsaar wrote: > Could you raise a ticket at http://tmail.rubyforge.org/ ? Click on > the project tab and then the tracker. Done. Let me know anything else you need. Thanks, Jose ....................................................... Jose Hales-Garcia UCLA Department of Statistics jose at stat.ucla.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/tmail-talk/attachments/20080414/5dde13fc/attachment.html From raasdnil at gmail.com Tue Apr 15 04:56:14 2008 From: raasdnil at gmail.com (Mikel Lindsaar) Date: Tue, 15 Apr 2008 18:56:14 +1000 Subject: [Tmail-talk] Capturing first found headers In-Reply-To: <342D40FA-6180-4B29-83B2-A709FE77CB4C@stat.ucla.edu> References: <7619BA67-A3B9-4671-9A62-8234FE4096BC@stat.ucla.edu> <57a815bf0804141713j4fb288d7qa5c1116b892bcad7@mail.gmail.com> <57a815bf0804142109p5c409680ja5fdf988b179a463@mail.gmail.com> <342D40FA-6180-4B29-83B2-A709FE77CB4C@stat.ucla.edu> Message-ID: <57a815bf0804150156v53bf7349gae766b650996f8d5@mail.gmail.com> On Tue, Apr 15, 2008 at 2:44 PM, Jose Hales-Garcia wrote: > On Apr 14, 2008, at 9:09 PM, Mikel Lindsaar wrote: > Could you raise a ticket at http://tmail.rubyforge.org/ ? Click on > the project tab and then the tracker. > Done. Let me know anything else you need. Heh... a working, submitted patch? :p :D I'll get onto it. Mikel From jonathan.stott at gmail.com Wed Apr 16 10:58:50 2008 From: jonathan.stott at gmail.com (Jonathan Stott) Date: Wed, 16 Apr 2008 15:58:50 +0100 Subject: [Tmail-talk] Simple Parsing Example fails Message-ID: <20080416155850.5d60dca4@hzhangpg02.ph.man.ac.uk> Hey all I'm trying to use TMail to parse some emails in my inbox, and to strip the pictures from them, saving them to another directory, for what will eventually become a claws action. It's a very simple script, which I saved to a pastie ( http://pastie.caboo.se/181721 ). When I run it, it takes a noticeable amount of time to run, but doesn't output any images, or any information from the inspect. Any pointers would be appreciated, Jon From jonathan.stott at gmail.com Wed Apr 16 13:13:39 2008 From: jonathan.stott at gmail.com (Jonathan Stott) Date: Wed, 16 Apr 2008 18:13:39 +0100 Subject: [Tmail-talk] Simple Parsing Example fails In-Reply-To: <20080416155850.5d60dca4@hzhangpg02.ph.man.ac.uk> References: <20080416155850.5d60dca4@hzhangpg02.ph.man.ac.uk> Message-ID: <20080416181339.39ea67a0.jonathan.stott@gmail.com> > Hey all > > I'm trying to use TMail to parse some emails in my inbox, and to strip the pictures from them, saving them to another directory, for what will eventually become a claws action. It's a very simple script, which I saved to a pastie ( http://pastie.caboo.se/181721 ). When I run it, it takes a noticeable amount of time to run, but doesn't output any images, or any information from the inspect. > > Any pointers would be appreciated, > Jon > > As an addendum to this email, if I seperate things out somewhat, to add: email = TMail::Mail.load ( ARGV[0] ) puts email.body email.attachments ... Then it shows that the message has several attachments, though still, the block isn't called. Regards, Jonathan From aquasync at gmail.com Wed Apr 16 18:12:11 2008 From: aquasync at gmail.com (charles) Date: Thu, 17 Apr 2008 08:12:11 +1000 Subject: [Tmail-talk] Simple Parsing Example fails In-Reply-To: <20080416181339.39ea67a0.jonathan.stott@gmail.com> References: <20080416155850.5d60dca4@hzhangpg02.ph.man.ac.uk> <20080416181339.39ea67a0.jonathan.stott@gmail.com> Message-ID: <89bd8880804161512h2f2e0a49v52debc9cc86718da@mail.gmail.com> I think you'd need to change it to ".attachments.each do |attach|" no? On Thu, Apr 17, 2008 at 3:13 AM, Jonathan Stott wrote: > > Hey all > > > > I'm trying to use TMail to parse some emails in my inbox, and to strip > the pictures from them, saving them to another directory, for what will > eventually become a claws action. It's a very simple script, which I saved > to a pastie ( http://pastie.caboo.se/181721 ). When I run it, it takes a > noticeable amount of time to run, but doesn't output any images, or any > information from the inspect. > > > > Any pointers would be appreciated, > > Jon > > > > > > As an addendum to this email, if I seperate things out somewhat, to add: > > email = TMail::Mail.load ( ARGV[0] ) > > puts email.body > > email.attachments ... > > Then it shows that the message has several attachments, though still, the > block isn't called. > > Regards, > Jonathan > _______________________________________________ > Tmail-talk mailing list > Tmail-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/tmail-talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/tmail-talk/attachments/20080417/515f4490/attachment-0001.html From jonathan.stott at gmail.com Wed Apr 16 18:44:27 2008 From: jonathan.stott at gmail.com (Jonathan Stott) Date: Wed, 16 Apr 2008 23:44:27 +0100 Subject: [Tmail-talk] Simple Parsing Example fails In-Reply-To: <89bd8880804161512h2f2e0a49v52debc9cc86718da@mail.gmail.com> References: <20080416155850.5d60dca4@hzhangpg02.ph.man.ac.uk> <20080416181339.39ea67a0.jonathan.stott@gmail.com> <89bd8880804161512h2f2e0a49v52debc9cc86718da@mail.gmail.com> Message-ID: <14cf210a0804161544x13e7af35uad394b30549eb88e@mail.gmail.com> On Wed, Apr 16, 2008 at 11:12 PM, charles wrote: > I think you'd need to change it to ".attachments.each do |attach|" no? ... ... Yes. Yes, I would. ^^; Ooops. Oh well, thank you for pointing out the obvious for me :) Regards, Jon