Exchange 2013 OWA strips SMTP address of original sender when forwarding?
I have a customer that we just deployed Exchange 2013 to. They have an issue whereby User A, alice@gmail.com sends an email to bob@exchangedomain.com. Bob then forwards to Carol, who is also on exchange, via OWA. OWA appears to strip alice@gmail.com from the original email making it impossible for Carol to respond to Alice. If this a known issue? Is there a fix for this? Thanks in advance.
May 16th, 2013 10:23pm

On Thu, 16 May 2013 19:23:27 +0000, InquisIT Dave wrote: >I have a customer that we just deployed Exchange 2013 to. They have an issue whereby User A, alice@gmail.com sends an email to bob@exchangedomain.com. Bob then forwards to Carol, who is also on exchange, via OWA. OWA appears to strip alice@gmail.com from the original email making it impossible for Carol to respond to Alice. If this a known issue? Is there a fix for this? Fowarding a message always removes the original information in the message and makes it appear to come from the person that did the forwarding. It's always worked like that. If you use "Forward as an attachment" the recipient of the forward gets the original message and can respond as usual. Of course, the original sender may be surprised to get a reply from someone they never heard of! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2013 12:48am

On Thu, 16 May 2013 19:23:27 +0000, InquisIT Dave wrote: >I have a customer that we just deployed Exchange 2013 to. They have an issue whereby User A, alice@gmail.com sends an email to bob@exchangedomain.com. Bob then forwards to Carol, who is also on exchange, via OWA. OWA appears to strip alice@gmail.com from the original email making it impossible for Carol to respond to Alice. If this a known issue? Is there a fix for this? Fowarding a message always removes the original information in the message and makes it appear to come from the person that did the forwarding. It's always worked like that. If you use "Forward as an attachment" the recipient of the forward gets the original message and can respond as usual. Of course, the original sender may be surprised to get a reply from someone they never heard of! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
May 17th, 2013 12:48am

OWA in Exchange 2010 does not strip the SMTP address of the original sender. I do that all the time. How do you "forward as an attachment" in OWA 2013?
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2013 4:58pm

Select the email to be forwarded, Above the reading pane (Top Right Corner), you will see reply, reply all, forward, .... Click on the ... to see if we have an option to forward as attachment.
May 20th, 2013 10:32pm

On Mon, 20 May 2013 13:58:53 +0000, InquisIT Dave wrote: >OWA in Exchange 2010 does not strip the SMTP address of the original sender. It most certainly does. When the message arrives the "From" address is the person that forwarded the message, not the original sender. >I do that all the time. Are you sure you're not confusing the "From:" address of the forwarder with the address you see in the textual representation of the message headers in the forwarded message? They aren't the same thing. If you reply to the forwarded message you reply to the person that forwarded the message, not the person that originated the forwarded message. >How do you "forward as an attachment" in OWA 2013? Probably the same way you did in 2010. Select the message, right-click it, and select "Forward as an attachment". --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2013 1:50am

Yes. I understand that when you forward an email, the From address is the forwarder. What concerns me is the From address in the original email (now in the body of the forwarded or replied message), gets stripped of the SMTP address. In OWA 2010, this is preserved when forwarding, but in OWA 2013, it is not. As soon as you click on forward, it gets stripped out. (It's not just forwarding, but reply and reply all strip it out as well.) I use Chrome on Linux, so a right-click in OWA 2010 does nothing meaningful with respect to Exchange. Right-clicking on the message in OWA 2013 merely brings up: "delete, mark as unread, set flag, move, ignore conversation, categorize and create rule." No option to Forward as Attachment. Clicking on the three dots in the upper right hand corner next to "reply, reply all and forward" has a handful of options more than right clicking on the email in the list, but none of those are helpful in preserving the SMTP address of the original sender in the body of the email. My customer receives an email from someone on the internet. The office admin views the email and determines who to forward it to. When she forwards it, the original SMTP address is lost and the recipient of the forwarded email has to request the email address of the original sender.
May 21st, 2013 5:15am

Sorry. No dice. I have: replyreply by IMdeletecategorizemark as junkopen in separate windowprintcreate ruleview message details
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2013 5:17am

Hi Yes, as your understanding , when you reply to the forwarded email, the To filed filled in forwarder, original sender is not there, you can find the original sender from the message mail to :xxx and add the original sender manually.Wendy Liu TechNet Community Support
May 21st, 2013 4:04pm

Wendy. That's the thing. Under Exchange 2013 OWA, it's _not_ there. It strips the mailto: out of the original message. In Exchange 2010 OWA, it *IS* there, but in 2013, it's not. THAT is my issue. I've looked through the admin console to see if there's some magic setting that restores this, but I'm at a complete loss here.
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2013 4:29pm

I found out that it's a bug in Exchange 2013. =( Now the wait begins for a fix.
May 27th, 2013 9:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics