Solved Replies to emails from MS account go to my other MS acct

SOLVED: Replies to emails from MS account go to my other

OK, I'm stumped.

My primary MS account is John@JohnsDomain.com. It has an alias JohnsALIAS@outlook.com. When I send email, the sender is John@JohnsDomain.com. I use this account for all my email and is my sign in for all my Windows machines and Windows Phone.

I have a 2nd MS account, John@outlook.com. I use this just for email and mainly for bills and notices.

I use Outlook.com web access for email and can sign in to either account and email from either. It had been working fine for years. About a month ago, in the course of changing passwords, I did something. Now, replies to emails I send from John@JohnsDomain.com started going to John@outlook.com. Doesn't matter if I use PC or WP. Doesn't matter if I reply to an email received originally on John@JohnsDomain, if I send out an email from John@JohnsDomain, any reply will go to John@outlook.

Anybody know this problem or have any ideas? TIA

can you show the header information from

1. an outgoing email
2. a reply that goes to the wrong account.

Here's an outgoing (I'm replying to an email received at John@JohnsDomain.com):

X-TMN: [YJOafn2ZdEDbjbFoljajBJNDof91g+0z]
Message-ID: <BAY178-W5B667CADF18691960CC48CC1E0@phx.gbl>
Content-Type: multipart/alternative;
boundary="_d621078d-fcc5-440b-938c-565d809cd59a_"
Reply-To: <bobbyyee@outlook.com>
From: Bobby Yee <bobby@bobbyyee.com>
To: Rick Webber <rickewebber@comcast.net>
Subject: RE: Lunch
Date: Mon, 23 Jun 2014 17:17:01 -0700
Importance: Normal
In-Reply-To: <00de01cf8f3a$919c52d0$b4d4f870$@comcast.net>
References: <00de01cf8f3a$919c52d0$b4d4f870$@comcast.net>
MIME-Version: 1.0

--_d621078d-fcc5-440b-938c-565d809cd59a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

no problemo=2C same place=2C 12:30?
=20
From: rickewebber@comcast.net
To: bobby@bobbyyee.com
Subject: Lunch
Date: Mon=2C 23 Jun 2014 16:26:32 -0700

Hey Bobby=2C Could we change lunch date to Thursday? =

Here's an incoming reply from a sender that went to the wrong account:

x-store-info:J++/JTCzmObr++wNraA4Pa4f5Xd6uensWQjutc4PB1CXtvQh/hoNtHcBvuEM8phrke+bSuur6/3ZaG2UNX9/xPea6PDkloJSnRtUxuAIuLw87+XJuVnyvzTRGiKkjle+wnw7feAU5iQ=
Authentication-Results: hotmail.com; spf=pass (sender IP is 76.96.30.96; identity alignment result is pass and alignment mode is relaxed) smtp.mailfrom=rickewebber@comcast.net; dkim=pass (identity alignment result is pass and alignment mode is relaxed) header.d=comcast.net; x-hmca=pass header.id=rickewebber@comcast.net
X-SID-PRA: rickewebber@comcast.net
X-AUTH-Result: PASS
X-SID-Result: PASS
X-Message-Status: n:n
X-Message-Delivery: Vj0xLjE7dXM9MDtsPTE7YT0xO0Q9MTtHRD0xO1NDTD0w
X-Message-Info: rLItp1kDnk6RmCZquIVwumbCogmiFZ1CjK+l7fLia/i+o/9CYTeC30aSug0G99N5serc4S5+kaUzeuQmLbVB2G5Cl7V1X6BayB2e8ZpZ18gG3vkIIsETlEq8iO5B5mu6G5zyHF5sRiZAljRlALiJzvRknfbHFcPLOBiwGwC6YowxqJdPDGp1K2hDWvS18VgOdscwIhwnK25ksyOUvutnPC1qKh+mLIs5
Received: from qmta09.emeryville.ca.mail.comcast.net ([76.96.30.96]) by BAY004-MC2F59.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22712);
Mon, 23 Jun 2014 16:28:13 -0700
Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60])
by qmta09.emeryville.ca.mail.comcast.net with comcast
id HyQQ1o0031HpZEsA9zUCSy; Mon, 23 Jun 2014 23:28:12 +0000
Received: from rick ([24.4.125.206])
by omta14.emeryville.ca.mail.comcast.net with comcast
id HzUB1o00z4TJRRk8azUCKk; Mon, 23 Jun 2014 23:28:12 +0000
From: "Rick Webber" <rickewebber@comcast.net>
To: "'Bobby Yee'" <bobbyyee@outlook.com>
References:
In-Reply-To:
Subject: FW: Lunch
Date: Mon, 23 Jun 2014 16:28:08 -0700
Message-ID: <00e301cf8f3a$cad3ff80$607bfe80$@comcast.net>
MIME-Version: 1.0

Hmmm, looks like it's something with my outgoing email ...

Problem is solved.

Thanks @wullail, attaching the outgoing header enabled me to see the reply to address and realize it could be set to the 2nd account. I finally found where to change it, and there was the 2nd address.

I just got back home and noticed the issue too..but I'm glad it helped you solve it yourself.