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

Good morning

I am not sure if this is possible but what I am trying to acheive is the following:

When an internal user sends and email to a particular internal email address and CC's in an external email address, I want to block that cc'd email to the external address but still allow the email to the internal address to make it through.

Hopefully I have explained this well enough. Is this possible?

Kind regards

Hi!

Our exchange server 2013 receiving emails on port 443. If we disable the rule for incoming 443 then it receives on 25 but then we cannot connect outlook.

Any Suggestions?

Thanks.

Hello!

Our Exchange infrastructure description, briefly:

1. Using Exchange 2013 CU7

2. 2 x MBX+CAS servers (EX1, EX2)

3. 2 x Edge servers (mx1, mx2)

4. DAG, 4 DBs

5. Hybrid Configuration: 200 local users, 15 cloud users

Our case: sometimes our users receive NDR while sending messages to existing mailboxes:

"Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'

For example, user sent 2 messages, first caused NDR, second was successfully delivered:

Get-MessageTrackingLog -Sender sender@domain.ru -Recipient recipient@domain.ru | fl EventId, Source, TimeStamp, EventData

EventId   : HAREDIRECT
Source    : SMTP
Timestamp : 15.04.2015 16:58:36
EventData : {[DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : RECEIVE
Source    : SMTP
Timestamp : 15.04.2015 16:58:36
EventData : {[FirstForestHop, EX1.local.domain.ru], [Oorg, domain.ru], [ProxiedClientIPAddress, 10.0.100.21], [Proxie
            dClientHostname, mx1.domain.ru], [ProxyHop1, EX1.local.domain.ru(192.168.0.11)], [DeliveryPriority, Normal]
            , [AccountForest, local.domain.ru]}

EventId   : AGENTINFO
Source    : AGENT
Timestamp : 15.04.2015 16:58:36
EventData : {[AMA, SUM|action=st|error=|atch=0], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : FAIL
Source    : ROUTING
Timestamp : 15.04.2015 16:58:36
EventData : {[DeliveryPriority, Normal], [Oorg, domain.ru], [AccountForest, local.domain.ru]}

EventId   : HAREDIRECT
Source    : SMTP
Timestamp : 15.04.2015 18:17:23
EventData : {[DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : RECEIVE
Source    : SMTP
Timestamp : 15.04.2015 18:17:23
EventData : {[FirstForestHop, EX2.local.domain.ru], [ProxiedClientIPAddress, 10.0.100.22], [ProxiedClientHostname,
            mx2.domain.ru], [ProxyHop1, EX2.local.domain.ru(192.168.0.12)], [DeliveryPriority, Normal], [AccountForest,
            local.domain.ru]}

EventId   : AGENTINFO
Source    : AGENT
Timestamp : 15.04.2015 18:17:23
EventData : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.195.3371.0|name=|file=], [TRA, ETR|ruleI
            d=068e0c20-5de5-48e0-9b53-ea90e5deb5b9|st=12.12.2014 18:27:31|action=SetSCL|sev=1|mode=Enforce], [CompCost
             |AMA=0|ETR=0], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : SEND
Source    : SMTP
Timestamp : 15.04.2015 18:17:25
EventData : {[E2ELatency, 4.863], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel, Opportunistic], [
            DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : DELIVER
Source    : STOREDRIVER
Timestamp : 15.04.2015 18:17:25
EventData : {[MailboxDatabaseName, IT], [Mailboxes, c1357fa5-52f2-4d16-8c70-09c9f9c4ab0e], [ToEntity, Hosted], [E2ELate
            ncy, 4.863], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

How can I investigate this issue? 

Hi All,

This is my first post to ms exchange forum am getting  Log onto incoming mail server (POP3): Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance. in my outlook clients, till last Sunday (12.04.15) my exchange was well & good, Monday morning suddenly the problem started like none of our outlook pop3 clients are able to communicate with exchange (rest  IMAP, SMTP & Exchange accounts are working fine). i have tried with all port no but no luck. please help me to get raid of this one.

Exchange 2013 CU6 with server 2012 Std 64Bit

Thanks,

Murali 

I'm having trouble sending email (via powershell for now) using an AD account which has been granted Send As permissions to a valid email account.  I am passing the credentials for the AD account and using the FROM address of the email account.  (This is being done from powershell usign smtp.Send.) If I change the credentials to another account it does send, so there's something different about this particular AD account.

When I attempt to send I get "the SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 client was not authenticated"

In the SMTP receive log I see this:

Inbound Negotiate failed because of LogonDenied  

User Name: NULL

535 5.7.3 Authentication unsuccessful

MAIL FROM:<the-valid-email-account@yyy.com>,

530 5.7.1 Client was not authenticated

What has me perplexed is that I'm doing the same thing from another machine, where I'm using an AD account to send as this same valid email account.  All I did in that case was grant the Send As permission to the AD account and it worked.

In this instance where it's not working I've also tried adding the ms-Exch-SMTP-Submit permission to the receive connector, but still cannot send email.

So I'm stumped as to what is different and needs changed in order to allow this AD account to send mail.

Thanks for any help you can provide.

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 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.

Hello all

Running Exchange 2013 sp1 RU8. 

On our CAS servers we have configured our front end transport receive connectors with a  "maximum message size limit" of  150 megs, and "maximum recipients per message" with a 500 limit. Based on these numbers,  this mean an external sender can send an email that is 150 megs in size to 500 recipients. 150megs x 500 = 100 gigs. Does  this mean one email has the potential to increase the database size by 100 gigs?

Thank you

Bulls on Parade

Hi everybody,

I'm having some issues with an Exchange 2013 server.

When some users try to logon to the OWA page it keeps loading the page and ends with a time-out.
This only applies to 6 or 7 users, other users can login and open the page.

I tried to replace the signed certificate to solve this problem, and did a online analyzer check, most tests come out good.

I can't seem to find the source of this problem.

There are also multiple users that are having trouble to receive e-mail through the wifi on phones and tablets at home but when they switch to 3g it works fine.

You might need more information, just ask.. i don't know where to search anymore.

I tried inheritance on the AD, disabled SSL in the IIS, restarted the server, replaced the signed cert. etc.

Update:

I set the selfsigned cert in the IIS default web page,, to check if it responds to the certificate and it does, so the issue doesn't come from the certificate.

This issue probably came up after CU1, and i've read something about healthboxes..

I'm going to install CU6 and hope for good result.

Kind regards,

Tim

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.

We are currently receiving a large amount of spam email in a shared mailbox (reception@mydomain) that is showing the to address as info@mydomain and that email address does not exist within the organisation.

If I try to send to info@mydomain (internally or externally) it is bounced back say the email address does not exist.

How can I stop this spam mail.

Thanks

I have a new Exchange 2013 server on premisses.  Twice in the last week some of the server components have been marked as inactive.  Is there a way ti figure out why this is happening?

This is randomly stopping mail flow from our ticket tracking software because it uses POP3

These are the commands I had to run before.  I will correct this IMAP proxy one in just a bit;

Set-ServerComponentState -Identity lo-exch2 -Component imapproxy -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component forwardsyncdaemon -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component PopProxy -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component provisioningrps -Requester HealthAPI -State Active

Dear friends,

in my company I have setup Microsoft Exchange server 2013 with windows 8.1 but now we have expand our network with another company so I want to send and receive emails from but of servers, now how to do in Microsoft exchange server 2013? if u have any information it will help me a lot thanks in advance.

I have an Exchange 2010 SP3/Office 365 hybrid deployment and I'm having a problem with a specific external email address sending us email. When he tries to send email, it'll usually bounce with a "Delivery not authorized, message refused" error. I thought I had this figured out a couple weeks ago, but it appears not. 

This is a copy of the error log from his end. I have just enabled verbose logging on my SMTP connector, so please let me know if there's something in there I should be looking for.

Received: from BY1PR0201CA0034.namprd02.prod.outlook.com (25.160.191.172) by
 DM2PR02MB288.namprd02.prod.outlook.com (10.141.55.149) with Microsoft SMTP
 Server (TLS) id 15.1.136.25; Tue, 14 Apr 2015 13:16:17 +0000

Received: from BL2FFO11FD010.protection.gbl (2a01:111:f400:7c09::199) by
 BY1PR0201CA0034.outlook.office365.com (2a01:111:e400:4814::44) with Microsoft
 SMTP Server (TLS) id 15.1.136.25 via Frontend Transport; Tue, 14 Apr 2015
 13:16:16 +0000

Authentication-Results: spf=pass (sender IP is 63.141.144.137)
 smtp.mailfrom=nomoocookies.com; bader.org; dkim=none (message not signed)
 header.d=none;

Received-SPF: Pass (protection.outlook.com: domain of nomoocookies.com
 designates 63.141.144.137 as permitted sender)
 receiver=protection.outlook.com; client-ip=63.141.144.137;
 helo=smtp20.bigcommerce.net;

Received: from smtp20.bigcommerce.net (63.141.144.137) by
 BL2FFO11FD010.mail.protection.outlook.com (10.173.161.16) with Microsoft SMTP
 Server id 15.1.142.12 via Frontend Transport; Tue, 14 Apr 2015 13:16:15 +0000

Received: from mail3.bigcommerce.com (10.16.220.131) by smtp.bigcommerce.com (PowerMTA(TM) v3.5r17) id h5k9hu0q
in8h for <brian@bader.org>; Tue, 14 Apr 2015 08:15:47 -0500 (envelope-from <david@nomoocookies.com>)

Received: from mail3.bigcommerce.com (localhost [127.0.0.1])

        by mail3.bigcommerce.com (Postfix) with ESMTP id B8A83233201D

        for <brian@bader.org>; Tue, 14 Apr 2015 08:15:45 -0500 (CDT)
Received: from [10.1.20.159] (173-15-182-105-BusName-Philadelphia.hfc.comcastbusiness.net [173.15.182.105])

        by mail3.bigcommerce.com (Postfix) with ESMTPSA

        for <brian@bader.org>; Tue, 14 Apr 2015 08:15:45 -0500 (CDT)
Message-ID: <552D1302.1010609@nomoocookies.com>Date: Tue, 14 Apr 2015 09:15:46 -0400
From: David Bader <david@nomoocookies.com>User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: <brian@bader.org>Subject: Fwd: Undeliverable: Honoring a promise
References: <791c19a1-8028-47ed-8ce4-7e2019b81afa@CY1PR02MB1229.namprd02.prod.outlook.com>In-Reply-To: <791c19a1-8028-47ed-8ce4-7e2019b81afa@CY1PR02MB1229.namprd02.prod.outlook.com>X-Forwarded-Message-Id: <791c19a1-8028-47ed-8ce4-7e2019b81afa@CY1PR02MB1229.namprd02.prod.outlook.com>Content-Type: multipart/mixed;

        boundary="------------040601090609080707090005"
Return-Path: david@nomoocookies.comX-EOPAttributedMessage: 0
X-Forefront-Antispam-Report:

        CIP:63.141.144.137;CTRY:US;IPV:NLI;EFV:NLI;SFV:SKN;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:DM2PR02MB288;H:smtp20.
bigcommerce.net;FPR:;SPF:None;LANG:;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR02MB288;
X-Exchange-Antispam-Report-Test: UriScan:;

X-Exchange-Antispam-Report-CFA-Test:
        BCL:0;PCL:0;RULEID:(601004);SRVR:DM2PR02MB288;BCL:0;PCL:0;RULEID:;SRVR:DM2PR02MB288;

X-OriginatorOrg: bader.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Apr 2015 13:16:15.7318

 (UTC)
X-MS-Exchange-CrossTenant-Id: 00dd0db2-6ec4-4617-a994-3eb80c681d91
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR02MB288
X-OrganizationHeadersPreserved: DM2PR02MB288.namprd02.prod.outlook.com
X-CrossPremisesHeadersFilteredByDsnGenerator:

        DM2PR02MB288.namprd02.prod.outlook.com

Guys,

The server is unresponsive. It was rebooted with message in submission queue.

What will happen to message after reboot? Does it gone or it was delivered?

Thanks!

BR,

Roldan

Hello,

When I received a message from the external, I have a "loop" in my mail flow. I have not a problem with the receiving but it is strange.

My headers are the follow :

Received: from exchsrv.domain.com (192.168.1.x) by exchsrv.domain.com
 (192.168.1.x) with Microsoft SMTP Server (TLS) id 15.0.1044.25 via Mailbox
 Transport; Fri, 24 Apr 2015 13:05:07 +0200
Received: from exchsrv.domain.com (192.168.1.x) by EXCHSRV.domain.com
 (192.168.1.x) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 24 Apr
 2015 13:05:07 +0200
Received: from antispam (192.168.1.x) by exchsrv.domain.com (192.168.1.x) with
 Microsoft SMTP Server id 15.0.1044.25 via Frontend Transport; Fri, 24 Apr
 2015 13:05:07 +0200

Note the uppercase in the second receive.

I do not really understand when the problem could be.

Thanks

If I telnet to my exchange 2013 server and do an EHLO it returns the local server name and not the external FQDN.

Mxtoolbox.com flags this as a problem as it doesn't match my reverse DNS which is to the external FQDN.

How do I change it to return my external FQDN ?

thanks