PDF附件在正文中显示为随机文本

时间:2019-01-11 00:22:30

标签: email pdf

我是一位几乎不了解电子邮件...东西的开发人员。我的任务是解决与该电子邮件相关的问题。

我们遇到了某些pdf电子邮件报告发送给我们的问题(它们是由第三方软件生成的,但是据我所知,该软件正在使用我们自己的MX服务器将其发送给我们)。我已经在下面复制了标题信息,但是经过一些简单的测试:

1)作品-Gmail / hotmail收件人-PDF作为附件正确显示

2)不起作用-OURDOMAIN.com收件人或Rogers.com收件人(在线和MS Outlook客户端)-PDF显示为乱码(我知道,它实际上不是乱码):

begin 666 /data/[file path and name here].pdf
M)5!$1BTQ+C0-"B7Y^IKG#0HT(#`@;V)J#0H\/`HO12`T.#`P.`HO2"!;-#(X...

3)作品-将Gmail / hotmail电子邮件转发到OURDOMAIN

4)工作原理-将来自测试2的垃圾邮件转发到gmail或hotmail

如果有人遇到此问题,请问如何解决此问题的任何建议(通过告诉第三方更改电子邮件脚本或调整我们的邮件服务器设置)?

标题:

Outlook中的Internet标头(“文件”>“属性”):

Received: from qad1.OURDOMAIN.com (10.99.41.10) by
 SCOOTEX01A.AD.OURDOMAIN.com (10.99.42.100) with Microsoft SMTP Server id
 14.3.210.2; Thu, 10 Jan 2019 10:57:26 -0500
Received: (from root@localhost) by qad1.OURDOMAIN.com (8.9.3
 (PHNE_35950)/8.9.3) id KAA16277;   Thu, 10 Jan 2019 10:56:46 -0500 (EST)
Date: Thu, 10 Jan 2019 10:56:46 -0500
From: <root@qad1.OURDOMAIN.com>
Message-ID: <201901101556.KAA16277@qad1.OURDOMAIN.com>
To: <me@gmail.com>, <others@OURDOMAIN.com>,
    <me@OURDOMAIN.com>
Subject: TYGMSPOSD DELJIT Report
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-Path: root@qad1.OURDOMAIN.com
X-MS-Exchange-Organization-AuthSource: SCOOTEX01a.AD.OURDOMAIN.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 10

GMAIL:

Delivered-To: me@gmail.com
Received: by 2002:a50:95ed:0:0:0:0:0 with SMTP id x42csp2161688eda;
        Thu, 10 Jan 2019 08:27:56 -0800 (PST)
X-Google-Smtp-Source: ALg8bN5RiZ6QpXjU5ifJAaYoJwUkq5VUHg8XQOv9eEWgSVx8vPBM8u71ToT4dGz6/jMMn8Jc2YuL
X-Received: by 2002:a5e:db44:: with SMTP id r4mr6416635iop.142.1547137675743;
        Thu, 10 Jan 2019 08:27:55 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1547137675; cv=none;
        d=google.com; s=arc-20160816;
        b=TQgJBOipnrDgMmj7fDV9akUi4gxHPIaUaqGPQqOToSzjvqMZvh/IzAjs3WHSQ1diVD
         OBYBMniGUR8PohtuJ5dJPCJUrW+E3eNEu8KoVXyc1F0WNWqPmnWAi4zT4eY76cBnMgX6
         ejOsFwJwxERcAmj65riCQ0hwMWiq8zyg6XJiohDBIMWc5cIvrR4AWfw3odzg5RYc4Kdo
         Sop8+IRjlqzAAhAtpLcZVZ14U1Of4EpsTEUhDkb7DL9oAZqsUIe8pO5ZBep4UG4GzWc6
         rLGdDMk7iVZKF03F7E05IX5zo1GBu9QKfC9sRfKIehHxiuubiVWhU2OWiDu7CqvgIsdV
         31Uw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=content-transfer-encoding:mime-version:subject:to:message-id:from
         :date;
        bh=XnZ3szAGfipXM3+HnWo9CKZKYWY1Uud5fCUWvPMPKEU=;
        b=jwbok8bSBv12Rn4k/SisV0FFxBP2uxvtAiejIuhuhlUTcUhL3Uh6l4xRIL5CaiMrKV
         jkRxiDVk7pimXjjayPGdUCFbKqrkgQbxXMi/x9iwSnPluDLyqErLf38OYg0B4E/MBxOn
         evNlHIfLZa90lWo89emwtle2uKwr2lPpASjMva5TiQtmWzkcm/OZQYhgEDayJC2EhwxM
         uxZ7S2NqiUMfJ6R/KkhZUq+EOwHW9zieDoZ0jYTBWFAVGnhUVmdA+yW4LFlmHnfQYpOj
         xtII441ow1VrwKUYaUVYi3jainGd+VzSIVdp9tC2XVX3J5RN1dbi/y4x+OHie3XG4Gcj
         01eg==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: best guess record for domain of root@qad1.OURDOMAIN.com designates 209.171.90.3 as permitted sender) smtp.mailfrom=root@qad1.OURDOMAIN.com
Return-Path: <root@qad1.OURDOMAIN.com>
Received: from mail3.OURDOMAIN.com (mail3.OURDOMAIN.com. [209.171.90.3])
        by mx.google.com with ESMTP id r15si10247731itc.55.2019.01.10.08.27.55
        for <me@gmail.com>;
        Thu, 10 Jan 2019 08:27:55 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of root@qad1.OURDOMAIN.com designates 209.171.90.3 as permitted sender) client-ip=209.171.90.3;
Authentication-Results: mx.google.com;
       spf=pass (google.com: best guess record for domain of root@qad1.OURDOMAIN.com designates 209.171.90.3 as permitted sender) smtp.mailfrom=root@qad1.OURDOMAIN.com
X-ASG-Debug-ID: 1547137671-09c42418c2374140002-QUTJxp
Received: from SCOOTEX01a.AD.OURDOMAIN.com ([10.99.42.100]) by mail3.OURDOMAIN.com with ESMTP id pVkVkwY1yxfRxEA7; Thu, 10 Jan 2019 11:27:53 -0500 (EST)
X-Barracuda-Envelope-From: root@qad1.OURDOMAIN.com
X-ASG-Whitelist: Sender
Received: from qad1.OURDOMAIN.com (10.99.41.10) by SCOOTEX01A.AD.OURDOMAIN.com (10.99.42.100) with Microsoft SMTP Server id 14.3.210.2; Thu, 10 Jan 2019 11:06:51 -0500
Received: (from root@localhost) by qad1.OURDOMAIN.com (8.9.3 (PHNE_35950)/8.9.3) id LAA24693;   Thu, 10 Jan 2019 11:06:12 -0500 (EST)
Date: Thu, 10 Jan 2019 11:06:12 -0500
From: <root@qad1.OURDOMAIN.com>
Message-ID: <201901101606.LAA24693@qad1.OURDOMAIN.com>
To: <me@gmail.com>, <others@OURDOMAIN.com>, <me@OURDOMAIN.com>
Subject: TYGMSPOSD DELJIT Report
MIME-Version: 1.0
X-ASG-Orig-Subj: TYGMSPOSD DELJIT Report
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Barracuda-Connect: UNKNOWN[10.99.42.100]
X-Barracuda-Start-Time: 1547137672
X-Barracuda-URL: https://10.99.42.22:443/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at OURDOMAIN.com
X-Barracuda-Scan-Msg-Size: 67734
X-Barracuda-BRTS-Status: 1

1 个答案:

答案 0 :(得分:1)

在您发布的标头中,似乎正在创建和发送这些电子邮件的应用程序正在使用UUENCODE将PDF附加到该消息。 UUENCODE是一种用于将文件附加到电子邮件的非常古老的编码方法,它可以比MIME编码早一些,而MIME编码如今已越来越普遍。

虽然从您的观点看来,Gmail和Hotmail仍支持UUENCODE,但Outlook(可能还有Microsoft Exchange)似乎不支持。参见https://support.microsoft.com/en-us/help/2590107/inline-uuencoded-attachments-of-email-messages-from-a-unix-based-appli

如果可以将创建和发送这些电子邮件的应用程序更新为使用MIME编码而不是UUENCODE,则应该可以解决问题。