Situation: Domain:A and Domain:B

Server 1: Win2012 + Exchange2013 + Domain A

Server 2: Win2012R2 + Domain B

user victor@domainA has mailbox now the same uservictor@domainB wonts to use in one logon the both.

so he wants to choise from wich account he sends email.

I tried to make a linked mailbox but I got this error: The value "victor@prinfotech.com" of property "UserPrincipalName" is used by another recipient object "". Please specify a unique value.

What went wrong.

Hello,

A users is complaining she doesn't receive a certain e-mails. I check the usual stuff, anti-spam, see if her Outlook is connected etc.

Everything checks out, when I check message tracking I see the mail is delivered to Exchange but Exchange can't put it in her mailbox and reports the following: Message delivery is taking longer than expected. There may be system delays. For more information, contact your helpdesk.

After reading several threads I get something about diskspace but this machine (and the location of the queue and databases) has 50GB+ free space and reside on the same machine. I have also installed the update rollup 10 for Exchange 2013 with a few reboots but this doesn't seem to help.

This only seems to happen to specific messages. No strange eventlog messages are generated.

Exchange 2013 with the latest updates + Rollup 10
Server 2012 Std. 64-bit

Dear All,

We are running exchange 2010 and 2013 in coexistence the owa url is different for both the servers,we are using a third part ssl certificate on our exchange 2010 ,the certificate is about to expire,recently we have bought wildcard certificate for our domain my question is can i replace the existing ssl certificate with the wildcard certificate ? instead of renewing the old ssl certificate.

and also i have one more query till now i have been using my default certificate for my exchange 2013 servers ,can i use a third party ssl certificate for my exchange 2013 and use the same for exchange 2010 also,i want to know if i replace the existing certificate with 3rd party ssl what will be the impact for users connecting to the 2013 server etc?and is there any other chnages i have to do?

Regards

Tom.

TechGUy,System Administrator.

Hi,

 i have a exchange 2013 environment giving me this problem. I did not install this env. This environment was earlyer a DAG with

 two exchange servers both servers having all roles installed. Now I have removed the DAG and there i only one exchange server 

 with all roles. This problem started after I removed the DAG. I have increased the memory so I do not think this is because of

 lack of resources. The system will recover after ca 30 min. Restarting the transport service. There is nothing in eventlogs.

 So what is the best thing I can do regarding this. I have seen someone mention to delete receive connector and recreate them

 again not using the HubTransport but use FrontendTransport insted??

 His is how this looks,

PS] C:\Windows\system32>Get-ReceiveConnector

Identity                                Bindings

--------                                --------

EXCH03\Default EXCH03                           {0.0.0.0:2525, [::]:2525}

EXCH03\Client Proxy EXCH03              {[::]:465, 0.0.0.0:465}

EXCH03\Default Frontend EXCH03          {[::]:25, 0.0.0.0:25}

EXCH03\Outbound Proxy Frontend EXCH03   {[::]:717, 0.0.0.0:717}

EXCH03\Client Frontend EXCH03           {[::]:587, 0.0.0.0:587}

EXCH03\AnonSMTPRelay                      {0.0.0.0:25}

EXCH03\Comendo reinjection             {0.0.0.0:25}

EXCH03\RR-SCWEB01 Relay                 {0.0.0.0:25}

EXCH03\ScanReley                                  {0.0.0.0:25}

C:\Windows\system32>netstat -aon | find ":25 "

  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       6840

  TCP    10.141.1.32:25         192.168.250.251:54771  TIME_WAIT       0

  TCP    [::]:25                [::]:0                 LISTENING       6840

 pls adv

Erro

Hi Guys

We're using Exchange 2013 and we're having a problem where we're completely unable to send any mails to 1 specific domain. We get bounce backs saying unable to deliver but will keep trying, and eventually get:

Received: from REMOVED by REMOVED

(10.0.0.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Dec 2015

14:33:14 +0000

Received: from REMOVED ([::1]) by REMOVED ([::1])

with mapi id 15.00.1104.000; Wed, 9 Dec 2015 14:33:14 +0000

From: Sender

To: Recipient

Subject: RE: Blocking

Thread-Topic: Blocking

Thread-Index: AdEyjlFXWf+hfTFkR16j7SdFhr2+0AAADMhQ

Date: Wed, 9 Dec 2015 14:33:13 +0000

Message-ID: REMOVED

References: REMOVED

In-Reply-To: REMOVED

Accept-Language: en-GB, en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-ms-exchange-transport-fromentityheader: Hosted

x-originating-ip: [10.0.1.113]

Content-Type: multipart/related;

        boundary=REMOVED

        type="multipart/alternative"

MIME-Version: 1.0
When checking Exchange Queue Viewer the message in the queue has the error

Last Error: 451 4.7.0 Recipient rejected (R20)

I've removed any identify data from the above.

Have been in touch with the IT guys of the company we're trying to contact and they assure us that they can't see any issues on their side. We don't have any issues sending mail to any other domains.

Do you have any ideas on what may be causing this issue, let me know what other info you need and i will try to provide it.

Thanks

old286

I've been dancing around this subject a bit, usually taking the path of least resistance.  I would, however, like to know the correct answer.

I've had to make special receive connectors to enable various applications, like SharePoint for example, to have the ability to relay mail off of my 2013 MB/HUB server to my organization, usually by creating an open receive connector with no authentication, then using the ip scope for security.

I now have to do something similar but different.  I have an internal application (backup product) that needs to send notifications through Exchange to an outside domain.  I'm wondering if there is a more precise way to configure this? The reason this comes up is that this application can already send internally to my corporate domain, but gets denied when sending externally.  Obviously it's able to do this via one of my connectors.  I feel like I'm missing something.

Thanks, 

How can we solve this?

mx.google.com

Remote Server returned '550-5.7.1 [2605:e000:5b0c:b600:217b:9d84:ff0f:e17a] Our
system has detected that 550-5.7.1 this message does not meet IPv6 sending
guidelines regarding PTR 550-5.7.1 records and authentication. Please review
550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_error
for more 550 5.7.1 information. t10si67058629pfa.174 - gsmtp'

bostjanc

Hello!

I have a problem with the exchange server because when I want to send an e-mail that has this combination ".@" it gives the following error: "one or more recipients are invalid" and that is NOT true. There is any possibility to solve the regular expresion that verify the format of an e-mail address?

Gmails users are allow to choose that combination for an e-mail address and is impossible send an e-mail throw an exchange server.

Thanks in advance.

Hey guys,

Exchange 2010 latest SP3 with RU 10.

Been getting a lot of these, I installed wireshark and changed it's filter to ssl, once I was able to determine that alert 70 meant protocol version not supported.

I managed to link it to my boses phone Note 4, running android 5.01...

26518 2015-08-20 13:44:10.758922000 172.#.#.# 172.16.20.38 TLSv1 73 Alert (Level: Fatal, Description: Protocol Version)

Thing is at first he was having issues with ActiveSync internally but not externally (Split DNS for our activesync.

I went into his settings and unchecked "use SSL" -> Auth Failed (AS it should as SSL is required) -> "Use SSL" -> internal ActiveSync started to work, at which point I had hoped the events would stop.. I did this just before lunch today...

As you can tell by the timestamp they are still occurring... does anyone know what I could possible check to help resolve the issue?

I checked the packets from other ip addresses and they all seem to be using the same protocol version of TLS 1.0.

Any thoughts welcome, and thanks!

We are having sporadic issues with internal email delayed delivery.

This is the topology:

Single Exchange 2013 (Version 15.0 ‎Build 995.29) running on Windows 2012R2

‎Here is a message tracking log example of the problem:

**This is the STOREDRIVER RECEIVE**

RunspaceId              : ef020c77-b0f5-470d-85c4-1de5df3a78ed
Timestamp               : 1/4/2016 8:21:26 AM
ClientIp                : fe80::d974:571a:8e74:dca6
ClientHostname          : RXMAIL.rxbenefits.local
ServerIp                : fe80::d974:571a:8e74:dca6%12
ServerHostname          : RXMAIL
SourceContext           : 08D2F4D6F76C2B95
ConnectorId             : 
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 0
MessageId               : <e02a50e8518649eb8a36316731d1be38@RXMAIL.rxbenefits.local>
Recipients              : {kmcdanal@rxbenefits.com, lisa@rxbenefits.com}
RecipientStatus         : {To, To}
TotalBytes              : 49512
RecipientCount          : 2
RelatedRecipientAddress : 
Reference               : 
MessageSubject          : RE: BCBS/Rx Benefits and ID's
Sender                  : tressa@rxbenefits.com
ReturnPath              : Rx4AMs@rxbenefits.com
Directionality          : Originating
TenantId                : 
OriginalClientIp        : 192.168.50.67
MessageInfo             : 04I: 
MessageLatency          : 
MessageLatencyType      : None
EventData               : {[MailboxDatabaseGuid, a20269a8-f110-4887-8434-00acd1e6d988], [ItemEntryId, 00-00-00-00-2A-A8
                          -DB-69-13-CB-F1-43-B6-E2-D8-10-29-07-FE-F0-07-00-53-06-B1-2C-1B-01-E1-4A-A5-EF-E2-41-F7-39-5B
                          -58-00-00-00-80-0F-88-00-00-F2-46-95-A2-41-7B-FC-4D-A4-74-3B-03-B3-87-BF-A2-00-01-00-DD-3F-A7
                          -00-00], [DeliveryPriority, Normal], [PurportedSender, Rx4AMs@rxbenefits.com]}

**This is when it finally got submitted 35 minutes later**

RunspaceId              : ef020c77-b0f5-470d-85c4-1de5df3a78ed
Timestamp               : 1/4/2016 8:56:34 AM
ClientIp                : fe80::d974:571a:8e74:dca6%12
ClientHostname          : RXMAIL
ServerIp                : 
ServerHostname          : RXMAIL.rxbenefits.local
SourceContext           : MDB:a20269a8-f110-4887-8434-00acd1e6d988, Mailbox:cc57c1d6-6755-442a-921d-82cccd31498a, 
                          Event:197459615, MessageClass:IPM.Note, CreationTime:2016-01-04T14:21:25.534Z, 
                          ClientType:MOMT
ConnectorId             : 
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       : 
MessageId               : <e02a50e8518649eb8a36316731d1be38@RXMAIL.rxbenefits.local>
Recipients              : {kmcdanal@rxbenefits.com, lisa@rxbenefits.com}
RecipientStatus         : {}
TotalBytes              : 
RecipientCount          : 2
RelatedRecipientAddress : 
Reference               : 
MessageSubject          : RE: BCBS/Rx Benefits and ID's
Sender                  : tressa@rxbenefits.com
ReturnPath              : 
Directionality          : Originating
TenantId                : 
OriginalClientIp        : 192.168.50.67
MessageInfo             : 2016-01-04T14:21:25.534Z;LSRV=RXMAIL.rxbenefits.local:TOTAL=2109.081|SA=2088.066|MTSSDC=0.047
                          |MTSSDMO=20.311|MTSSDPL=0.015|MTSSDSS=0.312|MTSSDS=0.656|MTSS=21.024
MessageLatency          : 00:35:09.0810000
MessageLatencyType      : LocalServer
EventData               : {[ItemEntryId, 00-00-00-00-2A-A8-DB-69-13-CB-F1-43-B6-E2-D8-10-29-07-FE-F0-07-00-53-06-B1-2C-
                          1B-01-E1-4A-A5-EF-E2-41-F7-39-5B-58-00-00-00-80-0F-88-00-00-F2-46-95-A2-41-7B-FC-4D-A4-74-3B-
                          03-B3-87-BF-A2-00-01-00-DD-3F-A7-00-00], [PurportedSender, Rx4AMs@rxbenefits.com]}

Note the MessageInfo SA value is 2088 seconds. I cannot find a reference to what this value refers to.

If I export the logs to HTML the logs indicate the following:

Hey there,

We have our Exchange environment configured to deliver all mail through a send connector that authenticates with our ISP's reputable mail server for mail delivery, in order to avoid having to deal with trust and blacklisting ourselves directly.  We discovered the other day, that while we have an agreement with them to not cap our daily message sending (where their average user is), we are still subject to a 200 message/30min limit, after which subsequent message are rejected/bounced with the below error:

Remote Server returned '550 User has exceeded outgoing limit G_SPAM_USER_MAX or send_limit(200)

and if our server continues to try to send mail, we eventually start getting:

451 4.4.0 SMTPSEND.SuspicousRemoteServerError; remote server disconnected abruptly; retry will be delayed

I started looking at send connector configuration options, as well as Message throttlinghttps://technet.microsoft.com/en-us/library/bb232205(v=exchg.150).aspx

but I'm not sure the best way (if there is any) to accommodate for this.  I was hoping for configuration options that would allow me to setup the existing send connector to work around this limitation by queuing, either before the limit is reached, or after by reacting differently to the 550 send limit response, but so far I'm not seeing anything like that.

I get the feeling from the Message Throttling article that I should be looking at this more from a per-user standpoint, and throttling message sending for each user, which would likely resolve the issue as the limit is only an issue of someone tries to send an excessive mass email, but I'm not sure.

Can anybody give me a swift kick in the right direction on this?  Or maybe a couple different directions if there are options on how to address this? Thanks!

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.

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

hi all , 

recently we have added new Exchange Server Node ( one CAS/HUB and one Mail box ) to our environment exchange 2013 .

we trying to send email to outside some emails are going and other are failed to deliver with below NDR : 

Remote Server at [172.20.1.24] (172.20.1.24) returned '400 4.4.7 Message delayed' 1/10/2016 2:37:42 PM - Remote Server at [172.20.1.24] (172.20.1.24) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." 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 172.20.1.24:25'

when shutdown the new add mailbox server all are working fine any idea ? 

Hi, We are migrating some users from one forest/Exchange org to another. In the old forest they use S/MIME digital IDs (issued by an internal Enterprise root CA)  for signing and encrypting email. In the new forest they will not need to sign and encrypt any new emails but they will need to be able to read encrypted emails migrated over from the old infrastructure.

I have played around with exporting a recipient's S/MIME certificate (inlcuding private key) from the certificate store of their old PC into the certificate store of their new PC and they are able to read migrated encrypted emails fine.

However, presumably when the certificate reaches its expiry date it will not be able to renew because the old CA will be unreachable. Will this cause the encrypted mail to be unreadable or will the recipient just get a warning message ?

We do already have an existing Enterprise root CA in the target forest so I wonder is there a way to export/import the relevant S/MIME digital IDs over to that somehow ?

Thanks for any help on this...

Edit: I just set the clock forward, on the test user's PC, past the cert expiry date and am still able to read the encrypted emails (since the expired cert is still in the cert store of the PC). So I think this is a workable solution. ( I suppose if we did ever need S/MIME encryption on new emails, post-migration, then we just get users to enroll a new cert off the new CA...)

Hi there.

A user marked a folder properties that it should delete items older then 7 days, but those items still stays in that folder.

Any suggestion why this not working?

bostjanc

Using Exchange 2013 CU11 on Windows Server 2008 R2.  Upgraded from CU9 and issues didn't seem to happen then -- this is a testing environment before I deploy the server.

Outlook 2010 connects fine, can compose email and send but it never goes anywhere, doesn't show up in the Exchange Toolbox Queue.  If I use OWA the mail stays in the Drafts folder when I click Send.  When I try to send again it says "you do not have permission to perform this action"  Finally, if I compose something in Outlook 2010 or OWA it will hit the Drafts folder if I "save" it so I know they are communicating correctly.

I have searched for the issue on the Internet and tried all DNS, host file, Exchange fixes I can find but still no luck.  My MX record is correct and the Receive Connectors are all default.  This server is not internet connected at the moment and I am just trying to route mail internally from a few mailboxes I have created.  AD, DNS are on the same machine as we only have one server at the moment.  I was fine with CU9 but then did Windows Updates and CU11 update and this happened.  Also, we use POP3 and I tried via that method and it won't accept any authentication so there are definitely a few things going on.