Relaying an internal PHP application by Exchange 2013

Hello, dear Fellows,
We use an Exchange 2013 server
to relay two web applications via a Front-End Transport Receive Connector, properly configured.
All messages sent by the ASP Web Application, are received
by all the recipient domains.
But somes messages sent by the PHP Web Application are not received
by some Domains, remaining within the queue, with error messages:
554 5.4.4 SMTP.SEND.DNS.NonExistentDomain;non existent domain
451 4.4.0 Primary Target IP responded with 421 4.7.0 "ServerName" Too many errors "Cannot achieve “Exchange Server authentication”.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery
failed to all alternate hosts…"
Do you think this is a PHP problem, or an Exchange problem ?
Thanks for your answers
Djamal Belouizdad
Exchange Administrator

Hello Djamal,
I do not know if it's the right answer, but I'll
tell you about my problem and how we solved the
problem.
We had a problem with two sites developed
in PHP, when we send emails from applications
in PHP, recipients receive the email
but with an empty corp.
We just added a new line (un saut de ligne PHP <br /><br />)
at the beginning of corp email.
before the modification:
$Body="Bonjour,<br /><br />
            Vous avez reçu un fichier .......<br /><br />"
after the modification:
$Body="<br /><br />
Bonjour,<br /><br />
            Vous avez reçu un fichier .......<br /><br />"
Thanks
Samir TABTI
Administrateur Réseau et Système (AXONES)

Similar Messages

  • Configuring Lync Server 2013 to be a partner Application for Exchange 2013

    Hello Guys,
    I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever. 
    As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013. 
    But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
    I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain. 
    So I started to review the script to find the issue and I found that the script was configured  as below 
    $acceptedDomains = Get-AcceptedDomain ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains[0].Name;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    which is totally wrong as below: 
    firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain. 
    Not all customers configure the name of the Accepted Domain to be the Domain Name.
    Secondly  it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
    The first domain may be not the default Accepted Domain. 
    So I have configured the script as below
    $acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"}  ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains.DomainName;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    I hope This help. 
    Thanks 
    Ahmed Fouad

    Hi,
    This is helpful, thanks for sharing.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

    Hello,
    I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;
    Error:
    The following error was generated when "$error.Clear();
                        $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
                        $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
                        $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
                        if(test-path ($regPath))
                            Write-ExchangeSetupLog -info ("Removing " +  $RoleLanguagePackType + " Language Packs.");
                            Get-ChildItem ($regPath) | foreach{
                                if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                    $langPackPackageCode = $matches['ProductCode'];
                                    if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne
    0) {
                                        Write-ExchangeSetupLog -info ("Removing package
    $langPackPackageCode");
                                        $language = $langPackPackageCode.Substring(20,4);
                                        $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")
    + '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                        uninstall-MsiPackage -ProductCode ($langPackPackageCode)
    -LogFile ($logFilePath);
                            Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach
    ($_) {remove-item $_.fullname};
                            Write-ExchangeSetupLog -info "Remove Language Packs completed.";
            " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
    I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server.

            " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
    Hi,
    Based on this error, possible cause may the path of language package is too long. Please check the following things:
    Where is your language package installed? Please check it.
    Under 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}", please check the following entries. By default, it should be like this.
    InstallSource (Z:\Applications\Server\Exchange\2013\64-Bit\RTM\en\)
    ModifyPath (MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C})
    UninstallString MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C}
    Under 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup, check this entry MsiInstallPath. By default, the value should be “C:\Program Files\Microsoft\Exchange Server\V15\”
    Best Regartds.
    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]
    Lynn-Li
    TechNet Community Support

  • Exchange 2013 Outlook Client connectivity

    I'm migrating from Exchange 2010 to Exchange 2013 and on the final stages. I pointed the external and internal DNS records to Exchange 2013. I moved one mailbox to Exchange 2013 and then tried to create a new Outlook client profile and bring the mailbox
    up however the client would not connect. It stated trying to connect encrypted and unencrypted. It did not work. I checked nslookup and the IPs are all set pointing to Exchange 2013. I then checked my certificates. I have a certificate that is a wild card.
    When I checked assigned services on my wild card it had IIS and SMTP assigned. Also in IIS on the default site bindings what should you use as a certificate on the two https settings? Originally they were the local generated certificate. I changed them to
    the wild card no luck. Please assist.

    Try running through this and see if it gives you some ideas on what is wrong:
    https://testconnectivity.microsoft.com/
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Exchange 2013 Create an smtp relay to allow sending emails to other domains from web application

    Hello,
    We have an exchange 2013 and we want to allow a web application that is outside the organisation to send emails through our sever to external domain.
    Do we have to create an smtp receive or sending connector? How this on has to be configured ?
    Thank you in advance.
    m

    Hello Mehdi,
    be sure that you enable exchange servers permission and externally secured authentication after you create the receive connector.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. My blog:http://msibrahim.wordpress.com/

  • Exchange 2013 Relay issue (SMTP Authenticated)

    Hi,
    I installed Exch 2013 and is working great - both incoming mail and outgoing mail work fine in OWA and outlook.
    Problem we are having is SMTP authenticated relay. We install application on all client computers which sends emails externally/internally. 
    Though we had authenticated in application, we are not able to send emails externally. Internally it works fine from application.
    Our backup software stopped sending notifications on failures. Literally we are logging into each and every server and making sure backups are successful.
    We never had a problem with Exchange 2010
    I don't want to create relay and allow my whole ipaddress range (I think that's stupid)
    Can anyone please help?

    Hi,
    You could create a Receive connector on the 2013 Mailbox server, and then configure the Receive connector with the following properties:
    Create/configure a service account for the applications/copier to use.
    Create a new Receive connector with the Usage value 'Custom', and don't assign any permission groups to the connector.
    Specify the IP address(es) of the application servers/copiers as the only remote IP addresses that are allowed to use this Receive connector.
    Use the Add-AdPermission cmdlet to add the ms-Exch-SMTP-Submit permission to the Receive connector for the service account.
    The combination of restricting the IP addresses that the Receive connector listens to, and restricting permissions on the connector so that only the service account can send messages should do the trick.
    For more information, see these topics:
    Add-ADPermission
    Receive Connectors
    Receive Connector Permissions
    Link
    Deepak Kotian.
    MCP, MCTS, MCITP Server / Exchange 2010 Ent. Administrator
    Disclaimer:
    Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
    All the opinions expressed here is mine. This posting is provided "AS IS" with no
    warranties or guarantees and confers no rights.

  • Exchange 2013 External Relay gives me a headache... Anonymous relay fail to external address

    I tried to set up external relay on my Exchange 2013 but was not able to do it. I don't know what else to do. I tried these:
    http://technet.microsoft.com/en-us/library/bb232021.aspx
    and these (which is pretty much same thing)
    http://www.shudnow.net/2013/06/04/how-anonymous-relay-works-in-exchange-2013/
    http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
    http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
    http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
    But still no luck. Here is somewhat detailed description what I tried do accomplice. 
    Server which need  to send mail reports is sending these from web server on another location connected with site-to-site VPN to location server resides like on picture. I am able to send relay to all of
    addreses of local domain but when I tried to send mails to my clients to external e mail addresses exchange return me message unable to relay.
    Here is log from unsuccessfully operation
    Connecting to [smtp.mydomain.com] port [25]...
    220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 17:19:45 +0100
    >HELO webserver
    250 smtp.mydomain.com Hello [89.x.x.x]
    >MAIL FROM: <[email protected]>
    250 2.1.0 Sender OK
    >RCPT TO: <[email protected]>
    ERR: Received the following unexpected repsonse:
    550 5.7.1 Unable to relay
    >QUIT
    221 2.0.0 Service closing transmission channel
    Here is log from successfully operation:
    Connecting to [89.x.x.x] port [25]...
    220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 18:04:52 +0100
    >HELO webserver
    250 smtp.mydomain.com Hello [89.x.x.x]
    >MAIL FROM: <[email protected]>
    250 2.1.0 Sender OK
    >RCPT TO: <[email protected]>
    250 2.1.5 Recipient OK
    >RCPT TO: <[email protected]>
    250 2.1.5 Recipient OK
    >DATA
    354 Start mail input; end with <CRLF>.<CRLF>
    >From: Dane <[email protected]>
    >To: [email protected]
    >Subject: asd
    >Date: Fri, 24 Jan 2014 18:03:08 +0100
    >X-Mailer: Qm Version 2.1
    >MIME-Version: 1.0
    Content-type: text/plain
    >
    >test>
    250 2.6.0 <3ffb1fd6-e5e0-4232-9a6e-cac7b59db9df@exchange.mylocaldomain.local> [InternalId=6240587481093] Queued mail for delivery
    >QUIT
    221 2.0.0 Service closing transmission channel
    And here is picture:

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Regards,
    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 OWA/ECP HTTP 500 Internal Server Error

    So I know there are a lot of these threads, so I'll list what I've done and what I've tried so far.
    The setup is a pair of multirole servers with a DAG.  We have a root domain and sub domain.
    I've created 4 databases associated with the DAG, I successfully removed the default database on the 2nd mail server, then migrated the arbitration/system/discovery etc... mailboxes to one of the DAG databases.  I then removed the 1st mail server's default
    database after killing it's healthmailbox.  Rebooted the pair of servers and after that the ECP/OWA were inaccessible.
    To run tests I installed .NET 3.5 SP1 so I could run the ExBPA which really didn't get me anywhere.
    I can access the logon screen for both, but when I enter my username and password, I get the http 500 internal server error.
    I have used: Get-OwaVirtualDirectory -Server <server name> | fl *auth*
    To verify that basic and forms based auth are enabled, and they are.
    I've verified all services have started.
    I've tried to remove and re-add the app pools and the ecp virtual directories.
    http://social.technet.microsoft.com/Forums/ie/en-US/bb148ccb-a75e-4571-bfc7-76950f8e638e/exchange-2013-cu2-cant-access-ecp-unexpected-error-500?forum=exchangesvrgeneral
    I've tried to use ADSI Edit to purge the Canary Data.
    http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients
    I've tried to run test-ecpconnectivity but stated that the test user wasn't available.
    So I tried to use the powershell script to create a new test user, but it doesn't seem to work either I think it's related to the exchange machine not being a member of the root domain, but not sure on that one.
    I seem to be able to manage everything with command-line still.  Create and remove mailboxes etc.
    As far as errors/warnings go exchange wise I get an ASP.NET 4.0 warning Event ID 1309 stating that an unhandled exception occurred, which seems to coincide with the logon attempt.  I'm sure this has something to do with it, but not real sure what yet.
     Nothing I can see within the logon attempt from IIS or anything else really.
    I think that's about all I have.

    Hi,
    Please check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It maybe the incompletely installation of Framework that causes this error.
    If so, We can try to run the following command as Administrator:
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
    Or change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS to have a try.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • How to configure AD on windows 2012 server for Exchange 2013 internal and external email flow

    Dear Experts,
    I have to configure exchange 2013 on Windows server 2012 STD. Company has registered Static IP addresses and can get the MX record pointing to any of this Static IP.  
    The registered domain name is e.g.  contoso.com. 
    a. What should I use as domain name on AD? contoso.com or contoso.local
    b. Is it recommended to have two different servers  for AD and Exchange?
    c. What should be my connector settings for mail flow?
    d. how can I set 2 email servers in company for load balancing?

    Hi,
    a, I suggest use contoso.com as domain name. It is convenient to add urls into our certificate for internal and external mail flow.
    b, Recommended that installing AD
    and Exchange Server on two separate
    Servers. If Exchange Server downed unfortunately, it can prevent AD server from crushing at the same time.
    c, Found some articles for your reference:
    Configure Mail Flow and Client Access
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
    Configuring Outbound Mail Flow in Exchange Server 2013
    http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
    d, Load Balancing
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Internal email marked as Junk - Exchange 2013

    Hello,
    As per the title, I have an issue whereby internal email from a reporting server is being classed as Junk in Outlook 2010 and 2013 for all recipients.
     -The Junk-email filtering level for all users in Outlook is set to "Low" and is applied via group policy.
     -I have anti-spam agents installed on all Exchange mailbox servers, but the "InternalMailEnabled" parameter is set to "false" for all agents.
     -The receive connector used to receive internal email has the "Externally secured" flag set, which allows spam-filtering to be bypassed.
     -The "InternalSMTPServers" parameter of the transport config contains the IP of the sending server.
    - The email address has been added to several users "Safe Senders" list in Outlook.
     -I have a transport rule set up to bypass spam filtering for the sending address of the [email protected], yet the email header on any of these messages does not contain the "SCL -1" stamp as per the below:
    #↓    Header    Value
    1    MIME-Version    1.0
    2    From    <[email protected]>
    3    To    <[email protected]>, <[email protected]>
    4    Date    Tue, 10 Mar 2015 07:35:32 +0000
    5    Subject    Report was executed at 10/03/2015 07:35:08
    6    Content-Type    multipart/mixed; boundary="--boundary_90_638c99de-c35d-4d06-b992-536e14201c6d"
    7    Message-ID    <[email protected]>
    8    Return-Path    [email protected]
    9    X-MS-Exchange-Organization-AuthSource    SERVER01.domain.localnet
    10    X-MS-Exchange-Organization-AuthAs    Internal
    11    X-MS-Exchange-Organization-AuthMechanism    10
    12    X-MS-Exchange-Organization-Network-Message-Id    8d357628-f2e9-48d5-77e2-08d2291beca4
    13    X-MS-Exchange-Organization-AVStamp-Enterprise    1.0
    Can anyone assist in explaining why these emails are being continually marked as Junk in Outlook, and any further troubleshooting steps.
    Thanks
    Matt

    Hello
    please show transport rules settings.
    sorry my english
    Hello Sneff,
    Transport Rule output below
    Thanks
    RunspaceId                                   : 503d1c3b-4ab8-4e90-a5dd-a3eefdcbe404
    Priority                                     : 18
    DlpPolicy                                    : 
    DlpPolicyId                                  : 00000000-0000-0000-0000-000000000000
    Comments                                     : 
    ManuallyModified                             : False
    ActivationDate                               : 
    ExpiryDate                                   : 
    Description                                  : If the message:
                                                       Includes these patterns in the From address: 
                                                   '[email protected]'
                                                       and Is received from 'Inside the organization'
                                                   Take the following actions:
                                                       Set the spam confidence level (SCL) to '-1'
    RuleVersion                                  : 15.0.0.0
    Conditions                                   : {FromAddressMatches, FromScope}
    Exceptions                                   : 
    Actions                                      : {SetSCL}
    State                                        : Enabled
    Mode                                         : Enforce
    RuleErrorAction                              : Ignore
    SenderAddressLocation                        : HeaderOrEnvelope
    RuleSubType                                  : None
    UseLegacyRegex                               : False
    From                                         : 
    FromMemberOf                                 : 
    FromScope                                    : InOrganization
    SentTo                                       : 
    SentToMemberOf                               : 
    SentToScope                                  : 
    BetweenMemberOf1                             : 
    BetweenMemberOf2                             : 
    ManagerAddresses                             : 
    ManagerForEvaluatedUser                      : 
    SenderManagementRelationship                 : 
    ADComparisonAttribute                        : 
    ADComparisonOperator                         : 
    SenderADAttributeContainsWords               : 
    SenderADAttributeMatchesPatterns             : 
    RecipientADAttributeContainsWords            : 
    RecipientADAttributeMatchesPatterns          : 
    AnyOfToHeader                                : 
    AnyOfToHeaderMemberOf                        : 
    AnyOfCcHeader                                : 
    AnyOfCcHeaderMemberOf                        : 
    AnyOfToCcHeader                              : 
    AnyOfToCcHeaderMemberOf                      : 
    HasClassification                            : 
    HasNoClassification                          : False
    SubjectContainsWords                         : 
    SubjectOrBodyContainsWords                   : 
    HeaderContainsMessageHeader                  : 
    HeaderContainsWords                          : 
    FromAddressContainsWords                     : 
    SenderDomainIs                               : 
    RecipientDomainIs                            : 
    SubjectMatchesPatterns                       : 
    SubjectOrBodyMatchesPatterns                 : 
    HeaderMatchesMessageHeader                   : 
    HeaderMatchesPatterns                        : 
    FromAddressMatchesPatterns                   : {[email protected]}
    AttachmentNameMatchesPatterns                : 
    AttachmentExtensionMatchesWords              : 
    AttachmentPropertyContainsWords              : 
    ContentCharacterSetContainsWords             : 
    HasSenderOverride                            : False
    MessageContainsDataClassifications           : 
    SenderIpRanges                               : 
    SCLOver                                      : 
    AttachmentSizeOver                           : 
    MessageSizeOver                              : 
    WithImportance                               : 
    MessageTypeMatches                           : 
    RecipientAddressContainsWords                : 
    RecipientAddressMatchesPatterns              : 
    SenderInRecipientList                        : 
    RecipientInSenderList                        : 
    AttachmentContainsWords                      : 
    AttachmentMatchesPatterns                    : 
    AttachmentIsUnsupported                      : False
    AttachmentProcessingLimitExceeded            : False
    AttachmentHasExecutableContent               : False
    AttachmentIsPasswordProtected                : False
    AnyOfRecipientAddressContainsWords           : 
    AnyOfRecipientAddressMatchesPatterns         : 
    ExceptIfFrom                                 : 
    ExceptIfFromMemberOf                         : 
    ExceptIfFromScope                            : 
    ExceptIfSentTo                               : 
    ExceptIfSentToMemberOf                       : 
    ExceptIfSentToScope                          : 
    ExceptIfBetweenMemberOf1                     : 
    ExceptIfBetweenMemberOf2                     : 
    ExceptIfManagerAddresses                     : 
    ExceptIfManagerForEvaluatedUser              : 
    ExceptIfSenderManagementRelationship         : 
    ExceptIfADComparisonAttribute                : 
    ExceptIfADComparisonOperator                 : 
    ExceptIfSenderADAttributeContainsWords       : 
    ExceptIfSenderADAttributeMatchesPatterns     : 
    ExceptIfRecipientADAttributeContainsWords    : 
    ExceptIfRecipientADAttributeMatchesPatterns  : 
    ExceptIfAnyOfToHeader                        : 
    ExceptIfAnyOfToHeaderMemberOf                : 
    ExceptIfAnyOfCcHeader                        : 
    ExceptIfAnyOfCcHeaderMemberOf                : 
    ExceptIfAnyOfToCcHeader                      : 
    ExceptIfAnyOfToCcHeaderMemberOf              : 
    ExceptIfHasClassification                    : 
    ExceptIfHasNoClassification                  : False
    ExceptIfSubjectContainsWords                 : 
    ExceptIfSubjectOrBodyContainsWords           : 
    ExceptIfHeaderContainsMessageHeader          : 
    ExceptIfHeaderContainsWords                  : 
    ExceptIfFromAddressContainsWords             : 
    ExceptIfSenderDomainIs                       : 
    ExceptIfRecipientDomainIs                    : 
    ExceptIfSubjectMatchesPatterns               : 
    ExceptIfSubjectOrBodyMatchesPatterns         : 
    ExceptIfHeaderMatchesMessageHeader           : 
    ExceptIfHeaderMatchesPatterns                : 
    ExceptIfFromAddressMatchesPatterns           : 
    ExceptIfAttachmentNameMatchesPatterns        : 
    ExceptIfAttachmentExtensionMatchesWords      : 
    ExceptIfAttachmentPropertyContainsWords      : 
    ExceptIfContentCharacterSetContainsWords     : 
    ExceptIfSCLOver                              : 
    ExceptIfAttachmentSizeOver                   : 
    ExceptIfMessageSizeOver                      : 
    ExceptIfWithImportance                       : 
    ExceptIfMessageTypeMatches                   : 
    ExceptIfRecipientAddressContainsWords        : 
    ExceptIfRecipientAddressMatchesPatterns      : 
    ExceptIfSenderInRecipientList                : 
    ExceptIfRecipientInSenderList                : 
    ExceptIfAttachmentContainsWords              : 
    ExceptIfAttachmentMatchesPatterns            : 
    ExceptIfAttachmentIsUnsupported              : False
    ExceptIfAttachmentProcessingLimitExceeded    : False
    ExceptIfAttachmentHasExecutableContent       : False
    ExceptIfAttachmentIsPasswordProtected        : False
    ExceptIfAnyOfRecipientAddressContainsWords   : 
    ExceptIfAnyOfRecipientAddressMatchesPatterns : 
    ExceptIfHasSenderOverride                    : False
    ExceptIfMessageContainsDataClassifications   : 
    ExceptIfSenderIpRanges                       : 
    PrependSubject                               : 
    SetAuditSeverity                             : 
    ApplyClassification                          : 
    ApplyHtmlDisclaimerLocation                  : 
    ApplyHtmlDisclaimerText                      : 
    ApplyHtmlDisclaimerFallbackAction            : 
    ApplyRightsProtectionTemplate                : 
    SetSCL                                       : -1
    SetHeaderName                                : 
    SetHeaderValue                               : 
    RemoveHeader                                 : 
    AddToRecipients                              : 
    CopyTo                                       : 
    BlindCopyTo                                  : 
    AddManagerAsRecipientType                    : 
    ModerateMessageByUser                        : 
    ModerateMessageByManager                     : False
    RedirectMessageTo                            : 
    RejectMessageEnhancedStatusCode              : 
    RejectMessageReasonText                      : 
    DeleteMessage                                : False
    Disconnect                                   : False
    Quarantine                                   : False
    SmtpRejectMessageRejectText                  : 
    SmtpRejectMessageRejectStatusCode            : 
    LogEventText                                 : 
    StopRuleProcessing                           : False
    SenderNotificationType                       : 
    GenerateIncidentReport                       : 
    IncidentReportOriginalMail                   : 
    IncidentReportContent                        : 
    RouteMessageOutboundConnector                : 
    RouteMessageOutboundRequireTls               : False
    ApplyOME                                     : False
    RemoveOME                                    : False
    GenerateNotification                         : 
    Identity                                     : SQLReportingServices
    DistinguishedName                            : CN=SQLReportingServices,CN=TransportVersioned,CN=Rules,CN=Transport 
                                                   Settings,CN=Domain,CN=Microsoft 
                                                   Exchange,CN=Services,CN=Configuration,DC=domain,DC=localnet
    Guid                                         : 11f1083e-9e12-45d1-8e8f-3b878d4ca183
    ImmutableId                                  : 11f1083e-9e12-45d1-8e8f-3b878d4ca183
    OrganizationId                               : 
    Name                                         : SQLReportingServices
    IsValid                                      : True
    WhenChanged                                  : 10/03/2015 13:23:11
    ExchangeVersion                              : 0.1 (8.0.535.0)
    ObjectState                                  : Unchanged
    Matt

  • Exchange 2013 autodiscover finds external & internal SSL certificate causing autodiscover to fail

    <p>Hi:</p><p>I'm currently working on a windows 2012 server, with exchange 2013, lets say our internal domain is "cars.com" and ALSO the case for&nbsp;our external domain. We have purchased an SSL wildcard positive certificate
    *.cars.com so that we could configure Outlook Anywhere, we have created the needed DNS records at godaddy and our internal server, OWA, ECP it all works if you go to&nbsp; <a href="https://bird.cars.com/owa">https://bird.cars.com/owa</a>
    because we have a DNS record for bird in godaddy and out local server, so all of that is working like a pro ! here comes the tricky part, our website is registered in godaddy but hosted by someone else a company called poetic systems; when we test the connection
    with the remote connectivity analyzer website we get a very peculiar error that says SSL certificate not valid, now it provides the name of the certificate it found and is not ours, we found that the hosting company is listening in port 443, therefore, it
    is pulling their self signed certificate also, does anyone have a fix for this, I have done this same setup before for other companies and this is the first time a situation like this happens. I REALLY NEED HELP !!!!!</p>

    Hi,
    According to your description, there is a certificate error when you test Outlook Anywhere connection by ExRCA.
    If I misunderstand your meaning, please feel free to let me know.
    And to understand more about the issue, I’d like to confirm the following information:
    What’s detail error page?
    Check the Outlook Anywhere configuration: get-outlookanywhere |fl
    Check the certificate : get-exchangecertificate |fl
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Error 550 5.7.1 unable to relay with SMTP PORT 25 Exchange 2013

    Hi All,
    I know this issue has been posted for a while, but still can't resolved issue. We've new Exchange 2013 SP1 (CU4) installation, everything is working properly, the OWA, Exchange Client Connection, SMTP/POP with SSL, except with SMTP Using Port 25 Non-Encrypted
    Connection.  
    If I'm using the SMTP Port 25 without TICK "My Outgoing Server (SMTP) Requires authentication", I've got the error: "550 5.7.1 Unable to relay", but if I TICK the option above, my message will be deliver without any error, how do i get
    rid this problem, I need to UN-TICK the option above for the time being, since we've hundreds email account, I want to avoid to educate and tell the user and even remote their PC, just to configure this issue, it will drive me crazy, we're going to use the
    Exchange Client Connection in the future, If everything is smooth and ok.
    I research this problem on the Internet and of course with TECHNET, but still can't, anyone can help me on this?
    fyi, I tried so many things, delete the default the Default Front End Transport for Port 25, it also not fix my issue.
    Thx
    Irwan

    Hi
    You can paste the output of below result
    Get-receiveconnector | fl name,bindings,PermissionGroups
    I think your default receive connector should be missing out some permissions.
    Also try to see if you get any message on protocol logs and paste them too
    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 on http://exchangequery.com Thanks Sathish
    (MVP)

  • Exchange 2013 DNS for internal and external domain

    Hi All,
    I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
    We have an Active Directory domain myinternaldomain.net, and we have a public domain
    mypublicdomain.com and we have setup email policy to have
    mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
    mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
    hardware LB is out of scope due to budget constrains.
    We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
    that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
    Thanks

    Hi Sccmnb,
    You can easily achieve this using split DNS.
    Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
    Reverse proxy server IP.
    Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
    The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
    SN= mail.mypublicdomain.com
    SAN= autodiscover.mypublicdomain.com
    You don't need to have the active directory domain name present in the certificate.
    Additional  to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
    Some additional Info:
    *Internal vs. External Namespaces
    Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
    based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
    This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
    Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
    *Managing Certificates in Exchange Server 2013 (Part 2)
    *Nice step by step article
    Designing a simple namespace for Exchange 2013
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Maybe you are looking for

  • How can I use Automator or AppleScript to get text from a web page and paste it in execl?

    I don't know how to make scripts or complexed automator workflows... that's why I'm asking. I'm trying to make a simple app or script to ask me what text to extract from a web page, like name, address and phone number of a web page and paste each one

  • How to mark row in OO ALV ?

    Hi , I am using OO editable ALV . Method set_table_for_first_display has been used . In the report, user can select a row /rows and click on button 'EDIT' in the toolbar . Then one pop up screen will be displayed where user can change the fields . Th

  • Staroffice 8 / Outlook Adressbook

    It would like to use my Outlook conatcts ( not Outlook Express !). How do I do this. Very likely it's something very simple, but I am st........ Thanks in advance Michael

  • Cartoon Network issue with Flash Player 11.6.602.180

    My son cant log into the http://www.cartoonnetwork.com.br/#/toonix using the new version of Flash Player 11.6.602.180. I cant uninstall it even with the uninstaller from the site.

  • Ipod problem, someone help me out

    When I update my ipod it gets to about the 150th song or so and then it freezes up and makes some "skipping" noises. I've let it work through this issue before but the songs that it froze on didn't go on my ipod correctly and therefore would cause th