Hi everyone,

Currently we have 5 exchange servers 2010 :

• 2 CAS Servers (Virtual)
• 2 MB and Hub Transport servers (Physical)
• 1 Edge server in DMZ. (Virtual)

Now I have added 2 more servers with MB and Hub Tranport Roles (VIRTUAL) and want to configure the mail flow from these new transport servers.

Can anyone help with the steps I should follow. Please note we have 1 existing Edge server in 2010 and email flow should be from Hub Transport to Edge server then from Edge to internet.

Existing environment is working fine without any issues. Main reason to do this is to virtualize the physical servers. Mailbox DB already migrated to new servers.

Thanks.

Manish Kumar MCSA, MCITP Enterprise Admin. MCTS Exchange server 2007, MCITP Virtualization Admin.

Hi,

  After a brand new installation of Exchange 2013 I have problem with multipart/mixed messages:

some emails that was correctly handled by the old 2007 Exchange are now "broken" and it seems to be a MIME wrong decode..

this is the header of a message received with the old Exchange server

Received: from was1-mh251.smtproutes.com (174.36.154.126) by
 SERVER-MAIL.iptechnology.it (192.168.50.6) with Microsoft SMTP Server id
 8.3.279.5; Thu, 6 Dec 2012 19:33:01 +0100
X-Katharion-ID: 1354818768.26441.was1-mh251 (12.0W)
Return-Path: <statistics@reporting.smtproutes.com>
Received: from was1-cp021.smtproutes.com ([10.21.46.88]) by
   was1-mh251.smtproutes.com [(10.20.102.93)] with ESMTP via TCP; 06 Dec
   2012 12:32:48 -0600
Received: from was1-cp021.smtproutes.com (was1-cp021.smtproutes.com
 [174.36.154.80]) by was1-cp021.smtproutes.com (Postfix) with ESMTP id
 318BBB955B for <coelli@iptechnology.it>; Thu,  6 Dec 2012 12:32:45 -0600
 (CST)
X-Katharion-ID: 1354818762.83562.was1-cp021 (12.0W)
Date: Thu, 6 Dec 2012 12:32:42 -0600
From: Digest Report <statistics@reporting.smtproutes.com>
To: coelli@iptechnology.it
Subject: Your Message Digest: coelli@iptechnology.it
Message-ID: <1354818762.hae83zru@1354818762.83562.was1-cp021>
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="_e00094c7-df45-4c8c-a227-cb431141090d_"

and that one is the broken email header received with Exchange 2013

Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
 EXCHANGE-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
 15.0.516.32 via Mailbox Transport; Mon, 17 Dec 2012 18:47:49 +0100
Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
 exchange-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
 15.0.516.32; Mon, 17 Dec 2012 18:47:48 +0100
Received: from was1-mh254.smtproutes.com (174.36.154.129) by
 EXCHANGE-01.iptech.local (192.168.50.4) with Microsoft SMTP Server id
 15.0.516.32 via Frontend Transport; Mon, 17 Dec 2012 18:47:47 +0100
X-Katharion-ID: 1355766453.92161.was1-mh254 (12.0W)
Return-Path: <statistics@reporting.smtproutes.com>
Received: from was1-cp021.smtproutes.com ([10.21.46.88]) by
   was1-mh254.smtproutes.com [(10.20.102.99)] with ESMTP via TCP; 17 Dec
   2012 11:47:33 -0600
Received: from was1-cp021.smtproutes.com (was1-cp021.smtproutes.com
 [174.36.154.80]) by was1-cp021.smtproutes.com (Postfix) with ESMTP id
 177FCB95A1 for <coelli@iptechnology.it>; Mon, 17 Dec 2012 11:47:33 -0600
 (CST)
X-Katharion-ID: 1355766451.94043.was1-cp021 (12.0W)
Date: Mon, 17 Dec 2012 11:47:31 -0600
From: Digest Report <statistics@reporting.smtproutes.com>
To: <coelli@iptechnology.it>
Subject: Your Message Digest: coelli@iptechnology.it
Message-ID: <1355766451.hatwc91h@1355766451.94043.was1-cp021>
MIME-Version: 1.0
Content-Type: text/plain
X-MS-Exchange-Organization-Network-Message-Id: 62d785b9-0645-413d-ed81-08cfaa95c35c
X-MS-Exchange-Organization-AuthSource: exchange-01.iptech.local
X-MS-Exchange-Organization-AuthAs: Anonymous

as you can see the second one is wrongly reported as "Content-Type: text/plain"

I tried to change the content conversion as described here:

http://technet.microsoft.com/en-us/library/bb232174.aspx

but nothing has changed..

do you have any suggestion?

thank you

Alessandro

Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.

Hi,

We got an application sending out emails internally to our end users, it does so in bulks of about 50 or so. The application sends via a Exchange 2013 receive connector where the application server is listed as an allowed relay.

About 30% of the emails go through fine, but most are dropped in Exchange as such:

TimestampSourceContextSourceEventId

2/04/2015 13:02ExplicitlyDiscardedSMTPHADISCARD

Its different recipients that get dropped every time and no other issues sending to any of these users.

Hi ,

In exchange 2013 sp1 SUBMITFAIL event id is happening for some messages .But at the second time that the same message is delivered perfectly to the end users.

My question is simple ,is this an bug in exchange 2013 sp1 if so on which CU it will be corrected ?We have to update to our customers so all of us please provide your suggestions as soon as possible.

Thanks & Regards S.Nithyanandham

The log field 'SmtpResponse' contains '550-5.7.1' preceding the custom error message.  The Get-Agentlog cmdlet in Exchange Management Shell throws an exception on these records as below.

The standard error message contains '550 5.7.1'. The Get-Agentlog cmdlet in Exchange Management Shell is happy on these records.

Is this behavior by design? I would like to use both custom error messages and the Get_Agentlog cmdlet.

Thanks in advance.

Hi,

we're investigating a migration of Lotus Notes to Exchange. One issue is the migration of encrypted mail. How to keep them confidential in Exchange?

We have users like a secretary that has read/write access to a mailbox of a manager. If another user mails the manager with confidential information, he encrypts it in LN before sending it, so only the mailbox owner can open the message. Is this possible in Exchange 2013 and in Exchange online? Heard that you can set things via IRM, but that with Outlook web access the secretary can set the manager's mailbox as primary and than will be able to open the confidential email....

best regards,

Hans

Hi,

My Frontend Transport server is placed behind a firewall which uses NAT to forward port 25 to it. The following is a sample of the header of incoming email from external source.

Received: from verifier.port25.com (xxx.xxx.xxx.xxx) by myserver.local (a.b.c.d) with Microsoft SMTP Server id 15.0.1044.25 via Frontend Transport; Wed, 8 Apr 2015 17:55:27 +0800
Received: from verifier.port25.com (127.0.0.1) by verifier.port25.com id h4jtgu20i3gm for <recipent@domain.com>; Wed, 8 Apr 2015 

Note the (xxx.xxx.xxx.xxx) is my WAN IP instead of the actual IP for verifier.port25.com, most likely due to the fact that the Frontend Transport is behind the NAT firewall (I'm using Centos 7 with iptables). How do I fix this?

I believe for Exchange Server 2003, the solution is as shown in http://www.exchangeinbox.com/article.aspx?i=44. However, I can't find any such configuration for Exchange Server 2013.

Thanks.

Hi Dear.

I have done fresh installation of Exchange server 2013, I have created send connector. But I am unable to send any external emails. My email ID is ramiz@resemblesystems.com

I am getting delivery failure message as below..

Received: from MAIL1.alreeda.local (192.168.20.110) by mail1.alreeda.local
 (192.168.20.110) with Microsoft SMTP Server (TLS) id 15.0.516.32; Wed, 8 Apr
 2015 18:16:14 +0400
Received: from MAIL1.alreeda.local ([fe80::1daa:cf21:cd66:2cbc]) by
 mail1.alreeda.local ([fe80::1daa:cf21:cd66:2cbc%12]) with mapi id
 15.00.0516.029; Wed, 8 Apr 2015 18:16:14 +0400
From: Sidharth Somadutt <sidharth@tadreesholding.com>
To: "gazi.ramiz@gmail.com" <gazi.ramiz@gmail.com>
Subject: 123332
Thread-Topic: 123332
Thread-Index: AQHQcgaS325wwSIJ8UmxfWNeEBadNw==
Date: Wed, 8 Apr 2015 14:16:14 +0000
Message-ID: <e7abc0108c0f4d6a918bb985c3860b0e@mail1.alreeda.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.20.106]
Content-Type: multipart/alternative;
        boundary="_000_e7abc0108c0f4d6a918bb985c3860b0email1alreedalocal_"
MIME-Version: 1.0
Please help me..

Hello Team,

We are running Exchange 2010 and RMS with Autonomy app which archives older than 30 day emails.

Parent company is in Tokyo, all incoming email goes through them and then via a hub transport service delivers email to North America.  For some reason, emails are encrypted and the Archive app cant get to them.

I just want to find how to proceed further and what to do to exclude emails to North America from it.

Any suggestions would be appreciated !

Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hello Folks,

I've got a problem understanding the usage of "InternalRelay" domains in conjunction with a shared mail-domain, hopefully someone can help me out:

I have the following situation:

Company A:

Exchange Server using "xy.com" as "InternalRelay" domain and a SendConnector for "xy.com" to Company B

Company B:

Vice versa, Exchange using "xy.com" as "InternalRelay" domain and SendConnector for "xy.com" to Company A

Both companies (partially) use "xy.com" as primary SMTP addresses for their mailboxes.

Now - to my understanding - when a user in Company A sends a mail to a non-existing Mailaddress in the "xy.com", this mail will generate a mail loop, as both exchange servers forward the mail to each other (--> please correct me if this assumption is wrong! i didn't have the possibility to practically test it) until one of them breaks the loop by discarding the mail with an NDR.

To avoid this, i've tried to configure recipientFiltering (setting RecipientValidationEnabled and additionally "AddressBookEnabled" on the "xy.com" AcceptedDomain) on Company A's Exchange Server (and creating Contacts in Company A for every valid xy.com recipient in Company B). However, Exchange is still forwarding every unknown xy.com Recipient to Company B and doesn't reject invalid recipients by itself as i thought it would.

The "Recipient filter" Transport agent is enabled of course.

I'd be glad on any hint you can give me on this topic.

Thanks in advance,

Juergen

Dear All,

I having a Exchange 2007 migrate to Exchange 2013 issue.

I deploy a all in one Exchange 2013 server.

When telnet it's 25 port, it will show "451 4.7.0 Temporary server error. Please try again later. PRX4"
after enter mail from, rcpt to, data.

Exchange 2013 now can't receive and email and send out any email....

I have read all relating post from fourm, i tried below:

- Revise the DNS issue
- Add hosts file
- Review Receive connector , ensure there have Exchange Server
- Dcdiag also normal
- Get-ServerCompentState HubTransport also is active
- Tried create another receive connector ( Open relay...also get same error...)
- AntiSpam was disabled
- Malware filter also disable and bypass 

Some SMTP Receive Log:

50-Hello [127.0.0.1],
,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,
<,MAIL FROM: inboundproxy@contoso.com,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
*,08D22B73408371ED;2015-03-13T15:22:46.990Z;1,receiving message
>,<,RCPT TO: HealthMailbox1bcaf8efe11243d0ade60c4d14533685@artapower.com,
,>,250 2.1.5 Recipient OK,
,<,DATA,

,>,354 Start mail input; end with <CRLF>.<CRLF>,
,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
,*,,"Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""421 4.4.1 Connection timed out."" 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 10.0.182.19:2525"
,>,451 4.7.0 Temporary server error. Please try again later. PRX4 ,
,<,QUIT,
>,221 2.0.0 Service closing transmission channel,
,-,,Local
,+,,

Front END Connect Log:

2015-03-13T18:12:03.069Z,08D22BD02A6B29D2,SMTP,client proxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:03.081Z,08D22BD02A6B29D2,SMTP,client proxy,-,Messages: 0 Bytes: 0 (Retry : Security status InternalError)
2015-03-13T18:12:49.821Z,08D22BD02A6B29D5,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD02A6B29D4
2015-03-13T18:12:49.822Z,08D22BD02A6B29D5,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:12:49.823Z,08D22BD02A6B29D5,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:49.833Z,08D22BD02A6B29D5,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:12:53.123Z,08D22BD02A6B29D7,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD02A6B29D6
2015-03-13T18:12:53.124Z,08D22BD02A6B29D7,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:12:53.124Z,08D22BD02A6B29D7,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:53.134Z,08D22BD02A6B29D7,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:14:25.580Z,,Transport,,*,service stopped
2015-03-13T18:14:32.144Z,,Transport,,*,service started; MaxConcurrentSubmissions=240; MaxConcurrentDeliveries=240; MaxSmtpOutConnections=Unlimited
2015-03-13T18:15:16.903Z,,Transport,,*,service stopped
2015-03-13T18:15:23.699Z,,Transport,,*,service started; MaxConcurrentSubmissions=240; MaxConcurrentDeliveries=240; MaxSmtpOutConnections=Unlimited
2015-03-13T18:16:40.566Z,08D22BD0E053AA0E,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD0E053AA0D
2015-03-13T18:16:40.793Z,08D22BD0E053AA0E,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:16:40.886Z,08D22BD0E053AA0E,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:16:40.903Z,08D22BD0E053AA0E,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:17:03.076Z,08D22BD0E053AA11,SMTP,client proxy,+,Client proxy session for HealthMailbox6c592afa20d245b6b1bde8e7179ada20@artapower.com. Proxied session id 08D22BD0E053AA10
2015-03-13T18:17:03.077Z,08D22BD0E053AA11,SMTP,client proxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:17:03.078Z,08D22BD0E053AA11,SMTP,client proxy,>,Established connection to 10.0.182.19
2015-03-13T18:17:03.090Z,08D22BD0E053AA11,SMTP,client proxy,-,Messages: 0 Bytes: 0 (Retry : Security status InternalError)

Hello There ,

Our organisation has 2 different entities at different locations.Both place we have Exchnage 2010 setup for emails as different exchange organisations.Is it possible to transport emails each other through a VPN connectivity ? We wanted to reduce the delay the email transfers.

Much apreciate any support

Regards,

Ratheesh

Having many of these below:

Event ID 16028 A forced configuration update for Microsoft.Transport.TransportServerConfiguration has successfully completed.

Followed by this every few hours.

Event ID 15004 Resource Pressure Increased from Medium to High

Version buckets =219

Did not have this issue before CU5 update.  Updated from CU5

When ip block list providers are configured the standard error message for rejected messages in the Agentlog log field 'SmtpResponse' contains '550 5.7.1' at the beginning of the message.

When ip block list providers are configured the custom error message for rejected messages in the Agentlog log field 'SmtpResponse' contains '550-5.7.1' at the beginning of the message.

The Get-Agentlog powershell cmdlet in the Powershell Exchange Management Shell throws an exception on the customized log records as below and the record is skipped by the Get-Agent cmdlet.

This behavior prevents the use of the Exchange Management Shell Get-Agentlog cmdlet in the processing of the Exchange Agentlog files. Is this behavior by design? I would like to use both custom error messages and the Get_Agentlog cmdlet.

Thanks in advance.

I have an issue with my Exchange 2013 deployment.  I am unable to send attachments over 10MB.  I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.

So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize to 2047MB.

I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box.  I have closed and opened my Outlook Client Several times but when ever I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"

There must be something I am missing but I can't see it.  I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or blank in the EMC which my research has told means there is no limit on the account.

Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.

Here is the output of Get-TransportConfig

AddressBookPolicyRoutingEnabled                             : False
AnonymousSenderToRecipientRatePerHour                       : 1800
ClearCategories                                             : True
ConvertDisclaimerWrapperToEml                               : False
DSNConversionMode                                           : UseExchangeDSNs
JournalArchivingEnabled                                     : False
ExternalDelayDsnEnabled                                     : True
ExternalDsnDefaultLanguage                                  :
ExternalDsnLanguageDetectionEnabled                         : True
ExternalDsnMaxMessageAttachSize                             : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority                               :
ExternalDsnSendHtml                                         : True
ExternalPostmasterAddress                                   :
GenerateCopyOfDSNFor                                        : {}
HygieneSuite                                                : Standard
InternalDelayDsnEnabled                                     : True
InternalDsnDefaultLanguage                                  :
InternalDsnLanguageDetectionEnabled                         : True
InternalDsnMaxMessageAttachSize                             : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority                               :
InternalDsnSendHtml                                         : True
InternalSMTPServers                                         : {}
JournalingReportNdrTo                                       : <>
LegacyJournalingMigrationEnabled                            : False
LegacyArchiveJournalingEnabled                              : False
LegacyArchiveLiveJournalingEnabled                          : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling                : False
MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
MaxDumpsterTime                                             : 7.00:00:00
MaxReceiveSize                                              : Unlimited
MaxRecipientEnvelopeLimit                                   : 500
MaxRetriesForLocalSiteShadow                                : 2
MaxRetriesForRemoteSiteShadow                               : 4
MaxSendSize                                                 : Unlimited
MigrationEnabled                                            : False
OpenDomainRoutingEnabled                                    : False
RejectMessageOnShadowFailure                                : False
Rfc2231EncodingEnabled                                      : False
SafetyNetHoldTime                                           : 2.00:00:00
ShadowHeartbeatFrequency                                    : 00:02:00
ShadowMessageAutoDiscardInterval                            : 2.00:00:00
ShadowMessagePreferenceSetting                              : PreferRemote
ShadowRedundancyEnabled                                     : True
ShadowResubmitTimeSpan                                      : 03:00:00
SupervisionTags                                             : {Reject, Allow}
TLSReceiveDomainSecureList                                  : {}
TLSSendDomainSecureList                                     : {}
VerifySecureSubmitEnabled                                   : False
VoicemailJournalingEnabled                                  : True
HeaderPromotionModeSetting                                  : NoCreate
Xexch50Enabled                                              : True

Thanks in advance for any assistance.

Carl

Hello everyone,

2015-03-27T20:46:34.219Z,08D236728F26DC58,192.168.5.31:25,107.158.253.253:38235,107.158.253.253,<,NewConspiracyAlerts@info.getallthenew-conspiracyalerts.us,ConstitutionalProtectionAgency@getallthenew-conspiracyalerts.us;,goodman@nhautism.org,1,Content" style="font-family:Calibri, Arial, Helvetica, sans-serif;font-size:16px;line-height:normal;" target="_blank">myem@domain.com Filter Agent,OnEndOfData,AcceptMessage,,SCL,1,,a9765756-c29b-49ab-2014-08d236e63413,,Incoming

[PS] C:\>test-ipblocklistprovider zen.spamhaus.org -ipaddress 107.158.253.253

flavio

Team.

   I have an open question regarding changes to the mail flow connector for Exchange Online:http://community.office365.com/en-us/f/156/p/343149/929997.aspx#929997

************************************************************************************************

Hello all,

    I'm working on a Hybrid 2010 configuration.  When modify the connectors in Exchange Online EAC, I noticed that the connectors changes, and opportunistic TLS is gone.  What happened?  Can someone please provide some information regarding the TLS changes?  Did opportunistic TLS get removed? 

I was following these articles:

Configure mail flow using connectors in Office 365

https://technet.microsoft.com/en-us/library/ms.exch.eac.connectorselection(v=exchg.150).aspx

Set up connectors to route mail between Office 365 and your own email servers

https://technet.microsoft.com/en-us/library/dn751020(v=exchg.150).aspx

Any information on theses changes will be appreciated.

-KloudSavvy

I received this response:

•                       Microsoft Support                      

Hi guys!

We got Exchange 2013 in the Internet facing ADsite.

If an externat user use telnet to port 25, we need to prevent that a mail from our own domain can be accepted.

In Exchange 2010, we prevent this removing the ExtendedRights ms-exch-smtp-accept-authoritative-domain-sender on ther Internet connector.

Now in Exchange 2013, we remove this ExtendedRights in the FrontEnd Internet Connector, but the mail is accepted anyway.

Any idea if this behavior change in Exchange 2013?

Regards,

Esteban

http://nextadmin.blogspot.com