HOSTS file not used 451 4.4.0 DNS query failed

Follow me Recently, while working on an issue with Email Delivery on Microsoft Exchange 2007 Service Pack 3 Servers. Environment: Exchange 2007 Hub & Exchange 2007 Edge Servers separately configured. Analysis: Further checking on the issue found the following error message on the Exchange Server Messaging Queue: HOSTS file not used 451 4.4.0 DNS query failed After a lot of research and wasted hours, I was able to figure out the solution which worked for me. Hoping that this shall also help you. Solution: Under the Network Binding order, “Network Connections – Advanced – Advanced Settings”, ensure that you have the proper Network Adaptor on the top of the list. You can also consider to disable any unused Network Adaptors on the Servers. This shall be a very good practice. Follow...

Exchange: Auto Forward emails missing Sender information

Follow me If a user setup an outlook rule to auto forward all the emails to some other user, than the end user cannot find out the original sender of the email. Solution Unfortunately none, this is by design and has been an issue since Exchange 2003 and is present uptil Exchange 2013, though there are a couple of workarounds to the issue 1) While creating the auto forward rule, select the option to Blind Carbon copy (BCC)the message to addresses” and provide the required recipient addresses 2) Or you can always modify the rule to forward the email as an attachment to required people or group Feel free to start a new thread on our forum to seek expert help. Follow me...

Exchange:NDR due to X500 address change Error:The email address you entered couldn’t be found

NDR with junk email address It is not uncommon that in Microsoft Exchange environment some times a user to whom uptill yesterday everyone was able to send the email, suddenly all the internal users start to get an NDR (Non Delivery Report) with a junk email address when trying to send email to the person. And If you are unlucky as me then that guy would always be some VVIP of the company 🙂 . we receive complain like some users are not able to send email to a particular user, and they get NDR as below: You might notice the user name is hyper linked and when you resolve it by pressing (Ctrl+Click) , new memo opens with junk email id. Example: Delivery has failed to these recipients or groups: Harish Chadda The email address you entered couldn’t be found. Please check the recipient’s email address and try to resend the message. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: CPUNEXCHOTZP14.xyx.itm IMCEAEX-_o=One+20Xyx+20Messaging_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23 SPDLT+29_cn=Recipients_cn=2b52ff2434754ff6b3ea72e2f0465c42-Vij@xyx.com Remote Server returned ‘550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found’ Cause: If you go behind the scene, you will find the tech team is not completely innocent in the case, some thing weird happened last night the original mailbox was deleted for the user and a new mailbox was created with the same SMTP address or something similar happened. This issue occurs because the value for the LegacyExchangeDN attribute changed. The auto-complete cache in Microsoft Outlook and in Microsoft Outlook Web App (OWA) uses the value of the LegacyExchangeDN attribute to route email messages internally. If the value changes, the delivery of email messages may fail with...

Office 365 users sending Winmail.dat attachment

Follow me Ever wondered about people complaining that they got weird attachment with your email named WinMail.dat, they even try to open it but it didn’t open, actually they didn’t have a program capable to open that file. It was the Job of their email client (Mac Mail, Mozilla Opera) whatever they were using and that’s the sole reason that it removed all the styling which you did in your brand new Microsoft outlook and attached it as a strange file called WinMail.dat and presented the user with a dull  text only email. Here is what Microsoft says about it: By default, email messages that are sent from Exchange Online in Office 365/Outlook 2013/Microsoft Exchange Server use the Transport Neutral Encapsulation Format (TNEF) format. Messaging systems that aren’t based on Microsoft Exchange may be unable to interpret messages that use this rich text format. If the recipient’s messaging system can’t process this format, a file attachment that’s called Winmail.dat is added to the message. So now that we know about the issue lets talk about the solution. Well as we have already explained that the issue is not with your computer but with the outdated email client that Recipient using. What needs to be done is that you send him an email in plain text which his email client can understand.  So we have a couple of options here. If the recipient is someone to whom everyone (in your company) sends email and its an issue with everyone then we can do a change on the exchange server itself or if its only your problem then you can make...

Exchange 2010 users receiving winmail.dat attachment

Follow me Problem The client had an Exchange 2010 environment with 2008 R2 DC’s , some of the users were complaining that every now and then they get Winmail.dat attachments and the Issue affects both Outlook and OWA users Troubleshooting After extensive troubleshooting we found out that there was a Firewall/ SMTP Gateway Watch Guard XTM device in place to receive the emails and it was striping out the header of the email that identify it as Rich Text formatted.  This header is needed by the outlook client to interpret the winmail.dat attachment. When the email client cannot read the proper formatting of the email, it displays the attachment as a winmail.dat file Resolution Before running towards the solution or editing the config of the SMTP gateway , it would be best to probably bypass the gateway and forward port 25 (TCP) directly towards the Hub Transport server, than test the issue again to see if its resolve.  As now if are not getting the winmail.dat attachment and are receiving the emails fine then we can be sure its the SMTP gateway issue. In our case, we made changes to SMTP-proxy on the Watch Guard to allow the header of type •X-MS-Has-Attach:* 
•X-MS-TNEF-Correlator:* 
•X-MimeOLE:* through the SMTP proxy.You may have to make similar changes to what ever SMTP gateway you have. Hope this helps you to fix the issue in hand, for more visit our support options here Follow...

Unable to open Queue Viewer on Exchange server with error can’t connect to the RPC server on computer “TransportServer”

Follow me Recently while working on an Exchange 2010 SP2 environment, we were trying the view the Mail Queue on the Transport server but we kept getting the following error. Exchange can’t connect to the RPC server on computer “TransportServer”. Verify that you used a valid computer name. + CategoryInfo          : InvalidOperation: (:) [Get-Queue], LocalizedException + FullyQualifiedErrorId : AC9CA77A,Microsoft.Exchange.Management.QueueViewerTasks.GetQueueInfo Solution Fortunately solution to the issue was as simple as restarting the Transport Service on the server, as soon as it was restarted the queues console was able to connect just fine Additional Information In Microsoft Exchange Server 2013, you can use the Queue Viewer in the Exchange Toolbox or the Exchange Management Shell to manage queues. For more information about using the queue management cmdlets in the Exchange Management Shell Hope this help you fix the simple issue quickly, else reach out to us for paid support here Follow...