Re: Problem with S/MIME signed mail, Piler 1.31 on Ubuntu LTS 16.04

[Daniel Abegglen]

Hello Janos,

thanks for your reply. I think I was run in two different errors.
The error with the missing body, was my fault sorry, On one machine the
email was not sent without the plain text message if signed.
The other problem, outlook isn't opening the .eml file correctly and
doesn't interpret recipient, sender ans dates, coul be drilled down to a
"carriage return" on top of the .eml file.
If the [r] was manually removed, the .eml file is displayed correctly in
Outlook, if it's not a signed email.
But I've no clue where this [cr] is coming from.

Daniel

You find an corrupt .eml Message attached.


2018-01-31 19:46 GMT+01:00 :

>
>
> Hello Daniel,
>
> On 2018-01-31 17:51, Daniel Abegglen wrote:
>
>>
>> I've problems with S/MIME signed mails. There is no body visible. If I
>> download the .eml file there is not recipient or sender, nor a
>> subject, just header and the S/MIME-part.
>>
>
> can you share such a signed and non sensitive email (the complete eml
> file)?
> Then I'd check what's wrong.
>
> Janos
>
>

Received: from VI1PR0902MB2029.eurprd09.prod.outlook.com (10.170.231.12) by
 VI1PR0902MB1839.eurprd09.prod.outlook.com (10.171.108.145) with Microsoft
 SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.11; Wed, 31
 Jan 2018 19:58:38 +
Received: from VI1PR0902MB2029.eurprd09.prod.outlook.com
 ([fe80::c68:6ef6:7fcd:9904]) by VI1PR0902MB2029.eurprd09.prod.outlook.com
 ([fe80::c68:6ef6:7fcd:9904%13]) with mapi id 15.20.0444.016; Wed, 31 Jan 2018
 19:58:38 +
From: Daniel Abegglen | IQantum 
To: "''daniel.abegg...@gmail.com' (daniel.abegg...@gmail.com)'"

Subject: Signed Test for debugging
Thread-Topic: Signed Test for debugging
Thread-Index: AdOazeFu6afwhfs9RdOaLZkbBLhrmw==
Date: Wed, 31 Jan 2018 19:58:38 +
Message-ID: 

Accept-Language: de-CH, en-US
Content-Language: de-DE
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-AuthSource: VI1PR0902MB2029.eurprd09.prod.outlook.com
X-MS-Exchange-Organization-TransportTrafficType: Email
X-MS-Exchange-Organization-TransportTrafficSubType:
X-MS-Has-Attach: yes
X-MS-Exchange-Organization-Network-Message-Id: 
9debf322-d0ac-432c-89c5-08d568e50552
X-MS-Exchange-Organization-SCL: 1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
x-ms-exchange-organization-recordreviewcfmtype: 0
x-ms-exchange-organization-originalsize: 19329
x-ms-exchange-organization-originalarrivaltime: 31 Jan 2018 19:58:38.8575
 (UTC)
x-ms-exchange-organization-messagesource: StoreDriver
x-ms-exchange-organization-fromentityheader: Hosted
x-ms-exchange-organization-messagedirectionality: Originating
x-ms-exchange-organization-id: 6b4f4920-7d8d-4f96-b88b-4197caa4dd18
X-MS-Exchange-Organization-BCC:
x-ms-exchange-organization-originalclientipaddress: 80.219.49.110
x-originating-ip: [80.219.49.110]
x-ms-exchange-organization-originalserveripaddress: 25.172.123.11
x-ms-exchange-organization-submissionrecipientcount: 1
x-ms-exchange-organization-transporttraffictype: Email
x-ms-exchange-organization-transporttrafficsubtype:
x-ms-publictraffictype: Email
x-ms-exchange-organization-mailboxtype: HOSTED
x-ms-exchange-organization-exchange-diagnostics-stage-securedatacontainer: 0
x-microsoft-exchange-diagnostics: 
1;VI1PR0902MB1839;7:DpaL7cm87cHuiNcaIQIE/WFHTc7JT5s4qKeggCTTLjsZi0u+Bi4CUYiZsYebY4RBc0lszt9B771ssYZJXj1EcrgEsmwE76lUS6Nlc341vlfASB5lgD+Y6IQ8gPG5ZAfukZcmpcwGa0aaGUrX9qfIG9WpCT1CAGYiytynAjivqj5eRYIA6i+o93Y2sp52KaFF7K3MxiZESGiufjFeKxXsYTB/BPT5mm2xmCRuBKABhYL310zts+bqgkUOKYafopdO;20:smdXqDNquj3otbg2EkTOaoag8PJpyOJeMktr8+WS5yaKyyr0mHIIV9/vJcsccxVABsC0LAmF5gzB/waO2L2BV+eNPg+MsczF0vtIrQFUh4C4YRKVs9iRbhmVfM4H+tYe/GQ9N53Ckik1cMTGv9NwEzXOs4yWlokTWKdSKDo9hdU=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-exchange-organization-ispotentialintraorgmail: False
x-ms-exchange-organization-avstamp-service: 1.0
x-ms-exchange-organization-orderedprecisionlatencyinprogress: 
LSRV=VI1PR0902MB2029.eurprd09.prod.outlook.com:TOTAL-SUB=0.140|MTSS-PEN=0.138(MTSSD-PEN=0.138(MTSCAT=0.095(MTSCATSM=0.094(MTSCATSM-Submission
 Malware=0.093 ;2018-01-31T19:58:38.998Z
x-ms-exchange-forest-arrivalhubserver: VI1PR0902MB1839.eurprd09.prod.outlook.com
x-ms-exchange-organization-messagescope: 40ea8f1c-6328-411f-9344-7f08a6789448
x-ms-exchange-forest-messagescope: 40ea8f1c-6328-411f-9344-7f08a6789448
x-ms-exchange-organization-cross-premises-headers-processed: 
VI1PR0902MB1839.eurprd09.prod.outlook.com
x-ms-exchange-organization-antispam-protocolfilterhub-scancontext: 
ProtocolFilterHub:SmtpOnEndOfData;
x-ms-exchange-organization-accepteddomain: True
x-ms-exchange-organization-oldtenant: True
x-ms-exchange-organization-mailtier: 1
x-ms-exchange-organization-tenantage: 869
x-ms-exchange-organization-istrial: False

Re: Problem with S/MIME signed mail, Piler 1.31 on Ubuntu LTS 16.04

[sj]

Hello Daniel,

On 2018-01-31 17:51, Daniel Abegglen wrote:


I've problems with S/MIME signed mails. There is no body visible. If I
download the .eml file there is not recipient or sender, nor a
subject, just header and the S/MIME-part.


can you share such a signed and non sensitive email (the complete eml 
file)?

Then I'd check what's wrong.

Janos

Problem with S/MIME signed mail, Piler 1.31 on Ubuntu LTS 16.04

[Daniel Abegglen]

Hello,

I've problems with S/MIME signed mails. There is no body visible. If I
download the .eml file there is not recipient or sender, nor a subject,
just header and the S/MIME-part.

It's the same result if the Mail is addressed direct to the piler box or if
it's comming from the journal rule in Office 365,.

The same mail sent to gmail.com, I can read the mail.

S/MIME signed Mail I've imported via PST=>readpst=>pilerimport are not
affected and everything is as expected.

Thanks in advance!