Quantcast
Viewing all 2249 articles
Browse latest View live

Route mails based on internal sender domain.

Hi All,

I have Hosted Exchange 2013 (1CAS and 1MBS) with the following domains. I already have an SMTP Send connector to route all mails (*) to a smart host.

DomainA.com

DomainB.com

DomainC.com

Now my requirement is - : I need to create an internet SMTP connector to route only mails from DomainC.com to use MX. How can it be configured or please let me know any other alternatives/best way.

Basically DomainC.com is for bulk emails, i need to outbound them through different IP.

Regards,

Vinod


Delivery has failed to these recipients or groups

Diagnostic information for administrators:<o:p></o:p>

Generating
server:
<o:p></o:p>

/o=corporation/ou=Exchange
Administrative Group
(FYDIBOHF23SPDLT)/cn=Recipients/cn=76dbb84d1f8748caa84b73cc13e0e943-aabb

Remote Server returned ''
<o:p></o:p>

/o=corporation/ou=Exchange
Administrative Group
(FYDIBOHF23SPDLT)/cn=Recipients/cn=4aa0338a0b7f46f9bd305613c3156b3d-ccdd

Remote Server returned ''
<o:p></o:p>

/o=corporation/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=cf9231f30d6743989c83162fad675411-eeff

Remote Server returned ''
<o:p></o:p>

This error came internally when sending an email to three internal addresses. - We don't have any issues sending email to these users, and this is actually their legacyexchangedn. This is a resource domain - so these are linked mailboxes.

Any idea ? no errors on the exchange servers, or IIS logs.

Exchange 2013 cu3

Exchange Server 2013: Not Receiving Internet email

Hello Guys, I have a new Exchange 2013 install and i am having problems receiving internet email. When testing from https://www.testexchangeconnectivity.com it fails at the last step when it tries to send a test email. I get the following response:

The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Exception details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()

Any Suggestions??

two send connector smart host and MX delivery

Dear All user,

I would also like the exchange server to send outbound email via these two servers (smarthosts) that are using out advanced filter to send out via the smarthosts and tenants who are not paying for filter to just send direct from the exchange server which is MX record delivery.

Any body idea how to configure this. I know i have to configure multiple connector but how it will distinguish it from selecting either by smart host or via MX record delivery.

mail.protection.outlook.com Delisting

We moved to another location and got a new ip from ISP and our exchange server is not able to send emails to some recipients getting .mail.protection.outlook.com error.

user@domain.com
BN1AFFO11FD036.mail.protection.outlook.com #550 5.7.1 Service unavailable; Client host [72.76.xxx.xx] blocked using Blocklist 1; To request removal from this list please forward this message todelist@messaging.microsoft.com ##

This is the error I am getting and I did email to delist@messaging.microsoft.com and I am wondering when will my IP get unblocked as this is causing a lot of communication issues. I checked my ip for blacklist but its not in any database. Hope I'll be able to find some solution soon on this.


 

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

Image may be NSFW.
Clik here to view.

We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:

Image may be NSFW.
Clik here to view.

PEC mail with attach .eml in empty

Hi, I receive in my Exchange PEC mail (italy electronic certified mail) this mail include in attach the original mail and is .eml. When I receive this mail, the attach is 35 byte and not the real size and is empty.

I full patch my Exchange 2010 sp3, I reboot the server and for 6 hours all work perfectly. Then If I receive another pec, the problem come back. I reboot and for 6 hours I work perfectly.

In addition: the mail already downloaded in my account or any account if it's downloaded when the problem is present are not visible after the restart of my Exchange. And he remain lost. Only the new mail are working after reboot.

I try to disable all tranfert agent but the problem persist. Can you help me? Thank's


Alessandro Romualdi

Disable automatic forwarding

Hi

We need to disable automatic forwarding for external emails because of security reasons.
That means forwarding to external addresses configured with an Outlook rule should not possible.

Is there a way to configure that?

Regards
Peter


where to configure forced TLS

Hello all

Currently all of our mailboxes are located in O365. Our MX records point to EOP, and we have Centralized mail transport enabled. This means that all emails sent from mailboxes in O365 are routed from EOP to On-prem, and then from on-prem to the intended recipient. The email flow is below. From my understanding when a transport rule exist in EOP that has a address space of * (all domains) that this transport rule will take precedence over all other transport rules.  Example is if i create a transport rule that uses MX record lookup to send emails to Yahoo.com, and i also have a transport rule that has an address space of * and uses a smarthost, the email sent to Yahoo.com will be sent using the connector that has an address space of *.  Also as i said earlier all mailboxes are hosted in O365, if i need to send forced TLS to a certain domain, and because we have Centralized mail transport enabled then where should i configure the forced TLS? it doesn't make sense to try and configure this in EOP because all emails go through on-prem first. If you look at my below routing hops the last hop the email takes before it leaves the environment is the Symantec SMG servers. I think this is where i would need to configure foreced TLS to external domains. 

user in O365 sends email to @gmail.com

EOP----->on-prem Hybrid Server------->Symantec SMG server------->@Gmail.com


Bulls on Parade

Exchange Server 2010 Mailflow between Internet Facing-Site and No Internet Facing-Site

Hi all,

My environment there are two sites, Internet Facing-Site and No Internet Facing-Site.

The mail flow between them, it isn't working. The messages stuck in the queue.

Default Receive Connector No internet facing-site is configured, bellow:

Defaul....

- Transport layer....

-Basic Authentication...

- Exchange Server Authentication.

- Integrated windows....


Configuration the Internet Facing-Site, bellow:

From intenet

- Transport layer....

-Basic Authentication...

- Integrated windows....


And i configured a new receive connector on the Internet Facing-Site, follow bellow:

Sites

- Transport layer....

-Basic Authentication...

- Exchange Server Authentication.

- Integrated windows....

But, the messages yet stay stuck in the queue.

Queue error:

451 4.4.0 Primary target IP address responded with: “421 4.2.1 Unable to connect.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

I'm needing help, pls.

Problems with mail flow to/from new Exchange 2007 SP3 server

Hi, I am having problmes getting a new Exchange 2007 SP3 box talking to the other servers in our company (I know, we are very behind but the company does not let me spend much on new kit...)

Our existing Exchange set-up consists of two Exchange 2003 server (London & Oxford) and two Exchange 2007 RTM servers (Manchester and Dubai). Mail is flowing fine between these servers and they have been up and running for some years now. All Internet mail comes in to the London server and is passed out to the other servers using defined Send connectors on the London server.

I have a new server in London installed with Windows 2008R2, on to which I have installed Exchange 2007 SP3 as the RTM version would not install. It is recognised in the Active Directory and there is obviously come communication between it and the other servers as I can create a new user on the London 2003 server and it appears on the London 2007 server.

However, I have two major issues:

1. The London server cannot connect to either of the other 2007 servers - it shows a "454 4.7.0 Temporary authentication failure" against both queues when I try and send from a test user on the new London box. I can successfully send external mail so it is not a network connectivity issue.

I have searched on Google and checked the following:

I can successfully ping all other servers by name regardless of which site they are on.

The time on the servers is within a minute of each other - allowing for the time zone difference in Dubai.

The Default receive connector on each 2007 server has the correct FQDN and the authorisation levels are set as per several answers (all except the bottom one) and the Permissions Groups are set to all except the bottom one.

I can connect to the other 2007 servers using the Management Console and make changes which I can very are being made on the remote machines.

I have dug around as much as I can and cannot see any other issues which might be causing this problem so I am at a bit of a loss. Can anyone suggest any other areas to look at so I can get this problem resolved?

2. The Dubai server was the first Exchange 2007 server in the company and so it tends to be the default for a lot of 2007 settings. If I send a message to a Manchester user it connects to Manchester, if I send a messages to a Dubai user it connects to Dubai but if I send a message to a London or Oxford user it routes it via Dubai.

Is there anyway to create the equivalent of a Send connector to tell it to route mail to London users to the old London server as that is on the same network and I will need to move a lot of mailboxes and folders around and so I want to try and avoid any London<->London replication traffic being sent via Dubai.

On the old London server I can see the Routing Groups in the 2007 Exchange Administrative Group but I cannot change them or add new connectors - it says I need version 8.0.30535.0 or greater of System Manager.

Many thanks in advance for any advice or assistance.

Regards, Eddie


Reroute all mail from specific receive connector

This is for Exchange 2010. 

We have a test web server that we need to test outgoing email on.  Obviously since this is a test server we want to limit where emails can go just in case something accidentally gets sent out wrong. 

I have setup a receive connector on exchange to relay the messages but I need to filter where it can go.  We have other receive connectors setup for live data.  Is there a way to limit a specific receive connector to certain email addresses?  Or a way to forward all mail that comes in on a specific receive connector to a distribution list of emails? 

Thanks

Mails go Deleted Items Folder

Hello,

I have 750 users on Exchange 2013 sp1. One of my user has a problem. Sometimes his incoming/sent mails go directly deleted items folder. outlook and owa are same ,problem exist both of them. I deleted all rules on outlook/owa but issue continue.

Outlook version is 2010 with sp

How can we solve this issue,plase help?

Thanks.


Murat ER Microsoft Certified Systems Administrator

Any else having problems with the Edge Transport Servers?

I have two Edge Servers both running EXCH2013 CU5 as well as the Mailbox Server. All running on Windows 2012 R2. Everything is fine with the mail flow until at some point it isn't and there are no errors in the logs. From the edge transport itself I can see all services are running. I can see port 25 is listening on 0.0.0.0 and I can even telnet port 25 but from the outside it's as if it's dead to the world. I even turned off the firewall to see if it was a firewall issue but that's not the case.

If I reboot the server everything could be fine for a few hours or a few days but eventually it just stops receiving. The other edge server picks up everything just fine but eventually it would do the same thing if I wasn't being alerted by a service monitoring my smtp port and let me know that it isn't working so I know at that point I need to reboot the server.

Did anyone else have this issue and fix it?

IP-BlockListProvider not working in Exchange 2013...

Ok so i've in this article(http://social.technet.microsoft.com/Forums/office/en-US/655d9baf-97f5-4a9d-aa89-b922aacfe02f/how-to-configure-an-ip-block-list-provider-like-zenspamhausorg-in-exchange-2013-rtm?forum=exchangesvrsecuremessaging) that there is a problem with Block List Providers not working with Exchange 2013. 

Is there any update on this subject? We are being spammed and our block list providers are not working...

Any help?


Exchange 2013 Address Book Policy Routing Agent Issue with Mailboxes Hidden From the Address Lists

When the AddressBookPolicyRoutingEnabled attribute is enabled by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $True, I am having an issue with delivery failures for mailboxes that are hidden from the address book. I receive the following undeliverable message:

'532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

If I disable the AddressBookPolicyRoutingEnabled attribute by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $False then emails are successfully delivered to the mailbox that is hidden from the address list.

I followed the installation instructions here: http://technet.microsoft.com/en-us/library/jj907308(v=exchg.150).aspx

Below is the status of the ABP Routing Agent on my Hub Transport/Mailbox server:

Enabled: True
Priority: 5
TransportAgentFactory: Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.AddressBookPolicyRoutingAgentFactory
AssemblyPath: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\AddressBookPolicyRoutingAgent\Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.dll
Identity: ABP Routing Agent
IsValid: True
ObjectState: New

Has anyone else run into this issue yet?

Mails stuck in queue when Automatic Replies are enabled

We have a new Exchange 2013 server and moved a few pilot users from the 2010 environment to it.

Everything seems to work OK but we just encountered a strange issue. One of the users turned on his automatic out of office replies and when people send E-mail to his mailbox they receive a 'Delivery delayed' e-mail. All mails to this account seem to be stuck in the queue (shown in the Exchange Toolbox – Queue viewer) but they DO actually arrive in his Outlook.

The error message in the queue for his messages is: Recipients:  User@domain.com;3;3;[{LRT=};{LED=432 4.2.0 STOREDRV.Deliver; Agent transient failure during message resubmission[Agent: Mailbox Rules Agent]};{FQDN=};

 After turning off his out of office replies, the queue emptied instantly, and no duplicate mails arrived in his mailbox. After turning it back on the queue started filling up again with new mails.

Other pilot users have the same issue.

Has anybody seen this issue before? I checked space on the drives and there seems to be no issue there (so no back pressure issue).

thanks!


2007 - 2013 Mail Flow

Migrating from 2007 to 2013. The 2013 servers are separated (2 CAS, 2 MBX) because client wanted to just use WNLB. Therefore, the CAS servers have two NICs. I thought I had this set up correctly with WNLB, but mail is not flowing from 2013 to 2007. However, mail does flow from 2007 to 2013. These are the modifications I made to the Receive Connectors on 2013 CAS.

The Default Front-End had the original IP range removed and replaced with only the IP Addresses of the Internal Exchange servers (both 2007 & 2013). The Scoping was set to the primary LAN NIC and not the NIC used for WNLB.

A new FrontEndTransport Receive Connector was created with Anonymous to accept mail from the Spam Appliance and was set to use the NLB NIC (thinking that the Spam appliance would be set to send email to the NLB VIP).

Can't send out from 2013 to 2007. The email is stuck in the Outbound queue "SMTP Relay to Mailbox Delivery Group." The connectors on the mailbox servers were not touched.


MCITP Exchange 2010 | MCITP Lync Server 2010 | MCTS Windows 2008

451 4.7.0 Temporary server error. Please try again later. PRX2

I'm getting the dreaded "

451 4.7.0 Temporary server error. Please try again later. PRX2

" error when receiving SMTP mail.

does anyone know exactly what causes this error? there are many references to it on the web, but nobody seems to know exactly what causes it. maybe it's something to do with DNS?

can someone please ask someone on the exchange team to help document this?


Migrating from Exchange 2010 to 2013, cannot send outbound messages when I update Send Connector to use Exchange 2013?

Hello,

I have a Exchange 2010 and 2013 environment (migrating to 2013) and I've noticed all my internal clients that are on Exchange 2013 send through the Exchange 2013 server onto the 2010, then externally (according to the headers).

I went in and reviewed my Send Connector settings and sure enough my Exchange 2013 server was not part of the SMTP Connector's source server. I went in and added Exchange 2013 and took out 2010 so that all mail is sent through my new server but it does not work, the messages never leave the on premise and are stuck.

Examining the Queue Viewer, there is no error they just sit there.

Once I remove Exchange 2013 from the "Source Server" and leave my Exchange 2010 server in there, it works fine, but mail is going from Outlook Client > Exchange 2013 > Exchange 2010 > External Relay Server (Microsoft EOP / Office 365).

I want to take Exchange 2010 out of this flow to prepare to completely uninstall it after all dependencies for this server are dealt with.

What is the issue? Thank you !!

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Viewing all 2249 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>