Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all 3660 articles
Browse latest View live
↧

Delayed Sending Mail Exchange 2013

August 10, 2013, 1:19 am
$
0
0

Hi,

I have recently setup a new Exchange 2013 system, I have having large delays and failure to send mail to the outside world. The setup is,

2 x Hub and 2 x Mailbox (in a DAG)

The delayed messages I am getting back is as follows,

Remote Server at KLA-SVR-EXHUB2.CAT.internal (10.0.XX.XX) returned '400 4.4.7 Message delayed'
09/08/2013 18:44:46 - Remote Server at KLA-SVR-EXHUB2.CAT.internal (10.0.XX.XX) returned '441 4.4.1 Error encountered while communicating with primary outbound frontend IP address: "421 4.4.2 Connection dropped due to TimedOut." Attempted failover to alternate frontend, but that did not succeed. Either there are no alternate frontend addresses, or delivery failed to all alternate frontend addresses. The last endpoint attempted was 10.0.XX.XX:717'

I have checked and changed the DNS settings on the server to ensure they can ping the outside world, I have ran a reverse lookup, I do still have an issue with the SMTP banner not matching.

Thanks in advance for any help

↧
Search

Send as Public Folder / Message get stuck in Outgoing Mail folder

August 11, 2013, 12:33 am
$
0
0

Hello!

We just finished the Migration of our public Folders from 2010 to 2013.
Now, if a user sends an E-Mail as the public Folder the message just hangs in the outgoing Folder in Outlook and nothing happens.

Do you have any idea what might be wrong?

Thank you all for reading and for the possible help! ;-)

best regards
Jürgen

[EDIT]

We get this error log every time a users tries to send as public Folder:

Event ID 2009 / MSExchange Mid-Tier Storage

[Prozess:Microsoft.Exchange.RpcClientAccess.Service PID:10360 Thread:19] Fehler beim Auflösen des Active Directory-Objekts für E-Mail-Adressfeld des Absenders: '/CN=Mail Public Folder/CN=Version_1_0/CN=9c969171-dbd7-4118-a94b-53d8ed61e9db/CN=0000000001E8196C6C6B834A896CD3E359E5A07C0100DF74E7DB1A837F4C847AE0B68CBCD68E0000000008290000'. Für diesen Fall wird kein Überwachungsprotokoll generiert. Ausnahmedetails:

Microsoft.Exchange.Data.Storage.ObjectNotFoundException: Der Active Directory-Benutzer wurde nicht gefunden. ### Translation: the active Directory user was not found. ###

   bei Microsoft.Exchange.Data.Storage.ExchangePrincipal.<>c__DisplayClass4.<FromProxyAddress>b__3()

   bei Microsoft.Exchange.Data.Storage.DirectoryHelper.DoAdCallAndTranslateExceptions(Action call, String methodName)

   bei Microsoft.Exchange.Data.Storage.ExchangePrincipal.FromProxyAddress(IRecipientSession session, String proxyAddress, RemotingOptions remotingOptions)

   bei Microsoft.Exchange.Data.Storage.ExchangePrincipal.FromProxyAddress(ADSessionSettings adSettings, String proxyAddress, RemotingOptions remotingOptions)

   bei Microsoft.Exchange.Data.Storage.COWAudit.GetSubmitEffectiveMailboxOwner(MailboxSession session, CallbackContext callbackContext)

and the second one with Event ID 1016 just says: The Sender for Event ID "12746623", Mailbox "GUID" is invalid.

↧
↧

Exchange 2013 SmartHost Can't Send Mail Outbound

August 11, 2013, 9:03 am
$
0
0

Hello

My Setup

Server01: Server 2012 Standard + Exchange 2013 Standard (MBX+CAS)

Server02: Server 2012 Standard + Exchange 2013 Standard (MBX+CAS)

No DAG Yet!

I have created a Send Connector(Smart Host) but when I try to send mail from Outlook 2013 It will be in the Send Folder, but when I take a look in the Queue Viewer it shows up there with Status Ready and Queue ID 39, What can be the problem?

port 25 Outbound is opened in the Firewall so I really don't get what the problem can be.

Hope someone can help me and give some Professional tips on this.

Thank You and have a nice day

↧

Exchange 2013 to Exchange 2007 migration unable to send mail to Exchange 2007

August 2, 2013, 11:25 am
$
0
0

I have a Windows Server 2012 Server with Exchange 2013 CU2, Revision 2.

I can send mail from Exchange 2013 to users on Exchange 2013, I can send mail from Exchange 2013 to people on the Internet.

I can send mail from Exchange 2007 to users on Exchange 2007, I can send mail from Exchange 2007 to users on Exchange 2013, I can send mail from Exchange 2007 to the Internet.

I cannot send mail from Exchange 2013 users to Exchange 2007 users.  The message is stuck in SMTP Relay to Mailbox Delivery Group, and it receives a 421 4.4.2 Connection dropped due to socket error.

I have verified that there are MX records for each server in the domain.  The two servers are next to one another and connected to the same Gigabit switch.

Looking at the receive connector logs it gets to passing the allowed forms of Authentication, the Exchange 2013 server sends back X-ANONYMOUSTLS - the Exchange 2007 server passes the certificate, last line shows - LOCAL and that is all. I can see 3 attempts in the log during each retry to send the mail from Exchange 2013.

I have tried to enable Verbose logging on the Exchange 2013 Send connector, and have not been able to see a log created for this delivery from Exchange 2013 to Exchange 2007.

Exchange 2013, has been upgraded to CU1, CU2, and CU2 Revision 2. Exchange 2007 has the latest SP and updates.

I created a self signed certificate and assigned that to SMTP on Exchange 2013 in case it did not like one of the names of that server being missing from the Certificate created during install.  That did not help.


↧

some mails delivered before 2 days from today

August 12, 2013, 9:51 pm
$
0
0

Hi ,

 

i am facing issue of some mails which are delivered before 2 days from today i.e mail received from x person on 13-Aug-13 (today) mail contains date is 15-Aug-13 .

this issue is not related to my laptop date/time as other mails are delivered correctly.

OS : windows 8

Outlook client 2013

Exchange 2010

can you please help me to resolve this issue.

↧
↧

Exchange 2010 - manage IP allow List provider - whitelisting IP addresses

August 12, 2013, 3:01 am
$
0
0

We are running a single Exchange 2010 server behind a TMG 2010 firewall.

A user is trying to use Mailchimp (an email marketing campaigns service) to send e-mails to external and internal recipients.

E-mails sent to internal users are not received as Exchange blocks e-mails that have sender addresses containing our own domain. The solution seems to be to setup an "IP Allow List Providers" on Exchange but I don't find a way of adding any allowed IP addresses on EMC > Organisation Configuration > Hub Transport > IP Allow List Providers.
These are the IP addresses I am trying to add: http://mailchimp.com/about/ips/
The only options seem to be Provider name & Lookup domain.

Can someone also explain what the lookup domain option is supposed to be?

Many thanks

Marco S

↧

Event ID 1003: MSExchangeFront End HTTP Proxy ([Oab] An internal server error occurred.)

August 13, 2013, 1:20 pm
$
0
0
Every 10 minutes or so i get the following two Events recorded at the same time in the system event log.  Anyone know what they point to?  OAB seems healthy.

Event ID 1003 MSExchange Front End HTTP Proxy
[Oab] An internal server error occurred. The unhandled exception was: System.ArgumentNullException: Value cannot be null.
Parameter name: sourceObject
   at Microsoft.Exchange.HttpProxy.AnchorMailbox..ctor(AnchorSource anchorSource, Object sourceObject, IRequestContext requestContext)
   at Microsoft.Exchange.HttpProxy.UserADRawEntryAnchorMailbox..ctor(ADRawEntry adRawEntry, IRequestContext requestContext)
   at Microsoft.Exchange.HttpProxy.OabProxyRequestHandler.ResolveAnchorMailbox()
   at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox)
   at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__27()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)


Event ID 1309 ASP.NET 4.0.30319.0

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 8/13/2013 2:00:35 PM 
Event time (UTC): 8/13/2013 8:00:35 PM 
Event ID: b30166423b674320a9304ba6528b18e5 
Event sequence: 3580 
Event occurrence: 1193 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT/OAB-1-130208036285056837 
    Trust level: Full 
    Application Virtual Path: /OAB 
    Application Path: D:\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\ 
    Machine name: ICTEXCH01 
 
Process information: 
    Process ID: 20368 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\SYSTEM 
 
Exception information: 
    Exception type: ArgumentNullException 
    Exception message: Value cannot be null.
Parameter name: sourceObject
   at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)
   at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

Request information: 
    Request URL: https://mail.contoso.net:443/OAB/25da1865-3771-44fc-9373-3f08467734b1/oab.xml 
    Request path: /OAB/25da1865-3771-44fc-9373-3f08467734b1/oab.xml 
    User host address: 172.16.14.188 
    User: contoso\username 
    Is authenticated: True 
    Authentication Type: Negotiate 
    Thread account name: NT AUTHORITY\SYSTEM 
 
Thread information: 
    Thread ID: 13 
    Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)
   at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)
 
 


↧

Emails not forwarding

August 13, 2013, 6:08 am
$
0
0

I have recently been trying to forward email from an internal account to a different internal account with no success. I have a very simple, single server Exchange 2010 setup, recently migrated from 2003 and with 2003 still up and part of the organization. The mailboxes in question are all on the 2010 box. I used the Mail Flow Settings >>> Delivery Options to check the Forward to: box and browse for the recipient. I tried two different addresses, but no luck. I restarted the Information Store and Transport service thinking that might be the issue, but no luck. What could be the issue?

The user whose email I am forwarding is in one child domain and I am forwarding the email to a user in another child domain, of course with two-way trusts, etc... I can't find any error messages or anything. It just doesn't work. Any ideas?

↧
Search

Exchange 2010 Mailbox Database Journaling Destination

August 13, 2013, 6:52 am
$
0
0
Currently we have a destination configured for journaling that goes to an exchange contact.  I was curious to know how I would go about accomplishing parallel testing with another vendor.  Can i point the journaling"contact" to a distribution list that has both addresses configured?
↧
↧

disable duplicate detection

August 2, 2013, 5:58 am
$
0
0

Hi everybody,

I know duplicate message detection is a nice feature at all.

I have one requirement (some kind of archiving) in which this is really not wanted.

I've seen that it might be possible to disable this at all by setting the following key to 0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server
 Name>\<Private/Public-Guid>\Track Duplicates (in hours)

As I don't want to disable duplicate detection at all but only for only recipient mailbox I didn't go into that direction.

Does anybody knows if it is possible to disable this on per user / per mailbox basis?

Thanks a lot,

Matthias

↧

Exchange 2010 SP1 connection very slow in Outlook

August 16, 2013, 11:31 am
$
0
0
I am having a pretty big issue that just started today. All of my users are getting messages that Outlook is trying to receive data from Exchange. It takes up to several minutes to send a message once you hit the send button. Switching between folders is causing outlook to say Not Responding. Basically anything that Outlook looks for on the server is taking an unusual amount of time for ALL users. We have been using this server for almost 2 years and this is the first time this has happened. It is running on a Hyper-V VM. So I dont think it is something gradual or something related to any one user. I have checked DNS response times and that looks ok. I need some advice on what could be causing this issue please. 

Chris V

↧

Exchange 2013 Recieve Connectors - Same port different RemoteIPRanges conflicts.

August 16, 2013, 1:05 pm
$
0
0

Trying to setup a receive connector to relay mail that would have a more restricted RemoteIPRange.  According to Technet, you can have multiple recieve connectors on the same IP/Port combination as long as the RemoteIPRange overlap, the most restrictive will be used.

So I setup a receive connector restricted to 2 server IPs but on the same port (25) as the Default FrontEnd Connector (single server environment).   The 2 servers would work fine and connect to the new Send Connector.   However, the Default Frontend EXCH01 would stop recieving traffic, which has a IP range of 0.0.0.0   Any connections from other servers would get the following message on connecting:  421 4.3.2 Service not available.    So for the time being, I've moved the receive connector to  for relaying to port 26 and everything is working.    

Is there something in the configuration of a receive connector that I'm missing.  I know i've done this on Exchange 2010 without issue.

↧

Email Communication between Exchange 2007 and 2013

August 17, 2013, 8:12 pm
$
0
0

Hi ,

for email communication between Ex2003 ---> Ex2007 / 2010 is through  interop routing group connector .

My question is how email communicate between Ex2007 ----> 2010-- 2013 or vice versa

↧
↧

Exchange 2010 SMTP Relay - 2nd internal domain name - HELP!!!

August 18, 2013, 1:51 pm
$
0
0

Hi,

Hoping someone can help me with a little issue I have please?

Our Exchange admin has left the firm and I have picked this up with very little experience of Exchange.

In short we have moved our internal SMTP relay from 2003 to 2010 and come up against some issues, all of which I have overcome bar one, our Finance team send various emails from their billing system to users and themselves in various ways, Anonymous, sending as an internal user to the same internal user but relaying with an admin account etc etc.

They also send emails to internal users as a completely different made up but relavant name to the actual firms domain, for example, our internal domain is company.com and all in internal users SMTP address is company.com, however they need their finance system to relay to users as an address from finance.com, this isn't a mailbox it's just a name their system uses and sends via our internal smtp relay/receive connectors.

I have setup a new internal receive connector that applies to only their finance subnet allowing anonymous, however I'm at a loss as to how to allow the finance.com domain to relay to our internal users, I'm assuming I need to create an authoritative domain or similar but do not just want to go playing around on a live environment.

Any help would be greatly received.

Many Thanks

Steve




↧

Routing logic for Delivery agent connector

July 29, 2013, 1:29 am
$
0
0

Hello,

I have this setup: ExchSever1 (first server in organization, mailbox and CAS ), ExchServer2 (second server, mailbox server). Both are Exchange 2013 servers.

Both servers has installed a custom transport agent. Then a delivery agent type connector is created

for a SMTP domain, say, ABC.com.

Everything is running fine. But I would like to know how Exchange route the email actually.

Currently, wheneven I sent an email addressed to ABC.com, the email is routed from ExchServer1 to ExchServer2 and then

to the final destination server through the delivery agent connector. Is it possible for Exchange to always use a predefined

server (e.g. ExchServer1 ) to send through the connector ?

(Even if transport agent is not installed on ExchServer2 and ExchServer2 is not listed as the source server for the connector, the email addressed to ABC.com is still routed to ExchServer2 )

Thanks.

Kelvin




↧
Search

Exchange 2013 to Exchange 2010 Edge results in 4.3.2 Service not available

July 31, 2013, 2:12 am
$
0
0

Hi!
I had a existing Exchange 2010 with all roles except edge and a Exchange 2010 edge (co-located on a Forefront TMG). I have now installed Exchange 2013 and want to keep my edge. All mailflow works, exept from Exchange 2013 to the outside World (i.e through the Edge server).

If I check the queue Viewer it says 4.3.2 Service not available, same if I Telnet from the Exchange 2013 server to the Exchange 2010.

If was under the impression that I didn't need to do anything more than just install the Exchange server, the existing Edge subscription would take care of mailflow. Am I wrong?

Best regards

Andreas

↧

Exchange Rejecting Email NDR (SMTP 4.3.2)

August 2, 2013, 11:49 am
$
0
0
It seems 4.3.2 can have many causes.   I get this code in my SMTP log randomly and have no idea how to troubleshoot it.
↧
↧

Transport Service Crashes Regularly

August 6, 2013, 6:15 am
$
0
0

I have installed Exchange 2013 CAS and am experiencing a Transport Service Crash once a day. I have other CAS servers and CAS installed also on the Mailbox servers. However, only this server is experiencing the service crash. Only a reboot of the server allows us to restart the service. The Error is as follows:

Faulting application name: MSExchangeFrontendTransport.exe, version: 15.0.712.0, time stamp: 0x5199c77c

Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.712.14, time stamp: 0x51b4dcae

Exception code: 0xc00000fd

Fault offset: 0x000000000069d857

Faulting process id: 0x28d0

Faulting application start time: 0x01ce925a65a3cf0f

Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeFrontendTransport.exe

Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\8aaad3fd24b2f1606acb17becb5d561f\Microsoft.Exchange.Net.ni.dll

Report Id: ac2363fe-fe4d-11e2-93f7-005056b53a73

Faulting package full name:

Faulting package-relative application ID:

Anthony Sheehy - MCP, MCITP

↧

Support for TLS 1.2 over Exchange 2013 on Server 2012?

August 19, 2013, 1:12 pm
$
0
0

Greetings,

We're trying to roll out TLS 1.2 in our test environment and can't seem to get Exchange to work with the protocol.

We've been using this method to enable TLS 1.2 (and disable the other protocols - TLS1.0, SSL2.0, SSL3.0, PCT1.0): http://www.adminhorror.com/2011/10/enable-tls-11-and-tls-12-on-windows_1853.html

We originally tried using Exchange 2010 on 2008 R2, but then I ran across this article saying that it is not supported: http://support.microsoft.com/kb/2709167/en-us

We've since tried to set it up with Exchange 2013 on Server 2012. Still no luck. The only time Exchange wants to work is when TLS1.0 is enabled.

I suspect that TLS1.1 and TLS 1.2 are also not supported on Exchange 2013, or that I'm changing the wrong registry keys, but I wanted to find confirmation. I've searched extensively and can't find any documentation leading me to believe one way or the other if it's supported.

Any help or insight would be greatly appreciated. Thanks!

--Aric

↧

Error to send to gmail.com

August 19, 2013, 6:43 am
$
0
0
Friends, I have an Exchange 2013 and a sudden he no longer send emails to gmail.com

Googled the error but not its resolving, see:

mx.google.com rejected your message to these email addresses:

mx.google.com generated this error: [2002:3207:4784 :: 3207:4784 16] The sender does not meet basic guidelines ipv6 sending of authentication and RDNs resolution of sending ip. Please review https://support.google.com/mail/answer/81126for more information. e49si9606932eep.111 - gsmtp
Your message was not delivered due to permission problems or safety. She may have been rejected by a moderator, the address only accepts mail from certain senders, or another restriction prevented delivery.


Can you help me?

Silvio Tavares - Analista de Sistemas

↧
Viewing all 3660 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>