Showing posts with label thunderbird. Show all posts
Showing posts with label thunderbird. Show all posts

Tuesday, 1 June 2010

How to see what is in multi-part MIME messages your email prog cannot decode: munpack

Pauline has "Got a nokia e63, takes jpegs. I send it via hotmail using 3 as the server" and I could see some of the pictures she sent in Thunderbird, but not others. Same for my Mum using Windows+some version of Outlook.
 
How to see what is in multi-part MIME messages your email prog cannot decode:


1. From Thunderbird/Evolution/gmail/wherever: Save message (as .eml).
2. $ sudo apt-get install mpack # or equivalent for your OS - install package called "mpack"
3. $ munpack message.eml

# bash, multiple files:
$ for f in *.eml; do munpack $f; done
 
 How to not see it: open it in Thunderbird/Evolution/Outlook
Upgrade Thunderbird to 3.x (ESET antivirus immediatelyu goes crazy scanning Thunderbird indexing Inbox urgh!). Forward to gmail. Try to open .eml with mutt. Thunderbird attachment for viewing emails. Not sure if it would manage to unpack these messages.
http://nic-nac-project.de/~kaosmos/mboximport-en.html
Mutt looking very lovely these days on ubuntu, be careful it will write changes to mail file that it opens!
$ mutt -f ~/.thunderbird/meh.default/ImapMail/meh/INBOX

Where I say "I see same problem." I'm quite wrong :( whoops.
Reverse reverse! Nuns! Pass the retractor please nurse.


https://bugzilla.mozilla.org/show_bug.cgi?id=87653#c28
I see same problem. 
With latest Thunderbird 3.0 (and previous 2.x versions) MIME boundary
containing commas (and other non-alpha chars) doesn't get decoded. MIME message
just shown inline as text not decoded.

Coming from someone using a nokia E65 phone.

2 messages okay:
  boundary="EPOC32-z1G82Qp+YQsMY44N0z3DsrBDJ5L2s9mKj+Ykc140ms_jxhkn"
  boundary="EPOC32-Lx73B+hVbJ5wSRpXTlLKyjwD8YWVf1hg8bHk+'Tssd4tJHbT"

5 messages not okay (note the one without the comma in boundary .. a - at end
of boundary is a problem?):
  boundary="EPOC32-GQ-K-kR,QDS7Gvzz5VbDXdBbM477'73Sc_wWCYc,nmD9fKgf"
  boundary="EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6"
  boundary="EPOC32-0VSK1,9DqPMqGctWX_PyNxx,2+FmXKn5b1DM9_K7yclDZlst"
  boundary="EPOC32-yMNqRYYmV'jRmXlDTj7rtscB8H9mtYrjHfxb0JFc7VyYK47-"
  boundary="EPOC32-WnvGdp2s03kDPHxjvTW,khRc1,4_C-q1BWv_lMZdg6_-CwBs"


The headers seem to have some corruption.
X-OriginalArrivalTime: and Date: header get inserted in To: line which maybe had some end of line chars in a row in it.

This is probably the REAL problem. "probably is when there is a small chance the thing won't happen" - Kate @ dinner this tea-time.

The problem I see seems to be because the email headers have a blank line inside the To: header line. Email readers Thunderbird/Evolution/Outlook/mutt display the message body starting after the blank line in To: line and MIME message type is not detected. nokia + hotmail
munpack extracts attachments okay.

 >From muh  Tue May 11 16:00:42 2010
Return-path:
Envelope-to: muh@meh.mah
Delivery-date: Tue, 11 May 2010 16:00:42 +0100
Received: from meh.hotmail.com ([meh.mah.meh.moo])
    by dspsrv.com with esmtp (Exim 4.71)
    (envelope-from )
    id 1OBqwr-0008WG-4B
    for muh@meh.mah Tue, 11 May 2010 16:00:42 +0100
Received: from meh ([meh.mah.meh.moo]) by meh.hotmail.com with Microsoft SMTPSVC(meh.mah.meh.moo);
     Tue, 11 May 2010 08:00:39 -0700
X-Originating-IP: [meh.mah.meh.moo]
X-Originating-Email: muh@meh.mah
Message-ID:
Received: from [meh.mah.meh.moo] ([meh.mah.meh.moo]) by meh.hotmail.com over TLS secured channel with Microsoft SMTPSVC(meh.mah.meh.moo);
     Tue, 11 May 2010 08:00:24 -0700
From: muh@meh.mah
Reply-to: muh@meh.mah
To: ,
 , ,
X-OriginalArrivalTime: 11 May 2010 15:00:26.0865 (UTC) FILETIME=[B0A6DE10:01CAF11A]
Date: 11 May 2010 08:00:26 -0700

, ,
 , ,
  ,,
  , ,
  ,
 
Subject: Does this mean
Date: Tue, 11 May 2010 16:00:19 +0100
Message-ID:
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
Content-Type: multipart/mixed;
  boundary="EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6"

This is a MIME Message

--EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

text of message muhed mehed and mahed too
--EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6
Content-Type: image/jpeg
Content-Disposition: attachment;
    filename="11052010.jpg"
Content-Transfer-Encoding: base64

/9j/4RusRXhpZgAASUkqAAgAAAAIAA8BAgAGAAAAbgAAABABAgAEAAAARTYz
ABIBAwABAAAAAQAAABoBBQABAAAAdAAAABsBBQABAAAAfAAAACgBAwABAAAA
AgAAABMCAwABAAAAAQAAAGmHBAABAAAAhAAAAKoBAABOb2tpYQAsAQAAAQAA
.
.
9pceYAFO7jp7VV1NAkxKD7wzg1E04yEmmivbSOjZwRnqPWr28FVPbINataXI
vpY//9k=

--EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6--

Monday, 16 July 2007

svn switch in svn FAQ (and posting patch without attatchment - DOH!)

Yay! :) The svn people go fast.

FAQ into svn svn and onto web while we were away visiting Cobh for the weekend.
http://subversion.tigris.org/faq.html#switch-problems

I investigated the svn switch thing and make a FAQ entry but then
started to understand the problem so had to investigate more and
revise emails and the FAQ entry I had made. A few late nights last week.

Anyway eventually got everything together and posted to the svn dev list.
WITHOUT the patch for the FAQ entry!!! :( DOH.
But clever svn person Karl Fogel got it from the copy I put up for review.
And everyone is very nice on the dev and users list.

For Thunderbird I have found this: Check and Send extension:
https://addons.mozilla.org/en-US/thunderbird/addon/2281
YouI have to configure it and add list of attach keywords "attach|patch|attached|attachment"
it works! Warning dialog and lots of lovely yellow highlighting.

My internal paranoid over-shoulder watcher has not been good last week.
With root too :(
It's very twitchy now though.

  user@develop$ cd
  user@develop$ ls -al
   [ lots of stuff owned as root ]
  user@develop$  su -
  password:
  root@develop$ chown -r user:user .
  *AUGH!*

  telnet was method of connecting to machine and telnet in broken after that  spectacularily unspectacular method of making a huge mess. :(