Mails von unserer Server landen im SpamFolder von Gmail
Nur Google handelt unsere mails als Spam.
check-auth2@verifier.port25.com result ist voll okey, und kein spam für yahoo, hotmail, aol
The Port25 Solutions, Inc. team
Summary of Results
SPF check: pass
DomainKeys check: pass
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham
Windows Server 2008
Plesk 9.5.2
MailEnable enterprice 4.26
Testmail gesendet von Horde
Beispiel mail:
Ich werde für jeden Tipp danken.
check-auth2@verifier.port25.com result ist voll okey, und kein spam für yahoo, hotmail, aol
The Port25 Solutions, Inc. team
Summary of Results
SPF check: pass
DomainKeys check: pass
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham
Windows Server 2008
Plesk 9.5.2
MailEnable enterprice 4.26
Testmail gesendet von Horde
Beispiel mail:
Delivered-To: mymailid@gmail.com
Received: by 10.229.7.78 with SMTP id c14cs389640qcc;
Fri, 29 Oct 2010 02:40:20 -0700 (PDT)
Received: by 10.223.114.135 with SMTP id e7mr5288760faq.78.1288345219404;
Fri, 29 Oct 2010 02:40:19 -0700 (PDT)
Return-Path: <mymailid@unsertld.com>
Received: from mail.unsertld.com (golf805.server4you.de [xx.xx.xxx.xxx (unser IP)])
by mx.google.com with ESMTP id a18si1313198faa.155.2010.10.29.02.40.17;
Fri, 29 Oct 2010 02:40:18 -0700 (PDT)
Received-SPF: pass (google.com: domain of mymailid@unsertld.com designates xx.xx.xxx.xxx (unser server IP) as permitted sender) client-ip=xx.xx.xxx.xxx (unser IP);
Authentication-Results: mx.google.com; spf=pass (google.com: domain of mymailid@unsertld.com designates xx.xx.xxx.xxx (unser IP) as permitted sender) smtp.mail=mymailid@unsertld.com; dkim=pass header.i=mymailid@unsertld.com
dkim-signature:v=1; c=relaxed; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
d=unsertld.com; s=main; i=mymailid@unsertld.com; a=rsa-sha256;
bh=NPLa9ZDOrczo1tFcwoY3PIU0sR2qkLDmY7QtM6CgESs=;
b=tJATRZYoTlZfGcQzFxB0QmU/uBit2Da/TgUXFtv+wzDBYw+U92QNL8N5y3oSkzyCn
MAbpXHAhVW9/okERML/6QqgZH1qp832dm9s5xecPvaopXAcAtnkzaxk/8iGKxyc;
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=unsertld.com; b=oqaYJoxFB+HLJv1czTsWRCOMFUafX262ZKZxKZ3qVUMCgrHf77Ion9iWxKJn1f2xqeiOYEYERJ33fiBrJals5XQYAM4doQH+cxPlE1woJZBaTOrgfGgRscII/QEJsv8e; h=Received:Received:Message-ID:Date:From:To:Subject:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:User-Agent:X-ME-Bayesian;
Received: from localhost ([127.0.0.1]) by unsertld.com with MailEnable ESMTP; Fri, 29 Oct 2010 10:40:16 +0100
Received: from xx.xx.xxx.xxx (client IP) ([xx.xx.xxx.xxx (client IP)]) by webmail.unsertld.com
(Horde Framework) with HTTP; Fri, 29 Oct 2010 10:40:16 +0100
Message-ID: <20101029104016.11966jb1a1nijg8w@webmail.unsertld.com>
Date: Fri, 29 Oct 2010 10:40:16 +0100
From: mymailid@unsertld.com
To: mymailid@gmail.com
Subject: my Subject
MIME-Version: 1.0
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.3.6)
X-ME-Bayesian: 0.000000
Ich werde für jeden Tipp danken.
Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 154034
Url: https://administrator.de/contentid/154034
Ausgedruckt am: 24.11.2024 um 03:11 Uhr
4 Kommentare
Neuester Kommentar