Link to home
Start Free TrialLog in
Avatar of Dan
DanFlag for United States of America

asked on

exchange email rejected

I am running exchange 2013.  We have a website where we are advertising a live streaming event.   People can then enter their email address and their friends email adders to send an evite.  When the server sends the email, the email go to the name specified and the from is the person who entered their email address. Looks like somewhere there's a problem, as people, I think everyone are getting their emails returned back to them.  Here's the error message, I'm trying to figure out if it's my problem, or is it yahoo's problem or who's ever email provider they are using.

I changed my domain name to @mydomain.org, but can someone validate if this is my problem with exchange, or yahoo's issue?

Thanks, Dan



On Thursday, October 16, 2014 9:19 PM, Mail Delivery System <Mailer-Daemon@mail.mydomain.org> wrote:

This message was created automatically by the SMTP relay on mail.myDomain.com.org.
 
A message that you sent could not be delivered to all of its recipients.
The following address(es) failed:

  dickwilson822@yahoo.com
    SMTP error from remote mail server after end of data:
    host mta6.am0.yahoodns.net [98.138.112.34]: 554 5.7.9 Message not accepted for policy reasons.  
      See http://postmaster.yahoo.com/errors/postmaster-28.html

------ This is a copy of the message, including all the headers. ------

Return-path: <daveekstrom@yahoo.com>
Received: from [74.116.125.253] (port=57387 helo=levi)
    by mail.myDomain.com.org with esmtp (Exim 4.82_1-5b7a7c0-XX)
    (envelope-from <daveekstrom@yahoo.com>)
    id 1Xf1K9-0000A3-2x
    for dickwilson822@yahoo.com; Thu, 16 Oct 2014 23:47:41 -0700
MIME-Version: 1.0
From: daveekstrom@yahoo.com
To: dickwilson822@yahoo.com
Reply-To: daveekstrom@yahoo.com
Date: 16 Oct 2014 21:19:05 -0700
Subject: Dave Ekstrom has sent you an eVite!
Content-Type: multipart/alternative;
boundary=--boundary_86_8204d11c-c020-4021-b1b4-cbcde3d91eef


----boundary_86_8204d11c-c020-4021-b1b4-cbcde3d91eef
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

ICBEYXZlIEVrc3Ryb20gd2FudHMgdG8gaW52aXRlIHlvdSB0byBMYW5kbWFya3Mgb2Yg
UHJvcGhlY3khIA0KICAgDQogd3d3LmxhbmRtYXJrc29mcHJvcGhlY3kuY29tICA=
----boundary_86_8204d11c-c020-4021-b1b4-cbcde3d91eef
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<center><div style=3D"font-family: arial; font-size: 14px; line-h=
eight: 21px;">Dave Ekstrom wants to invite you to Landmarks of Pr=
ophecy!</div><br><a href=3D"http://www.landmarksofprophecy.com/ev=
ent-resources/evite-a-friend/cardtype/view/messageid/205106"><img=
src=3D"http://manna.myDomain.com.org/myDomain.com/website/landma=
rksofprophecy/images/lop-invite-unopened.jpg" border=3D"0"></a><b=
r><a href=3D"http://www.landmarksofprophecy.com/event-resources/e=
vite-a-friend/cardtype/view/messageid/205106" target=3D"_blank" s=
tyle=3D"font-family: arial; font-size: 11px;">www.landmarksofprop=
hecy.com</a></center>
----boundary_86_8204d11c-c020-4021-b1b4-cbcde3d91eef--
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Dan

ASKER

interesting, as it does work some of the time.  We tested different emails, hotmail, gmail and yahoo, countermail, and some worked and some did not.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It will work some of the time because not everyone implements SPF and therefore a receiving server that checks SPF for incoming emails and doesn't find a published SPF record for the sending domain will not fail the SPF check.

Other domains that do implement SPF will fail the check (unless their SPF record is extremely loose / incorrect) and thus there is no 100% guaranteed way to fix the problem when using a 'spoofed' sender as opposed to a genuine sender on your domain (or a noreply@ as suggested above).

Alan
Avatar of Dan

ASKER

Thanks guys, we just changed the configuration to use an internal email address from our domain, and it seems to be working now.