Sponsor:

Server and Web Integrator
Link:
Kloxo-MR logo
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:
Click Here
Please login or register. 2024-03-28, 17:44:14

Author Topic: Emails Going to Spam  (Read 27244 times)

0 Members and 1 Guest are viewing this topic.

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #30 on: 2013-09-10, 07:25:11 »
It does appear that it is going to be obsolete - hmmm... Interesting.  I will investigate more.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #31 on: 2013-09-10, 07:29:24 »
SPF TXT is still a must.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #32 on: 2013-09-10, 12:12:38 »
It was already enable it since I installed Kloxo-MR with no effect.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #33 on: 2013-09-10, 12:38:07 »
I just checked again with check-auth@verifier.port25.com and all seems fine :

Code: [Select]
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:  trader.adresemail.com
Source IP:      188.215.51.97
mail-from:      suport@adresemail.com

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=suport@adresemail.com
DNS record(s):
    adresemail.com. 300 IN SPF "v=spf1 a mx ~all"
    adresemail.com. 300 IN A 188.215.51.97

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: header.From=suport@adresemail.com
DNS record(s):
    private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJfqovcVQ94FaawMyCZxqsCD51unOf851HIDCLcMJo6LCevKb0MLJmY3VRShZPNWKQ1SNYWt33gIvJIMQIDAQAB"

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: suport@adresemail.com)
ID(s) verified: header.d=adresemail.com
Canonicalized Headers:
    message-id:<344A85AFB4444980A868799D66540940@traderPC>'0D''0A'
    from:"AdreseMail"'20'<suport@adresemail.com>'0D''0A'
    to:<check-auth@verifier.port25.com>'0D''0A'
    subject:spf'20'rec'0D''0A'
    date:Tue,'20'10'20'Sep'20'2013'20'09:29:23'20'+0300'0D''0A'
    mime-version:1.0'0D''0A'
    content-type:multipart/alternative;'20'boundary="----=_NextPart_000_0003_01CEAE08.3C1280A0"'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha1;'20'c=relaxed;'20'd=adresemail.com;'20'h='20'message-id:from:to:subject:date:mime-version:content-type;'20's='20'private;'20'bh=m7B3VGaAVYBbSyQegRRvB/O8NaI=;'20'b=

Canonicalized Body:
    Acesta'20'este'20'un'20'mesaj'20'cu'20'mai'20'multe'20'par?i'20''EE'n'20'format'20'MIME.'0D''0A'
    '0D''0A'
    ------=_NextPart_000_0003_01CEAE08.3C1280A0'0D''0A'
    Content-Type:'20'text/plain;'0D''0A'
    '09'charset="iso-8859-1"'0D''0A'
    Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
    '0D''0A'
    spf'20'record'20'?'0D''0A'
    '0D''0A'
    '0D''0A'
    ------=_NextPart_000_0003_01CEAE08.3C1280A0'0D''0A'
    Content-Type:'20'text/html;'0D''0A'
    '09'charset="iso-8859-1"'0D''0A'
    Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
    '0D''0A'
    <HTML><HEAD></HEAD>'0D''0A'
    <BODY'20'dir=3Dltr>'0D''0A'
    <DIV'20'dir=3Dltr>'0D''0A'
    <DIV'20'style=3D"FONT-SIZE:'20'12pt;'20'FONT-FAMILY:'20''27'Calibri'27';'20'COLOR:'20'#000000">'0D''0A'
    <DIV>spf'20'record'20'?</DIV>'0D''0A'
    <DIV>&nbsp;</DIV>'0D''0A'
    <DIV>&nbsp;</DIV></DIV></DIV></BODY></HTML>'0D''0A'
    '0D''0A'
    ------=_NextPart_000_0003_01CEAE08.3C1280A0--'0D''0A'
   

DNS record(s):
    private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJ3qov87VQE4FaawMyCZxqsCD51unOfhu51HIDCLcMJo6LievKb0MLJmY3VRShZPNWKQ1SNYWt33gIvJIMQIDAQAB"

Public key used for verification: private._domainkey.adresemail.com (1024 bits)

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=suport@adresemail.com
DNS record(s):
    adresemail.com. 300 IN SPF "v=spf1 a mx ~all"
    adresemail.com. 300 IN A 188.215.51.97

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)

Result:         ham  (-4.4 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-2.4 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
 0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                            domain
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature

==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================

SPF and Sender-ID Results
=========================

"none"
      No policy records were published at the sender's DNS domain.

"neutral"
      The sender's ADMD has asserted that it cannot or does not
      want to assert whether or not the sending IP address is authorized
      to send mail using the sender's DNS domain.

"pass"
      The client is authorized by the sender's ADMD to inject or
      relay mail on behalf of the sender's DNS domain.

"policy"
     The client is authorized to inject or relay mail on behalf
      of the sender's DNS domain according to the authentication
      method's algorithm, but local policy dictates that the result is
      unacceptable.

"fail"
      This client is explicitly not authorized to inject or
      relay mail using the sender's DNS domain.

"softfail"
      The sender's ADMD believes the client was not authorized
      to inject or relay mail using the sender's DNS domain, but is
      unwilling to make a strong assertion to that effect.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability to
      retrieve a policy record from DNS.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being absent or
      a syntax error in a retrieved DNS TXT record.  A later attempt is
      unlikely to produce a final result.


DKIM and DomainKeys Results
===========================

"none"
      The message was not signed.

"pass"
      The message was signed, the signature or signatures were
      acceptable to the verifier, and the signature(s) passed
      verification tests.

"fail"
      The message was signed and the signature or signatures were
      acceptable to the verifier, but they failed the verification
      test(s).

"policy"
      The message was signed but the signature or signatures were
      not acceptable to the verifier.

"neutral"
      The message was signed but the signature or signatures
      contained syntax errors or were not otherwise able to be
      processed.  This result SHOULD also be used for other
      failures not covered elsewhere in this list.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability
      to retrieve a public key.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being
      absent. A later attempt is unlikely to produce a final result.


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

Return-Path: <suport@adresemail.com>
Received: from trader.adresemail.com (188.215.51.97) by verifier.port25.com id h5qu3s11u9ck for <check-auth@verifier.port25.com>; Tue, 10 Sep 2013 02:29:18 -0400 (envelope-from <suport@adresemail.com>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=suport@adresemail.com
Authentication-Results: verifier.port25.com; domainkeys=pass header.From=suport@adresemail.com
Authentication-Results: verifier.port25.com; dkim=pass (matches From: suport@adresemail.com) header.d=adresemail.com
Authentication-Results: verifier.port25.com; sender-id=pass header.From=suport@adresemail.com
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=private; d=adresemail.com;
  b=wHzBgkQjzwqMa02TXYJtNitsqKf5OL5Ug2eCEAI6br7TvsgZnxiPFuDhzCMPqe+xkWWiQdsfLn6IW2faKyCKHVDSa1jOSI9VBLCQc9dcBkEGgcS5mjHl5nkaZFLUYP47wNCstn/b6dHGwtPQE1abq+UkrtfnLiQyjUa9X/0gz4k=;
  h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:Importance:X-Mailer:X-MimeOLE;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=adresemail.com; h=
message-id:from:to:subject:date:mime-version:content-type; s=
private; bh=m7B3VGaAVYBbSyQegRRvB/O8NaI=; b=zWa2zcNMcfnU94KzCcoO
UMzzzoBuHulojDkVyB6A5mNKUGwJf2LJk8TAlQBjslF5B2+bUvXBhJzY3x+Ur5VU
ByG/kb9YqukHbK0lI71P8T9GXNkhXyUr00OZfDREhIMItY4gXY6pxl4rOtuerGdv
5T0H8H7jnJXYtuw4ZAuekRU=
Received: (qmail 17528 invoked from network); 10 Sep 2013 06:28:00 -0000
Received: from unknown (HELO traderPC) (suport@adresemail.com@86.105.94.7)
  by trader.adresemail.com with ESMTPA; 10 Sep 2013 06:28:00 -0000
Message-ID: <344A85AFB4444980A868799D66540940@traderPC>
From: "AdreseMail" <suport@adresemail.com>
To: <check-auth@verifier.port25.com>
Subject: spf rec
Date: Tue, 10 Sep 2013 09:29:23 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0003_01CEAE08.3C1280A0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3508.205
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3508.205

Acesta este un mesaj cu mai multe par?i în format MIME.

------=_NextPart_000_0003_01CEAE08.3C1280A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

spf record ?


------=_NextPart_000_0003_01CEAE08.3C1280A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>spf record ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0003_01CEAE08.3C1280A0--






But the mail are still going to Gmail SPAM folder and the same problem on header :

Code: [Select]
Received: from unknown (HELO traderPC) (suport@adresemail.com@86.105.94.7)
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #34 on: 2013-09-10, 17:22:50 »
Under server setting in KloxoMR - goto Mail settings and for the mailserver name put the FQDN of the i.p. (reverse dns).

Example.  If your main i.p. resolves back to server1.myserver.com - use that as your mail server name.

You have the HELO name set and it is not resolving back to that name.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #35 on: 2013-09-10, 17:28:25 »
If the mail server is set correctly (over looked your check-auth again) then check the reverse dns for your i.p.

If it resolves back to TraderPC - that is the problem.  It has to resolve back to the FQDN.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #36 on: 2013-09-10, 17:36:35 »
86.105.94.7 resolves to
"ppp94105867.ambra.ro"
Top Level Domain: "ambra.ro"
Country IP Address: ROMANIA

This is your HELO problem.  Your i.p. does not resolve back to your mail server name.  This is a MUST.

You must have your provider set a PTR record for your i.p. - it needs to be trader.adresmail.com to have a correct HELO check (reverse dns to i.p.)

:)
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #37 on: 2013-09-10, 18:28:10 »
But its already there http://www.intodns.com/adresemail.com

Also Server Mail Settings have correct 'My Name' :
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #38 on: 2013-09-11, 04:14:28 »
Into DNS did you not see the BIG red block under MX concerning reverse dns PTR records?

You have none.  So public email hosts try to verify your SPF and your HELO name and it comes back wrong.

You must have your provider put in a reverse dns record (PTR).

Look again at intodns.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #39 on: 2013-09-11, 17:14:46 »
I don't see any red but only green, I don't know where you sow that  :( First thing I did when mail went to SPAM was to ask ISP to put PTR  http://postimg.org/image/74481yd0f/
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #40 on: 2013-09-12, 09:57:13 »
yes the PTR is now showing.  At this point you should NOT be going to spam.  Unless you have sent so much mail testing gmail has flagged the i.p.

I would mark mail as not spam.  send mail to gmail and make sure it goes to inbox.  then open a new gmail account and test.

it appears that some mail providers (hotmail and yahoo) will flag as junk/spam when a new ip starts sending mail to thier servers.  if after time your mail is marked as not spam your server will start sending mail directly to inbox.

Has it started going to inbox?
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

Offline MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,807
  • Karma: +119/-11
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: Emails Going to Spam
« Reply #41 on: 2013-09-12, 14:50:04 »
Think about this.

Say it, we did to set wrong domain settings (without SPF and or domainkeys). And then we sent email to gmail.com. Yes, our message as 'spam'.

And then we corected domain settings and but why still as 'spam'?.

1. The answer is not every message check by qmail.com one-by-one. Gmail look up to their 'spam' database. If our email as 'spammer' in database so gmail think our  message as 'spam'.

2. If someone set our message as 'not spam' in gmail panel, then gmail remove out email as 'spammer' in gmail database.

3. If no action like step 2 (set as 'no spam'), gmail will be evaluate periodically (say it every month) for 'spam' status in their database.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #42 on: 2013-09-12, 19:29:20 »
Well, the problem its still there , all mails are sent to gmail SPAM folder. Some friend used his own server to test my domain and mails are sent ok to inbox. I even changed PTR on ISP and accordinly hostname, mailname, mx, a and cname records. The exact same result. I asked hosting provider about IP and they told me I'am the first one using it. any spam test are fine . This problem is killing me.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline crossing

  • Senior Member
  • *
  • Posts: 336
  • Karma: +0/-0
    • View Profile
Re: Emails Going to Spam
« Reply #43 on: 2013-09-12, 19:49:12 »
Even when I send from webmail I get on gmail header 'Received: from unknown (HELO mx.zumzi.eu) (marius@zumzi.eu@127.0.0.1)'

Code: [Select]
                                                                                                                                                                                                                                                             
Delivered-To: senuke22@gmail.com
Received: by 10.70.69.161 with SMTP id f1csp21771pdu;
        Thu, 12 Sep 2013 06:45:34 -0700 (PDT)
X-Received: by 10.14.183.130 with SMTP id q2mr10764547eem.5.1378993534232;
        Thu, 12 Sep 2013 06:45:34 -0700 (PDT)
Return-Path: <marius@zumzi.eu>
Received: from mx.zumzi.eu (mx.zumzi.eu. [188.215.51.97])
        by mx.google.com with ESMTPS id p9si3192288eeu.204.1969.12.31.16.00.00
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Thu, 12 Sep 2013 06:45:33 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of marius@zumzi.eu designates 188.215.51.97 as permitted sender) client-ip=188.215.51.97;
Authentication-Results: mx.google.com;
       spf=pass (google.com: best guess record for domain of marius@zumzi.eu designates 188.215.51.97 as permitted sender) smtp.mail=marius@zumzi.eu;
       dkim=pass header.i=@zumzi.eu
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=private; d=zumzi.eu;
  b=IELt3c1NpTXyVyrG6qE+Lpo2LW/QtiIz2eWQWP5eYAwWcmpw/Ww1yzqALDPuoIKzHZXyjYuSaBffXBUI6R+aYBSDgpr5jXOh10iqBk9qbSJoR8Slt7S4I8KuxLmo5DfRtr8U0j9DJvQOLwCrH6jyfj/lpGuxGFumfObuV8FUgr4=;
  h=Received:Received:Mime-Version:X-Mailer:Message-ID:Date:Content-Type:From:Subject:To:X-Priority;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zumzi.eu; h=mime-version
:message-id:date:content-type:from:subject:to; s=private; bh=WkB
6nGuVC2SQoEad87298nOztas=; b=s4zNWgDOfXNjG5Rt+KSPkXkn1utYHvSgqNo
3lwovRT2sdEeVp9FvK3nO/OPAWaduysRr4zsR0P+D5IpIy3C5pStHEL44AXh3wlt
R+UGE7ZW6/y9Mm4OGChRPDRlm3xppSuWfAClpFrVbO0jKKqrtpWKbZ/eUkLsd9P+
qWsKN4lc=
Received: (qmail 7359 invoked from network); 12 Sep 2013 13:44:11 -0000
Received: from unknown (HELO mx.zumzi.eu) (marius@zumzi.eu@127.0.0.1)
  by mx.zumzi.eu with ESMTPA; 12 Sep 2013 13:44:11 -0000
Mime-Version: 1.0
X-Mailer: AfterLogic WebMail PHP
Message-ID: <b9d50d40cd17dfdb688609f71249cafc@webmail.zumzi.eu>
Date: Thu, 12 Sep 2013 13:44:11 +0000
Content-Type: multipart/alternative;
 boundary="----=_Part_918_628832272.1378993451"
From: marius@zumzi.eu
Subject: right
To: senuke22@gmail.com
X-Priority: 3 (Normal)


------=_Part_918_628832272.1378993451
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable

wrong

------=_Part_918_628832272.1378993451
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable

<!DOCTYPE html><html dir=3D"ltr"><head><meta http-equiv=3D"Content-Type" =
content=3D"text/html; charset=3Dutf-8" /><head><body><div><div>wrong</div=
></div></body></html>

------=_Part_918_628832272.1378993451--
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Kloxo-MR -> Great Panel ->  Great person behind it ->  Mustafa

Offline chrisf

  • Senior Master
  • **
  • Posts: 883
  • Karma: +11/-1
  • Gender: Male
  • Be the change that you wish to see in the world.
    • View Profile
    • Conviction's Hosting
Re: Emails Going to Spam
« Reply #44 on: 2013-09-13, 00:08:48 »
I do not understand how every time you post your HELO name changes.  Why is google not able to resolve where the mail is coming from?

I am not familiar with cloudflare.
« Last Edit: 1970-01-01, 01:00:00 by Guest »
Christopher

Knowledge in: PHP, Perl, MySQL, Javascript, Actionscript, FLASH, HTML, CSS
Server Administrator / Developer: https://convictionshosting.com

 


Top 4 Global Search Engines:    Google    Bing    Baidu    Yahoo
Click Here

Page created in 0.034 seconds with 18 queries.

web stats analysis