Note for 40tude Dialog users:
Your uuencoded attachments can't be seen my Mozilla/Netscape Mail
or News users unless you remove the headers mentioned below.
On Sun, 24 Dec 2006 23:28:31 -0500, Rinaldi J. Montessi wrote:
> Steve Wertz wrote:
>> This seems to be a problem with all Mozilla newsreaders (SM, TB,
>> and Suite) while viewing messages w/attachments posted my 40tude
>> Dialog.
>
> Interesting problem. I did some searching and found this:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=61810
>
> Read down to item 12 for your solution.
>
>> I've uudecoded the messages manually just fine under Unix. I've
>> added a trailing NL/CR after my sig, and have posted files
>> without blanks or special characters in them. There's no
>> difference I can see between my 40tude Dialog messages and other
>> newsreaders messages/attachments.
>
> Yes, I did that also before investigating further. Wanted to make sure
> the file was properly encoded.
>
>> Can anybody shed any light or tell me how I can debug this?
>
> Following the guidelines in the bug I saved the message, removed all
> MIME and Content headers, restarted the application (SeaMonkey), opened
> the message and the images displayed properly.
Thank you for your help. I did a cursory search of Bugzilla but
it was half-assed and I didn't see that bug report.
I have created a Dialog script and installed it in the trigger
OnBeforeSendingMessage that removes both the MIME-Version: and
Content-Type: headers (Content-Transfer-Encoding: not necessary,
but probably good to remove it just for consistency).
And then posted a couple attachments with Dialog and viewed them
in Seamonkey. Everything works OK. I just hope I didn't break
anything else on other clients. It will remove those headers
form all posts to all [text] groups.
Problem solved. At least for the Mozilla users wishing to see my
posts. Thanks again, Rinaldi.
[Crossposting across servers to news.software.readers]
-sw