From: James Edward Gray II <james@...>
Date: 2007-11-05T01:50:13+09:00
Subject: Re: Gateway Upgraded

Mikel, I have some TMail questions for you…

On Nov 3, 2007, at 11:10 AM, Douglas Wells wrote:

> In article  
> <57a815bf0711030047x813fe18r6f6d79c1be251092@mail.gmail.com>,
>   raasdnil@gmail.com writes:
>> Thanks for your work James.
>>
>>>> According to my scan of the log this morning, every email the  
>>>> gateway
>>>> sent since yesterday's upgrade was accepted by Usenet.  I was even
>>>> able to find messages modified by the gateway and they looked great
>>>> on comp.lang.ruby.
>>>>
>>>> This transition appears to be a success.
>>>>
>>>> James Edward Gray II
>
> Well, there appears to be at least one little glitch remaining.
> The following header line in the immediately referenced article
> shouldn't appear with an unencoded article body:
>
>     Content-Transfer-Encoding: Base64

This was caused by some code like:

   incoming = TMail::Mail.parse($stdin.read)
   outgoing = TMail::Mail.new

   outgoing.transfer_encoding = incoming.transfer_encoding
   outgoing.body              = incoming.body

I assume that's because TMail is undoing the Base64 encoding for me  
and not putting it back to match the transfer_encoding() of  
outgoing.  Do I have that right?

What's the best way for us to fix this?  Should I not copy the  
transfer encoding of the original message?  Will TMail normalize all  
of them for me?  What does it normalize to?  Maybe I should declare  
that.

Note that the affected message here was not one the gateway does any  
translation for, so this is going to be a widespread issue with the  
new gateway and we need to find a sensible solution for it.

> And just as a side remark, I'll note that the following comment
> should be wrapped at normal text width.
>
>     X-Received-From: This message has been automatically forwarded  
> from the
>         ruby-talk mailing list by a gateway at comp.lang.ruby. If  
> it is SPAM, it did
>         not originate at comp.lang.ruby. Please report the original  
> sender, and not
>         us. Thanks! For more details about this gateway, please  
> visit: http://blog.grayproductions.net/categories/the_gateway

Mikel, why is TMail not wrapping this?  I know you added some checks  
to ignore X-* headers, but shouldn't it only ignore them if they  
aren't easily wrapped?  This one has a lot of whitespace in it, so  
it's wrappable, right?

Thanks for the help.

James Edward Gray II