Changing FQDN for Send Connector

I have Exchange 2013 CU3 here, all is working fine, as far as i see.
Recently i used DNSStuff for checking thing and discovered that SMTP Abuse results give me:
EHLO dnsstuff.com host.domain.local
and not host.domain.com
Checked my Send Connector - Internet settings in Scoping section
FQDN:
Specify the FQDN this connector will provide in response to HELO or EHLO.
is set to host.domain.com not local.
Should i also change the same on Receive connectors?
If so, how? Because it gives me:
error
If the AuthMechanism attribute on a Receive connector contains the value
ExchangeServer, you must set the FQDN parameter on the Receive connector
to one of the following values: the FQDN of the transport server
"HOST.domain.local", the NetBIOS name of the transport server "HOST", or
$null.

Sorry for late replies..
it is still unclear to me. I made new domain company.local and installed Exchange 2013, All is working good.
One thing bothers me.. for example NDR from my server includes company.local server, for example NDR to non existing user:
Diagnostic information for administrators:
Generating server: SERVER.company.local
Remote Server  returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Original message headers:
Received: from SERVER.company.local (10.0.0.69) by SERVER.company.local (10.0.0.69)
with Microsoft SMTP Server (TLS) id 15.0.775.38; Mon, 14 Apr 2014 14:41:20
+0200
Received: from mail-wi0-f174.google.com (209.85.212.174) by SERVER.company.local
(10.0.0.69) with Microsoft SMTP Server id 15.0.775.38 via Frontend Transport;
or SPF check from the same NDR
Received-SPF: Pass (SERVER.company.local: domain of GMAIL_ADDRESS
designates 223.85.333.111 as permitted sender) receiver=SERVER.company.local;
client-ip=223.85.333.111; helo=mail-wi0-f174.google.com;
Is it all OK?
Thank you

Similar Messages

  • Changing the FQDN for receive connectors on Edge servers

    Hi everyone,
    I need to make a change to the default receive connector on our edge servers. Currently they have mx1.internaldomain.intra and mx2.internaldomain.intra, I need to change this to mx1.publicdomain.com and mx2.publicdomain.com. This is primarily in order to
    get TLS to work, checktls.com shows that it cannot resolve the current names, for obvious reasons.
    These receive connectors are for receiving inbound mail from the internet only.
    The question I wanted to ask was - if I make this change, will I have to redo the edge subscription for these servers?
    Some people here seem to think edgesync will be broken if this is changed, I personally think it'll be fine. As we don't have a test environment I can't check on that, and also our DR site was configured correctly (as I configured this myself ;) )
    Does anyone have any concrete information regarding this? I have tried so many searches but they haven't produced anything definitive.
    Thanks in advance
    Andoni

    I changed this and TLS starts OK now. checktls.com produces the expected results (OK). There is no need to redo the edgesync as that's only used to pass credentials between edge and CAS/HT servers.
    Closing this post.

  • How to send email to a SMTP server over a secure channel using STARTTLS setting of a send connector (Exchange and SMTP server are in the same domain)

    I’m trying to send email using exchange send connector STARTTLS setting to the SMTP server. I have read multiple documents on configuring TLS for send connector, but they talks about outbound connections to internet facing servers. My Exchange 2013 and SMTP
    server is in the same domain (let’s say A.com) and I’m creating dummy domains on my SMTP server (e.g.
    [email protected],
    [email protected] ) and their respective send connectors on the exchange server end. In the smart host section added the IP address of the SMTP server and in the scoping section added the SMTP domain address (e.g. dummy1.local ). In the FQDN field, added
    the FQDN of the exchange server 2013 which certificate is enabled with SMTP service.
    Could you tell me a step by step procedure, where I’m going wrong or any extra settings needs to added?
    Presently, it is giving me an error that 530 5.5.1 TLS encrypted connection is required.
    Note: I’ve created the Microsoft CA certificates for the SMTP and exchange servers and imported them in the personal certificate container. In which, the exchange certificate is created with FQDN name of the server and enabled for the SMTP service.
    I’m using OPENSSL certificate for making the SMTP server TLS enabled. (let me know, if I need to import the OPENSSL certificate anywhere on the exchange end)?
    Thanks!

    -IgnoreSTARTTLS is set to false on the send connector properties.
    I'm trying to established a HTTP over TLS connection. I'm not using mutual TLS between these two server.
    The send connector protocol logging is attached as below,
    2014-09-22T20:09:45.468Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,2,10.219.3.74:24939,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
    2014-09-22T20:09:45.546Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,3,10.219.3.74:24939,10.219.3.73:25,>,EHLO Exchange.A.local,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,4,10.219.3.74:24939,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,5,10.219.3.74:24939,10.219.3.73:25,<,250-SIZE,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,6,10.219.3.74:24939,10.219.3.73:25,<,250-8BITMIME,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,7,10.219.3.74:24939,10.219.3.73:25,<,250-BINARYMIME,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,8,10.219.3.74:24939,10.219.3.73:25,<,250-PIPELINING,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,9,10.219.3.74:24939,10.219.3.73:25,<,250-HELP,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,10,10.219.3.74:24939,10.219.3.73:25,<,250-DSN,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,11,10.219.3.74:24939,10.219.3.73:25,<,250-CHUNKING,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,12,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,13,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,14,10.219.3.74:24939,10.219.3.73:25,<,250-STARTTLS,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,15,10.219.3.74:24939,10.219.3.73:25,<,250-DELIVERBY,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,16,10.219.3.74:24939,10.219.3.73:25,<,250-MT-PRIORITY,
    2014-09-22T20:09:45.640Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,17,10.219.3.74:24939,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
    2014-09-22T20:09:45.655Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,18,10.219.3.74:24939,10.219.3.73:25,>,STARTTLS,
    2014-09-22T20:09:45.671Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,19,10.219.3.74:24939,10.219.3.73:25,<,220 2.7.0 Ready to start TLS,
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,20,10.219.3.74:24939,10.219.3.73:25,*,,Sending certificate
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,21,10.219.3.74:24939,10.219.3.73:25,*,CN=Exchange.A.local,Certificate subject
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,22,10.219.3.74:24939,10.219.3.73:25,*,"CN=DC-CA, DC=A, DC=local",Certificate issuer name
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,23,10.219.3.74:24939,10.219.3.73:25,*,63E7E70100000000000B,Certificate serial number
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,24,10.219.3.74:24939,10.219.3.73:25,*,CAEB1200CDF49715E5F2E4B8315EFDDC01F8F945,Certificate thumbprint
    2014-09-22T20:09:45.780Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,25,10.219.3.74:24939,10.219.3.73:25,*,Exchange.A.local,Certificate alternate names
    2014-09-22T20:09:46.654Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,26,10.219.3.74:24939,10.219.3.73:25,-,,Local
    2014-09-22T20:09:46.669Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,0,,10.219.3.73:25,*,,attempting to connect
    2014-09-22T20:09:46.685Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,1,10.219.3.74:24940,10.219.3.73:25,+,,
    2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,2,10.219.3.74:24940,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
    2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,3,10.219.3.74:24940,10.219.3.73:25,>,EHLO Exchange.A.local,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,4,10.219.3.74:24940,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,5,10.219.3.74:24940,10.219.3.73:25,<,250-SIZE,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,6,10.219.3.74:24940,10.219.3.73:25,<,250-8BITMIME,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,7,10.219.3.74:24940,10.219.3.73:25,<,250-BINARYMIME,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,8,10.219.3.74:24940,10.219.3.73:25,<,250-PIPELINING,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,9,10.219.3.74:24940,10.219.3.73:25,<,250-HELP,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,10,10.219.3.74:24940,10.219.3.73:25,<,250-DSN,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,11,10.219.3.74:24940,10.219.3.73:25,<,250-CHUNKING,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,12,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,13,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,14,10.219.3.74:24940,10.219.3.73:25,<,250-STARTTLS,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,15,10.219.3.74:24940,10.219.3.73:25,<,250-DELIVERBY,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,16,10.219.3.74:24940,10.219.3.73:25,<,250-MT-PRIORITY,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,17,10.219.3.74:24940,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,18,10.219.3.74:24940,10.219.3.73:25,*,,sending message with RecordId 52652004081667 and InternetMessageId <[email protected]>
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,19,10.219.3.74:24940,10.219.3.73:25,>,MAIL FROM:<> SIZE=7653 BODY=BINARYMIME,
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,20,10.219.3.74:24940,10.219.3.73:25,>,RCPT TO:<[email protected]>,
    2014-09-22T20:09:46.825Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,21,10.219.3.74:24940,10.219.3.73:25,<,530 5.5.1 A TLS-encrypted connection is required,
    2014-09-22T20:09:46.950Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,22,10.219.3.74:24940,10.219.3.73:25,<,503 5.5.1 unexpected RCPT command,
    2014-09-22T20:09:46.981Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,23,10.219.3.74:24940,10.219.3.73:25,>,RSET,

  • Adding alternative FQDN for local domain.

    Hi,
    I'm trying to configure RDS for my standalone Windows Server 2012 Essentials and it's almost done.
    (Probablly) last thing i need to do is to change FQDN for my local domain to .com to use RDS externaly.
    So, like i said, i've done dyndns config, added ssl cert, configured RDWeb, RD Gateway, RD License and RD Broker.
    Now, when i'm logging into remote.mydomain.com/RDWeb , i can login with Active Directory credentials, get rdp i try login into server. But i can only try, becuase there is an error about wrong FQDN for server (know and not new error for anyone). So, what I
    had done was changing FQDN for my domain by this powershell script http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80 (if anyone had problems with digitally unsigned script, google for "Set-ExecutionPolicy Unrestricted"), in
    theory, this script changed FQDN, but in reality, i still have same problem trying to connect externally.
    I also read that i should add new DNS Zone for my .com domain and there add (A) record for my subdomain for remote desktop, that points to internal IP adress of my server. When i tried that, it was even worse because i couldn't even open RDWeb site. When that
    dns zone was deleted, everything came back to previous state.
    And now i'm here, out of ideas. Any suggestion what I did wrong? Maybe it was something with this DNS Zone for .com ? Maybe there should be Zone, but not normal one but "stub zone"?
    I would be happy for any suggestion.

    " suspect we may have a basic mis-understanding of what each of us is trying to say.  Let me try again. 
    There are (at least) three ways to reach a LAN computer from the internet with Essentials.  Remote Web Access, direct RDP and VPN.  There are also third party solutions, such as Go To My PC and Log Me In.  The third party type
    usually involve a subscription model with recurring charges, the others may involve a fee for SSL certificates, but they are (usually) much less expensive and do not rely on a third party."
    Yes, i can agree we difinitelly had problem with mis-uderstanding so, sorry for that. I was talking about direct RDP to my server because Anywhere Access is already configured (but remote desktop from there to server opened only Essential Dashboard, that's
    why i left this solution). Also, like i said, i'm aware of risks and i'll
    take responsibility for that.
    "Direct RDP is configured at the router and points the port (3389, but it can be changed) to the IP of the device you want to contact.  then, simply opening the RDP applet on your remote computer and typing in the public IP of the router/firewall
    will automatically connect you to the chosen computer.  This is a very high security risk and should be avoided when ever possible."
    Here is double facapalm for me - when you wrote about 3389 TCP port, i got enlightenment that i didn't do that (because i ealier tried to work on 443 with Anywhere Access and forgot about it), also information i got after tries to connect weren't usefull neither
    - because Windows gave me back information about wrong FQDN, i was strictly focused on that problem, but like we know now, problem was in much different place. When i opened that port, everything started to be like i wanted (i also find out, after testing
    RDP client from remoteapp in web menu that why i'm using this when i want to used direct RDP anyway). So much facepalm.
    Next thing for now will be different port then 3389 and in future, VPN instead of direct RDP.
    Anyway, really, thanks for help!

  • Providing external url for the fqdn for webfeed returns error in eventlog that shows internal url is being used - how to change to the external url?

    I've got my Rdweb accessible on both my internal and external network by using split dns locally to resolve the external url (remote.domain.com/rdweb) to resolve and everything works fine. However users don't want to use the rdweb interface (as it is slower
    than just clicking on a rdp shortcut.
    Following the notes at http://social.technet.microsoft.com/wiki/contents/articles/14488.distribution-of-remote-apps-and-desktops-in-windows-server-2012.aspx - I've tried to set up the webfeed on a Win7+ machine but when I enter the external url that
    is protected by an SSL cert the eventlog shows that the internal address is being used and it doesn't match the certificate. - "There is a problem with this connection's security certificate.
    The remote computer cannot be authenticated due to problems with its security certificate.                        
    Security certificate problems might indicate an attempt to fool you or intercept data you send to the remote computer.                       
    Windows cannot continue setting up this connection. Contact your workplace administrator for assistance.                         
    Connection name:
    Connection URL: https://internalservername/rdweb/feed/webfeed.aspx
    How do I set the servers to use the external address rather than the internal one - i'm assuming it's similar to exchange's
    Set-webservicesvirtualdirectory command but I can't find the equivalent command documented anywhere.
    http://absoblogginlutely.net

    Hi,
    Thank you for posting in Windows Server Forum.
    Please check below mention point. 
    •  Create a relevant DNS entry in the mentioned zone to point to the RDS environment’s internal IP address
    •  Create a relevant DNS entry in external DNS to point to the firewall which is publishing RDS’s external IP address
    •  You can use the below mention script to change the FQDN of the RDP files provided by RD Web Access / RemoteApp and Desktop connection feed. 
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    In addition please check below mention thread.
    How do I change the URL to the Remote Web Access server in Windows Server 2012?
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/67dfab70-7e10-4e0b-a3c8-63ce776f2355/how-do-i-change-the-url-to-the-remote-web-access-server-in-windows-server-2012?forum=winserverTS
    Apart from this, also check the settings under; IIS in RDWeb Server as per below mention path.
    Expand the default Website >Pages >Application Settings >DefaultTSGateway >
    Enter the external address (FQDN) of the RD Gateway in the Value Field.
    Hope it helps!
    Thanks,
    Dharmesh

  • Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

    I am in the final stages of a 2007->2013 migration that has gone very well.  I was just about to move my Send Connector over to the Exchange 2013 side when my monitors alarmed that "Transport.ServerCertMismatch.Monitor" had gone unhealthy.
    There is not a whole lot of information out there, but I did find this in each of the MBX logs:
    Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support
    the STARTTLS SMTP verb for the connector Internet e-mail with a FQDN parameter of mail.domain.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there
    is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
    I checked my SAN and I do have mail.domain.com in it.  I also confirmed that the Send Connector was using mail.domain.com as its HELO/EHLO reply.  I have cycled the service and that did not seem to help either.  Mail will still flow in my
    testing, but I do not like unhealthy statuses so I would prefer to fix it.
    Thoughts?

    Did you install and enable an SSL certificate with the "mail.domain.com" SAN on the Exchange 2013 CAS for the available Exchange services?
    Normally, when migrating from Exchange 2007, you need to request a new SSL certificate which includes the legacy namespace in the SAN field and install it both on the new Exchange 2013 and the legacy Exchange 2007 servers.
    Step by Step Screencasts and Video Tutorials

  • Send connector for forwarded emails not being used by Exchange 2013

    Hi we have 3 Exchange 2013 CU5 servers in a DAG setup and need to forward emails for some of the users to another domain. The problem is our outgoing spam filter seems to quarantine a lot of these emails which are  not spam. The problem is that I
    created a send connector for  the domain we are forwarding to (say contonso.com for illustrative purposes). Gave the send connector the name contonso.com, selected use MX record (didn't select Use the external DNS lookup settings on servers with transport
    roles) and added contonso.com in the address space gave it cost of 1. Added all the exchnage servers under source server. And clicked save. I then changed the cost to 2 on the main send connector with the domain as * which goes trhough our oput bound spam
    filter yet email I  send to one of the recipients with a forward inplace still go through that connector. Can anyone tell what i'm doing wrong or explain why this wouldn't work as expected ?   

    Easy question, did you enable the connector? :)
    Do you have more than one site in your org?
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Send connector with smart host redirection for particular domain

    Hello,
    We have quite big environment with Ex2007 CCR cluster with 2x CAS/HUB and 2x Edge servers with few accepted authoritative domains for several countries. Currently all mails from these are routed through one send connector.
    We're moving to a different mail filtering service and I wanted to setup one of our domains to send through the new service to get it all setup and working correctly before moving the other domains over to it.
    So i have configured dedicated new custom send connector ( in accordance with techent article: http://technet.microsoft.com/en-us/library/aa998814%28v=exchg.80%29.aspx) for one of our domains let's say contoso.com with priority 1, and in next step i have
    entered smart host ip's and at the end source servers (2x edge servers).
    I have spotted that mail would still not send through my new send connector for those with email addresses with that domain. I turned on verbose logging but still all emails are not going through new connector. I checked that changes were replicated succesfully
    on Edge servers and I restarted  on Cas/Hub machines "EdgeSync" service but still no luck.
    Please help me did I forgot to check/change something?

    Let me be sure I understand how you have your new send connector configured, so I don't give you the wrong information.  You said you configured the new send connector with the contoso.com email domain.  From how you said it, though ("one of
    our domains"), it appears that email domain is one of your internal email domains.  If this is the case, this is why this send connector isn't being used - the send connector will send only to those email domains listed in the address
    space tab.  If I am right, it will never send to any external recipients with an contoso.com email address - those mailboxes are internal.  If you have an external SMTP domain in that list (such as hotmail.com), you should see messages sent to recipients
    on that system through this connector.
    If I am not right in how I read your posting, let me know so we can figure out how to get your send connector working properly.

  • Required Changes in FCC Paramenters for Sender File Adapter.

    Hi
    I am Doing File-File Scenario.I am using FCC in the Sender File Adapter. I have defined the structure as below.
    My Source Structure
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Source xmlns:ns0="http://city.net/filecopy">
       <Message>
          <Id>123</Id>
          <Head>
             <Id>123</Id>
             <Filename>test.xml</Filename>
          </Head>
          <Body>Helloworld</Body>
       </Message>
    </ns0:MT_Source_FILE>
    So for the above structure, I have defined the FCC Parameters as
    Document Name: MT_Source (Message Type)
    Document Namespace:http://city.net/filecopy(Namespace)
    Recordset Name: Message (root node)
    Recordset Structure: Message,1,Head,1
    Recordset Sequence: Ascending
    Recordsets per message:1
    Keyfield Type: string
    In the Table Rows I have defined
    Message.fieldFixedLengths: 3,10
    Message.fieldNames: Id, Body
    Message.fieldSeparator: ,
    Message.endSeparator: 'nl'
    Head.fieldFixedLengths: 3,8
    Head.fieldSeparator: ,
    Head.endSeparator: 'nl'
    Head.fieldNames: Id, Filename.
    My Input Text file
    123,Helloworld
    123,text.xml
    I am Getting Output as
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns:MT_Source xmlns:ns="http://city.net/filecopy">
    - <Message>
    - <Message>
      <Id>123</Id>
      <Body>HelloWorld</Body>
      </Message>
    - <Head>
      <Id>123</Id>
      <Filename>test.xml</Filename>
      </Head>
      </Message>
      </ns:MT_Source>
    I should get Body field after Head Structure as in the Source Structure, So Please what changes do I need to do in the Parameters Specified above to get the desired Output.
    So How should I define the FCC Paramenters For Sender File Adapter ?
    Any Help Would be Appreciated.
    Regards,
    Varun

    Hi Everyone,
    I could Succeed to some extent.
    I have defined the parameters as follows
    Recordset Structure: Message,*,Head,1
    Key Field Name: KZ
    Key Field Type: integer
    In the table, I defined the Parameters as
    Message.fieldFixedLengths:1,3
    Message.fieldNames:KZ,Id
    Message.keyFieldValue:1
    Message.keyFieldInStructure:ignore
    Message.fieldSeparator:,
    Message.endSeparator:'nl'
    Head.fieldFixedLengths:1,3,8
    Head.fieldNames:KZ,Id,filename
    Head.keyFieldValue:2
    Head.keyFieldInStructure:ignore
    Head.fieldSeparator:,
    Head.endSeparator:'nl'
    Message.fieldFixedLengths:1,11
    Message.fieldNames:KZ,Body
    Message.keyFieldValue:3
    Message.keyFieldInStructure:ignore
    Message.fieldSeparator:,
    Message.endSeparator:'nl'
    My source text file
    1,123
    2,123,test.xml
    3,Hello World
    my output is
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns:MT_Source xmlns:ns="http://city.net/FileCopy">
    - <Message>
    - <Message>
      <Id>123</Id>
      </Message>
    - <Head>
      <Id>123</Id>
      <Filename>test.xml</Filename>
      </Head>
      </Message>
      </ns:MT_Source>
    I got the output almost correct except I am not getting the value in the Body
    Any help would be appreciated.
    Please correct me If I am wrong.
    Regards,
    Varun
    Edited by: Varun on Sep 2, 2008 12:06 PM
    Edited by: Varun on Sep 2, 2008 12:15 PM

  • How to create send connectors for multiple sites in the same domain?

    Current Scenario:
    We have 2 offices, 1 in London and 1 in India. Both are in the same domain and are connected via VPN. Both have their own separate Exchange 2003 server. Each location sends out their mail via the Default SMTP Virtual Server on their exchange server through
    their local ISP. There are no Send connectors created currently.
    We have now installed an additional Exchange 2010 server with Hub, CAS and Mailbox roles at the London site. Internal mail flow between the sites seems to be working fine.
    I believe the Exchange 2010 needs a Send connector to send out mail to the internet. However as soon as we create a Send connector on Exchange 2010, mail from the older 2003 servers at both sites start to flow out from the exchange 2010 server. This is not
    optimal for our India site since their outgoing mail now has to flow via the VPN to London and out via the new server.
    How can we configure it so that each server sends outgoing mail independently?
    Thanks

    Hi,
    In India site, you can create a SMTP connector which point to the local ISP.
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Configure send connector for exchange online protection

    Hello Forum members,
    I am trying to configure send and receive connectors for Exchange 2010 to route
    on-premises mailboxes to Exchange OnLine Protection.  The "help" info MS provides
    is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
    Exch Management Console.  How can I configure connectors to properly connect to the Exchange Online Protection?
    I have seen where the ip addresses are posted, etc.  I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
    Any tips will help,
    Thanks,
    Eric H.
    Network and Server Installs

    Hello Wesleyhe,
    You cannot use AD anything with EOP - if you mean exchange on-line protection.
    you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
    on the SBS server.  the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
    Then you need to configure the outside ip for your SBS server access in the EOP admin area.
    Hope this helps.
    eholz
    Network and Server Installs

  • Change published FQDN for 2012 R2 RDS

    I have Windows Server 2012 R2 (single server hosting all the roles for RDS). I'm using RDS for publishing RemoteApps for both internal and external users. External users connect to remote.company.com and I have certificate from public ca (issued to remote.company.com).
    Active Directory is company.local. 
    When external users connect through the rds gateway and run remoteapp they receive this warning message that is caused by fqdn mismatch 
    I tried to use this script to change fqdn to match remote.company.com and it does that but after that external users cannot open remoteapps anymore. Internally they work.
    https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    I get this error in eventlog:
    The user "COMPANY\username", on client computer "xx.xx.xx.xx", did not meet resource authorization policy requirements and was therefore not authorized to resource "remote.company.com". The following error occurred: "23002".
    If I change the published fqdn back to rds.company.local remoteapps starts to work again but with certificate error.
    How can I fix this?

    Hi,
    In RD Gateway Manager, please edit the properties of the RD RAP.   On the Network Resource tab, please select Allow users to connect to any network resource.  After modifying the RD RAP please use Set-RDPublishedName cmdlet to change the published
    name to the correct FQDN as you did before.
    Once you verify it is working you could go back in (if you want to) and create a RDG-managed group with all of the required names.
    Thanks.
    -TP

  • Is send connectors fault tolerant for source servers?

    Hi!
    I am in the process of applying SP3 on our Exchange 2010 environment. I have two Hubs that are both specified as source servers in our send connector to the internet. I just want to double check that when I'm applying SP3 to one of the server, that the other
    server is taking care of sending all emails. 
    My fear is that it is only load balancing so every other email will fail to be sent because on of the hubs are down.
    So can I safely update one of the servers and mail will be still sent from the other? Or should I just remove it as a source server from the send connector?
    I will of course redirect incoming emails to the hub that are up at the moment.
    Thanks!

    Hi ,
    Based on my knowledge while doing service pack upgradation on the hub transport severs there is no need to remove that particular server from source server list on the send connectors.
    In addition to that mail flow will load balanced across both the hub transport servers listed on the source server list .So on such case if anyone of the server in send connector's source server list is not funtional for the particular point of time then
    it will prefer the second funtional server to send emails to internet.Finally i would like to say that there wouldn't be an loss in emails.
    Thanks & Regards S.Nithyanandham

  • In using MS Word for mac, and using track changes, and I send a copy, the recipient cannot see the track changes, nor do they show up on the printed copies, even though I highlight show changes in print

    In using MS Word for Mac, and in using Track Changes, when I send an email with the changes, the recipient cannot see the highlighted changes, nor do the printed pages show the highlighted changes, even though I have checked "show highlighted changes"

    In using MS Word for Mac, and in using Track Changes, when I send an email with the changes, the recipient cannot see the highlighted changes, nor do the printed pages show the highlighted changes, even though I have checked "show highlighted changes"

  • Changed password for e-mail account and cannot send e-mails

    Went into setting, "mail, contacts and calendar" under my e-mail account I changed the password, but now I can't send any e-mails out.  Checked with comcast and all the settings are correct.  What is the problem?

    If your email provider requires the password for sending emails then as well as changing it on the account when you tap on it in Settings > Mail, Contacts, Calendars, you may also need to tap on SMTP (under the 'outgoing mail server' heading) on that popup screen and then tap on the outgoing server name on the next screen and update the password there as well.

Maybe you are looking for