 |
|
| Linux Forum Index » Linux Hardware » Newegg invoices (OT)... |
|
Page 1 of 1 |
|
| Author |
Message |
| brownh... |
 Posted: Fri Oct 30, 2009 4:16 pm |
|
|
|
Guest
|
Sorry for this being OT, but this forum is where I'm most likely to
find people with the same problem.
When I order hardware from Newegg, the e-mail invoices and tracking
information messages are sent with broken MIME content (yes, they use
a Windows MUA).
Apparently they find it necessary for some reason to send these
messages as binary files, and so they are MIME'd, but lack the header
necessary for my mail utility (mutt) to umime them. Usually I
deal with this situation by pasting in a standard header and then
un-miming with with munpack, but in the case of the Newegg messages,
munpack can't recognized them as MIME.
Anyone with a similar problem and who might offer work-arounds?
Haines Brown |
|
|
| Back to top |
|
|
|
| Thad Floryan... |
| Posted: Fri Oct 30, 2009 5:18 pm |
|
|
|
Guest
|
On 10/30/2009 3:16 PM, brownh wrote:
Quote: Sorry for this being OT, but this forum is where I'm most likely to
find people with the same problem.
When I order hardware from Newegg, the e-mail invoices and tracking
information messages are sent with broken MIME content (yes, they use
a Windows MUA).
Apparently they find it necessary for some reason to send these
messages as binary files, and so they are MIME'd, but lack the header
necessary for my mail utility (mutt) to umime them. Usually I
deal with this situation by pasting in a standard header and then
un-miming with with munpack, but in the case of the Newegg messages,
munpack can't recognized them as MIME.
Anyone with a similar problem and who might offer work-arounds?
Haines Brown
FWIW, Thunderbird handles the Newegg messages just fine and, until your
posting, I didn't notice their emails were binary encoded. Following is
the header from one of my Newegg purchase emails earlier this year (in
case you are unable to access full headers on your system), with a "|"
prepended to each line; this one is a UPS tracking info email:
|X-Spam-Level: *
|X-Spam-Status: No, score=1.7 required=3.0 tests=AWL,HTML_MESSAGE,
| MIME_HTML_ONLY,RDNS_NONE,SPF_PASS autolearn=disabled version=3.2.4
|Delivered-To: thad at (no spam) thadlabs.com
|Received: (qmail 70175 invoked by uid 19250); 17 Mar 2009 12:14:07 -0000
|Received: from unknown (HELO smtp04.newegg.com) ([216.52.208.142])
| (envelope-sender <info at (no spam) newegg.com>)
| by 192.220.75.50 (qmail-ldap-1.03) with SMTP
| for <thad at (no spam) thadlabs.com>; 17 Mar 2009 12:14:07 -0000
|Received: from e3msq02 ([172.16.21.203]) by smtp04.newegg.com with InterScan
|Message Security Suite; Tue, 17 Mar 2009 05:14:07 -0700
|Received: from E3MSQ03 ([172.16.21.203]) by e3msq02 with Microsoft
|SMTPSVC(6.0.3790.3959);
| Tue, 17 Mar 2009 05:14:06 -0700
|MIME-Version: 1.0
|From: "info at (no spam) newegg.com" <info at (no spam) newegg.com>
|To: thad at (no spam) thadlabs.com
|Date: 17 Mar 2009 05:14:06 -0700
|Subject: =?utf-8?B?TmV3ZWdnLmNvbSAtIFVQUyBUcmFja2luZw==?=
|Content-Type: text/html; charset=utf-8
|Content-Transfer-Encoding: base64
|Return-Path: info at (no spam) newegg.com
|Message-ID: <E3MSQ03yhOwlVZmSox900004afa at (no spam) e3msq02>
|X-OriginalArrivalTime: 17 Mar 2009 12:14:06.0100 (UTC)
|FILETIME=[DE27FD40:01C9A6F9]
|X-ClamAV: clean
|
|PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlv
|bmFsLy9FTiINCiJodHRwOi8vd3d3LnczLm9yZy9UUi9odG1sNC9sb29zZS5kdGQiPjxodG1s
|[...] |
|
|
| Back to top |
|
|
|
| James Michael Fultz... |
| Posted: Fri Oct 30, 2009 6:35 pm |
|
|
|
Guest
|
* brownh <brownh at (no spam) teufel.historicalMaterialism.info>:
Quote: Sorry for this being OT, but this forum is where I'm most likely to
find people with the same problem.
When I order hardware from Newegg, the e-mail invoices and tracking
information messages are sent with broken MIME content (yes, they use
a Windows MUA).
Apparently they find it necessary for some reason to send these
messages as binary files, and so they are MIME'd, but lack the header
necessary for my mail utility (mutt) to umime them. Usually I
deal with this situation by pasting in a standard header and then
un-miming with with munpack, but in the case of the Newegg messages,
munpack can't recognized them as MIME.
Using Mutt here, and it decodes Newegg's mail including invoices just
fine.
Mutt 1.5.18 (2008-05-17)
What version of Mutt are you using?
Quote: Anyone with a similar problem and who might offer work-arounds?
I don't know a solution, but you might find answers on comp.mail.mutt or
the Mutt Users mailing list[1].
1. Mutt mailing lists: <http://www.mutt.org/mail-lists.html>
--
James Michael Fultz <xyzzy at (no spam) sent.as.invalid>
Remove this part when replying ^^^^^^^^ |
|
|
| Back to top |
|
|
|
| brownh... |
| Posted: Sat Oct 31, 2009 7:46 am |
|
|
|
Guest
|
Thad,
I've spent some time experimenting and scratching my head, and the
header you supply for the Newegg message is the same as the one in my
message from Newegg. I now find I am able to manually un-MIME the
message and was initially mislead by an oversight on my part. It seems
that when Content-Type has no name= argument and there is no
Content-Disposition: inline; filename="..." line in the header,
munpack returns an error message that "Did not find anything to unpack
from...", but nevertheless generates the expected output which it
names "tempdesc.txt". This behavior initially misled me.
It seems that my mail utility (mutt) could not cope properly with the
header. Perhaps it expected the MIME header to be after the message
header rather than within it, and there may be an issue concerning a
following blank line, for I don't know if that line can be simply the
blank line after the message header. It's difficult to resolve this
problem by experimenting, but it does seem a mutt problem more than
a problem with Newegg HTML MIME's messages.
Thanks,
Haines |
|
|
| Back to top |
|
|
|
| brownh... |
| Posted: Sat Oct 31, 2009 8:27 am |
|
|
|
Guest
|
James,
See my message to Thad, which suggests that the problem is more with
mutt's ability to handle Newegg's MIME header than with their message.
I'm using the same version of mutt as you are, and it is 1.5.18-6.
Thanks to folks being forebearning in response to an OT question that
points more to a mutt issue than Newegg messages. I'll turn to the
mutt list for help.
Haines |
|
|
| Back to top |
|
|
|
|
|
All times are GMT - 5 Hours
The time now is Tue Dec 01, 2009 5:17 pm
|
|