I'm trying to configure a transport rule in Exchange 2013 to block all emails from the TLD .eu We get nothing but a TON of spam that is not caught by the Exchange 2013 spam filter, and it's always from a different domain. I have seen guides for 2007 and 2010, but nothing for 2013.
Do I just use the rule "The sender domain is" and use the value ".eu"? I just want to verify this is the correct way to block a TLD.
Today I got an email from a user saying she just received an internal email that was sent November 5th 2013. I tried using Exchange Tracking Log Explorer but nothing shows as being received on 11/5/13 and nothing from todays date that matches the Subject. Here are is the msg header which has been modified to hide our domain. This is a small business with 12 users with SBS 2011. This isn't the first time this has happened either. Another user had email delayed for 3 months.
In Exchange 2007, when my cutomer sent an email to an outlook distribution list (i.e 20 people) with a delivery receipt requested, it would return a single email with all the group members.
Now since changed to Exchange 2013, the same email to the distribution list returns individual delivery receipts from 'microsoft outlook'. I would like to know if it's by-design behaviour, or if it is configurable.
Hi,
I have two mailbox servers in exchange 2013 and I am maintaining DAG on both servers. I recently added a new mailbox server in my environment. Now I have 3 mailbox servers. But the third mailbox server does not have any DAG nor it is the member of any DAG in the organization.
The problem is that when I want to uninstall exchange from mailbox 3. It gives the following error.
Error:
This computer is a member of a database availability group (DAG). It must be removed from the DAG before you can uninstall Exchange.
Please suggest.
Thanks.
We are currently using a wildcard certificate: *.ourdomain.com
We are going to change from a wildcard and start using: mail.ourdomain.com
I did the following:
1. Added the intermediate certs on each CAS server in the "Intermediate Certificate Authority" section
2. Imported the mail.ourdomain.com cert in Exchange on each CAS server.
3. Assigned the IIS and SMTP services to the mail.ourdomain.com cert on the CAS server.
4. Ran the following commands in EMS:
Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.ourdomain.com
Set-OutlookProvider EXCH -CertPrincipalName msstd:mail.ourdomain.com
5. Imported the cert on our antispam appliance
6. Restarted each CAS server
Outlook users received the following errors:
Also, when I test with CheckTLS.com with the mail.ourdomain.com, I see the following:
How can I resolve this?
Hello everyone,
First off, I would like to state that I have around five years of Microsoft Server experience, but I have never set up an Exchange environment from scratch, and my knowledge in that area is admittedly not so great. So if there are any areas of my questions that are either incorrect or going in the wrong direction, I would appreciate your help in getting pointed in the right direction :-)
So for some background, I have my own Windows Server 2012 R2 environment set up, consisting of a primary and secondary domain controller, and my newly set up Exchange 2013 SP1 server (making for a total of three servers).
After some struggle, I was able to get my Exchange server set up and configured to the point where I can send and receive emails internally. I have followed step-by-step guides that I found on TechNet to accomplish this, so I am fairly certain that I have set up at least all the basics correctly, such as Mail Flow and Send / Receive Connectors.
Here is where my inexperience comes into play, however. I purchased / reserved a domain through GoDaddy in the hopes of using it as the @domainname.com portion of my email address. I set up my @domainname.com portion of my email addresses to match the domain name that I purchased, and as I mentioned I am able to send and receive internally (which is obvious, since it is internal and hasn't actually gone out to the Internet yet.)
So now I am trying to figure out how to both send emails to external destinations (testing it using my gmail account), and to receive emails back from the same gmail account. When I sent off a test email, I checked the message queue and discovered that the email I tried to send was stuck in a loop where it was trying to be resent, and the only error message that displayed was:
The last attempt to send the message was at 4/9/2014 10:16:26 AM (UTC-05:00) Eastern Time (US & Canada) and generated the error '[{LRT=};{LED=};{FQDN=};{IP=}]'.
I have searched and looked at numerous blogs and articles that potentially address this error/issue, but so far have been unable to figure out a solution to be able to send/receive externally.
For the receiving part, I am uncertain what exactly I need to do on the GoDaddy hosted domain side to make it so that emails will get routed over to my Exchange server, so I would also appreciate any help on this step of the process.
Thank you in advance for your time and help with this, I really do appreciate it!
Good morning
We are having a problem in that we are receiving a lot of spam to externally available distribution groups (ones that accept email from the internet as well as from within my organisation).
After viewing headers on mail received by a user who is a member of one of these distribution groups we see that there is no'X-MS-Exchange-Organization-SCL' header.
Does this mean that Exchange is not performing spam checking on emails sent to distribution groups? If this is the case is there anyway of turning this on?
This TechNet question seems to suggest this is the case, but in their situation they are using Forefront, we are not: http://social.technet.microsoft.com/Forums/en-US/467d092e-35e0-47ab-873e-2ce34aa6db0c/content-filter-and-distribution-groups-receiving-external-senders?forum=exchange2010
Any help or advice would be greatly appreciated.
Kind regards
Hi,
I have an Exchange Server 2013 running on one Server. I have set up a receive connector for the internal Scanner (Scan to Email). this works most of the time - but occasionally fails with the following error: "51 4.4.0 Error encountered while communicating with primary target IP address: ""421 4.4.2 Connection dropped" - any help will be appreciated.
I have run the health tests on the server and these are the unhealthy returns:
| Server | State | Name | TargetResource | HealthSetName | AlertValue | ServerComp |
| onent | ||||||
| ------ | ----- | ---- | -------------- | ------------- | ---------- | ---------- |
| EXCHVM | NotApplicable | ActiveSyncCTPMonitor | ActiveSync | ActiveSync | Unhealthy | None |
| EXCHVM | Offline | OutlookProxyTestM... | MSExchangeRpcProx... | Outlook.Proxy | Unhealthy | RpcProxy |
| EXCHVM | Offline | RWSProxyTestMonitor | MSExchangeReporti... | RWS.Proxy | Unhealthy | RwsProxy |
| EXCHVM | Offline | RPSProxyTestMonitor | MSExchangePowerSh... | RPS.Proxy | Unhealthy | RpsProxy |
| EXCHVM | Offline | OWAProxyTestMonitor | MSExchangeOWACale... | OWA.Proxy | Unhealthy | OwaProxy |
| EXCHVM | Offline | AutodiscoverProxy... | MSExchangeAutoDis... | Autodiscover... | Unhealthy | AutoDis... |
| EXCHVM | Offline | OWAProxyTestMonitor | MSExchangeOWAAppPool | OWA.Proxy | Unhealthy | OwaProxy |
| EXCHVM | Offline | OABProxyTestMonitor | MSExchangeOABAppPool | OAB.Proxy | Unhealthy | OabProxy |
| EXCHVM | Offline | ActiveSyncProxyTe... | MSExchangeSyncApp... | ActiveSync.P... | Unhealthy | ActiveS... |
| EXCHVM | Offline | EWSProxyTestMonitor | MSExchangeService... | EWS.Proxy | Unhealthy | EwsProxy |
| EXCHVM | Offline | ECPProxyTestMonitor | MSExchangeECPAppPool | ECP.Proxy | Unhealthy | EcpProxy |
| EXCHVM | NotApplicable | AutodiscoverCtpMo... | EXCHVM.theplantpe... | Autodiscover | Unhealthy | None |
| EXCHVM | Online | OnPremisesInbound... | FrontendTran... | Unhealthy | Fronten... | |
| EXCHVM | NotApplicable | EWSCtpMonitor | EXCHVM.theplantpe... | EWS | Unhealthy | None |
| EXCHVM | NotApplicable | HealthManagerHear... | Monitoring | Unhealthy | None | |
| EXCHVM | NotApplicable | OwaIMInitializati... | OWA.Protocol.Dep | OWA.Protocol... | Unhealthy | None |
| EXCHVM | Online | HubAvailabilityMo... | HubTransport | HubTransport | Unhealthy | HubTran... |
| EXCHVM | Online | Messages.failed.t... | HubTransport | Unhealthy | HubTran... | |
| EXCHVM | NotApplicable | OwaCtpMonitor | OWA | Unhealthy | None | |
| EXCHVM | NotApplicable | Mapi.Submit.Monitor | MailboxTransport | MailboxTrans... | Unhealthy | None |
| EXCHVM | NotApplicable | OutlookMailboxCtp... | Outlook | Unhealthy | None | |
any idea where I should start?
Hi,
Does anyone know a way to set a receive connector to only request authentication in certain circumstances?
Let me explain the scenario: If you have a receive connector that is set to accept general inbound emails from anyone then it will be set to accept emails from any sender address.
However, if someone is trying to spoof the sender address and they use an email address which is valid within your organisation then it would be really useful if it could request authentication at that point, since emails from internal users should only come from authenticated devices.
Is there any way to do this?
Thanks in advance.
Neil
Hello,
I installed Microsoft Exchange 2010 on Windows Server 2008.The installation was successfully completed. The URL for the OWA is also working.But there is a problem in sending and receiving emails.The user is unable to send and receive emails.The emails get moved into DRAFTS folder as soon as it is sent and a message "The message has not been sent" is displayed.
Please help me out with the above issue.
Thanks,
Shatadiya Saha
I am having a new issue on my mailserver where most of my DDL's are not being delivered.
I can review the properties of the DDLs and they show the necessary recipientes in the filter.
When I send to them, they do not deliver and I do not get an NDR from the server. I get two events in the Message tracking, the first, Source:STOREDRIV EventID:Receive
the second: Source AGENT EventID:Fail
with that, I cannot find anything that is helping me find why it is failing, where can I look in the logs for more clues?
Hello
I am facing an unusual behaviour which drives me crazy.
A user (it’s unfortunately an important one) receives every night at 02:07 meeting confirmations in his “deleted items” folder.
During this time the Exchange Database Maintenance is scheduled. But I have no idea why this should generate such mails.
I think somehow this maintenance Task sends out a meeting request which is automatically approved by the recipient and the confirmation is sent back to my users deleted item folder.
Someone got an idea what is causing this?
Hi guys,
I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails.
Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
Current Environment Configuration:
I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role. I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.
I am upgrading exchange 2010 to exchange 2013 and currently in coexistence. I cutover the mx to deliver mail to 2013 cas VIP last night and no mail was being received by the 2010 mailboxes, it was all being queued on the 2013 mailbox servers (mailbox and cas servers are separate in this deployment.) There are only a few 2013 mailboxes as I have not yet started migrating them. These 2013 internal mailboxes can not send to exchange 2010 either, but 2010 can send to 2013. 2013 to 2013 mail works fine. I have read somewhere about an issue with a receive connector having the same ip range that includes the mailbox servers, but I'm not clear on really which mailbox servers it is alluding to.
All the exchange 2010 servers are all on the 10.1.1.* network. Exchange 2013 CAS servers are all on the 10.1.1.* network and the 3 exchange mailbox servers are on 10.1.1.*, 10.1.2.* and 10.30.5.*. Only 1 AD site. On one of the 2010 receive connectors there is a scope of 10.1.1.0/24 I'm wondering if this is the culprit and by removing it should fix the problem. Any other ideas would be appreciated.
I have done the transition from Exchange 2007 to Exchange 2013.
mail.mycompany.com was my exchange 2007 + Domain Controller
I came up with mail1.mycompany.com which is my exchange 2013server
and also i came with another new domain controller mydc.mycompany.com
and i have decommisoned my exchange 2007+DC
now i dont have any server with mail.and also i have changed my current exchange 2013 servers ip to the old servers ip(Exchange2007 ip). I have my all external URL's pointing to mail.mycompany.com
What records do i need to create in DNS so that all my users do access mail.mycompany.com(internally and externally)
rather than mail1.mycompany.com
Hello,
1 week ago I've implemented a new Exchange 2013 at a company which used SBS 2011 before.
But now its impossible to send a mail to a recipient on Exchange Online.
Everytime we get a NDR with the following text:
Service unavailable; Client host [xx.xx.xxx.xxx] blocked using Blocklist 1; To request removal from this list please forward this
message to delist@messaging.microsoft.com
If I run a SPAM-Blacklist Check on mxtoolbox.com I can see that the IP is on none blacklist.
How can i determine why this IP is on the Exchange Online Blacklist? I'm sure that no spam was sent over this IP, the new infrastructure is 1 week old...
Could there be an other reason ?
I am trying to determine if every mailbox user has *READ* a certain email. In this particular use-case it is the company newsletter being sent from MailChimp.
I have tried getting the results of Get-MessageTrackingLog to display the status, e.g. whether it is READ or not. I am able to get the information I need one recipient at a time using the Delivery Reports in OWA but that is very labor intensive.
Since Exchange knows the status of the message and the physical location of the message via Delivery Reports, how/what can I do to include those elements in the output of my Shell command(s)?!
Hello,
For a particular messgae i.e announcement message that i send i do not want any oof, auto-reply from any users for only that
particular e-mail.
I know that any e-mail which has header as below can suppress oof, auto-reply
Auto-Response-Suppress: OOF, DR, RN, NRN
Please let me know how to do it.
Thanks,
Abhishek Gupta
Hi all
I am using my applications server to send mail through my exchange 2010 server. I also have my DR Site server for Exchange 2010 with DAG concept.
please find below my server setups
Main site
1. Exchange MBX
2.Exchange HUB/CAS
3.Exchange Edge Server.
DR site
1. Exchange MBX/HUB/CAS
2. Exchange Edge
MBX Server are configured with DAG for Database High availlablity. we have p2p link between main site and DR Site.
We created the below receive connector in both our HUB server for accept the mails from my applications server.
1. connector name : Application_ connector- selected the Custom option
2. network --> use the local ip address to receive mail --> All available ipV4 port 25
Receive mail from remote server that have these ip address --> 10.X.X.X --> my application server.
3.Authentication --> basic authentication, Exchange server Authentication
4.Permission group --> anonymous user, Exchange users, Exchange Servers, Legcy exchange servers.
it was working fine its send the mail internally not issue.
All the DBs are mounted in our main site Only.
1. last week my DR Site P2P link got down that time the mails sent from application server was not received by our users. I don't know why?
2. once the Link got up the mail flow happened. For testing purpose I disabled the application receive connector in DR HUB server and immediately the application mail flow got down. since all the mail flow taking care by main site, How my applications server mail itself taking my DR. I also checked my application server mail config and its configured with my main site HUB server only.
3. now I also want my application to send mail to external users. How to enable this? how secure it was?
I am not able to complete the above issue for the past week. any body will help me to resolve the issue much appreciated....
thanks in advance
Jags
Hello everyone.
We had a very weird error this morning on our Exchange 2013.
We were not able to receive email from outside, but we were able to send to the outside.
I was doing some testing with an outside account and I noticed that when I sent an email from outside(google) to the exchange, in the Delivery Report, you can see the email but at the bottom there was a message saying.
The message couldn't be delivered.The message never reached my mailbox.
We rebooted the server and the mail started to flow, but all those test email and of course the real email that was coming in at that time is lost.
Does anybody know what this could be?
Any guidance will be great. Thanks in advance.
Jack.