look at the stored .eml file - is body right encoded ?

Thomas





Von:    Christian Vielhauer <[email protected]>
An:     ASSP development mailing list <[email protected]>
Datum:  25.09.2014 08:19
Betreff:        Re: [Assp-test] Problem receiving some mails. Broken 
Content,        missing attachments.



Dear list, dear Thomas


I am using ASSP 2.4.4(14264).

I noticed some mails with broken content again. The body-part stops always 
with a =
Last time (ASSP 2.4.4 (14246) Thomas thought about a too strict UTF-8.

After that fix in upcoming version 14253 I received only one broken 
message content from Amazon.


This time the mail content looks a bit different and is not complete. 
After „an=„ is a line break and the next line begins with a .:




--_000_67b32707c44648108e3e4db25d210a9fwinhexbeeu31winmail_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sehr geehrter Herr NameRemoved,

vielen Dank f=FCr Ihre unten aufgef=FChrte Anfrage, die sich bereits in 
der=
Bearbeitung befindet.
Allerdings ergeben sich aktuell folgende Fragen bzw. Anmerkungen:

Eine Schwei=DFbarkeit der beiden Bauteilmaterialien, insbesondere der 
Achse=
, sehen wir als =E4u=DFerst problematisch bzw. ggf. nicht durchf=FChrbar 
an=






Somebody can help me to fix this issue? Any ideas?

Please tell me what you need. Perhaps the config file or a detailed log?



Thanks

Regards Chris






Am 12.09.2014 um 09:23 schrieb Christian Vielhauer <[email protected]>:

> Hi Thomas,
> 
> thanks for your reply. 
> 
> Today I received again a broken massage from Amazon.
> 
> I have attached the message body  as jpeg. Hope that’s possible at the 
mailing list, but I don’t want to destroy this message. 
> 
> 
> Hopefully u have an idea to fix my problem.
> 
> 
> Kindly Regards
> Chris
> 
> 
> 
> 
> Return-Path: 
<[email protected]>
> X-Original-To: [email protected]
> Delivered-To: [email protected]
> Received: by mail.mydom.com (Postfix, from userid 5001)
>                id 29212C10; Fri, 12 Sep 2014 08:18:52 +0200 (CEST)
> Received: from smtp-out-127-100.amazon.com (unknown [192.168.2.22])
>                by mail.mydom.com (Postfix) with ESMTPS id 2D9585FB
>                for <[email protected]>; Fri, 12 Sep 2014 08:18:50 
+0200 (CEST)
> Received: from smtp-out-127-100.amazon.com ([176.32.127.100]
>                helo=smtp-out-127-100.amazon.com) by ASSP.nospam with 
SMTP (2.4.4);
>                12 Sep 2014 08:18:50 +0200
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>   d=amazon.de; [email protected]; q=dns/txt;
>   s=amazon201209; t=1410502712; x=1442038712;
>   h=date:from:reply-to:to:message-id:subject:mime-version;
>   bh=n4oZNI/vd9JN5wq91GcFJIYuOBxMljhsDlpXdGe7Gik=;
>   b=lfLr6MK3hqazq0gXRogeGTKAkiOQUDnZabaXmMjeTfAePe9jbQiAcErz
>    Ftch26PJVf1VnY+xZFg5yIqf94BYR9QX1SHjyTDlhxRojkB4Hiny+vdTe
>    tOYkrTVHQ0PC/hDz9cUve7u9VLYqUrxfu4CLfPsA0am09SEBtPt4zz+9F
>    0=;
> Date: Fri, 12 Sep 2014 06:18:47 +0000
> From: "Amazon.de" <[email protected]>
> Reply-To: "[email protected]" 
<[email protected]>
> To: Christian <[email protected]>
> Message-ID: 
<urn.rtn.msg.2014091206184537b0feb617024acbbc3e89bf9e668...@1410502727713.rte-svc-eu-1bbig-i-37eedf76.eu-west-1.amazon.com>
> Subject: 
=?UTF-8?Q?Ihre_Amazon.de_Bestellung_von_"Ligawo_=C2=AE_Verlegekabe?=
>  =?UTF-8?Q?l_Cat.7..."_und_3_andere(r)_Artikel_wurde_versandt!?=
> MIME-Version: 1.0
> Content-Type: multipart/mixed; 
>                boundary="----=_Part_1267952_991423031.1410502727708"
> Bounces-to: 
[email protected]
> X-AMAZON-MAIL-RELAY-TYPE: notification
> X-AMAZON-RTE-VERSION: 2.0
> X-Original-MessageID: 
<urn.rtn.msg.2014091206184537b0feb617024acbbc3e89bf9e668...@1410502727713.rte-svc-eu-1bbig-i-37eedf76.eu-west-1.amazon.com>
> X-Assp-ID: ASSP.nospam m1-02730-03060
> X-Assp-Session: 7F46ADC64A98 (mail 1)
> X-Assp-Version: 2.4.4(14253) on ASSP.nospam
> X-Assp-Server-TLS: yes
> X-Assp-Delay: not delayed (176.32.127.100 in whitebox ); 12 Sep 2014
>                08:18:50 +0200
> X-Assp-Whitelisted: Yes
> X-Assp-DKIM: not verified
> 
> ------=_Part_1267952_991423031.1410502727708
> Content-Type: multipart/alternative; 
>                boundary="----=_Part_1267953_521264944.1410502727708"
> 
> ------=_Part_1267953_521264944.1410502727708
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> Amazon.de Versandbest=C3=A4tigung
> Bestellnummer: #305-XXXXX-XXXX17=20
> https://www.amazon.de/ref=3D
> 
> 
___________________________________________________________________________
> 
> Guten Tag,=20
> 
> wir m=C3=B6chten Ihnen hiermit mitteilen, dass #ConverterStore# - 
g=C3=BCns=
> tig kaufen + schneller Versand - (nur 1x Versandkosten egal wie viele 
Artik=
> el Sie zusammen kaufen - AGB + Widerrufsbelehrung) Ihre Bestellung 
verschic=
> kt hat.=20
> 
> Ihre Sendung befindet sich nun auf dem Versandweg; eine =C3=84nderung 
ist n=
> icht mehr m=C3=B6glich.
> 
> 
> <Ihre Amazonde Bestellung von Ligawo  Verlegekabel Cat7 und 3 anderer 
Artikel wurde versandt Kopie.jpeg>
> 
> 
> 
> 
> 
> Am 10.09.2014 um 07:25 schrieb Thomas Eckardt 
<[email protected]>:
> 
>> seem the UTF8 fix in 2.4.4 build 14250 was too stict - build 14253 will 

>> fix it.
>> 
>> Christian - if you use a dev version (2.4.4) , please use the "ASSP 
>> development mailing list" <[email protected]> to report 
>> problems.
>> 
>> Thomas
>> 
>> 
>> 
>> 
>> 
>> Von:    Christian Vielhauer <[email protected]>
>> An:     [email protected]
>> Datum:  09.09.2014 10:32
>> Betreff:        [Assp-user] Problem receiving some mails. Broken 
Content, 
>> missing attachments.
>> 
>> 
>> 
>> Dear list, dear Mr Eckardt,
>> 
>> I am using ASSP 2.4.4(14246).
>> 
>> I noticed some mails with broken content. The body-part stops always 
with 
>> a =
>> 
>> In some other mails we noticed missing attachments. In Log I can see 
the 
>> following line, but no stored .eml file.
>> [TLS-in] [TLS-out] [MessageOK] 123.123.123.123 <[email protected]> 
to: 
>> [email protected] message ok - (noProcessing - message size 
(3013802) 
>> is above 500000 (npSize)) - [Subject]
>> 
>> After I received this message in my mail client it das a size of 5190 
>> byte.
>> 
>> The sender domain is whitelisted. The problem occurs by one of hundred 
>> mails. Sometimes sender uses Outlook, sometimes LotusNotes and some 
>> others.
>> 
>> 
>> 
>> Somebody can help me to fix this issue? Any ideas?
>> 
>> Please tell me what you need. Perhaps the config file or a detailed 
log?
>> 
>> 
>> 
>> Thanks
>> 
>> Regards Chris
>> 
>> 
>> 
------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce.
>> Perforce version control. Predictably reliable.
>> 
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk

>> 
>> _______________________________________________
>> Assp-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-user
>> 
>> 
>> 
>> 
>> 
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential, 
legally 
>> privileged and protected in law and are intended solely for the use of 
the 
>> 
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no 
>> known virus in this email!
>> *******************************************************
>> 
>> 
------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce
>> Perforce version control. Predictably reliable.
>> 
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk

>> _______________________________________________
>> Assp-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-user
> 

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test





DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to