Exchange Server 2013 email rejections from free ISP accoounts

We have an Exchange 2013 box, and we are getting random mail no deliveries to mostly free email isps (gmail, hotmail, yahoo, and aol) where errors are like:
Generating server: OPCSEX.opcs.local
Receiving server: mailin-04.mx.aol.com (64.12.91.196)
[email protected]
8/31/2014 2:56:52 PM - Remote Server at mailin-04.mx.aol.com (64.12.91.196) returned '550 4.4.7 QUEUE.Expired; message expired'
8/31/2014 1:49:53 PM - Remote Server at mailin-04.mx.aol.com (64.12.91.196) returned '451 4.4.0 Primary target IP address responded with: "554 mtaig-mcb02.mx.aol.com ESMTP not accepting connections." Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 64.12.91.196:25'
When I research I am reading thinks like the mail record should be a cname, not a record. That dosent make sense to me. Is there a tool that can help me track down the issue, or that verifies that all my DNS records are correct?
Thanks

Hi,
In your case, I recommend you create a send connector that force HELO for these problematic domains and check the result. Use the following cmdlet to create the special send connector.
New-SendConnector -Name ForceHelo -AddressSpaces problematicdomain.com -ForceHELO $true
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

Help with Moving Emails from Exchange Server 2013

Hi Team,
Help, I need a solution on how to copy incoming and outgoing emails together with their attachments and was hoping someone could help with a solution I need to find for this problem.
1) I have a need to copy all incoming and outgoing emails & attachments from Exchange Server 2013 mailboxes on a daily basis, so they can be archived into an external 3rd party database overnight.
I believe that the first step is that I can set up another Exchange mailbox, through Journaling to receive these emails.
Is there any way that these emails can then be moved direct from the Journaling mailbox that I have created, to a shared folder on the network? If so what format would they be sent out as e.g. .msg, .ems and what is the process?
Failing that, could they be sent to an Outlook client (not another Exchange mailbox) on the network and stored in a .pst file? (I have a program that will export them from .pst)
I would really appreciate any assistance that you can provide in this matter.
Regards, Greg.

Hi,
You can set auto-forward on journaling mailbox and auto-forward emails to another mailbox. Why don’t directly archive the emails from the journaling mailbox “an external
3rd party database”.
Thanks,
Simon Wu
TechNet Community Support

Blocking Spam Emails by subject name in Exchange Server 2013

Hello Guys,
I need to know how to block spams by subject from Exchange Server 2013's Anti-spam/message filter.
In general, I'm using Exchange's anti-spam agents and configured spam blocking by domain name.. but I need to filter unnecessary emails by subject name also.
So, if you know how to resolve this issue, please post here the real solution..
Thanks a lot,

Hi GMG,
Thank you for your question.
We could install Exchange 2013 edge server, then we could create item which block spam base on subject name in “Protection”, we could refer to the following link:
https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx
There is a another method, we could use transport rule to filter spam by subject name by the following link:
https://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Exchange Server 2013 SP1 - Internal Email Flow slowness

Hi Fellows,
I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
Header analysis shows the message exchange between mailbox servers is taking time. any clue?
Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
Network communication, Storage performance, Server performance are all as good as we love to.
Thanks.
J.A

Hello,
When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
Cara Chen
TechNet Community Support

Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

Hi people,
What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
Thanks

Hey AlbertWT,
Can you clarify exactly what you mean when you say "server patching?" Do you mean patching at the ESXi host level or something within the guest?
As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer. Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role. NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
Matt
http://www.thelowercasew.com

Recover mailbox from Exchange server 2010 information store to exchange server 2013

I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
I would like to recover a couple of mailboxes to an exchange server 2013.
Can anyone give me a detailed walk through of how I can accomplish this?
Thank in advance

Well if your AD is messed up that leaves you in a jam for sure because;
1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
3. Here is a good article on how to accomplish
http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB. We make a product that can do this (DigiScope), however if you don't
have any budget to handle its a non-issue.
The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
BTW if you AD is messed up, where are you putting this new 2013 server?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Internal NAV2013 to relay email externaly through our internal exchange server 2013

ello,
We are using NAV 2013 to externally relay email outside and inside through our in house Exchange server 2013.
I created a new Frontend connected with "TYPE" Custom and selected specific ip to configure relay through exchange server.
Once created the Receive connectors I want only Anonymous permission to be set under permission group and not exchange users as this is allowing external 3rd party exchange server to relay emails through our exchange server.
When i edit the properties of the exchange server to uncheck Exchange Server it gives me an error
"You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative."
My motive is that I want to allow only the NAV2013 to relay emails through our exchange and no other exchange server or any other application for security reasons.
Once i created a Receive Connectors bydefault TLS is selected and then i put a tick mark on Anonymous but as soon as i save i get error "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter
to a value of ExternalAuthoritative." and it doesn't let me save unless i select Exchange Server
I have followed the same link that you provided me.
There is another problem as well, I have restricted a distribution group from receiving email from external to the organisation but as soon as i created this relay connectors this group starts receiving email external to the organisation which is very strange.
I tested by disabling the relay connector and then sending email from gmail and then i get a bounce in gmail and the DG doesn't receive email but as soon as I enable relay connector the distribution group starts receiving email.
I have also recreated the connector as well but still the same issue.
Please help

Hi,
Please double check whether the "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative" is an error, we can safely ignore it if it
is only a warning message.
I found a related KB for your reference even if the Exchange server version is mismatched.
Exchange 2010: Get-ReceiveConnector warns that an Exchange 2007 connector is corrupted and in an inconsistent state
http://support.microsoft.com/kb/2291884
Please double confirm the following setting:
Authentication tab: Checked TLS and Externally Secured.
Permission Groups: Anonymous users, Exchange Servers
Thanks
Mavis
Mavis Huang
TechNet Community Support

Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
Example
[email protected]
[email protected]
[email protected]
I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email
Thank you
Benhur

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

Hello,
We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
The error we received at the Exchange Server is:
C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
stallWindowsComponents /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup
COMPLETED
Stopping Services COMPLETED
Language Files COMPLETED
Removing Exchange Files COMPLETED
Preparing Files
COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Mailbox role: Transport service FAILED
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
t Transport roles on a single server must listen on unique local IP address & po
rt bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
o different Transport roles on a single server must listen on unique local IP ad
dress & port bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Hello Gadget,
Please find the solution as follows
This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
1- Go to IIS Manager and select server certificate,
2- Select “Create Self-Signed Certificate”,
3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
4- Now go to ” Management Service”,
5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
6- Apply,
7- Now start service of “Web Management service”.
https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
Exchange Queries

Exchange server 2013 content filter rejecting all incoming messages as spam.

Hello All,
Today out of the blue our Exchange server 2013 install started rejecting any inbound message as spam. It first started with only one user not being able to receive any mail because of this anomaly and
then after 12 or so hours all users were getting their mail rejected.
I currently had the threshold set to 5 on external messages only. Internal is disabled.
I have tried setting the threshold to 8 and 9, and rebooted the server after restarting
all services just to make sure everything reset. Even dished out a IISRESET just in case. Whatever I tried still does not work.
The install is a stand alone server facing the outside world (no edge server) living
in a 2 domain controller environment with a share point farm thrown in (ESXI5.5 environment)
Everything works just fine and dandy if I disable the content filter all together. Not seeing anything in the application logs out of the ordinary. Everything was working great and the same settings I used on this server worked well for a totally different
server that runs just fine.
Any ideas?
fr0stsp1re

RunspaceId                            : 87157b62-a061-436b-8fb9-dab446be3473
Name                                  : ContentFilterConfig
RejectionResponse                     : Message rejected as spam by Content Filtering.
OutlookEmailPostmarkValidationEnabled : True
BypassedRecipients                    : {}
QuarantineMailbox                     :
SCLRejectThreshold                    : 6
SCLRejectEnabled                      : False
SCLDeleteThreshold                    : 9
SCLDeleteEnabled                      : False
SCLQuarantineThreshold                : 9
SCLQuarantineEnabled                  : False
BypassedSenders                       : {}
BypassedSenderDomains                 : {}
Enabled                               : False
ExternalMailEnabled                   : True
InternalMailEnabled                   : False
AdminDisplayName                      :
ExchangeVersion                       : 0.1 (8.0.535.0)
DistinguishedName                     : CN=ContentFilterConfig,CN=Message Hygiene,CN=Transport Settings,CN=Smith And
                                        Smith,CN=Microsoft
                                        Exchange,CN=Services,CN=Configuration,DC=XXXXXXXXXXX,DC=com
Identity                              : ContentFilterConfig
Guid                                  : 8f86e0b6-da37-42d3-b7cd-b9635b7db271
ObjectCategory                        : XXXXXXXXXXXXXXXXXXX/Configuration/Schema/ms-Exch-Message-Hygiene-Conten
                                        t-Filter-Config
ObjectClass                           : {top, msExchAgent, msExchMessageHygieneContentFilterConfig}
WhenChanged                           : 5/28/2014 12:15:21 PM
WhenCreated                           : 5/1/2014 4:17:55 PM
WhenChangedUTC                        : 5/28/2014 7:15:21 PM
WhenCreatedUTC                        : 5/1/2014 11:17:55 PM
OrganizationId                        :
OriginatingServer                     : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
IsValid                               : True
ObjectState                           : Unchanged
This is what it is set at now. Completely disabled. It worked fine for quite some time filtering out spam pretty nicely then one day everyone's mail was being rejected as spam by the content filtering agent. I know of someone else who also had this
issue except their box was running 2008R2 with EX2007. They too disabled the content filter as it was giving them too many problems with mail being rejected.
fr0stsp1re

TS3899 In ios7 how do you limit the number of emails downloaded from your ISP server? Previous version allowed you to limit it to 50, 100, etc.

In ios7 how do you limit the number of emails downloaded from the ISP server? Previous version allowed you limit the download to the last 50, 100, etc.

Hi,
Unfortunately, this is a feature that Apple have taken away.
The best way to let them know you want it back is via http://www.apple.com/feedback/
Regards

Best way for Email Notifications in EWS Managed API 2.0 [ Exchange Server 2013]

Hi ,
I want to know best way for Email Notifications in Exchange server. My
organisation has
10 users, i want to get notification if any user mailbox got any new mail.
i need to create API,
that was consumed by another Team in their Application.
I am using Exchange server 2013.
Please share Your Ideas.
Thank you

Take a look at EWS Notifications
http://msdn.microsoft.com/en-us/library/office/dn458791(v=exchg.150).aspx .
Cheers
Glen

Migration from Exchange server 2010 to Exchange server 2013

Hi All,
We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

Run these commands and post the update.
Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2013 email rejections from free ISP accoounts

Similar Messages

Maybe you are looking for