Solved

Exchange 2013 emails marked as SPAM

Posted on 2014-02-17
4
629 Views
Last Modified: 2014-02-19
Hello ,


I have an Exchange 2013 Infastracture , 2 Servers . An all in one Exchange 2013 and an exchange 2010 EDGE . Some emails are marked as spam in yahoo and  gmail .  My ip's are not blacklisted , i have SPF records , reverse dns records .  Unfortunately i don't have the headers of this emails that marked as spam . Is there something i can look on it ?


Thanks
0
Comment
Question by:Anestis Psomas
  • 2
  • 2
4 Comments
 
LVL 15

Expert Comment

by:MarkMichael
ID: 39865223
You seem to have covered the bases around preventing your servers from looking fraudulent.

This would be much easier with headers, could you create yourself a gmail account or do you have one you can use temporarily to retrieve the headers?
0
 

Author Comment

by:Anestis Psomas
ID: 39866684
I have already a yahoo account . Here is the headers . This email delivered in inbox without any problems. For some reaseon some emails go to spam folders . I dont have any example with headers for spam email ,


From Anestis Psomas Mon Feb 17 02:07:25 2014
X-Apparently-To: anestis.psomas@yahoo.com via 72.30.236.223; Mon, 17 Feb 2014 10:07:43 +0000
Return-Path: <a.psomas@interworkscloud.com>
Received-SPF: pass (domain of interworkscloud.com designates 178.23.73.31 as permitted sender)
 QWRtaW5pc3RyYXRvciBNQ0lUUCAsIE1DVFMgLCBDQ05BIGVtYWlsOiBhLnBz
 b21hc0BpbnRlcndvcmtzY2xvdWQuY29tIHdlYnNpdGU6IGh0dHA6Ly93d3cu
 aW50ZXJ3b3Jrc2Nsb3VkLmNvbSBUZWwuOiAwMDMwIDIzMTAgNjg4LjE4Niwg
 RmF4OiAwMDMwIDIzMTAgNjg4LjE4NCABMAEBAQEDdGV4dC9wbGFpbgMDMAID
 dGV4dC9odG1sAwMz
X-YMailISG: AXszLAUWLDsfQBTYqe51Y.ENq99Y1M43V9kSNS0IGnZqAtyN
 F9G8aqb6gIjnk4en9G8NZuFf0addHwUbT0uzi07gTvKIE3Do0HdpbTJbW58k
 EHO7EYI6zoLHhWV0RunefTY.SW6KImlN8FeamGg4ZVKTvYx35DBJe8V3tSEI
 tScOJR3Gg5c9ZTeT_xNogdJiW_OuHdu5_NJmtGPIwSzfCbVSAseicUirWpB6
 49tp6lMWQ3zokE5CTy.EkDWk7u7R8X6ezo3T5PF_x.uJFiVvIaVA4Q_cEPVo
 Q_kohotxsQZzMWGZBs0yJqt7BPzp.6_k35At5wpfAtinn0m.djdzQkOi4Zrp
 atxrWWFMNAuk2tdGe1LzkhWZQFtzLmhn5fVJ_rb.x0le40o.iy8wL8YANpM6
 KHQf10L14j6Jk.aUpiz0AJn1yoJmwCIIuunSUIEO8WFIKVHtGsrGedWIDR._
 xOb9zqU2QvjO1DfjU9KqPj6JNGrIsQDsuxHPXQtpfxQ9yIrg.m7guuysN_ad
 G.6wxfkcjlfK6Dqw.7LSgfhl9GUKrFPn9bmSUnIf_LcC1.SwBpFe1hj6K2KM
 KTKhkmMPYr2JxBhkRhjxoUOfsGM_JINf_3IvDPECLkzaa1BxnzryRAt1HacU
 _QcHm2p04__uropUdGhEA40d8WpPQxFKgk2OQEMI1iPhU4JRjG_0wPCz5SJN
 rpUi2bcmuDqO0.SZ8XUFIvslVboHrl6TrkBnlZ.6PKoj5FXy6EIqtnuZ31DC
 f.1PnNXMKxmoCLm17_mVK_hS9_SMKUGtGAYbDASOMdRzk5AFKnclAFunX.xB
 Nph.7QgO0EAGduQ2hwUXIiAYMDH_4ytM.J66pewYnE6pCdPMeGgS98swUt5T
 xyHExC1ec3ez7MU0f1GWZ9sj.Rbwyhit4en3WLduEczh8d_RV6o2LZ4KfEEr
 tO3dTxR6LPzKms2Wg.MkmoXTbx_EL3yyJXGqOVPJ56JP5hY2IMWaIMZ6WFaG
 hq8rhU61rAM8vx5LqpLFsJ6Ov3GioRHEQEIqA8nc9m5cqL0RAVF5XkzkAG.y
 .VwUSd.EPoqAm93r7VmIEFu.82nvoD.fmAP5imH4uElxZFUKNPi2tv1e.JOz
 C92OyFgi3dNDHL57XNB_8nT14JLtMC7Lwrmae6RYH9gwrcVajmc7y59kmtZ0
 2d0yFwoEeKoYX8mPOl3fVVf69uD_iGUqfK.HDM1KnXhbdRhZCaxzl9RQOGk8
 JcDxKGqCvwEK2WIyrohL3e_FWYfWUChJ.FwEFLjYd3IdM0nMbiJ2UQs265..
 h2YlUSvKmMJmGiKyjX4GcUz2PBA-
X-Originating-IP: [178.23.73.31]
Authentication-Results: mta1451.mail.bf1.yahoo.com  from=interworkscloud.com; domainkeys=neutral (no sig);  from=interworkscloud.com; dkim=neutral (no sig)
Received: from 127.0.0.1  (EHLO mail.interworks.gr) (178.23.73.31)
  by mta1451.mail.bf1.yahoo.com with SMTPS; Mon, 17 Feb 2014 10:07:42 +0000
Received: from EXCHANGE2013.interworks.eu (192.168.0.166) by
 exchange2013.interworks.eu (192.168.0.166) with Microsoft SMTP Server (TLS)
 id 15.0.712.24; Mon, 17 Feb 2014 12:07:26 +0200
Received: from EXCHANGE2013.interworks.eu ([fe80::3910:d2fd:d940:65d5]) by
 exchange2013.interworks.eu ([fe80::3910:d2fd:d940:65d5%12]) with mapi id
 15.00.0712.012; Mon, 17 Feb 2014 12:07:26 +0200
From: Anestis Psomas <a.psomas@interworkscloud.com>
To: "anestis.psomas@yahoo.com" <anestis.psomas@yahoo.com>
Subject: test
Thread-Topic: test
Thread-Index: Ac8ryA1IVBXOyfPQQ7GAme21j1DF3Q==
Date: Mon, 17 Feb 2014 10:07:25 +0000
Message-ID: <a9bf475de7c24686879500bfcf821bf6@exchange2013.interworks.eu>
Accept-Language: en-GB, el-GR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.40.17]
Content-Type: multipart/alternative;
      boundary="_000_a9bf475de7c24686879500bfcf821bf6exchange2013interworkse_"
MIME-Version: 1.0
Content-Length: 3264
0
 
LVL 15

Accepted Solution

by:
MarkMichael earned 500 total points
ID: 39866754
I can't see any problems with this particular header.

It's always good to put the header into mxtoolbox header analyser too, to have a look for errors:

http://mxtoolbox.com/EmailHeaders.aspx
0
 

Author Comment

by:Anestis Psomas
ID: 39870088
I thing maybe the problem with yahoo is that i have no DKIM and Domain Keys. I have create just to be sure .

Thanks
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now