SPF-Record und E-Mail-Weiterleitung

K

kasthood

New Member
Hallo,

ich hoffe ich habe für meinen ersten Beitrag das richtige Forum gewählt :)

Eigentlich funktioniert alles soweit, bis auf die kuriose Sache, dass Emails aus dem Ausland zB. von mail@isp.bg nicht da ankommen wo sie sollen.

Angenommen ich schicke eine Mail von mail@isp.bg an mail@yahoo.de, wobei mail@yahoo.de weiterleitet an mail@meineeigenedomain.de, dann landet zwar die Mail bei yahoo.de wird, jedoch nicht weitergeleitet an meineeigenedomain.de. Bekomme dann einen Unzustellbarkeitsbericht.

Weiterhin, schicke ich eine Mail von mail@hotmail.com an mail@yahoo.de, wobei wieder mail@yahoo.de weiterleitet an mail@meineeigenedomain.de, dann landet die Mail bei yahoo.de und wird weitergeleitet an meineeigenedomain.de. Alles funktioniert soweit.

Warum das eine geht und das andere nicht ist mir schleierhaft, trotz lesen von pobox.xom und openspf.org, ob ich das richtig verstanden habe... Dass der SPF-Record von meineeigenedomain.de dafür verantwortlich ist hatte ich zuerst angenommen, weil im Bericht stand:

<mail@meineeigenedomain.de>: host mx1.meineeigenedomain.de[#.#.#.#] said: 550 See
SPF: Why
(#5.7.1) (in reply to RCPT TO command)

Jetzt bin ich mir nicht mehr sicher ...


Kann mir jemand erklären warum die Mails nicht weitergeleitet werden?
Ist der SPF-Eintrag dafür verantwortlich, wenn ja bei welcher Domain?
Was kann ich tun damit es funktioniert?

Vielen Dank vorab für die Hilfe
 
Last edited by a moderator:
Zuerst einmal: Am SPF-Record für Deine Domain liegt es nicht, denn die ist nur für die Absender relevant.

Wie es scheint, führst Du auf Deinem Rechner SPF-Checks durch -- das suggeriert zumindest die Fehlermeldung. Damit die Weiterleitung funktioniert, muss der weiterleitende MX-Rechner Sender-Rewriting durchführen. Da ich keine Yahoo-Mailadresse habe, weiß ich nicht, ob die das korrekt durchführen.
Du könntest mal den vollständigen Header der Mail, die durchgekommen ist, hier posten (bitte in [noparse]
Code: 
...
[/noparse]-Tags, dann könnte man mehr dazu sagen.

Ansonsten scheint Dein Fall ein weiteres schönes Beispiel dafür zu sein, warum SPF nicht wirklich funktioniert.
 
Du hast also eine Mail:

Code: 
Envelope-To: mail@meineeigenedomain.de
From: mail@hotmail.com
To: mail@yahoo.de

Zunächst must Du bei mx1.meineeigenedomain.de (Dein Server) eintragen, daß mail@yahoo.de ein legitimer Empfänger ist (ggf. mit eigenem Postfach). Zudem darf Dein SPF-Check für mail@hotmail.com yahoo.de nicht als ungültig ablehnen (Whitelist).

Prinzipiell stimme ich LinuxAdmin völlig zu, bei funktionierendem SRS sollte es einfach so funktionieren.
 
Hallo, danke nochmal für eure Antworten.

Das Problem wird überwiegend an mich herangetragen, deshalb habe ich mir eine Adresse bei einem bulgarischen Anbieter und bei Hotmail registriert, um das zu testen. Habe bei port25.com den Verifier ausprobiert, jedoch kann ich mit der Antwort nichts anfangen, vielleicht hilft es euch mir zu helfen (weiter unten).

Der Versuch den Verifier von MEINEEIGENEDOMAIN.de aus zu starten ist fehlgeschlagen, auch nach dem 5. Versuch kommt nichts zurück.

Hinweis: Ich benutze eine Freemail Adresse mit Weiterleitung auf mein eigentliches Postfach, sodass ich mein wahres Postfach nicht preisgeben muss (als Schutz vor Spam). Funktioniert prima, ausser die Weiterleitung von Emails die offensichtlich von einem bulgarischen Server versendet wurden.

Die Emails die zurückgekommen sind:

Von web.de aus:
Code: 
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can delete your own text from the attached returned message.

			The Postfix program

<MYUSERNAME@MEINEDOMAIN.de>: host mx1.MEINEDOMAIN.de[217.13.200.24] said: 550 See
    http://spf.pobox.com/why.html?sender=MYUSERNAME%40abv.bg&ip=217.72.192.234&receiver=0
    (#5.7.1) (in reply to RCPT TO command)

Code: 
Reporting-MTA: dns; fmmailgate03.web.de
X-Postfix-Queue-ID: DECAEF935149
X-Postfix-Sender: rfc822; MYUSERNAME@abv.bg
Arrival-Date: Sat, 14 Mar 2009 18:02:08 +0100 (CET)

Final-Recipient: rfc822; MYUSERNAME@MEINEDOMAIN.de
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mx1.MEINEDOMAIN.de[217.13.200.24] said: 550 See
    http://spf.pobox.com/why.html?sender=MYUSERNAME%40abv.bg&ip=217.72.192.234&receiver=0
    (#5.7.1) (in reply to RCPT TO command)

Bei Yahoo bekomme ich eine ähnliche Fehlermeldung.

ABV.BG:
Code: 
This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com. The service allows email senders to perform
a simple check of various sender authentication mechanisms. It is provided
free of charge, in the hope that it is useful to the email community. While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check: pass
DomainKeys check: pass
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname: smtp-out.abv.bg
Source IP: 194.153.145.80
mail-from: MYUSERNAME@abv.bg

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mail=MYUSERNAME@abv.bg
DNS record(s):
abv.bg. 86400 IN TXT "v=spf1 a mx ptr ip4:194.153.145.0/24 ip4:212.73.129.160/28 -all"
abv.bg. 86400 IN A 194.153.145.104
abv.bg. 86400 IN MX 10 pmx.abv.bg.
abv.bg. 86400 IN MX 20 smx.abv.bg.
pmx.abv.bg. 86400 IN A 194.153.145.94
pmx.abv.bg. 86400 IN A 194.153.145.106
pmx.abv.bg. 86400 IN A 194.153.145.10
pmx.abv.bg. 86400 IN A 194.153.145.69
pmx.abv.bg. 86400 IN A 194.153.145.75
pmx.abv.bg. 86400 IN A 194.153.145.77
pmx.abv.bg. 86400 IN A 194.153.145.78
pmx.abv.bg. 86400 IN A 194.153.145.85
pmx.abv.bg. 86400 IN A 194.153.145.93
smx.abv.bg. 86400 IN A 194.153.145.106
smx.abv.bg. 86400 IN A 194.153.145.10
smx.abv.bg. 86400 IN A 194.153.145.69
smx.abv.bg. 86400 IN A 194.153.145.75
smx.abv.bg. 86400 IN A 194.153.145.77
smx.abv.bg. 86400 IN A 194.153.145.78
smx.abv.bg. 86400 IN A 194.153.145.85
smx.abv.bg. 86400 IN A 194.153.145.93
smx.abv.bg. 86400 IN A 194.153.145.94
80.145.153.194.in-addr.arpa. 86400 IN PTR smtp-out.abv.bg.
smtp-out.abv.bg. 86400 IN A 194.153.145.80
smtp-out.abv.bg. 86400 IN A 194.153.145.99
smtp-out.abv.bg. 86400 IN A 194.153.145.70

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=MYUSERNAME@abv.bg
DNS record(s):
smtp-out._domainkey.abv.bg. 600 IN TXT "g=*; k=rsa; t=y; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPShtI1XjhVGpVrKyBuFP5K0jqFqy5gC8GujqF9lTCN/Epg/kObBOORSVAZ0DRawBHyRWDcscPwK8MhzQb2ZjRKGGK1L6OqaDQL5y9o0f2dqtuwMzGqJyaIL4Wrs3v0YbqD1w4G6pq/5NxfPpKyKqAbiCTGrutCo/dQaRF/YjPnQIDAQAB"

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=MYUSERNAME@abv.bg
Canonicalized Headers:
Date:'20'Sat,'20'14'20'Mar'20'2009'20'19:17:22'20'+0200'20'(EET)'0D''0A'
From: <MYUSERNAME@abv.bg>'0D''0A'
To:'20'check-auth@verifier.port25.com'0D''0A'
Message-ID:'20'<585376484.5868.1237051042339.JavaMail.apache@mail82.abv.bg>'0D''0A'
Subject:'20''0D''0A'
MIME-Version:'20'1.0'0D''0A'
Content-Type:'20'multipart/alternative;'20''0D''0A'
'09'boundary="----=_Part_5866_1597595449.1237051042229"'0D''0A'
DKIM-Signature:'20'v=1;'20'a=rsa-sha256;'20'c=simple/simple;'20'd=abv.bg;'20's=smtp-out;'0D''0A'
'09't=1237051044;'20'bh=IppAfsIM9vesXfkx6yY7XV6PT5o2JAOiN8VQ8ktCsBs=;'0D''0A'
'09'h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:DKIM;'0D''0A'
'09'b=

Canonicalized Body:
------=_Part_5866_1597595449.1237051042229'0D''0A'
Content-Type:'20'text/plain;'20'charset="UTF-8"'0D''0A'
Content-Transfer-Encoding:'20'8bit'0D''0A'
'0D''0A'
'0D''0A'
'0D''0A'
------=_Part_5866_1597595449.1237051042229'0D''0A'
Content-Type:'20'text/html;'20'charset="UTF-8"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
<HTML><BODY>'0D''0A'
&nbsp;</BODY></HTML>'0D''0A'
'0D''0A'
------=_Part_5866_1597595449.1237051042229--'0D''0A'


DNS record(s):
smtp-out._domainkey.abv.bg. 600 IN TXT "g=*; k=rsa; t=y; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPShtI1XjhVGpVrKyBuFP5K0jqFqy5gC8GujqF9lTCN/Epg/kObBOORSVAZ0DRawBHyRWDcscPwK8MhzQb2ZjRKGGK1L6OqaDQL5y9o0f2dqtuwMzGqJyaIL4Wrs3v0YbqD1w4G6pq/5NxfPpKyKqAbiCTGrutCo/dQaRF/YjPnQIDAQAB"

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=MYUSERNAME@abv.bg
DNS record(s):
abv.bg. 86400 IN TXT "v=spf1 a mx ptr ip4:194.153.145.0/24 ip4:212.73.129.160/28 -all"
abv.bg. 86400 IN A 194.153.145.104
abv.bg. 86400 IN MX 10 pmx.abv.bg.
abv.bg. 86400 IN MX 20 smx.abv.bg.
pmx.abv.bg. 86400 IN A 194.153.145.94
pmx.abv.bg. 86400 IN A 194.153.145.106
pmx.abv.bg. 86400 IN A 194.153.145.10
pmx.abv.bg. 86400 IN A 194.153.145.69
pmx.abv.bg. 86400 IN A 194.153.145.75
pmx.abv.bg. 86400 IN A 194.153.145.77
pmx.abv.bg. 86400 IN A 194.153.145.78
pmx.abv.bg. 86400 IN A 194.153.145.85
pmx.abv.bg. 86400 IN A 194.153.145.93
smx.abv.bg. 86400 IN A 194.153.145.106
smx.abv.bg. 86400 IN A 194.153.145.10
smx.abv.bg. 86400 IN A 194.153.145.69
smx.abv.bg. 86400 IN A 194.153.145.75
smx.abv.bg. 86400 IN A 194.153.145.77
smx.abv.bg. 86400 IN A 194.153.145.78
smx.abv.bg. 86400 IN A 194.153.145.85
smx.abv.bg. 86400 IN A 194.153.145.93
smx.abv.bg. 86400 IN A 194.153.145.94
80.145.153.194.in-addr.arpa. 86400 IN PTR smtp-out.abv.bg.
smtp-out.abv.bg. 86400 IN A 194.153.145.80
smtp-out.abv.bg. 86400 IN A 194.153.145.99
smtp-out.abv.bg. 86400 IN A 194.153.145.70

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.2.5 (2008-06-10)

Result: ham (1.8 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-1.0 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust
[194.153.145.80 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE BODY: HTML included in message
2.2 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
1.8 MISSING_SUBJECT Missing Subject: header
1.4 EMPTY_MESSAGE Message appears to have no textual parts and no
Subject: text

==========================================================
Explanation of the possible results (adapted from
draft-kucherawy-sender-auth-header-04.txt):
==========================================================

"pass"
the message passed the authentication test.

"fail"
the message failed the authentication test.

"softfail"
the message failed the authentication test, and the authentication
method has either an explicit or implicit policy which doesn't require
successful authentication of all messages from that domain.

"neutral"
the authentication method completed without errors, but was unable
to reach either a positive or a negative result about the message.

"temperror"
a temporary (recoverable) error occurred attempting to authenticate
the sender; either the process couldn't be completed locally, or
there was a temporary failure retrieving data required for the
authentication. A later retry may produce a more final result.

"permerror"
a permanent (unrecoverable) error occurred attempting to
authenticate the sender; either the process couldn't be completed
locally, or there was a permanent failure retrieving data required
for the authentication.

==========================================================
Original Email
==========================================================

Return-Path: <MYUSERNAME@abv.bg>
Received: from smtp-out.abv.bg (194.153.145.80) by verifier.port25.com (PowerMTA(TM) v3.5r11) id hnfioi0hse8q for <check-auth@verifier.port25.com>; Sat, 14 Mar 2009 12:12:39 -0500 (envelope-from <MYUSERNAME@abv.bg>)
Authentication-Results: verifier.port25.com smtp.mail=MYUSERNAME@abv.bg; mfrom=pass;
Authentication-Results: verifier.port25.com header.From=MYUSERNAME@abv.bg; domainkeys=pass;
Authentication-Results: verifier.port25.com header.From=MYUSERNAME@abv.bg; dkim=pass;
Authentication-Results: verifier.port25.com header.From=MYUSERNAME@abv.bg; pra=pass;
Received: from mail54.abv.bg (mail82.ni.bg [192.168.151.129])
by smtp-out.abv.bg (Postfix) with ESMTP id 847E987AFA
for <check-auth@verifier.port25.com>; Sat, 14 Mar 2009 19:17:24 +0200 (EET)
DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns;
b=SW8z+qf9j9yC0sXV6352opSO9UlqqEZv2r+5RRj/H82wWoToGsnQV9So0408alb1A
V8dQFQ+ZG3j4bjv61wNDKz8X8bnh5RAMQs+QjtG1TIyHcTS6lQyGc/lDBvVMwT8Cf2y
ijmed8A3V9q9ISijvBtIkW5FJ3B5acBe8P4bDqc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abv.bg; s=smtp-out;
t=1237051044; bh=IppAfsIM9vesXfkx6yY7XV6PT5o2JAOiN8VQ8ktCsBs=;
h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:DKIM;
b=riOvknhgrzdYfbX22R1fAxEcEPlIiXvMy3pWegXvDvMtuAD5W0j2w8MdF79juRnw5
ZARRfrTYibNdSLb/c6/BhdZ8Rmij9U91D+Wnkr8rQEUODNr2z8b0CwJwydt11iBxAO
8C4hQTpk7TgQTdBMkRUTZrAfQ/xWCzt/5+5QtzpE=
Received: from mail82.abv.bg (localhost.localdomain [127.0.0.1])
by mail54.abv.bg (Postfix) with ESMTP id 5332F57C47
for <check-auth@verifier.port25.com>; Sat, 14 Mar 2009 19:17:22 +0200 (EET)
Date: Sat, 14 Mar 2009 19:17:22 +0200 (EET)
From: <MYUSERNAME@abv.bg>
To: check-auth@verifier.port25.com
Message-ID: <585376484.5868.1237051042339.JavaMail.apache@mail82.abv.bg>
Subject:
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_5866_1597595449.1237051042229"
X-Priority: 3
X-Mailer: AbvMail 1.0
X-Originating-IP: 85.178.117.96

------=_Part_5866_1597595449.1237051042229
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit



------=_Part_5866_1597595449.1237051042229
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<HTML><BODY>
&nbsp;</BODY></HTML>

------=_Part_5866_1597595449.1237051042229--



HOTMAIL.COM:
Code: 
This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com.  The service allows email senders to perform
a simple check of various sender authentication mechanisms.  It is provided
free of charge, in the hope that it is useful to the email community.  While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.
 
Thank you for using the verifier,
 
The Port25 Solutions, Inc. team
 
==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         neutral
Sender-ID check:    pass
SpamAssassin check: ham
 
==========================================================
Details:
==========================================================
 
HELO hostname:  snt0-omc2-s3.snt0.hotmail.com
Source IP:      65.55.90.78
mail-from:      MYUSERNAME@hotmail.com
 
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: smtp.mail=MYUSERNAME@hotmail.com
DNS record(s):
    hotmail.com. 3600 IN TXT "v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all"
    spf-a.hotmail.com. 3600 IN TXT "v=spf1 ip4:209.240.192.0/19 ip4:65.52.0.0/14 ip4:131.107.0.0/16 ip4:157.54.0.0/15 ip4:157.56.0.0/14 ip4:157.60.0.0/16 ip4:167.220.0.0/16 ip4:204.79.135.0/24 ip4:204.79.188.0/24 ip4:204.79.252.0/24 ip4:207.46.0.0/16 ip4:199.2.137.0/24 ~all"
 
----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: header.From=MYUSERNAME@hotmail.com
DNS record(s):
 
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: 
 
NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.
 
----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: header.From=MYUSERNAME@hotmail.com
DNS record(s):
    hotmail.com. 3600 IN TXT "v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all"
    spf-a.hotmail.com. 3600 IN TXT "v=spf1 ip4:209.240.192.0/19 ip4:65.52.0.0/14 ip4:131.107.0.0/16 ip4:157.54.0.0/15 ip4:157.56.0.0/14 ip4:157.60.0.0/16 ip4:167.220.0.0/16 ip4:204.79.135.0/24 ip4:204.79.188.0/24 ip4:204.79.252.0/24 ip4:207.46.0.0/16 ip4:199.2.137.0/24 ~all"
 
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.2.5 (2008-06-10)
 
Result:         ham  (0.7 points, 5.0 required)
 
 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS               SPF: sender matches SPF record
 0.0 HTML_MESSAGE           BODY: HTML included in message
-1.1 BAYES_05               BODY: Bayesian spam probability is 1 to 5%
                            [score: 0.0305]
 1.8 MISSING_SUBJECT        Missing Subject: header
 
==========================================================
Explanation of the possible results (adapted from 
draft-kucherawy-sender-auth-header-04.txt):
==========================================================
 
"pass"
        the message passed the authentication test.
 
"fail"
        the message failed the authentication test.
 
"softfail"
        the message failed the authentication test, and the authentication
        method has either an explicit or implicit policy which doesn't require
        successful authentication of all messages from that domain.
 
"neutral"
        the authentication method completed without errors, but was unable
        to reach either a positive or a negative result about the message.
 
"temperror"
        a temporary (recoverable) error occurred attempting to authenticate
        the sender; either the process couldn't be completed locally, or
        there was a temporary failure retrieving data required for the
        authentication.  A later retry may produce a more final result.
 
"permerror"
        a permanent (unrecoverable) error occurred attempting to
        authenticate the sender; either the process couldn't be completed
        locally, or there was a permanent failure retrieving data required
        for the authentication.
 
==========================================================
Original Email
==========================================================
 
Return-Path: <MYUSERNAME@hotmail.com>
Received: from snt0-omc2-s3.snt0.hotmail.com (65.55.90.78) by verifier.port25.com (PowerMTA(TM) v3.5r11) id hnfm3g0hse87 for <check-auth@verifier.port25.com>; Sat, 14 Mar 2009 12:41:12 -0500 (envelope-from <MYUSERNAME@hotmail.com>)
Authentication-Results: verifier.port25.com smtp.mail=MYUSERNAME@hotmail.com; mfrom=pass;
Authentication-Results: verifier.port25.com header.From=MYUSERNAME@hotmail.com; domainkeys=neutral (message not signed);
Authentication-Results: verifier.port25.com; dkim=neutral (message not signed);
Authentication-Results: verifier.port25.com header.From=MYUSERNAME@hotmail.com; pra=pass;
Received: from SNT102-W65 ([65.55.90.71]) by snt0-omc2-s3.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Sat, 14 Mar 2009 10:46:00 -0700
Message-ID: <SNT102-W659D95AA610EDA0B5543AED89D0@phx.gbl>
Return-Path: MYUSERNAME@hotmail.com
Content-Type: multipart/alternative;
	boundary="_9e5c6012-fc1f-4ae0-818b-6ef8b86a6eca_"
X-Originating-IP: [85.178.117.96]
From: John McLain <MYUSERNAME@hotmail.com>
To: <check-auth@verifier.port25.com>
Subject:
Date: Sat, 14 Mar 2009 13:46:00 -0400
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 14 Mar 2009 17:46:00.0538 (UTC) FILETIME=[BCD8D3A0:01C9A4CC]
 
--_9e5c6012-fc1f-4ae0-818b-6ef8b86a6eca_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
 
 
 
 
_________________________________________________________________
Express your personality in color! Preview and select themes for Hotmail=AE=
.=20
http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=3DTXT_MS=
GTX_WL_HM_express_032009#colortheme=
 
--_9e5c6012-fc1f-4ae0-818b-6ef8b86a6eca_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
 
<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
<br><br /><hr />Express your personality in color! Preview and select theme=
s for Hotmail=AE.  <a href=3D'http://www.windowslive-hotmail.com/LearnMore/=
personalize.aspx?ocid=3DTXT_MSGTX_WL_HM_express_032009#colortheme' target=
=3D'_new'>See how.</a></body>
</html>=
 
--_9e5c6012-fc1f-4ae0-818b-6ef8b86a6eca_--

@Whistler: hotmail.com versendet an yahoo.de und leitet korrekt weiter.
Ich empfange doch nur Emails von yahoo.de oder web.de etc. warum soll ich diese Domians als leg. Empfänger eintragen? Post dahinzusenden funktioniert super, auch mit Weiterleitung zurück ins Postfach (Email an sich selbst).

@LinuxAdmin: Sender-Rewriting müsste doch bei allen eingehenden Emails durchgeführt werden, ob diese von hotmail.com oder "po4ta.bg" :) kommen.

Könnte es sein, dass Bulgarien prinzipiell von deutschen ISP geblockt werden, was die Weiterleitung anbelangt. Weiss jemand was davon?
 
@Whistler: Oder meinst du dass ich Yahoo als leg. Server für den Empfang meiner Emails in den MX-Rec. eintragen muss, damit der die Emails an mich weiterleitet? So macht das für mich eher Sinn!

Wenn ja was muß ich da reinschreiben?

Gruß.
 
Ähm, hast Du die angegebene URL mal aufgerufen? Ich finde den Text eindeutig:
rejected a message that claimed an envelope sender address of MYUSERNAME@abv.bg.
received a message from fmmailgate03.web.de (217.72.192.234) that claimed an envelope sender address of MYUSERNAME@abv.bg.
However, the domain abv.bg has declared using SPF that it does not send mail through fmmailgate03.web.de (217.72.192.234). That is why the message was rejected.
Click to expand...

Das ist auch völlig verständlich, den abv.bg hat den SPF-Record
Code: 
v=spf1 a mx ptr ip4:194.153.145.0/24 ip4:212.73.129.160/28 -all
Dieser gibt an, von wo MYUSERNAME@abv.bg-Mails kommen dürfen (sehr detailliert in den Testmails von port25 beschrieben), web.de gehört da nunmal nicht dazu.

Du mußt also entweder web.de überreden, per SRS eine @web.de-Addresse als Absender zu bekommen (SRS0+yf09=Cw=abv.bg=MYUSERNAME@web.de), wobei ich jetzt nicht weiß, wie man das über das Web-Interface einstellen kann.
Andernfalls bleibt Dir nix anderes übrig als auf mx1.MEINEDOMAIN.de alles von web.de ohne SPF-Überprüfung zu akzeptieren.
 
You must log in or register to reply here.
Back
Top