Exchange 2013 Mail Receiving Issues
Hi everybody,
Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
All functions and rolls are configured and installed but i am having issues receiving external e-mails.
Almost all of the external mails are being deliverd a half hour to a hour after being sent.
To start of on the first level.
I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
The Draytek DHCP function is set to off.
192.168.168.2 (DC) -> 80 (HTTP IIS)
192.168.168.2 (DC) -> 1723 (RRAS)
192.168.168.3 (Exchange) -> 25 (SMTP)
192.168.168.3 (Exchange) -> 443 (SSL)
My Draytek router is connected through LAN1 to a HP switch (unmanaged).
The physical server has 3 NIC's, all of these are connected to the HP Switch
I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
The network has been configured as following.
I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
NIC1is setup for the physical server,
IP Address: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.254 (Draytek address)
DNS: 192.168.168.254 (Draytek address)
The Server software firewall has been set to a private network through the local security policy.
I have setup 2 VM's through the Hyper-V roll.
The first VM is the Server 2012 R2 Domain controller.
For this VM I created a virtual switch connected to my second NIC(2).
I unchecked the box where my host can communicate with the NIC(2).
The DC has been configured as following:
Hostname: SERVER
IP Address: 192.168.168.2
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 127.0.0.1
I can ping to all the adresses from this server (internal and external).
The server has been promoted to domain controller with the following rolls.
ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
Alle these rolls have been set and working. (all have been tested)
DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
A DNS simple and recursive test work fine.
I did no configuration on the DNS after the DC PROMO.
So i created users in the AD.
After that I created a second VM, this one is used for the Exchange.
I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
Hostname: SERVER
IP Address: 192.168.168.3
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 192.168.168.2 (pointing to the DC)
I joined this server to the domain, everything is working fine.
Both servers have internet and network.
Running portscans on 1723 and 80 all work like a charm.
No its time to install Exchange.
I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
Installed de needed API and filters.
Installed Frameworks 3.5 on both servers.
And the Exchange installation was succesfull.
CU3 is also installed.
I configured the send connector, accepted domains etc.
Created all needed certificates (self signed)
Did a portscan on 433 and 25 and they work.
All the hosting records are set mail.domain.nl etc. and MX records.
I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
Connecting through the internet to OWA works perfect and i can login with users.
Sending e-mail internally works perfect, the messages are being deliverd in an instant.
Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
I did online SMTP checks and e-mail checks, the all come out like it should.
One message from MX TOOLBOX on the SMTP:
SMTP Transaction Time
8.408 seconds - Not good! on Transaction Time
I have nog other receive connectors setup, just the standard connectors.
So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
I ran the best practices analyzer and get about 23 errors and 20 warnings.
A lot of services are unhealt like the "ExchangeTransport).
I have no idea what is causing the issues and read almost every forum.
Does anyone have a clue what is going on?
Did i miss something, is there a misconfiguration?
Best regards,
Tim
The mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
The internal e-mail also works flawless.
The entire Exchange server just not received this mail in time.
I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
After you asked me about the firewall, i got a hunch..
It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
Still the same problem...
But there was still one ethernet device that could have a firewall, the internet modem!
This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
But I was wrong, there was a firewall enabled on the modem!
All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
creating the issue on the incomming e-mail.
I disabled the firewall and all the external e-mails are being received in an instant!
Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
Many thanks for your help Kjartan!
Similar Messages
-
Exchange 2013 - Mail receive problem -Help!
Exchange 2013 SP1 -fresh install -test environment with one test mailbox setup in addition to the Administrator account. Using default Receive Connectors and it is set for Anonymous. Using OWA and Outlook 2010 for testing.
We can send/receive mail INTERNALLY in both Outlook & OWA between our test user and the Administrator user.
We can send mail externally from both accounts.
We are not receiving mail into the Inbox of either OWA or Outlook.
We are not seeing any authentication issues with Outlook -always shows connected to Exchange. But if we have same problem in OWA then we are just testing with it for now.
We ran the Microsoft Connectivity Analyzer for both Inbound and Outbound SMTP and it passed with no errors/warnings L
We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:Thank you for replying. Yes the mailbox is at Time Warner and I can use their webmail interface and see the messages I sent to the test user are there.
No, our domain name is companyname.com (if you need the actual name..I am not sure if I should send it to you?) and we use
[email protected] for email.
Our external A records and MX records are at Network solutions and that is posted here-- but decided to start another thread with more concise information as I learned of it:
http://social.technet.microsoft.com/Forums/office/en-US/0b18e928-0207-4ab9-bc12-c00a75088bdc/new-deployment-outlook-can-send-but-not-receiving-messages?forum=exchangesvrsecuremessaging
When I do NSLOOKUP of our domain I get just the two MX records at Time Warner. Not anything with our actual domain name for email in it. I just added the A records for mail.companyname.com and autodiscover at Network Solutions yesterday...but though those
were only for use externally for OWA, ActiveSync, etc
Note we do not use Split-DNS on our internal domain either. Our AD name is different than our public domain name - The AD is named with a subdomain: qs.companyname.com
Lastly, I did not create an MX record at network solutions for mail.domainname.com. Should I do that and set it to a higher priority? -
Mails From Exchange 2013 are received as SPAM
Hello,
We have Exchange 2013 configured to send and receive mails internally and externally. Everything is going great except the fact that the mails sent FROM our Exchange 2013 are received as SPAM. For example, I send an email from exchange to my gmail account
(generally to any EXTERNAL receipt). I receive the mail in the SPAM folder.
Any ideas Please !!Hi,
Firstly, I’d like to recommend you find out exactly what the problem is and resolve it before bothering to delisting from the blacklist.
And based on my knowledge, there are the following reasons:
1. Exchange Server is pumping out SPAM emails because a mailbox password was compromised:
Please figure out which mailbox user is the culprit by looking over event viewer logs and change the password. Then clear email queue and see if any new spam emails are generated, if the change of password stops the flow of SPAM email, we can remove the domain
name from the blacklist.
2. One of our computers are infected with a mass mailing worm virus:
We can check our firewall log
For information about removing from blacklist, you can refer to the following similar thread:
http://social.technet.microsoft.com/Forums/en-US/b3b818a6-641a-4264-87ca-fa4183ffc50c/how-to-remove-my-ip-address-fro-blacklist?forum=exchangesvrsecuremessaginglegacy
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support -
Exchange 2007 - Exchange 2013 Mailbox Migration Issues
Exchange 2013 - Mail Flow is working. OWA Access is great. We have issues connecting Outlook 2010 Clients. If I create a new user and mailbox Outlook 2010 works fine. However, if we migrate a user's mailbox to the new Exchange
2013 server. Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server" There is something different about a newly created account and a migrated account. Any help would be great. I did check
inheritance in AD and it was on for these accounts. This occurs with any account migrated to the new server.1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
generates and provides the correct information.
2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
Step by Step Screencasts and Video Tutorials -
Exchange 2013 not receiving internal and external emails ..
I have a coexistence of exchange 2007 and exchange 2013 ..2013 mailboxes where able to receive and send mails (internal and external) but suddenly the mail flow has stopped.
Mail flow status
2013 to 2007 = OK
2013 to internet = OK
2013 to 2013 = OK
2007 to 2013 = FAIL
Internet to 2013 = FAIL
incoming internet mails return the NDR below
Diagnostic information for administrators:
Generating server: mydomain.com
[email protected]
Remote Server returned '< #4.4.7 smtp;400 4.4.7 Message delayed>'
What could be a possible reason for this?
Cheers guys ..
..forever is just a minute away*Hi Richard,
Thank you for your question.
When there is a coexistence of Exchange 2007 and Exchange 2013, external email will be sent and received by Exchange 2013.
4.4.7 means message expired, message wait time in queue exceeds limit, potentially due to remote server(your Exchange server ) being unavailable.
If your organization has correct MX record in ISP. We could refer to the following link to check if MX record is correct:
http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx
If we could telnet Exchange server by the following command: telnet mail.domain.com 25
If there is a receive connector on Exchange 2013 to receive Internet emails, we could create a receive connector to receive message from the Internet by the following link:
http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim -
Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured
Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured.
[PS] C:\Windows\system32>Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories
: True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode
: UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 10 MB (10,485,760 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml
: True
ExternalPostmasterAddress : [email protected]
GenerateCopyOfDSNFor :
HygieneSuite
: Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 10 MB (10,485,760 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml
: True
InternalSMTPServers
: {127.0.0.1}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime
: 7.00:00:00
MaxReceiveSize
: 50 MB (52,428,800 bytes)
MaxRecipientEnvelopeLimit : 5000
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize
: 20 MB (20,971,520 bytes)
MigrationEnabled
: False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime
: 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags
: {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled
: Truehi stephan... lets put in this way... are you sending attachment ...did you checked the max attachment size as mail send size and attachment size are two different things.. please check this for info on different size creteria
http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
can you please share the output of below three commands... i doubt your receive connector is not configured properly.
Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
Get-SendConnector | Format-List -Property Identity, MaxMessageSize
Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
you can also check this link which gives a perfect info on how exchange works for email size... http://rajisubramanian.wordpress.com/2014/01/26/exchange-server-2013-message-size-configuration-detail/
Mark as useful or answered if my replies helped you solving your query.
Thanks, Happiness Always
Jatin
Skype: jatider2jatin, Email: [email protected] -
Exchange 2013 Mail Size Limits
I am having an issue with setting the max send and receive size on Exchange 2013. I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
server to an external account:
#550 5.3.4
ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
I have checked the mail sizes and below is the report. I currently have both send and receive set to 100MB. Is there some other setting in 2013 that I am not aware of?
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories
: True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode
: UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 100 MB (104,857,600 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml
: True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor :
HygieneSuite
: Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 100 MB (104,857,600 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml
: True
InternalSMTPServers
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime
: 7.00:00:00
MaxReceiveSize
: 100 MB (104,857,600 bytes)
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize
: 100 MB (104,857,600 bytes)
MigrationEnabled
: False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime
: 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags
: {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled
: TrueHello Landfish,
Good Day...
The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue.
There are basically three places where you can configure default message size limits on Exchange:
Organization transport settings
Send/receive connector settings
User mailbox settings.
To check your server’s current limit you can open Exchange Management Shell
Try the below commands to check the Message quota size limit
get-transportconfig | ft maxsendsize, maxreceivesize
get-receiveconnector | ft name, maxmessagesize
get-sendconnector | ft name, maxmessagesize
get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
To change the above size limits based on your requirement.
Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
Attachment size limit
To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
For More info
https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
Remember to 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 Check out my latest blog posts @ Techrid.com -
Exchange 2013 mailbox migration issues
or I could just restart the 2013 mail server.... *sigh*
So Exchage 2013 is set up, sending and receiving emails is working, OWA access is working and redirecting to our old 2010 if the mailbox resides there.However after moving a mailbox from 2010 to 2013 there have been a few issues.The mailbox connects ok with Outlook 2013, but will not open the onprem Archive."cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available.."This works ok in OWA.I then deleted the outlook profile, but now Outlook cannot connect to create a profile at all!It detects my name and email ok, then when it gets to "logging on to the mail server" I get the error"Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this...
This topic first appeared in the Spiceworks Community -
Exchange 2013 stops receiving external email after about 8 hours
Hello,
Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night. I could not find anything wrong with receive connectors. Telnet works internally when this
happens but NO access from public side testing with telnet. After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
I dont know what to check or look for at this point. Very new to exchange 2013. Any kind of advice would be helpful at this time.
It is not a firewall issue. Same firewall and set of rules that we use for other/old mail servers. We only have 1 exchange server that has all roles.
Lead PusherOK... Did alot of testing and spent some time with Microsoft's support on the phone.
I believe there is actually two problems going on in this thread.
1. Exchange 2013 Admins that have changed the default receive connectors are experiencing a conflict on the scope settings. Make sure that none of the receive connectors are using the same ports, and that you have not modified the security settings in anyway
unless you really know what you are doing.
If you are unsure of what the settings should be after you have change them, the only suggestion I have right now, (as I have not taken the time to do screen shots or write down all the default settings) is to install Exchange 2013 on a virtual machine and
look at them, then change back the settings that do not match.
2. The Malware Agent has a flaw that is causing the the Microsoft Exchange Transport service to endlessly wait on the Malware Agent to process a message that it just can't handle. (Two reboots of the entire server may be needed to clear this, or sometimes
you can get away with restarting the Microsoft Exchange EdgeSync service.)
The Microsoft technician had me perform a sequence of steps that highlighted this. To see if this is infact your problem you can perform the following steps.
A) Once the Exchange server stops processing messages, figure out the rough time it stopped processing messages.
B) Open the event viewer.
C) Under "Windows Logs", right click "Application", select "Filter Current Log...", check "Warning" and "Error", then click "OK".
D) Scroll down the log to the rough time that your Exchange Server stopped processing messages. You are looking for a slew of errors about the same time from "MSExchange Extensibility" (1051), "MSExchange Transport" (9201), "MSExchange
Transport" (9201), "MSExchange Extensibility" (1056), "MSExchangeTransport" (10003), and "MSExchange Common" (4999).
It is the "MSExchangeTransport" (10003) that I believe is the real problem. The Microsoft technician agreed. He did not want to spectulate as to exactly what was going on, but it seems to me that since he had me disable the "Malware Agent"
for now, that it is indeed the problem.
E) So.... Open the Exchange Management Console and type "Disable-TransportAgent", followed by enter. It will prompt "Supply values for the following parameters:". Enter "Malware Agent", press enter again. Type "A",
for yes to all.
or
http://technet.microsoft.com/en-us/library/jj150526.aspx"
F) Go to run, enter "services.msc". On the window that opens, find "Micorosoft Exchange Transport" and restart it.
I know this is NOT a fix, but a work around that is less than desired as the Malware Agent is a filter to keep unwanted emails out. I highly recommend running some sort of 3rd party spam/Malware filter that has been fully tested to run with Exchange
2013 if you do this.
Microsoft is to contact me back once they can figure out why this is happening, and I believe in the end a patch for Exchange 2013 will be produce to correct the problem.
In the mean time.... don't waste your money on paying Micorosoft for support, as I have already done this.
For the individuals who say they are not experiencing trouble, I am going to go out on a limb here and say that either you have a 3rd party software program that is filtering the mail before it reaches the Malware Agent, you have disabled the Malware Agent,
or you are using another mail server to forward email to your Exchange 2013 server. With either of these cases you are much less likely to see this problem.
One last issue that a few people may be experiencing, is Exchange 2013, running on Server 2012 that is a VM. Several VM setups have a bug with the VM NIC management interface and Windows Server if you are using the same NIC for both. For example Xen
Server 5.6 and XEN XCP both have this bug. There is an patch for XEN Server 5.6, but so far nothing for Xen XCP.
I have spent many hours trying to figure my problems with Exchange 2013 and I will not swear that my entire post is correct, but I have gotten very much closer to a stable mail server after much work. If you feel that anything is incorrect, please reply
back and let me know why, so that we may all benifit.
P.S. Sorry for the mis-spellings and what not, I am very tired at the moment, and was forced to use explorer, because this site is not liking Chrome at the moment. (Will not let me login) -
Exchange 2013 Hybrid Deployment issues.
Hello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanksHello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanks
Make sure the accepted SMTP domains in the Office 365 EAC are set to Internal Relay rather then Authoritative.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Exchange 2010 to Exchange 2013 mail flow?
We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
Outlook 2013 with Exchange 2013: Mails stuck in Outbox
Hi everybody,
I am using Outlook 2013 connecting an Exchange 2013 server. After sending a mail, all outgoing mails remain in the outbox. After removing the cache files it works for a while until the problem occurs for the next time (approx. once every two days).
I already re-installed Windows 8 to test it on a completely clean environment...OWA works fine, the problem only exists with Outlook.
Additional note: It might be interesting that after sending a mail, the "Send/Receive progress" window states "sending [email protected] - complete" but the Mail is still in the outbox and was not delivered to the recipient. Safe mode doesn't work
for me. Other users connecting with Outlook 2010 don't have a problem with this exchange server.
Do you have any ideas? If I can provide you with further information, please let me know.
Greets,
BastiThanks for your answer. Here are the requested information:
>What addins are you using?
No 3rd party addins, at the moment "Microsoft Exchange Add-In", "Microsoft VBA for Outlook Addin",
"OneNote Notes about Outlook Items" and "Outlook Social Connector 2013" are activated. But the problem also occurs if no addin is active (or even in Safemode).
>Antivirus
scanners can prevent Outlook from moving messages to the sent folder.
I will try to deactivate the virus scanner the next time. (Avira is used)
>Can
any address trigger this behavior or does it happen with certain addresses?
No, it does happen with any address by random. Once the problem occurs, I can try to send as much mails as I want to
any address - nothing leaves the outlook client.
>Is
this your mailbox or a shared/secondary mailbox?
It is a user's mailbox, nothing shared. -
Exchange 2013 Attachment Size Issue
Hi everybody,
I'm having some trouble with an Exchange 2013 server.
The users are not able to receive messages with a size bigger than 10MB, i tried with serveral attachments.
I already did te following:
Changed the maximum receive size through the ECP to 60MB (on the default frontend Exchange), and restarted te transport service.
Set the receive size through PowerShell with the following command.
set-transportconfig -maxreceivesize 35MB
when i check the receive size properties, it accepts 35MB messages. (get-transportconfig -property maxreceivesize)
Also restarted serveral Exchange transport services.
Checked the router if there are any special firewall rules, but there are none.
When I send an email with an attachment (PDF about 4 meg), it receives like it should.
Once I send a same email but with an 11meg PDF file, it is not delivered.
When sending this e-mail and attechment, i checked the box to notify me when the message has been deliverd.
I don't get any response, no NDR, nothing...
Tried e-mail tracking but there is no trace of my message.
Am I missing anything?
Kind regards,
TimHi,
Please check the message size limit on receive connector, by default it’s 35MB
Get-ReceiveConnector “connector name”| fl MaxMessageSize
Also check if there are any message size limit in transport rule.
Get-transportrule | fl MessageSizeOver
Message size limits
https://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
Querying Exchange 2013 Mail server for email items using c# and Exchange Web Services
I am trying to upgrade an existing application that reads Exchange 2003 using WebDAV. The mail server is to be upgraded to Exchange 2013, so I am checking how I can use EWS.
I have a problem in that although I know the inbox has unread items with attachments, the query I am running against the
FindItems object is returning empty (results.totalCount=0)
Here is my code snippet:
private static void GetAttachments(ExchangeService service)
// Return a single item.
ItemView view = new ItemView(100);
ServicePointManager.ServerCertificateValidationCallback = CertificateValidationCallBack;
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);// .Exchange2007_SP1);
service.UseDefaultCredentials = true;
service.AutodiscoverUrl("[email protected]", RedirectionUrlValidationCallback);
ItemView view = new ItemView(1);
string querystring = "HasAttachments:true Subject:'ATTACHMENT TEST' Kind:email";
// Find the first email message in the Inbox that has attachments.
// This results in a FindItem operation call to EWS.
FindItemsResults<Item> results = service.FindItems(WellKnownFolderName.Inbox, querystring, view);
//FindItemsResults<Item> results = service.FindItems(WellKnownFolderName.Inbox, new ItemView(50));
if (results.TotalCount > 0)
// looping through all the emails
for (Int16 iDx = 0; iDx < results.TotalCount-1; iDx++)
EmailMessage email = results.Items[iDx] as EmailMessage;
if (email.IsRead == false) {
// Request all the attachments on the email message. This results in a GetItem operation call to EWS.
email.Load(new PropertySet(EmailMessageSchema.Attachments));
foreach (Attachment attachment in email.Attachments)
if (attachment is FileAttachment)
FileAttachment fileAttachment = attachment as FileAttachment;
What I am supposed to be doing is reading all the unread emails in the target inbox (only one Exchange server) and taking the attachments on disk so I can then add them as attachments as new cases on SalesForce.
Where am I going wrong?
Also, this line:
ItemView view = new ItemView(100);
was:
ItemView view = new ItemView(1);
Surely that will only look for one email item, right?thanks, do you know why I would be getting an error message like 'The specified object was not found in the store'
here is my code:
ServicePointManager.ServerCertificateValidationCallback = CertificateValidationCallBack;
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);// .Exchange2007_SP1);
service.Url = new Uri("https://sgexc.bocuk.local/EWS/Exchange.asmx");
//creates an object that will represent the desired mailbox
Mailbox mb = new Mailbox(@"[email protected]");
//creates a folder object that will point to inbox folder
FolderId fid = new FolderId(WellKnownFolderName.Inbox, mb);
//this will bind the mailbox you're looking for using your service instance
Folder inbox = Folder.Bind(service, fid);
FindItemsResults<Item> findResults = service.FindItems(new FolderId(WellKnownFolderName.Inbox, new Mailbox("[email protected]")),new ItemView(10));
it's happening on this line:
Folder inbox = Folder.Bind(service, fid);
and if I try to use AutoDiscoverURL then I just see my own inbox. -
Exchange 2013 mail flow problem
Hello!
We have problem, could not send mails via Exchange 2013 server.
Symptoms:
-no messages in message queue
-if sending mail to this domain, the message seems sent at Sender.
-if sending mail from this domain, the messages are in the mailboxes' DRAFT folder
Here are some SMTP logs:
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical
non matching options : Xrdst, . Failing over."
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,
Software Enviroment:
-Windows Server 2012 Server Standard
-Exchange Server 2013
-fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.
Regards.
molniHi
Can you run ipconfig/flushdns or create hosts file recorder?
Terence Yu
TechNet Community Support
Maybe you are looking for
-
Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS
hi all, while doing post goods issuse for a delivery causing a following dump The call to the function module "CEI0_COMPARE_CONFIGURATIONS" is incorrect: The function module interface allows you to specify only fields of a particular type under "IV_E
-
URGENT!!! Please help~ Process Multiple Files says folder empty
When I try to use the Process Multiple Files feature, it is giving me a message saying that the process was stopped or cancelled. Press continue or stop. When I click continue, it say that the folder is empty. It is not empty. This is what I us
-
Password was not setup correctly during DBUA upgrading
Hi Experts, I was using DBUA to upgrade our system from 11.2.0.3 to 11.2.0.4. There was one step to setup the password, I think I accidently put an extra "Enter" or "Space" in the end of the password. DBUA prompted a warning:"You have a invalid passw
-
Un-edited Images Won't Open Following Export
Greetings, and I hope you can help with this irritating little problem which either cropped up recently or which I just recently started to notice: • I have, say, a folder of 10 images which I Import into iPhoto 5. Of those, I edit 7 in iPhoto (red e
-
Possible to tell which programs are accessing the internet? Bandwidth?
I seem to have intermittent, severely limited access to the internet at times. Is it possible to tell if a particular program running in the background is either downloading or scanning or "online" in some manner...? Is it possible on a Mac to see ho