I currently have two 2013 exchange servers at our primary site in a DAG group.
DAG group replicaiton traffic is on its on subnet, traffic separate from MAPI network.
wanting to add 3rd exchange to the dag group at a remote site, connected via IPSEC VPN tunnel.
I have read that the DAG group cannot have a gateway, but my firewall people tell me they cannot route traffic to the remote site without a gateway.
so obviously I am misunderstanding something, can someone straighten me out here?
Hello,
I have recently ran into a problem with my Exchange 2010 server. I can not receive emails from certain domains. There is only 2 domain names in particular (only one user from each domain has tried sending emails to our domain).
thanks in advance
Hello,
i did test for smtp i found the below warning :
Is it necessary tocreate aPTR record,if so where you should create it
in DNS the publicorattheISP
Please advise
thanks in advance
My problem is with mail flow. If I go into the Exchange 2013 toolbox and open the queue viewer I can see over a hundred messages stacking up. What do I do to stop these errors?
In the Queues tab under Last Error I see the following error; majority of these errors in the "From Address" is<>
"[{LRT=(date\time);{LED=44
Win2012/Ex2013 sp1
PennyM
Hi All,
I am trying to share an SMTP address with 3 exchange organization. Is this possible with the use of Send Connectors ?
For Example :
Forest A is the main forest, Forest B and C will have to use the SMTP address of forest A, which will become their Primary address, and they will retain their SMTP address for Forest A and Forest B respectively.
When we setup the send connectors between Forest A and Forest B, the mail flow is working fine with users in Forest B receiving emails using Forest A smtp address.
When creating the send connector for Forest C, emails sent to this forest are being stuck in queue with Error "An local loop was detected".
Any ideas how to make this work ?
Kind Regards,
I am trying to remove a self-signed certificate so we can be certain we are only using the one we got from a trusted 3rd-party CA. When I try to remove the self-signed one, I get this error below.
A special Rpc error occurs on server MAIL14: The internal transport certificate cannot be removed because that would
cause the Microsoft Exchange Transport service to stop. To replace the internal transport certificate, create a new
certificate. The new certificate will automatically become the internal transport certificate. You can then remove the
existing certificate.
But if I create a new self-signed certificate, just to remove the old one, then I am not getting anywhere - is there any way to change the "internal transport certificate" to use the one we got from the 3rd-party CA? I already have the new certificate installed and I would rather not try to go through the process of generating a new cert request and all that. But if that is the only way to fix these issues, then I suppose that is what I must do.
Many thanks,
Sam
We have a customer with about 4000 Exchange 2013 Mailboxes onprem. He also posess an Office365 E1 Plan with Exchange Online Plan 1 included.
The customer whishes not to have an Exchange Hybrid Configuration, instead he will stay onprem but using Exchange Online Protection as an mailgateway with antimalware / antispam function.
Can we use Exchange Online Protection with this license, poiniting our mx Record to Exchange Online Protection, which send us the verified mail to our onprem Exchange 2013 Servers?
Can we also send the outgoing mail traffice to Exchange Online first for verification?
Do we have all the function of EOP with the Office365 E1 Plan?
Do we need first to establish dirsync for replication the user to Office365?
Best Regards - Bueschu
Bueschu
Good afternoon, all!
I'm having some inconsistencies in sending mail to a list on an internal SharePoint 2013 server. It seems that the mail flows from my Mailbox/CAS servers out to the Edge Transport servers, then the mail hangs there. However, I have had one internal mail to this SharePoint list work. I don't know precisely how the mail was received by the SharePoint server, but my theory is that the mail went over the LAN to the MB/CAS server at the datacenter where SharePoint lives, and was successfully delivered.
My question is about short-circuiting this by applying a new send connector. This would be configured as a Custom connector with a mail domain of sharepoint.contoso.com and point directly to the IP address of the SharePoint server. The object of the game is to have any mail going to this SharePoint server sent directly to the IP address of that server.
Yes? or is there a better/easier/more reliable way to handle this? Or am I barking up the entirely wrong tree?
Thanks to all for looking!
Gregg
Hello,
i did test for domain i found 2 warning in DNS as below:
1-Bad Glue Detected
2-SOA Expire Value out of recommended range
Do I need to solve this problem or leave it as it is. please advise me
thanks.
Hi Team,
We have one particular DL not receiving email from external addresses.Internal emails are getting delivered.
we are getting this error when checked from Connectivity analyser.
_______________________________________
Attempting to send a test email message to informatica@xyz.test using MX mx record name.______________________________
we are getting this error when checked fromGmail.
________________________________
The error that the other server returned was:
550 5.2.0 mailbox unavailable.
_____________________________
we have checked all settings for this DL, external delivery is also enabled.
Please assist.
Thanks
Abhishek Saxena
Hello,
Looking for clarification on Message Rate Limits.
If I have a Message Rate Limit of 50 on a Receive Connector.Hello,
I need to delay exchange 2013 messages that can't find the user. We are a 2013/10 hybrid with 365. It takes time for our identity management system to create an AD account and then DirSync it to 365 and then create the mailbox. But we want messages to those 'almost valid' email addresses to be queued during the time the mailbox is being provisioned.
Is there any way to do this?
Thanks,
Peter
Hi All
I have an EDGE Servers on E2013 CU10
BypassedSenderDomain contains ~450 records for now
When i trying to add BypassedSenderDomain i get an Error:
Set-ContentFilterConfig : The administrative limit for this request was exceeded.
At line:1 char:1
+ Set-ContentFilterConfig -BypassedSenderDomains @{add='domain.com'}
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-ContentFilterConfig], AdminLimitExceededException
+ FullyQualifiedErrorId : [Server=server,RequestId=8511a38c-ea36-4eb4-adfc-15c73e4d0c45,TimeStamp=12/29/2015 12:30:10 PM] [FailureCategory=Cmdlet
-AdminLimitExceededException] 5260967B,Microsoft.Exchange.Management.SystemConfigurationTasks.SetContentFilterConfig
Best Wishes, Andrew Golubenkoff
Hi -
We have an Exchange 2010 Organization called ABC
ABC.COM is our internal domain
our external domain is XYZEXTERNAL.COM
We have 2 cas/hub and 2 mailbox servers.
We have one linux SMTP Server running on a VM.
I need to forward email for the user: daemon@xyzexternal.com to the mail server running on the servervm.ABC.com
How can I Set this up?
Thank you!
Hi guys.
In EX2010-EDGE we had default RECIEVE connector which worked fine after we had added AnonymousUsers.
Now in EX2013-EDGE default RECIEVE connector is not working ok after we had added AnonymousUsers permission.
Are there any differences in default recieve connectors on EDGE2010 and EDGE2013?
We recieve error unable to relay 550 5.7.1).
Do you need to create "another" recieve connector on EDGE2013, and you didn't need to do this step on EDGE2010?
With best regards
bostjanc
How do you deny neutral SPF status on exchange edge 2013?
We already did "Set-SenderIDConfig -SpoofedDomainAction Reject"
How do you deny neutral SPF status?
bostjanc
Hi guys.
What are the best practices for tweaking mail filter on Exchange 2013 EDGE?
In past we used Exchange 2010 EDGE with forefront, now we are upgradin it to EDGE2013.
We ran command:
Add-IPBlockListProvider-Name zen.spamhaus.org -LookupDomainzen.spamhaus.org -AnyMatch$true-Enabled$true
Do you recommend anything else to tweak on EXCHANGE EDGE2013?
FYI: We Will not use EOP, so we would like to get the most of the edge as spam filter as possible.
bostjanc
Question:
User A replies to an Email from User B.
User A gets the email rejected and the error message
"You can't send a message on behalf of this user unless you have permission to do so."
The FORM field has been changed to User B and thus rejected.
I have examined the transaction logs and all appears that user A is trying to send an email on an account that he does not have sufficient rights. Next I check the message itself and sure enough the sender is User. Exchange appears to be behaving normally.
Users both are using Outlook 2010.
What could cause Outlook to change the field? Could it be an issue with the X400LegacyExchangeDN settings for the users?
Cache has been cleared and problem is intermittent. Not all emails replied to from A to B are rejected. Most go through. User doesn't have issue with other users.
Turning off cache resolves issue.
we are using exchange server 2013 and our exchange server receive and send email properly on local network, and receiving incoming emails from outside network but Outgoing e-mails stuck in queue with error {LED=441 4.4.1 error encountered while communicating with primary target IP Address:"421 4.4.2 connection dropped due to SocketError." attempted failover to alternate host, but that did not succeed. Either there are no alternate host.
Also created new send connector and did telnet to port 25 and uninstall Antivirus as well.
Hi guys.
We are dealing with RBL not working.
We have zen.spamhaus.org as one of the RBL's (priority 1).
This IP is reported as spam/blacklisted
http://mxtoolbox.com/SuperToolX.aspx?action=blacklist%3a38.68.18.194&run=toolpage
Is this result ok or not?
we also take a look that we don't have any DNS issues. We had exactly the same behavior as on this post "https://social.technet.microsoft.com/Forums/office/en-US/1252eb3d-949c-4cc3-a1d7-dc08f0bdd372/rbl-not-working-on-exchange-2013-edge-transport" but we have resolved this by changing forwarders on DNS and now it resolves just fine.
After that we have restarted transport service on Exchange 2013 EDGE.
Edge is on CU11.
Any other hints to check why RBL is not working ok?
With best regards
bostjanc