glennda Posted October 14, 2011 Posted October 14, 2011 I've had a few reports of when users try and reply directly to a forwarded email they get a IMCEAMAILTO bounce it. I've seen this here IMCEAMAILTO issue causing "Delivery has failed ...". but this refers to outlook 2007 and i'm using 2010. (using exchange 2k7 sp3 but i think its a client issue). Anybody any ideas? Toby
glennda Posted October 16, 2011 Author Posted October 16, 2011 here it is below, as previously mentioned i think it is outlook which is causing the error as its when somebody tries to reply directly to a forwarded message, for example below useremail has sent into our generic office@domain which is then forwarded onto sender@mydomain who replys directly to useremail but its failing as its adding mydomain.org.uk to the @ talktalk email address. does that make sense? if not i'll try and explain again! Diagnostic information for administrators: Generating server: site-svr-018.myinternaldomain.internal IMCEAMAILTO-useremail+40talktalk+2Enet@Mydomain.org.uk #550 5.4.4 ROUTING.NoNextHop; unable to route ## Original message headers: Received: from EXCHANGE-01.WEALDSCHOOL.internal ([0000:0000:0000:0000:0000:0000:0.0.0.1]) by wld-svr-018.WEALDSCHOOL.internal ([192.168.112.18]) with mapi; Thu, 13 Oct 2011 13:33:15 +0100 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: sender <[email protected]> To: "'useremail@talktalk.net'" Date: Thu, 13 Oct 2011 13:35:26 +0100 Subject: Documents for parents of Year 7 students Thread-Topic: Documents for parents of Year 7 students Thread-Index: AcyJo/lnp8nvrOgkSCCXEmMna7WBbA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: MIME-Version: 1.0
sukh Posted October 16, 2011 Posted October 16, 2011 it does appaer to be an outlook issue, when the email is composed set what type it is set to. If youre using 2010 SP1, remove SP1 and test and there have been issues with how Outlook handles HTML link/tags. 1
glennda Posted October 16, 2011 Author Posted October 16, 2011 yeah i will double check with the users inhow outlook is setup - from the microsoft article above it mentions that it was a word issue. I'll try playing with how outlooks sending the email.
sukh Posted October 16, 2011 Posted October 16, 2011 same issue with Office 2010 SP1 as above. Removing SP1 has helped resolve a very similar issue as yours. 1
glennda Posted October 16, 2011 Author Posted October 16, 2011 is there an easy way to remove through wsus?
glennda Posted October 16, 2011 Author Posted October 16, 2011 is there an easy way to remove through wsus? I've setup for removal - so will see what happens T
glennda Posted October 16, 2011 Author Posted October 16, 2011 I've put them in a group and removed the update for that group.
glennda Posted October 20, 2011 Author Posted October 20, 2011 What happened with this? Removing SP1 seems to have fixed the issue - sorry meant to post back! I've now removed across the site - not in tomorrow but going to report to MS next week.
sukh Posted October 20, 2011 Posted October 20, 2011 I believe this will be addressed in SP2. Will check for you. 1
sukh Posted December 15, 2011 Posted December 15, 2011 This has been addressed by this fix Description of the Word 2010 hotfix package (Word-x-none.msp): December 13, 2011 1
glennda Posted December 15, 2011 Author Posted December 15, 2011 Cool I can roll out SP1 again now! Cheers
sonofsanta Posted July 9, 2012 Posted July 9, 2012 (edited) Bit of a necro, but this thread just popped up in Google while I was trying to remember how to fix this, and figured I'd post as there is a much easier way than removing Service Packs or rolling out updates In the Outlook that is having the problem, open a new email and start addressing it to the problematic recipient, and tab to autocomplete the address. Then hover over the address and select Outlook Properties from the drop down on the hover box (4ith icon). It should open a small window like this: Note the email type is "mailto". This is the problem. Click the "Internet Type" button and click OK, then send the email (you have to send something to clear the error). It should be fine going forward now for that recipient. It's Outlook 2007/10 being thick with how it interprets email addresses from webpages. You can recreate it quite easily by addressing an email as [mailto:[email protected]] (with the square brackets and mailto: prefix) - once you've sent one email with the address in that format, any emails sent to the address in future will fail as above. You then have to go through the steps I just listed to clear it. Should be a bit quicker than the software fix if someone needs to get the email off quick. Once it's fixed it doesn't recur and it doesn't tend to crop up very often afterwards - hence me having to reGoogle to work out how I fixed it before! (image taken from this article on the same topic: Exchange: Delivery has failed to these recipients or distribution lists – IMCEAMAILTO | Robin CM's IT Blog) Edited July 9, 2012 by sonofsanta
glennda Posted July 9, 2012 Author Posted July 9, 2012 For Office 2007 there is a Hotfix - as yet I don't think there is a hotfix for 2010. Its only an issue with SP1 so i presume at some point M$ will release a similar hotfix for 2010.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now