Exchange 2007 Smarthost send connector backing up

I have seen some similar posts to this but none have had any good answers.
We route all outbound mail through an Barracuda spam/virus appliance. We are a busy college campus with roughly 2k staff banging away at our mail gateways with mass mailings to our students, homework assignments, class schedules, blah blah blah..
At no time is our outbound mail queue empty. The trouble is, is that at any given time the most "Active" delivery status messages I see in queue viewer is 6 messages. Whether there are 30 or 5000 messages stuck in there it never try's to send
more than 6 at a time.
Sometimes the queue viewer shows no "Active" connections just all "Ready's". I never see the status change to "Retry" or anything else other than "Ready" or "Active".
We often have delivery delays of 3 or 4 hours when mass mailing messages that do not exceed more than 10 to 20k.
Here is what we've tried so far:
In Powershell use: get-transportserver | fl   (to view these)
and use:  set-transportserver -ConfiguratorName  (to change the values)
updated MaxConcurrentMailboxDeliveries to 50
updated MaxConcurrentMailboxSubmissions to 50
updated PickupDirectoryMaxMessagesPerMinute to 200
MaxConnectionRatePerMinute 1200
MaxOutboundConnections 1000
MaxPerDomainOutboundConnections 1000
"...MaxMessageAttachSize" 100MB (For testing only)
use: get-sendconnector | fl    to verify the value of "MaxMessageSize". Ours is set to unlimited.
use: get-transportconfig   to check all the "Max" settings in there particularly the MaxDumpsterSizePerStorageGroup setting. Ours is 125MB.
Protocol logging is set to Verbose on the send connector. There are no error messages in the send or connectivity logs. The "Microsoft MailFlow Troubleshooter" is a joke.
We have no throttling turned on at the Barracuda level, so says their tech support. I of course have no way of verifying this as I do not have access to it.
I guess my question is. Does anyone know how or where we can increase the number of "Active" messages in the queue to more than 6 messages?

On Thu, 16 May 2013 20:19:55 +0000, Elvis P. Johnson wrote:
>We route all outbound mail through an Barracuda spam/virus appliance. We are a busy college campus with roughly 2k staff banging away at our mail gateways with mass mailings to our students, homework assignments, class schedules, blah blah blah..
>
>
>
>At no time is our outbound mail queue empty. The trouble is, is that at any given time the most "Active" delivery status messages I see in queue viewer is 6 messages. Whether there are 30 or 5000 messages stuck in there it never try's to send more than
6 at a time.
You're sending all mail to a single smart host? I'd be looking at that
machine's configuration.
>Sometimes the queue viewer shows no "Active" connections just all "Ready's". I never see the status change to "Retry" or anything else other than "Ready" or "Active".
You have only one queue, for the smart host, right? Is there a "Last
error" value for it?
Are there any "back-pressure" events in the server's application event
log?
>We often have delivery delays of 3 or 4 hours when mass mailing messages that do not exceed more than 10 to 20k.
[ snip ]
>Protocol logging is set to Verbose on the send connector. There are no error messages in the send or connectivity logs. The "Microsoft MailFlow Troubleshooter" is a joke.
>
>We have no throttling turned on at the Barracuda level, so says their tech support. I of course have no way of verifying this as I do not have access to it.
The barracuda has DOS protection. I *think* the default is to limit
the number of "parrallel connections" to 5, but that may be different
on different models. There are probably other "rate limiting"
settings, too.
>I guess my question is. Does anyone know how or where we can increase the number of "Active" messages in the queue to more than 6 messages?
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

Similar Messages

  • Exchange 2007 Multiple Send Connector Cost Best Practice

    Hi,<o:p></o:p>
    I am running exchange 2007 SP2 and have 2x exchange connectors set up with an equal default cost of 1.<o:p></o:p>
    Connector 1 is set to * address space and should forward all emails to two email security/management servers<o:p></o:p>
    Connector 2 is set to a internal sub domain server whose purpose is to file the emails on a CMS.  Emails are marked for "filing" when
    the Outlook plugin adds the connector 2's subdomain address into the bcc field.<o:p></o:p>
    What I want to clarify is if I was to change the cost of Connector 1 to 0 would all mail then only be routed via this connector?<o:p></o:p>
    I presume it would ignore the 2nd connector because the 1st connector's address space is *  and thus no emails would route through connector
    2 and therefore be filed to CMS ?<o:p></o:p>
    What would the best practice be for the costs of each connector ??<o:p></o:p>
    Thanks<o:p></o:p>
    Mat<o:p></o:p>

    I don't believe that 0 is a valid cost for a connector (I get an error if I try to see a connector with that).  If you have two connectors, Exchange will send to the one that matches the address space most correctly.  If you had no second connector,
    connector 1 would attempt delivery to your CMS.  Since you have that second connector, those messages will be delivered by it.
    Connector costs are normally used when you have multiple connectors with the SAME address space, and allows Exchange to fail from one to another when the preferred is not operational for some reason.  For example, if you have an ISDN line as your backup
    Internet connection, you want to give connectors that use it a higher cost than your MPLS connections use.
    I'll add that in most environments I've worked for the past several years, this redirection is handled at the network layer rather than the application layer.

  • Exchange 2007 OWA sends attachments Outlook connector clients cannot send attachments.

    Exchange Server 2007 SP1 + Rollup ***Problem with sending email attachments from Outlook 2007***
    * Inbound mail arrives in OWA and Outlook normally with and without attachments.
    * OWA email to external email account with attachment goes thru successfully.
    * Outlook 2007 sends to an external email address with attachments the message does not arrive at the external mailbox.   The messages leave Outbox but are never delivered. The messages appear in Sent Items also.
    * Outlook sends non attachment emails to external addresses successfully.
    * Outlook sends email attachments to local domain accounts fine.
    #1 Exchange Server on Server 2013 fully patched problem commences. Exchange Server on version less than first RTM release of Exchange 2007.
    #2 Outlook profiles were changed to see if that is the problem.
    #3 Upgraded Exchange to SP1 and Rollup 10(Rollup was autodownloaded by MSUpdate)
    #4 Ran EXBPA nothing of any interest in the report.
    --Unified Messaging not configed (Done nothing)
    --SenderID (Re-enabled) I had shut all of the antispam to eliminate these.
    -- Junk Store threshold not configed (No change)
    Any suggestions to get Outlook clients capable of sending attachments configured.
    Thx,
    -Scot

    Hi Scot,
    Providing some information on Poison Queue:
    The poison message queue is a special queue that's used to isolate messages that are determined to be harmful to the Exchange system after a transport server or service failure.
    The messages may be genuinely harmful in their content and format.
    Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
    The poison message queue is typically empty. If the poison message queue contains no messages it doesn't appear in Queue Viewer or
    Get-Queue results. The messages in the poison message queue are never automatically resumed or expired. Messages remain in the poison message queue until they're manually resumed or removed by an administrator.
    According to the description above, I suspect Outlook 2007 changed the email's format when send email with attachment. The reason as below:
    If the original email's (with attachment) content or format is harmful to the Exchange 2007 server, it will go to the Poison Queue when sending via OWA. However it didn't, sending via OWA is perfect. So I suspect it is an issue on the Outlook 2007
    client side.
    Please using Pipeline Tracing to verify whether there is something changed during transmission.
    More details in the following article:
    Using Pipeline Tracing to Diagnose Transport Agent Problems
    http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
    If it is convenient, I suggest doing following tests to narrow down this issue:
    Note: Same content, same attachment, same format.
    1. Please using Outlook 2010/2013 or others' Outlook clients for testing.
    2. Please change to another format for testing. More details in the following article:
    Change the message format to HTML, Rich Text, or plain text
    http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HP001232996.aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2007 wont send to AOL and a few other domains

    Have tried everything.  We switched from Time Warner Cable, to AT&T firber optic, and now we cant send email to AOL, and a few other domains.  rDNS is setup correctly, and still no go.  Any help would be good.

    Hi,
    How about the internal communication?
    Agree with both MAS and Rich, detailed errors will be helpful for the further troubleshooting.
    Please use mxtoolbox to check blacklist.
    Please check the Send Connector settings.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2007 when sending a calendar invite, a non-existent delegate shows up in an undeliverable message

    I had a test user that was removed. When it was removed, it was still listed as a delegate on someone's email. Now, whenever a Calendar invite is sent to the existing user, the sender receives an undeliverable message. The existing user does not receive
    notification of a calendar event, but the event does show up in the calendar.

    Hi,
    If the delegate user account or mailbox has been removed from domain or Exchange server, please also remove the delegate settings with this account.
    If a user is set as a delegate for a manager, the meeting request which is send to the Manager would be forwarded to the delegate automatically and ask for approving in the delegate side.
    Please do the following steps in the Manager’s Outlook client to remove the delegate settings for this non-existent delegate:
    1. Open the Manager’s Outlook.
    2. Click File > Account Settings > Delegate Access.
    3. In the Delegate list, click the non-existent delegate, click Remove.
    4. Click OK to save the settings.
    Then check whether the issue persists.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

    One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
    "Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
    Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
    Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
    "SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
    After testing DNS that all seems fine, so I don't believe it's a DNS problem.
    Any ideas why this would happen?
    Thanks,
    Matt

    Hi Matt....
    To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
    https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
    Hope this will work
    Thanks

  • Send connectors question

    Hi There,
    we have the 2 Ad sites and each site has the exchange server 2010 sp2 (HUB.MDB,UM and CAS). i want to route the messages based on Sites via each separate send connector. I would like to know send connectors use exchange cost routing to route the messages
    Many thanks
    David

    Under the send connector properties, scope it and then set the smarthost on each send connector to what you want. I assume that is what you are referring to.
    Note that there is *no* native source based routing in 2010.
    If you need source-based routing:
    If you want to use sender based routing in Exchange 2010, use an agent:
    http://routingruleagent.codeplex.com/
    or 3rd party software:
    http://ivasoft.com/routebysender.shtml
    http://grahamhosking.blogspot.com/2011/05/exchange-2007-2010-sender-based-routing.html
    http://technet.microsoft.com/en-us/library/aa997285(v=exchg.141).aspx
    Scoped send connector By default, all Send connectors that you create can be used by all the Hub Transport servers in your Exchange organization. However, you can limit the scope of any Send connector so that it can be used only by other
    Hub Transport servers that exist in the same Active Directory site. To limit the scope of this Send connector, select
    Scoped send connector.
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2007 to 2013

    hello 
    i am trying to migrate exchange 2007 to exchange 2013 but what a bout spam filtring feature which installed in hub and cas server
    how can i enabled in exchange 2013 and copy all configuration 
    what a bout accepted domain how can i migrate it ?
    Receive connectors ? how can i migrate it?
    MCP MCSA MCSE MCT MCTS CCNA

    I see a lot of confusion here - both in the way the questions are asked, and in the incorrect and misleading answers.
    The anti-spam feature in Exchange 2013 is performed by the Connection Filtering agent. It is not available in the Exchange 203 CAS or MBX roles. Exchange 2013 SP1 re-introduced the EDGE server role (about a year and a half after the RTM) and the
    missing connection filtering agent (the anti-spam feature or module as DareDevil says).
    Hence, you have the following options:
    1. Install and configure an Exchange 2013 EDGE server.
    2. Install a 3rd party Anti-Spam product.
    3. Use the Anti-Spam services of an external company - all inbound e-mail should go through the servers of this company.
    4. Install and use a linux server in the DMZ for the Anti-Spam filtering (that works amazingly well, and you'll be surprised how many companies are using this option).
    As a matter of fact, Yasser, you've asked four questions, not just one. The accepted domains, that are already configured in you existing Exchange 2007 organization, are configured automatically on the Exchange 2013 servers - you don't have to perform this
    task manually.
    Depending on your deployment - [CAS+MBX] or separate [CAS] and [MBX] servers, you'll have the minimum required receive connectors configured as well. If you have custom receive connectors, you'll have to re-create them manually. The same way, if you
    have custom transport rules,you'll have to export/import them manually as well.
    You'll have to create manually the Exchange 2013 Internet send connector(s) or add the Exchange 2013 CAS to the existing one(s).
    By default, the Anti-Malware feature is enabled when you install Exchange 2013, but if you are planning to use a third party product, you can disable it.
    Step by Step Screencasts and Video Tutorials

  • Send Connector TAB - Force Closed

    Hi
    I'm not sure why or how this has just started. When i open Exchange Management Console all is fine, but when i go to Organisation Configuration
    à Hub Transport and click on the Send Connector Tab an error box appears with a RED CROSS "Force Closed" and does not show my send
    connector, i have restarted the server, made sure all services are started except for POP and IMAP, done windows update, restarted again.
    but still the same issue, not sure what the problem is or where to go from here so any help would be much appreciated.
    Thanks
    T

    Hi, sorry its not fixed but the above was a work around.
    After running
    Get-SendConnector | fl fqdn
    in the shell cmd, when i opened exchange management console à send connectors tab it displays the connectors
    fine.
    but if i close the exchange management console then close the shell cmd then re-open the exchange management console
    à send connectors the error box is back and no connectors are displayed.
    Then if i re-run the
    Get-SendConnector | fl fqdn in the shell and then re-open the exchange management console
    à send connector tab it displays the connectors fine again.
    is there a way to find out what’s causing this issue
    Thanks
    T

  • Exchange 2007 and 2013 coexistance Problem

    We are in the process to migrate our current Exchange 2007 to Exchange 2013.
    Our environment is as follows:
    HT01= Hub CAS Server (Exchange 2007)
    MB1, MB2 = Mailbox CCR Cluster (Exchange 2007)
    CAS1= CAS Server (Exchange 2013)
    MBNew1, MBNew2 = Mailbox Servers (Exchange 2013)
    Emails for users that are on Exchange 2007 can send and receive external emails. But they cannot send emails to users that are on Exchange 2013.
    Users on Exchange 2013 can send/receive externally, send to Exchange 2007 users, but cannot receive emails from Exchange 2007 Users.

    Are you getting any NDR? Post it.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exhcnage 2010 send connector

    our exchange 2010 smtp  send connector shows we are sending an smtp request to an unwanted address every 10 minutes. How does one determine with the session number listed who/what is initiating that request? 

    Hi,
    SMTP logging is disabled on Exchange server 2010 by default. I recommend you use the following cmdlet to enable protocol logging for the Send connector.
    Set-SendConnector "xxx" -ProtocolLoggingLevel Verbose
    For more information, here is an article for your reference.
    Understanding Protocol Logging
    http://technet.microsoft.com/en-us/library/aa997624(v=exchg.141).aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Send connector from exchange 2007

    Currently since I have both environments up, I see that Exchange 2013 is using the send connector that was created in my exchange 2007 environment.  Will this send connector go away once I bring down my exchange 2007 environment? Shoould I create
    a new one for Exchange 2013?

    Hi
    From what i have seen running ex2010 and upgrading to 2013 it stayed (exchange 2013 is clever :-)). you can just modify your send connector and make sure that the settings are for your exchange 2013 server.

  • Exchange 2007 Send Connectors

    Hello,
    I'm relatively new to administering Exchange and I had some questions on Send Connectors. We send mail to a few different domains that usually 75% of the time will generate a message saying:
    Delivery is delayed to these recipients or distribution lists:
    This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
    Delivery of this message will be attempted until 1/9/2014 9:31:13 AM (GMT-05:00) Eastern Time (US & Canada). Microsoft Exchange will notify you if the message can't be delivered
    by that time.
    Sometimes messages will make it to the intended recipients and other times not. Most of the time they are just regular emails without any attachments on them. I'm not exactly sure how connectors work, but I'm thinking that I can set one up to tell exchange
    that it should route these certain emails to that domain. Is this the correct thought process on how a send connector would work and are there any ramifications I need to worry about if I set up a second or third send connector?
    I apologize if this is naïve or doesn't make sense. Please let me know if you need more information. We run Exchange 2007 on Windows SBS 2008.
    Thank you.

    Hi,
    It seems that it could be a reverse DNS lookup issue. I recommend you check if the reverse DNS record is configured correctly.
    If it is ok, I suggest you enable logging at your send connector. Then check the log to see if you could find some clues.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 Send Connector to postfix (v. 2.11) smarthost uses STARTTLS and cannot connect

    Dear all,
    I am having problems with exchange 2010 sending emails through a postfix smarthost server which disconnects the sessions. I also use a sendmail as a smarthost
    server which is working just fine but I have to switch to postfix and cannot do this as long as the encryption does not work.
    Here is the log file of the postfix server:
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: initializing the server-side TLS engine
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: connect from server1.mydomain.com[192.168.20.10]
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: setting up TLS connection from server1.mydomain.com[192.168.20.10]
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: server1.mydomain.com[192.168.20.10]: TLS cipher list "aNULL:-aNULL:ALL:+RC4:@STRENGTH"
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:before/accept initialization
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: read from 7F4823FA5210 [7F4823FAB1B0] (11 bytes => -1 (0xFFFFFFFFFFFFFFFF))
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: read from 7F4823FA5210 [7F4823FAB1B0] (11 bytes => 11 (0xB))
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0000 16 03 01 00 5a 01 00 00|56 03 01                 ....Z... V..
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: read from 7F4823FA5210 [7F4823FAB1BE] (84 bytes => 84 (0x54))
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0000 54 a9 3d b9 0d 5e 8b 64|7c 6b b5 21 f2 93 e7 84  T.=..^.d |k.!....
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0010 17 ea 33 d7 e5 13 f2 75|3a 87 38 32 01 85 82 5b  ..3....u :.82...[
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0020 00 00 18 00 2f 00 35 00|05 00 0a c0 13 c0 14 c0  ..../.5. ........
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0030 09 c0 0a 00 32 00 38 00|13 00 04 01 00 00 15 ff  ....2.8. ........
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0040 01 00 01 00 00 0a 00 06|00 04 00 17 00 18 00 0b  ........ ........
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0050 00 02 01                                         ...
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0053 - <SPACES/NULLS>
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 read client hello A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 write server hello A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 write certificate A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 write key exchange A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 write server done A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: write to 7F4823FA5210 [7F4823FB8B70] (1911 bytes => 1911 (0x777))
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: 0774 - <SPACES/NULLS>
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:SSLv3 flush data
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: read from 7F4823FA5210 [7F4823FAC803] (5 bytes => 0 (0x0))
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept:failed in SSLv3 read client certificate A
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: SSL_accept error from server1.mydomain.com[192.168.20.10]: lost connection
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: lost connection after STARTTLS from server1.mydomain.com[192.168.20.10]
    Jan  4 14:18:59 server7 postfix/smtpd[1659]: disconnect from server1.mydomain.com[192.168.20.10]
    I
    have read in the post at https://social.technet.microsoft.com/Forums/exchange/en-US/6db38364-cb08-45c0-b159-3ddf30ef0b3e/exchange-2010-send-connector-uses-ssltls-and-cannot-connect-to-smarthost-how-to-deactivate-ssl?forum=exchange2010
    how to deactivate the SSL encryption, but this is of course a security flaw, if I am not mistaken. I would like to encrypt the connection between the servers for obvious security
    reasons but I have come to a standstill...
    My Exchange server certificate is configured
    as follows:
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
                         ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKe
                         essRule}
    CertificateDomains : {server1, server1.solid-con.com}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=server1
    NotAfter           : 22/01/2017 13:18:02
    NotBefore          : 22/01/2012 13:18:02
    PublicKeySize      : 2048
    RootCAType         : None
    SerialNumber       : 6925D91285B649BD4D5E4297F1A48471
    Services           : IMAP, POP, IIS, SMTP
    Status             : Valid
    Subject            : CN=server1
    Thumbprint         : 939A37173BF84E352CEDC74F7D9A3D71F498A005
    AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
                         ule, System.Security.AccessControl.CryptoKeyAccessRule}
    CertificateDomains : {WMSvc-SERVER1}
    HasPrivateKey      : True
    IsSelfSigned       : True
    Issuer             : CN=WMSvc-SERVER1
    NotAfter           : 19/01/2022 12:56:44
    NotBefore          : 22/01/2012 12:56:44
    PublicKeySize      : 2048
    RootCAType         : Registry
    SerialNumber       : 1DB8711F7ADC5CB54196468EF2FF5D21
    Services           : None
    Status             : Valid
    Subject            : CN=WMSvc-SERVER1
    Thumbprint         : 191D86BDE274510453D58DDB91D253DABBCF05F1
    And My Default Send Connector is configured as follows:
    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     : System.Management.Automation.PSCredential
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : False
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         :
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : SERVER1
    Identity                     : Internet
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    LinkedReceiveConnector       :
    MaxMessageSize               : unlimited
    Name                         : Internet
    Port                         : 25
    ProtocolLoggingLevel         : None
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {server7.mydomain.com, server6.mydomain.com}
    SmartHostsString             : server7.mydomain.com,server6.mydomain.com
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {SERVER1}
    TlsAuthLevel                 :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False
    Any help would be greatly appreciated as I am
    stuck...
    Luca

    Hi Allen,
    Thank you very much for your reply.
    The Postfix TLS Manager is enabled in master.cf
    tlsmgr    unix  -       -       n       1000?   1       tlsmgr
    and running
    server7:/etc/postfix # ps -efa|grep tls
    postfix  11967 11863  0 11:21 ?        00:00:00
    tlsmgr -l -t unix -u
    Every other (Linux/UNIX) server has no problem e.g.:
    Jan  5 11:28:36 server7 postfix/smtpd[12215]: connect from server2.mydomain.com[192.168.20.20]
    Jan  5 11:28:36 server7 postfix/smtpd[12215]: Anonymous TLS connection established from server2.mydomain.com[192.168.20.20]: TLSv1 with cipher DHE-DSS-AES256-SHA (256/256 bits)
    Jan  5 11:28:36 server7 postfix/smtpd[12215]: B5502946AB0: client=server2.mydomain.com[192.168.20.20]
    Jan  5 11:28:36 server7 postfix/cleanup[12221]: B5502946AB0: message-id=<[email protected]>
    Jan  5 11:28:36 server7 postfix/qmgr[12200]: B5502946AB0: from=<[email protected]>, size=1026, nrcpt=1 (queue active)
    Jan  5 11:28:36 server7 postfix/smtpd[12215]: disconnect from server2.mydomain.com[192.168.20.20]
    Jan  5 11:28:37 server7 postfix/smtpd[12225]: connect from localhost[127.0.0.1]
    Jan  5 11:28:37 server7 postfix/smtpd[12225]: 4076A946AB1: client=localhost[127.0.0.1]
    Jan  5 11:28:37 server7 postfix/cleanup[12221]: 4076A946AB1: message-id=<[email protected]>
    Jan  5 11:28:37 server7 postfix/qmgr[12200]: 4076A946AB1: from=<[email protected]>, size=1778, nrcpt=1 (queue active)
    Jan  5 11:28:37 server7 postfix/smtpd[12225]: disconnect from localhost[127.0.0.1]
    Jan  5 11:28:37 server7 postfix/smtp[12222]: B5502946AB0: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.54, delays=0.05/0.01/0.01/0.47, dsn=2.0.0, status=sent
    (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4076A946AB1)
    Jan  5 11:28:37 server7 postfix/qmgr[12200]: B5502946AB0: removed
    Jan  5 11:28:37 server7 postfix/cleanup[12221]: 4401F946AB0: message-id=<[email protected]>
    Jan  5 11:28:37 server7 postfix/qmgr[12200]: 4401F946AB0: from=<[email protected]>, size=1920, nrcpt=1 (queue active)
    Jan  5 11:28:37 server7 postfix/local[12226]: 4076A946AB1: to=<[email protected]>, relay=local, delay=0.02, delays=0/0.01/0/0, dsn=2.0.0, status=sent (forwarded as 4401F946AB0)
    Jan  5 11:28:37 server7 postfix/qmgr[12200]: 4076A946AB1: removed
    Jan  5 11:28:37 server7 postfix/smtp[12227]: Untrusted TLS connection established to 192.168.20.10[192.168.20.10]:25: TLSv1 with cipher AES128-SHA (128/128 bits)
    Jan  5 11:28:37 server7 postfix/smtp[12227]: 4401F946AB0: to=<[email protected]>, orig_to=<[email protected]>, relay=192.168.20.10[192.168.20.10]:25,
    delay=0.29, delays=0/0.01/0.02/0.25, dsn=2.6.0, status=sent (250 2.6.0 <[email protected]> [InternalId=619] Queued
    mail for delivery)
    Jan  5 11:28:37 server7 postfix/qmgr[12200]: 4401F946AB0: removed
    and if you take a look at the lines in bold you will see that mails can be delivered over TLS to that very Exchange server (the mailboxes are on that server)...
    To summarise:
    exchange --> postfix with TLS = session disconnected (and everything seems to be initiated by the exchange server -if I read the logs correctly)
    postfix --> exchange with TLS = works
    any further hints?
    Thank you very much in advance,
    Luca

  • Import csv file in Address Spaces in an Exchange 2007 Send Connector

    hello , i must put more than 300 domains in the addres space of a Send connector.
    is possible have a csv file with the 300 domains and a powershell script to import this file in the address space of one send connector?
    example csv file :
    cepsa.es
    repsol.com
    parsi.es
    Regards
    Thansk in advance
    mcse 200x + mesaging 2000 2003 2007 2010

    Hi
    At First, you CSV should be set as the format like
    Name
    cepsa.es
    repsol.com
    parsi.es
    If you would like to set a new Send Connector. you can simply do
    New-SendConnector -Name ConnectName -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
    If you would like to add to a Send Connector that already existed, Please run
    $al = (Get-SendConnector -Identity <ConnectName>).AddressSpaces
    $al += (Import-CSV <PathOfCSV>) | ForEach {$_.Name})
    Set-SendConnector -Name ConnectName -AddressSpace $al
    Cheers
    Zi Feng
    Zi Feng
    TechNet Community Support
    The first script is still working as it should under Exchange 2013 when a send connector is created for the first time.
    The second part of adding (or removing)  address spaces from an existing send connector was a little bit trickier.
    the following script did it:
    Get-SendConnector "ConnectorName" | Set-SendConnector  -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
    Watch out! this command also removes domains which are not present in the csv file!

Maybe you are looking for