• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4342
  • Last Modified:

Incorrect reply to address Outlook 365

I have been using Outlook 365 for over a year now but in the last month or 2, I have had several clients telling me their emails to me are being bounced back.  After doing some digging and analyzing, I determined when the recipient replies to my email, the "reply to" address is filling in incorrectly.  My actual email address would be aperson@df.,com, but the reply to address being filled in and the address they are subsequently sending to is aperson@dgw.com.  How can I change this?  I am concerned about all the replies I am not getting.  This does not seem to affect all, but the list of clients and vendors it is affecting is growing.  I need to find where that setting is incorrect and change it.

Emails sent directly to the correct email address are not affected.

Thanks.
0
perk83
Asked:
perk83
  • 3
  • 2
1 Solution
 
Vasil Michev (MVP)Commented:
What is the second domain then, something random or something you have verified in Office 365? Are you sure you are not sending those messages on behalf of/as a different user? Any example NDR?

If the second domain is verified in Office 365, you should be able to run a trace on such messages. I suggest doing the same for the outgoing message to make sure the from/reply-to address is not overwritten by something.
0
 
perk83Author Commented:
The second domain would be the aperson@dgw.com.  That is the incorrect address replies are being sent to.  Nothing I have verified with 365,

Here is the NDR.  csg-dfw.com is the valid domain for my company.  csg-dgw.com is the invalid one that is popping in somehow.


Generating server: BY2PR04MB143.namprd04.prod.outlook.com
aperkins@csg-dgw.com
Remote Server returned '550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain''
Original message headers:
Received: from BY2PR04MB239.namprd04.prod.outlook.com (10.242.41.27) by
 BY2PR04MB143.namprd04.prod.outlook.com (10.242.40.148) with Microsoft SMTP
 Server (TLS) id 15.0.775.9; Tue, 22 Oct 2013 15:52:29 +0000
Received: from BY2PR04MB240.namprd04.prod.outlook.com (10.242.41.21) by
 BY2PR04MB239.namprd04.prod.outlook.com (10.242.41.27) with Microsoft SMTP
 Server (TLS) id 15.0.785.10; Tue, 22 Oct 2013 15:52:26 +0000
Received: from BY2PR04MB240.namprd04.prod.outlook.com ([169.254.15.99]) by
 BY2PR04MB240.namprd04.prod.outlook.com ([169.254.15.190]) with mapi id
 15.00.0785.001; Tue, 22 Oct 2013 15:52:26 +0000
From: Aaron Perkins <APERKINS@csg-dfw.com>
To: "Juma, Shereef" <Shereef.Juma@corp.earthlink.com>
CC: aperkins <aperkins@csg-dgw.com>, "Francisco.Ulloa@corp.earthlink.com"
 <Francisco.Ulloa@corp.earthlink.com>, "Charles.Wood@corp.earthlink.com"
     <Charles.Wood@corp.earthlink.com>, "Hudson, David"
        <David.Hudson@corp.earthlink.com>, Tina Atchley
      <tina.atchley@corp.earthlink.com>
Subject: RE: Conroe Memory Care EarthLink permanent solution order update.
Thread-Topic: Conroe Memory Care EarthLink permanent solution order update.
Thread-Index: Ac7PPf2+Xgo5mgSKi0CGk/tU0BXligAAINI9
Date: Tue, 22 Oct 2013 15:52:25 +0000
Message-ID: <29e391716a854527957f6cbdaa57993c@BY2PR04MB240.namprd04.prod.outlook.com>
References: <y8jkev5sxmt1r5kw4onx554f.1382456839926@email.android.com>
In-Reply-To: <y8jkev5sxmt1r5kw4onx554f.1382456839926@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.70.168.111]
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM;SFS:(377454003)(38605003)(51164003)(24454002)(199002)(189002)(479174003)(74366001)(15202345003)(74662001)(74706001)(85306002)(15975445006)(74876001)(33646001)(65816001)(63696002)(79102001)(77982001)(59766001)(66066001)(81686001)(49866001)(47736001)(54356001)(81542001)(50986001)(56816003)(31966008)(16236675002)(47446002)(69226001)(76576001)(47976001)(77096001)(76796001)(83072001)(76786001)(56776001)(54316002)(81342001)(74316001)(80976001)(19580405001)(19580395003)(83322001)(51856001)(4396001)(81816001)(46102001)(53806001)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:BY2PR04MB239;H:BY2PR04MB240.namprd04.prod.outlook.com;CLIP:207.70.168.111;FPR:;RD:InfoNoRecords;A:1;MX:1;LANG:en;
Content-Type: multipart/alternative;
      boundary="_000_29e391716a854527957f6cbdaa57993cBY2PR04MB240namprd04pro_"
MIME-Version: 1.0
Return-Path: APERKINS@csg-dfw.com
X-OriginatorOrg: csg-dfw.com
0
 
Vasil Michev (MVP)Commented:
What I meant is can you get an NDR from the other side, so that we can see where it is actually send to. You can also get the headers from a received message for comparison.


The @email.android.com bit hints for some mobile device involved and probably google's mail servers, god know what happens in between.
0
 
perk83Author Commented:
That is actually from the other side.  I replied to an email I sent myself and this was the NDR I received.

At first I thought it was only occurring from email generated from my cell phone, but this morning it occurred when I generate an email from OWA as well.
0
 
perk83Author Commented:
I believe I found the issue.  I went to delete the email account on my droid last night to see if that might be the cause and when I did, I noticed it had the email address listed as csg-dgw.com which is the incorrect one.  I had looked and looked and was unable to find where I could change that in the settings for my email on the phone but I believe by deleting the account, that has resolved the problem.  I now see it says the correct email address in my settings where it had the incorrect one.

I awarded vasilcho the points since the comment about the @email.android.com lead me to at least try to remove the account from my phone.

Thank you all for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now