One of my users has just received the following text in the body of an email
etc.Code:begin 600 00601I1697404.PDF M)5!$1BTQ+C,-"B5*971&;W)M(%!$1B!3=7!P;W)T(%9E<G-I;VX@,BXS+C`P M,`T*)45N8V]D:6YG3V)J96-T/3`-"B7[_/W^"C$@,"!O8FH*/#P*+U1Y<&4@ M+T-A=&%L;V<*+U!A9V5S(#,@,"!2"B]/=71L:6YE<R`T(#`@4@H^/@IE;F1O M8FH*#0HU(#`@;V)J"EL@,C<R(#(W,B`S-3(@-34R(#4U,B`X.#@@-C8T(#$X M-"`S,C@@,S(X(#,X-"`U-S8@,C<R(#,R."`R-S(@,C<R(#4U,B`U-3(@-34R M(#4U,B`U-3(@-34R(#4U,B`U-3(@-34R(#4U,B`R-S(@,C<R(#4W-B`U-S8@ M-3<V(#4U,B`Q,#`X(#8V-"`V-C0@-S(P(#<R,"`V-C0@-C`X(#<W-B`W,C`@
This is supposed to be an attached pdf file, but RC seems to be interpreting it as text.
I use Webmin to administer my server, and its built in email client reads the attachment just fine, so it has to be RC that is misinterpreting it.
Has anyone else had this problem? Any clues to fix it would be very handy.
Thanks.
Joel.
Comparing the source of this email to that of others with working PDF attachments, I can see there is no Content-Type header or Boundary to separate the body from the attachment.
But that doesn't explain why it works in other email clients. Maybe this format is a rare one that RC just hasn't got support for yet?
I'm using version 0.3 as the topic says.
We've just recieved another of these 'no content-type/boundry' emails.
Is anyone from the RC team looking into this bug?
The following has been edited to preserve anonymity:
Further investigation tells me that this is a uuencoded message, that according to this ticket has been fixed, but clearly it is not working...Code:Return-Path: <#################> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ############### X-Spam-Level: * X-Spam-Status: No, score=1.6 required=5.0 tests=DNS_FROM_OPENWHOIS,FB_HG_H_CAP, INVALID_DATE,OBSCURED_EMAIL,RCVD_IN_DNSWL_MED,UPPERCASE_50_75 autolearn=no version=3.2.5 X-Original-To: ################## Delivered-To: ################# Received: from localhost (localhost [127.0.0.1]) by ############# (Postfix) with ESMTP id A82D520E07 for <###############>; Thu, 25 Mar 2010 19:38:22 +1100 (EST) X-Virus-Scanned: Debian amavisd-new at ############### Received: from ############### ([127.0.0.1]) by localhost (############### [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wiN26liNYmvI for <###############>; Thu, 25 Mar 2010 19:38:16 +1100 (EST) Received: from ################## (#################### [###.###.###.###]) by ############### (Postfix) with SMTP id A5EB220E06 for <###############>; Thu, 25 Mar 2010 19:38:14 +1100 (EST) X-VirusChecked: Checked X-Env-Sender: ###################### X-Msg-Ref: ##########################!1269506237!38466519!5 X-StarScan-Version: 6.2.4; banners=###############,-,- X-Originating-IP: [###.###.###.###] Received: (qmail 20632 invoked from network); 25 Mar 2010 08:37:22 -0000 Received: from ################ (HELO ######################) (###.###.###.###) by ########################## with SMTP; 25 Mar 2010 08:37:22 -0000 Received: from ################## ([###.###.###.###]) by ################# (8.14.1/8.14.1) with ESMTP id o2P8bBvQ007877 for <###############>; Thu, 25 Mar 2010 19:37:11 +1100 Received: from ##################### ([###.###.###.###] RDNS failed) by ################# with Microsoft SMTPSVC(5.0.2195.6713); Thu, 25 Mar 2010 19:37:11 +1100 Subject: ##################################### From: ########################## Date: 25 MAR 10 08:37:11 UT To: ############### Message-ID: <CNSRVEXC1CH5n00zepD00002c38@##########################> X-OriginalArrivalTime: 25 Mar 2010 08:37:11.0155 (UTC) FILETIME=[5CB9BC30:01CACBF6] Please find attached Tax Invoice as requested. Regards, ######################## begin 600 00601I1702691.PDF M)5!$1BTQ+C,-"B5*971&;W)M(%!$1B!3=7!P;W)T(%9E<G-I;VX@,BXS+C`P M,`T*)45N8V]D:6YG3V)J96-T/3`-"B7[_/W^"C$@,"!O8FH*/#P*+U1Y<&4@ . . . 1>')E9@HQ-S0R,`HE)45/1@H` ` end ______________________________________________________________________ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of #############
Roundcube supports uuencoding only for attachments of MIME messages. It doesn't detects uuencoded content in plain messages.
Are there any plans to fix this? It's not like I can ask the sender to change their email system just because it's not compatible with mine.
I see the ticket has been updated. Thanks alec.
I'm not sure I'd personally call it a 'feature request', but hey as long as it happens, I'm happy![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)