Hi,
I'm still fighting with this problem. Using gmx as relay works fine, but I want to use my 'normal' email account.
This is the E-Mailheader if I send a mail from a php script on my server to amazon (in this case redirected to my normal mail address to analyse it).
This works fine with amazon!
Code:
Return-Path: <web111@web111.cyberwebserver-111.de>
X-Original-To: raimond@my-domainname.de
Delivered-To: raimond@my-domainname.de
Received: by cyberwebserver-111.de (Postfix, from userid 10355)
id 3EFF2BC85B0; Wed, 17 Aug 2016 18:50:13 +0200 (CEST)
To: raimond@my-domainname.de
Subject: Your story
X-PHP-Originating-Script: 10355:ww_scriptname.php
From:Downloaderscript<ffdl@my-other-domainname.net>
Reply-To: ffdl@my-other-domainname.net
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="-----=0cd80bd35dbdfd9a5d9d8d6590d1eb7a"
Date: Wed, 17 Aug 2016 18:50:12 +0200
Message-Id: <20160817165013.3EFF2BC85B0@cyberwebserver-111.de>
This is a multi-part message in MIME format.
-------=0cd80bd35dbdfd9a5d9d8d6590d1eb7a
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
the requested file is attached.
-------=0cd80bd35dbdfd9a5d9d8d6590d1eb7a
Content-Disposition: attachment;
filename="testfile.mobi";
Content-Length: .637666;
Content-Type: application/octet-stream; name="testfile.mobi"
Content-Transfer-Encoding: base64
And this is the emailheader if I send a mail from calibre (configured to use the same server).
This is not accepted by amazon:
Code:
Return-Path: <raimond@my-domainname.de>
X-Original-To: raimond@my-domainname.de
Delivered-To: raimond@my-domainname.de
Received: from Win7.fritz.box (unknown [213.xxx.xx.xxx])
by cyberwebserver-111.de (Postfix) with ESMTPSA id 4AFCCBC840B
for <raimond@my-domainname.de>; Wed, 17 Aug 2016 18:15:47 +0200 (CEST)
Content-Type: multipart/mixed; boundary="===============0515989056=="
MIME-Version: 1.0
Subject: E-book: Some kinde of book
To: raimond@my-domainname.de
From: raimond@my-domainname.de
Date: Wed, 17 Aug 2016 18:15:45 +0200
You will not see this in a MIME-aware mail reader.
--===============0515989056==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
QXR0YWNoZWQsIHlvdSB3aWxsIGZpbmQgdGhlIGUtYm9vawoKT2YgSW5rIGFuZCBTdGVlbDogQSBE
cmFjbyBNYWxmb3kgbG92ZSBzdG9yeQoJYnkgR2luZXZyYSBQb3R0ZWQgUGxhbnRzCgppbiB0aGUg
TU9CSSBmb3JtYXQuCgpBYm91dCB0aGlzIGJvb2s6CgpEcmFjbyBNYWxmb3kgT0M=
--===============0515989056==
Content-Type: application/x-mobipocket-ebook;
name="some kind of filename.mobi"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="some kind of filename.mobi"
Now, the one million dollar question: why?