Exchange 2013 Rule

How to stop certain users to send mail externally and allow some user to send externally. Well in my scenario I have 150 users out of which I want only 50 users to send mail externally while all other can only send internal mails?

Hi,
Yes, you need to use transport rule to achieve this goal.
In order to get it, you should create a distribution group first, and add the users which can't send emails externally to this group. Then you can create a transport rule to prevent users from sending outbound messages.
Here is an article which can help you for your reference.
Using Transport Rules to Restrict Users from Sending Email to External Recipients
http://exchangeserverpro.com/restrict-outbound-email-transport-rule/
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange 2013 Rule Disclaimer

    Hi all,
    Have now setup 2 rules on Our Exchange server.Both have same priority (also tried different priority) but only one is added.So question is,does Exchange only add 1 disclaimer at the time.Does Exchange only add one rule and ignore the rest if a rule already
    has been added?
    thanks!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Hi
    Nithyanandham and thanks for reply,
    to explain abit more about our two rules:
    Rule1: If a user is member of a  spesific group(1 distribution list),apply disclaimer to alle outgoing mails.
    Ruke2: Applies to everyone to messages sent Out of organisation,add disclaimer (different disclaimer than rule 1).
    I send test message and only rule 2 is applied.Im also sure that im member of that group and that AD gas been synced.
    Tested with different priority on these rules but only rule 2 is applied.For now we only have 4 rules which my account only should hit 2 rules.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

  • Exchange 2013 Mail flow rule using RegEx

    We're trying to implement a rule on certain mailboxes that it shouldn't accept an email without a subject.
    I found documentation from Microsoft on exchange 2010 to Configure
    a Transport Rule for Messages That Have a Blank Subject, but I tried using the ^$ RegEx
    with Exchange 2013 and it doesn't seem to work.
    I also looked at the Transport
    Rule Predicates for Exchange 2013 and it clearly says thatSubjectMatchesPatterns
    matches messages where text patterns in the Subject field match a specified regular expression.
    My workaround was to reject all messages to those specific mailboxes except if subject pattern matches. but
    if I want to add now conditions ie. to reject emails with a subject "Sent from my snipping tool" I can't do it.
    I found Here that
    Exchange 2013 now supports extended RegEx but I didn't find that the syntax for ^$should
    be any different in extended RegEx.

    If you use any special character in the RegEx you must use
    \m Escape m, where m is one of the meta characters described above: ^, ., $, |, (), [], *, +, ?, \, or /.
    as decribed in http://technet.microsoft.com/en-us/library/jj674702%28v=exchg.150%29.aspx

  • Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

    Hello guys,
    I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
    When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
    When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
    We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
    What should I check and configure to make it work?

    Hi,
    I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
    By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
    A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

    Hello,
    I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
    on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit". 
    Here is the error message I receive when creating transport rules in Exchange 2013:
    "You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
    exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
    I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
    I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

    Hi Sathish,
    How about the result after using ADSI Edit ?
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Exchange 2013: Inbox rules don't work on Journal Mailbox

    Hello,
    I've Exchange 2013 server with 2 databases:
    * First database has all user mailboxes & is journaled to second database
    * Second database has only 1 mailbox: Journal which collects all messages send / received  from / to first database.
    I made Inbox Rules on Journal Mailbox  to delete unnecessary messages e.g. :
    * HealthMailbox messages with Subject: Client submission probe
    * [email protected] messages with Subject: Inbound proxy probe.
    I noticed that these rules don't work. Why ?
    best regards Janusz Such

    Hi,
    How do you create these Inbox Rules on journal Mailbox? Please share the detailed rule content here and we can check whether the rule was created correctly or not.
    Instead of journaling all mailboxes residing on a mailbox database, I suggest we can configure journal rules to match your organization's needs by journaling individual recipients or members of distribution groups. For more information about
    journal rules, please refer to:
    https://technet.microsoft.com/en-us/library/jj651670%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Regards,
    Winnie Liang
    TechNet Community Support

  • Conditional Mail Routing in Exchange 2013

    Hello all,
    Is it possible to create a rule in Exchange 2013 based on a message header, and redirect to a custom send connector?
    It looks like you can do it within Exchange Online with outbound connectors, but I don't have the same options in 2013.
    "Apply this rule if...... A message head includes 'x-ibe-encrypted' header includes 'securemail'
    Do the following...... Use the following send connector....
    Redirect the message to.... the following send connector.

    Hello all,
    Is it possible to create a rule in Exchange 2013 based on a message header, and redirect to a custom send connector?
    It looks like you can do it within Exchange Online with outbound connectors, but I don't have the same options in 2013.
    "Apply this rule if...... A message head includes 'x-ibe-encrypted' header includes 'securemail'
    Do the following...... Use the following send connector....
    Redirect the message to.... the following send connector.
    No, not with 2013 on-prem.
    You would need to use something like:
    http://routingruleagent.codeplex.com/
    or 3rd party software:
    http://ivasoft.com/routebysender2013.shtml
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 Mail Size Limits

    I am having an issue with setting the max send and receive size on Exchange 2013.  I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
    server to an external account: 
    #550 5.3.4
    ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
    I have checked the mail sizes and below is the report.  I currently have both send and receive set to 100MB.  Is there some other setting in 2013 that I am not aware of?
    AnonymousSenderToRecipientRatePerHour                       : 1800
    ClearCategories                                            
    : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                          
    : UseExchangeDSNs
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                        
    : True
    ExternalPostmasterAddress                                   :
    GenerateCopyOfDSNFor                                        :
    HygieneSuite                                               
    : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 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                                             
    : 100 MB (104,857,600 bytes)
    MaxRecipientEnvelopeLimit                                   : 500
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                
    : 100 MB (104,857,600 bytes)
    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

    Hello Landfish,
    Good Day...
    The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue. 
    There are basically three places where you can configure default message size limits on Exchange:
    Organization transport settings
    Send/receive connector settings
    User mailbox settings.
    To check your server’s current limit you can open Exchange Management Shell
    Try the below commands to check the Message quota size limit
    get-transportconfig | ft maxsendsize, maxreceivesize
    get-receiveconnector | ft name, maxmessagesize
    get-sendconnector | ft name, maxmessagesize
    get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
    To change the above size limits based on your requirement.
    Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
    Attachment size limit
    To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
    New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
    For More info
    https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com

  • Mail flow in exchange 2013 and lotus domino coexistence

    scenario: Exchange 2013 CU3 running Windows 2012. coexsisting with lotus domino 8.5.1
    there two cas server and two mailbox server. users migrated using quest tool. distribution groups are still lotus notes.
    in one of distrbution group which containing around 5 users, 4 users are migrated to exchange 2013 cu3 one user still in lotus notes. the above mentioned distribution group members complaining they are not reciving mail which address to distribution group.
    I used exchange shell for message tracking and I found below entries.
    in source field the entry is mailboxrule i have verified there is no mail box rule in the user front
    in eventid field the entry is receive
    in the sourcehostname its show exchange 2013 server.
    recipientstatus {unknown}
    Since the distribution group is in lotus notes I want find event which sates that the message or exchange 2013 forwarding or checking the members of DL .
    which field will give the required details currently i am finding anything.
    please suggest

    Thanks.
    In current scenario we cant create any dl in the exchange 2013 front. I want to know what this mean
    recipientstatus {unknown}.
    secondly I have followed the link below
    http://social.technet.microsoft.com/Forums/exchange/en-US/194c0bd8-9c77-4750-9f47-944451f2dd40/message-tracking-in-large-distribution-list-challenges-please-help?forum=exchangesvrgenerallegacy
    I ran the below command:
    Get-MessageTrackingLog -MessageSubject
    "messageTrack" |select eventId, sender,@{l="recipeints";e={[string]($_.recipients)}}|ft
    -Aut
    oSize -Wrap
    I am getting enventid, sender field details but recipeints field is empty.
    Please suggest.

  • Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

    Hi everyone,
    Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
    On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
    The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
    The main problems are as follows:
    There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
    Service.
    The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long...  It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
    I receive an error in the Event Log regarding RPC over HTTP Proxy
    to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
    this post
    The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
    for over chatty warnings about disk space (the warning is that we have loads of space...)
    This is a brief outline of the environment:
    Exchange 2007 SP3 RU13
    UK - Two physical locations in a stretch LAN (100Mb WAN)
    4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
    Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
    Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
    Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
    2 x Virtual Windows 2003 R2 - Hub Transport Servers
    2 x Virtual Windows 2003 R2 - Client Access Servers
    1 x Virtual Windows 2003 R2 - Unified Messaging Server
    1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
    US - One physical location
    1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
    Exchange 2013 CU5
    UK - Installed into same site along side Exchange 2007 servers
    1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
    Problem 2 Error Message - Please note, server names and domain name changed:
    Log Name:      Application
    Source:        MSExchange Front End HTTP Proxy
    Date:          18/07/2014 10:00:37
    Event ID:      3005
    Task Category: Core
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      EXC2013.domain.local
    Description:
    [RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
    Event Xml:
    <Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
      <System>
        <Provider Name="MSExchange Front End HTTP Proxy" />
        <EventID Qualifiers="32768">3005</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
        <EventRecordID>64832</EventRecordID>
        <Channel>Application</Channel>
        <Computer>EXC2013.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>RpcHttp</Data>
        <Data>EXC2007CAS1.domain.local</Data>
        <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
        <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
      </EventData>
    </Event>

    Hi Off2work,
    I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
    Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
    I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
    I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
    rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
    As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
    The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
    I will see if UM drops out of that list once I've configured it shortly
    Thanks for taking the time to respond (and that goes to DareDevil too)

  • Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

    Hi,
    How can I enable recipient validation work in this design:
    2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
    From Exchange documentation:
    http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
    Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
    If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
    Enable Anti-Spam Functionality on Mailbox Servers.
    If You have a setup like this:
    Install antispam agents:
    Identity Enabled Priority
    Transport Rule Agent True 1
    Malware Agent True 2
    Text Messaging Routing Agent True 3
    Text Messaging Delivery Agent True 4
    Content Filter Agent True 5
    Sender Id Agent True 6
    Sender Filter Agent True 7
    Recipient Filter Agent True 8
    Protocol Analysis Agent True 9
    Have Recipient validation enabled:
    Name                  Enabled RecipientValidationEnabled----                  ------- --------------------------RecipientFilterConfig    True                      True
    Have AcceptedDomain AddressBook enabled:
    DomainName DomainType AddressBookEnabled
    contoso.com Authoritative True
    Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
    So .. HOW? Is it possible without Edge servers? Have I missed something?
    I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
    of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
    Sincerely,
    Vince

    Hello Vince,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2013 - Import-TransportRuleCollection from Exchange 2007 failing

    I am in the middle of a Exchange 2007 SP3 to Exchange 2013 Sp1/CU4 migration and am importing transport rules and it's failing.
    [PS] C:\Windows\system32>Import-TransportRuleCollection -FileData C:\2007TransportRules.xml -Verbose
    Cannot process argument transformation on parameter 'FileData'. Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte[]". Error: "Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte".
    Error: "Input string was not in a correct format.""
        + CategoryInfo          : InvalidData: (:) [Import-TransportRuleCollection], ParameterBindin...mationException
        + FullyQualifiedErrorId : ParameterArgumentTransformationError,Import-TransportRuleCollection
        + PSComputerName        : ex2013-mb1.MYDOMAIN.local
    Before you ask, I am still on SP1/CU4 because CU5 and CU6 are so buggy I refuse to install them. And that's probably not the fix anyway... WHEN IS CU7 coming out?

    I've seen an official list but, rules that were Edge transport rules are the first ones that come to mind. After the import you can look in the EAC and it should show you any rules that have errors or you can stare and compare the rules to your 2007 environment
    to determine if any weren't imported. 
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Exchange 2013 autodiscover not working from Externally

    Hi 
    i have exchange 2010 sp3(2Mb, 2hub/cas). I installed exchange 2013 servers(2MB, 2CAS). For coexistence i generated new certifcate with new cas from third party. I installed that certificate in that cas and assigned all services. i changed all my virtual
    directories service url. I didnt import the new certificate to exchange 2010 cas server and i didnt change url to legacy link.But still iam able to check exchange 2010 user mailbox owa, activesync and autodiscover without any certificate error. 
    If i try to browse owa, its going to 2013 server, if user is exchange 2010 user and its redirecting to exchange 2010 owa with same link.
    But i dont know how above things is working without importing to new certificate...
    Main problem is i am not able to configure exchange 2013 users outlookanywhere, Autodiscover from externally...
    So in tmg i pointed the outlook anywhere ip address new cas server, now both exchange 2010 and exchange 2013 users while OA from external, its keep on asking password... Not accepting it...
    Please help me to fix this issue..

    Hi ,
    On TMG please have the outlook anywhere rule like below and check the status.
    Step
    1 :
    On the TMG rule - >authentication delegation ---> select the option "no delegation users can authenticate directly"
    Step
    2 :
    on the users tab in the TMG rule - just add "all users" group on that rule.
    By having the above settings we have avoided the issues in your environment.
    Note : Based on the above setting's , Each and everyone in exchange will have a access to the outlook anywhere from external world , because there would not be having any restriction on the TMG rules.
    Please have a look in to the below link , it will give you some ideas which is related to TMG
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    Thanks & Regards S.Nithyanandham

  • After Migration Exchange 2013 does not send mail outside the organization

    Dear,
    After Migration Exchange 2010 to exchange 2013. We does not send email from the organization but we can received mail from others organization.
    Delivery has failed to these recipients or groups:
    [email protected] ([email protected]) The server has tried to deliver this message,
    without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
    Diagnostic information for administrators:
    Generating server: OGMAIL.domain.net Receiving server: gmail.com (2607:f8b0:400c:c01::1a)
    [email protected] 6/11/2014 10:16:10 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '550 4.4.7 QUEUE.Expired; message expired' 6/11/2014
    10:03:49 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." 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 2607:f8b0:400c:c01::1a:25'
    Original message headers:
    Received: from OGMAIL.domain.net (192.168.10.12) by ogmail.domain.net
     (192.168.10.12) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 9 Jun
     2014 16:13:30 +0600
    Received: from OGMAIL.domain.net ([::1]) by ogmail.domain.net ([::1]) with
     mapi id 15.00.0847.030; Mon, 9 Jun 2014 16:13:30 +0600
    From: Administrator <[email protected]>
    To: Administrator <[email protected]>
    CC: IT.HW-Masudur Rahman-MRT <[email protected]>, "[email protected]"
        <[email protected]>
    Subject: RE: Migration batch mrtmove has completed successfully.
    Thread-Topic: Migration batch mrtmove has completed successfully.
    Thread-Index: AQHPd1JEcid9YEi4F0ue6m1039EwR5top+xp
    Date: Mon, 9 Jun 2014 10:13:29 +0000
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    x-originating-ip: [192.168.10.2]
    Content-Type: multipart/alternative;
          boundary="_000_6b0d846f503942d99d44be9aff8d6adfogmaildomainnet_"
    MIME-Version: 1.0
    Queue viewer:
    Identity: ogmail\8786\3470333575194
    Subject: testing
    Internet Message ID: <[email protected]>
    From Address: [email protected]
    Status: Active
    Size (KB): 4
    Message Source Name: SMTP:Default OGMAIL
    Source IP: 192.168.10.12
    SCL: -1
    Date Received: 6/23/2014 3:22:49 PM
    Expiration Time: 6/25/2014 3:22:49 PM
    Last Error: 
    Queue ID: ogmail\8786
    Recipients:  [email protected];2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=SendMail,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=domain,DC=net;0
    Md. Ramin Hossain

    What I notice is Queue expired. The message is not going out.
    Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
    This error states that It tried to connect to the target system but failed to connect out.
    Is Exchange 2013 server added in the firewall rule to send communication over port 25?
    Do you have use Front end proxy checkbox checked on the Send connector to internet that was created on 2013 (if created)?
    If use front end proxy checkbox is checked, then you need to add permissions for your CAS server's IP in the Firewall for outbound port 25 rule. As it appears that the mail is originating from CAS to the firewall. If that checkbox is not checked, we need
    to add the Mailbox server's IP on the outbound rule for port 25.

  • #550 4.4.7 QUEUE.Expired; message expired ## With LastError "A storage transient failure has occurred during content conversion." In submission Queue. (Exchange 2013)

    Greetings,
    We seem to be having a problem with some users who are attempting to send e-mails from within the organisation to an external domain. Not all users are affected, and not all outgoing e-mails have this issue.
    Some e-mails get stuck in the submission queue. This is the error message in Last Error : "A storage transient failure has occurred during content conversion."
    Days later, the internal user who send the message gets a #550 4.4.7 QUEUE.Expired; message expired ## NDR.
    We did have some initial configuration issues, but these were fixed more than a week ago :
    - The external FQDN during EHLO was set to the wrong address, now pointing to the correct one.
    - SPF record was updated with new IP adress.
    Here is some additional information on the issue :
    - Not on any blacklists - checked using dnsbl.info
    - Telnet to remote servers works from exchange server, connections are accepted and can send mail.
    - Outbound SMTP test ran using Microsoft Remote Connectivity Analyser : Passed with both External (Static) and Smarthost IP.
    - This seems to happen only with emails that have an attachment and that are transfered, but only for the affected users. 
    - If content from these e-mails is manually copied over to a new email, email is sent to destination without problem.
    Configuration information :
    - Exchange 2013 running on Windows 2012 Datacenter with all latest updates.
    - Outgoing e-mail is sent via smarthost. Only one outbound transport rule is active.
    - Using internal DNS server.
    - There is only one mailbox database.
    Thank you for taking the time to read this!

    On Wed, 16 Jan 2013 15:31:14 +0000, Ipigi wrote:
    >Sorry, I often get some terms mixed up when I explain things as our users use the French version of outlook.
    >
    >E-mails are not transferred, but forwarded manually from their outlook. Message format in outlook is set to HTML and not Rich Text when they foward the e-mail.
    Do they forward the message as an attachment?
    >When forwarded internally, this is in the internet headers :
    >
    >Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary
    Within your organization I'm prety sure that messages will use TNEF.
    What does the message contain at the external recipient's side?
    >It really seems to me that Exchange is not converting RTF to Plain Text. The first link you provided states in it's final paragraph that Exchange should be doing this conversion.
    If you can, try creating a mail-enabed Contact for one of the external
    recipients and set the message format on that.
    >If I disabled TNEF as that link suggests, offending messages will get stuck in the submission queue again.
    >
    >I thank you for your help so far. This is not an issue I've had with any previous installations/migrations of Exchange that I have done.
    >
    >Please let me know if you need any additional information.
    Have you tried UNsetting TNEF on the remote domain?
    Set-RemoteDomain Default -TNEFEnabled $null
    That should leave it up to the client to determine the format. It's
    probably not what you're after, but see it makes a difference in the
    format.
    Rich Matheisen
    MCSE+I, Exchange MVP
    --- Rich Matheisen MCSE+I, Exchange MVP

Maybe you are looking for