when going to the webmail address it reads this:

The custom error module does not recognize this error.

The Big Lug

I've found bits and pieces on how to do this, but still cannot get it to work. Here's the scenario:
We've split Company A into Company A and Company B.  Company A (Exchange 2010) is configured and is working properly.  Company B (Exchange 2013) is configured and working properly (internal mail, won't send external because of connector issue).  What I want to do is route Company B's mail through Company A's Exchange.  The reason being because we already have our mxDNS records for Company B pointed to Company A, and I also wouldn't need to open another port up on the firewall or use another public IP up.   So what I'm trying to do is make a connector between the two Exchange Servers (separate domains, same network\dhcp) so we only have one public facing email server.  Here's what I've tried so far on Company B (Exchange 2013):  Relay 1 - Type: Custom, Delivery: MX record associated with recipient domain, Address Space: IP of Company A Exchange 2010, Source Server: Company B's Exchange 2013 server.  THIS DIDN'T WORK AT ALL.   Relay 2 - Type: Internet,    Delivery: MX record associated with recipient domain, Address Space: * (all), Source Server: Company B's Exchange 2013 Server.  THIS ALLOWED INTERNAL MAIL BUT NOT EXTERNAL.  So in a nutshell my questions are:  Whats wrong with my connectors on Exchange 2013?  Do I need to make a receive and\or send connector on Company A's Exchange 2010 server to pass Company B's Exchange 2013 mail?  Is what I want to do possible?  I appreciate any help and I will continue to Google but like I said, I'm only getting little bits here and there and its not working when I put it all together.  Thank You-  Daniel

I have just completed the process of migrating from Exchange 2007 Standard SP3 RP10 to Exchange 2013 Standard. I now have Exchange 2013 Standard CU3 installed on two Server 2012 Standard systems. The two new exchange servers are members of a DAG.

With Exchange 2007, I had to include the IP addresses of multi-function devices (MFDs) with scan to e-mail capability in a receive connector in order for the scan to e-mail to work. Five of the MFDs were on the same subnet as our Exchange 2007 servers, and one MFD was not. It is on the same subnet as our Exchange 2013 servers.

I created new Receive connectors on our Exchange 2013 servers for this purpose. The one MFD on the same subnet as the Exchange 2013 servers was mistakenly excluded from a receive connector. Much to my surprise, it is able to relay mail.

I removed the IP address of one of the other MFDs to see if the fact that it is on a different subnet than the Exchange 2013 servers made a difference. I replicated our domain controllers to help ensure that a lack of AD replication would not be an issue with this test. The excluded MFD is still able to relay items.

I have an application on a server.  The application relays messages, but the IP address of the server it is on is not included in any receive connectors.

By searching through  the SMTPreceive log, I found the IP address of the MFDs I did my scan to e-mail tests from in the log. I also found the IP address and relayed messages from the application server. The log indicates that the Default Frontend connector is handling this traffic. Does Exchange 2013, by default, relay messages from all internal IP addresses? Does this mean that I don’t need receive connectors for any internal devices (MFDs, servers, etc.). Our Exchange 2007 servers have been decommissioned.  Would I have needed connectors while we were still in a co-existence situation? Am I likely to need them when we have our next co-existence situation in a few years?

Hey guys, can someone explain to me what's the difference between DLP and IRM in Exchange  2013, I have to protect some messages sent from my managers so that unauthorized users can't read the messages and they can't forward them externally.

Thanks.

Hi,
I installed Exch 2013 and is working great - both incoming mail and outgoing mail work fine in OWA and outlook.

Problem we are having is SMTP authenticated relay. We install application on all client computers which sends emails externally/internally. 

Though we had authenticated in application, we are not able to send emails externally. Internally it works fine from application.

Our backup software stopped sending notifications on failures. Literally we are logging into each and every server and making sure backups are successful.

We never had a problem with Exchange 2010

I don't want to create relay and allow my whole ipaddress range (I think that's stupid)

Can anyone please help?

Hi All,

Hope its going all well, we are facing a problem, in our Exchange daily logs, there is always so many logins with the user name '-' (hyphen), also in our spam filter outbound traffic daily report there are so many emails with same sender ID '-' what is it? in Exchange Logs it shows logins from the different different IPs of different countries. I cant sort it out is it a virus, spam or what?? 

Virgo

okay so I've been working with Exchange Online for some time now, but I'm trying to figure some things out about working with just stand-alone Exchange 2013...no hybrid, no integration with Office 365.

It's a basic question really but I can't seem to find anything on it...what are the format that my DNS records are supposed to look like to point to the Exchange Server?  (MX; CNAME; TXT).

Any answers are greatly appreciated. 

Hi,

We are using Exchange 2007 and it was working fine till today.

Today we are getting the following error message on the exchange server:

451 4.4.0 Primary target IP address responded with: 421 4.4.2 Connection dropped. Attempted failover to alternate host, but did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. And the emails are stuck in the queue.

 I really need to solve this problem as the emails are stucked in the queue.

Can someone help me with this.

Thanks

I've created a two-way trust between two forests, which works fine for authentication to shares, apps and the like. However, I cannot get Distribution Groups to work. What I'm trying to achieve is: mail sent to one DG in forest 1 to be forwarded/copied/sent to another DG in forest 2. The way I'm trying to do this is create a Global Distribution Group in forest 2 and add  Universal Groups from forest 1 to this group. The ADUC allows me to do this, but when I try to send mail to the Global DG, it's only delivered to the DG members in the original forest (2). It's like the members from the other forest are completely ignored.

Also, I can't add any users from forest 1 to mailboxes or DGs in forest 2 or vice versa. This is probably by design, but if there's a way to do this, that would be very helpful. It would allow us to share calendars and mailboxes across forests.

Thanks!

[edit: oh crêpe, I should have posted this in the Exchange 2010 section as both Exchange orgs are at EX2010 SP3 RU4 - both forests at 2008 R2 functional level]

1. Please don't use acronyms without defining them first
2. I am trying to setup retention policies for my boss's email. He uses Outlook 2013 on his laptop. Am I correct in thinking that if I set up retention policies through his microsoft 365 Outlook Web App, the retention policies will be applied to Outlook 2013 client on his laptop? He does have exchange. 
3. As I understand it, retention policies cannot be applied to default folders (Inbox, sent items, deleted items, and junk mail). Retention policies can only be applied to created custom folders. Is this true?
4. Are Deleted items and Junk Mail retained for a certain period and then deleted by default? If so, what is the default retention period? Can it be changed?
5. Does Office 365 back up emails? If so, how long does it retain emails? Can it be changed?
6. I did setup a Test folder with a retention policy that was a week long. A week later I check on an email I placed in the Test folder and the email said it had 0 days until expiration. I checked the Test folder again a week later and it was deleted. Is the Test email recoverable? I would prefer that it is not. I did some research and found that the Managed Folder Assistant needs to run before expired items are deleted. How do I get Managed Folder Assistant to run every night? I don't know how to use Powershell and only have access to OWA.

Hi.

We are currently migrating from Exchange 2007 to Exchange 2013. We have Exchange servers across 3 AD Site (A, B &C). Right now, all our users are on Exchange 2007 except 2-3 test users. Exchange 2013 was installed in site A without any issue. At that moment, mail flow between users from site A to site B keep using Exchange 2007 hub servers in both directions; Exchange 2013 Transport Servers in site A were not used at all.

When we installed Exchange 2013 in site B, mailbox flow between Exchange 2007 users from site A to Exchange 2007 users in site B start using site B Exchange 2013 Transport servers. Why?

Right now, when site A users are sending email to site B, it’s using site B Exchange 2013 Transport Servers (Site A 2007 Mailbox Server, Site A 2007 Hub Server, Site B Exchange 2013 Transport Server, Site B 2007 Hub Server, Site b 2007 Mailbox Server). When site B users are sending email to site A, it’s keep using Exchange 2007 hub. (Site B 2007 Mailbox Server, Site B 2007 Hub, Site A 2007 Hub, Mailbox, Site A 2007 Mailbox Server).

Can someone explain why Exchange 2013 transport services are only used in site B and not A? Any documentation I can read that explain the result?

Thank you.

I just analyzed the email headers and notice that when sending out emails on Exchange 2013, the recipient receives the email via Microsoft SMTP Server (TLS) and not ESMTP. It says it in the email headers and there are some delays.

When I send out emails in Exchange 2010, the recipient receives the email via ESMTP.

When using Exchange 2013, the first email to a new domain takes around 30 seconds for the recipient to get it and subsequent emails takes likes 0 second. It's immediate on subsequent emails. If I haven't emailed that domain for a while again, I'm back to square one. First email takes around 30secs to arrive in recipient's mailbox and 0 seconds or immediately for subsequent emails right after I send the first one.

For example, Exchange 2013 sends first email to test@hotmail.com (30 seconds. takes some time to arrive in the recipient's mailbox). Exchange 2013 sends second email to test@hotmail.com (0 seconds or arriving immediately in the recipient's mailbox).

For example, Exchange 2010 sends first email to test@hotmail.com (0 seconds. arrive in the recipient's mailbox immediately). Exchange 2010 sends second email to test@hotmail.com (0 seconds or arriving immediately in the recipient's mailbox).

The only difference I notice is the email headers for Exchange 2013 show 'Microsoft SMTP Server (TLS)' and Exchange 2010 show 'ESMTP'.

It seems like Exchange 2013 first tries to send out the email via TLS but the remote server doesn't support it so it falls back to sending out the email without TLS thus the ~30 second delay.

How do I fix this? How do I turn off TLS for SMTP on Exchange 2013 so I can do another test with TLS off and see if that's the culprit?

Is it possible to selectively enable TLS for individual email addresses on an internal network/domain.

Meaning that i would like all emails that John Smith sends to internal recipients to be encrypted, wherever he is. So it would be based on the sender's address, and not recipient. These emails would be circulating on internal domain only.

Also, as an extended question: is it possible to enable TLS for a geographical location/group which is fixed for that location alone?

I am aware that you can turn on full TLS for all emails, but i'm looking for individual encryption only.

Hi,

              i want to host my own Webmail service in wms 2012 PREMIUM OPERATING SYSTEM. is it possible ?

HI all,

Experiencing issue With Exchange 2013 environment ( 2 servers With cas and mailbox role With DAG)where some of Our emails are beeing resubmitted.

So far cant see any pattern on why or where it sends Message twice to a recepient.

Any idea where i can start to troubleshoot or what that might cause this?

thanks!

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hello,

Please help. I have Exchange 2013 CU3 with multi-role of the CAS/MBX on Windows 2012 R2 servers. From one specific addresses from the internet, Exchange rejects the message, and to the sender returns NDR:

Remote Server returned '550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (WIN1250) is invalid or not installed.; cannot handle content of message with InternalId 1249835483212, InternetMessageId <messageID>.'

Received: from hostname (IP.33) by hostname

 (10.143.66.40) with Microsoft SMTP Server id 15.0.775.38; Wed, 15 Jan 2014

 16:05:21 +0100

X-AuditID: 0ae6cdd1-f79976d000000e60-ee-52d6a3b000f1

Received: from hostname (hostname [IP.210])  by

hostname (Symantec Mail Security) with SMTP id

 34.6B.03680.0B3A6D25; Wed, 15 Jan 2014 16:05:20 +0100 (CET)

Received: (qmail 18641 invoked from network); 15 Jan 2014 16:05:20 +0100

Received: from unknown (HELO matrix) (IP.86)  by IP.60 with

 SMTP; 15 Jan 2014 16:05:20 +0100

Date: Wed, 15 Jan 2014 16:05:20 +0100

From: <sender@domain.xx>

Sender: <sender@domain.xx>

Reply-To: <sender@domain.xx>

To: <recipient@domain.xx>

X-Mailer: Blat v2.2.2, a Win32 SMTP/NNTP mailer http://www.blat.net

Message-ID: <messageID>

Subject: =?WIN1250?B?Q1NCIE9iamVkbuF2a2EgSCBwcm8gS29zdGVsZWNr6SB1emVuaW55?=

  =?WIN1250?Q?_a=2Es=2E_=2800000082=29?=

MIME-Version: 1.0

Content-Type: multipart/mixed;

        boundary="=_BlatBoundary-QvNYMX6xOBMtYJX5A524P"

X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRWlGSWpSXmKPExsVydXrwJd0Ni68FGWx8ZWSx49tfFgdGjwUv

        /7MFMEZx2aSk5mSWpRbp2yVwZXxf9I6l4LFKRce3P8wNjJuVuxg5OSQETCQ6d15igrDFJC7c

        W8/WxcjFISRwkFFi9rKDYAkhAQ+Js2/aWCDsHInDC5tZQWwWAVWJL0u3M4PYbAKiEn0TmsHq

        hQXEJR7v+MoKUS8pMan9KViNiICIxLWLmxkhljlL7Dm4BMzmFbCQuLp7OyNEb6lE27JZTBBx

        QYmTM5+A7WUW8JP4eGI+2wRG/llIUrOQpCBsbYllC18zQ9iaEnNn3meHsG0kum5cYZrFyAFk

        u0u86LGECCtKbD6wm3UBI/sqRrHcxMwcIwO9xPSi/LTUohK9vMT0xLz8TYzAUOZ6dvbiDsZv

        7RaHGAU4GJV4eCfPuRYkxJpYVlyZe4hRBWjQow2rLzBKseTl56UqifCuXwCU5k1JrKxKLcqP

        LyrNSS0+xCjNwaIkzut2al2QkEB6YklqdmpqQWoRTJaJgx1EcJ5irJQS5+1eBDRAoLggMTej

        NK8EpkpKjHfHmytBQvxIEkmlOdlSMrwMMy8HCYkiieellhfnpJYAmVIKvFtBuiSRZItLiwsy

        kzPzS4vjS4vgCekSoxkHC9D0yuL4xJyc/PL4VFCYCIF9JSXMy8jAwCDEA3RzbmYJxEEwjVIN

        jKyxVxKUnvl5SjeaXNrE99OPh1GRSfDMVt3sjYuYF/Jo9B+xOcpZvXM32xu1jMUOv94tYjuy

        +5NUcsVdCwWfO6tmOU9tjdj1Jqx1S0S884+oGEfBKvatTRxhgi/Pz34+W6164b5az/kMB/dU

        ZQgqVPuYeV02cKgO+jo9ptRJ3zBj9a/CdYKblViKMxINtZiLihMBUZkBeScDAAA=

Return-Path: sender@domain.xx

I found the solution for this error for Exchange 2010 SP1 http://support.microsoft.com/kb/2536702/en-us , but it does not work in Exchange 2013 CU3. Nowhere on the Internet I could not find a way to solve this.

Thank you for the help

Hi,

we've got some issues when sending emails to some linux recipients, that attachments or s/mime signed emails are converted to the dreaded winmail.dat attachements. 

On Exchange 2010 i've just configured the corresponding remote domain (or the default one) to disable TNEF sending to this mail domain.

Apparently with Exchange 2013 this setting does not work anymore. With setting the parameter "TNEFenabled" to $false, the recipients still get winmail.dat attachments.

do you have any idea how to work this out?

Kind regards,

Peter

Hello guys,

we have been facing some issues for 3 days with Microsoft Exchange 2013 CU3,

As we have noticed after troubleshooting that Mail submission service is crashing (event 9036)

Service Microsoft Exchange Mailbox Transport Submission.  29 starts were made since the last clean stop. Startup will be delayed until 1/17/2014 11:26:35 AM.

For example at 11:26 email flow works normally for few minutes, then i get another event id 9036 with + 2 hours (so i should wait 2 more hours before mailflow works again)

What i mean by Mailflow is Outbound email (Inbound works normally) even if i send email to myself, i don't get it unless i reach this 2 hours time.

I am also having event ID (6535)

The description for Event ID 65535 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>MSExchangeFrontendTransport.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.</Message><StackTrace>  at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.CloseOutputSessionCore(TimeSpan timeout)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.CloseOutputSession(TimeSpan timeout)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnClose(TimeSpan timeout)

and eventID 4999

Watson report about to be sent for process id: 17352, with parameters: E12, c-RTL-AMD64, 15.00.0775.038, MSExchangeSubmission, unknown, M.E.D.I.T.VirtualBuffer.Read, System.ArgumentOutOfRangeException, cf47, unknown.
ErrorReportingEnabled: True

Any help?

Thanks

I'm hoping someone can help me figure this out or possible point me to a post that may have already solved this issue.

We are currently finalizing our migration from 2007 Exchange to 2013 Exchange. All our normal users are moved over to the 2013 Exchange. We are moving from a single server to multiple servers. Our current configuration is this:

Exchange 2007 server (current roles - Mailbox, Client Access, Unified Messaging, Hub Transport)

Exchange 2013 server B (current role - Client Access)

Exchange 2013 server C (current role - Client Access)

Exchange 2013 server D (Mailbox)

Exchange 2013 server E (Mailbox)

What is happening is that certain emails going to certain users are not making it to them, I would say 95 -98% of the emails are making it to the users with no issues. From what I'm seeing in message tracking is that any that go to the old 2007 server are not being sent to the onto the proper 2013 server that has the that users mailbox. What I'm trying to figure out is what can I do to resolve this. Any suggestions would be much appreciated.

Hi,

I'm comparing the hops between exchange2013 and exchange2010. I notice Exchange 2013 has an extra hop when sending out emails. Please note that exchange2013 and exchange2010 are not part of the same Active Directory. They are completely separate companies.

The reason why I'm asking about the extra hop is I notice ex2013 first email takes about 1 min to get delivered externally and subsequent email sends are instant. If I haven't emailed for a while (eg. 10mins), the first email takes about 1min to get delivered again externally and subsequent emails are instant. I don't notice this delay with Exchange 2010.

Exchange 2013 why is there an extra hop (hop #2, Microsoft SMTP Server (TLS))? Could the TLS be the reason of the delay because it is trying to talk to telus smtp via TLS but telus doesn't use TLS and exchange2013 falls back to smtp without TLS for email send?:

Exchange 2010 doesn't have the 'Microsoft SMTP Server (TLS)' hop: