[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35233] Re: Patch to Net::InternetMessageIO

From: mathew <meta@...>
Date: 2011-02-14 21:09:32 UTC
List: ruby-core #35233
On Fri, Feb 11, 2011 at 17:08, Daniel Cormier <daniel.cormier@gmail.com> wrote:
> Perhaps that is a better solution, but shouldn't sending a message
> using DATA work properly whether in ESMTP mode or not?

Yes, and the solution I proposed would work in ESMTP mode and also in
legacy SMTP mode. In ESMTP mode net/smtp would send the data verbatim;
in legacy SMTP mode it would perform the quoting as per your patch.

Basically, I don't think it's a good idea to perform unnecessary
quoting of data when in ESMTP mode.


mathew
-- 
<URL:http://www.pobox.com/~meta/>

In This Thread