Disable Send Connector BareLinefeedRejection

Hi,
Is it possible to disable BareLinefeedRejection for the Send Connector. similar to BareLinefeedRejectionEnabled for Receive Connectors?
We sometimes receive emails with bare line feeds, but these emails are rejected by the send connector used for journalling.

Hi,
Base on my knowledge, it is impossible to edit bare line feed on send connector.
It's by design that Exchange 2010 send connectors do NOT allow messages containing bare linefeeds to pass through.Bare line feeds aren’t allowed in SMTP communications. Although it may be possible for a message containing a bare line feed to be delivered
successfully, such messages don't adhere to the SMTP protocol standards and may cause problems with messaging servers.
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/exchange/en-US/8da8d33a-fac8-4cc3-8ac0-6ea7f86ebfc4/exchange-2010-barelinefeedsareillegal-error-when-journaling-to-external-box?forum=exchange2010
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

Multiple Smart Hosts within a send connector issue

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that as long
as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this send
connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that
as long as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this
send connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?
Not really possible with the native Exchange capabilities, no.
If you have a load balancer, you might be able to leverage that and have Exchange send to single namespace that is handled by the balancer.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Remove legacy Send connectors from Exchange 2010 after migration

Hello.
I have just removed the last legacy exchange 2003 server form our organisation.
I followed the official MS documentation for this and the remove went to plan with no errors.
The only issue I now have is that I have 2 legacy exchange send connectors in the Hub Transport view.
I have tried to disable and remove them but I get an undocumented error. The warning I get in the exchange server event logs is as follows
Process w3wp.exe () (PID=8148). Object [CN="Connector name",CN=Connections,CN="Organisation Name",CN=Routing Groups,CN="Group Name",CN=Administrative Groups,CN="Org Name",CN=Microsoft Exchange,CN=Services,CN=Configuration,DC="Domain
Name",DC="local"]. Property [HomeMtaServerId] is set to value ["Domain Name"/Configuration/Deleted Objects/Microsoft MTA
DEL:1bfa936f-c57e-4b7d-ad03-258acb560ad3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
Is ADSI edit the best way to remove these entries or is there another way to disable and remove?
Regards
Lee Gregory

Hi,
If the legacy send connector is no longer needed, it is ok to remove it from ADSIEdit.
For reference: select configuration as Connection point > domain > Services > MS Exchange > organizaiton name > Administrative Groups > Exchange Administrative Group > Routing Groups > First Routing Group > Connections
Regards,
Rebecca Tu
TechNet Community Support

Exchange 2010 - Send Connector High Availability

Hi All,
I performed a successful migration a few years back from a single node Exchange 2003 server to a two node Exchange 2010 organisation with a DAG and Kemp load balanced CAS array. The solution works well and when we simulate a site failure
I am able to get the second node to handle all mail functions.
The one problem I have though is that I have to manually disable the send connector on the primary server in order for the one on the secondary server to be in use. I should explain that I have two send connectors as I do not want the secondary server
to be used unless the primary server is down or the route is unavailable. I realise that Exchange 2010 does not know whether the SMTP route is down or not so will just continue trying to use the send connector from the primary server (until I tell it
not to by disabling it).
My question is how do I get this to happen automatically? Does anyone else have an example of how this could be done or use a PowerShell script to achieve this? I guess a script could check the route and disable the send connector on the primary
server if necessary, but how would one do this?
Any help greatly appreciated.
Rob

Hi,
According to your description, your secondary send connector cannot be automatically used when the first one is down. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if the settings of the secondary one is same with the first one and we can check the connectivity logs including diagnostic information for Healthy Server Selector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff634392(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

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.

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,

What are the correct Send Connectors settings in Exchange 2013

Hi
I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles. I am trying to set the send connectors settings, because I've not been able to send nor receive external email via owa. Since I'm separating the exchange roles, my mailbox
servers only use internal IP settings and cannot resolve external DNS. I'm thinking I need to tick, proxy through CAS for it to work? any suggestions?

Hi
Can you please let us know what version of Exchange that you are using
"I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles"
- Because Exchange 2013 does not hold hub role.
" I am trying to set the send connectors settings, because I've not been able to send
nor receive external email via owa."
It would be great if you could answer few questions so that people can help you out here
Are you able to send emails internally without any issues with Outlook ? If not can you paste the errors.
What error you are getting while trying to send emails through owa . Can you paste the errors.
If you are looking for steps to create new send connector please follow below technet article
http://technet.microsoft.com/en-us/library/aa998936(v=exchg.150).aspxFeel free to post your comments/errors you received to proceed
further
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)

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

Send connector and recieve connector

i recently figure out that send connector and reciece connector are not at the same level in EMC, why should it like this
if it is different, then please point me out some known issues about configuration about them

Hi,
In order to resolve the problem more efficiently, could you please explain in more detail?
If there is any update, please feel free to let me know. I'll be glad to help.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Using more than one Send connector

Hello
Is it possible to use more than one send connector? Of course it is ;-), but also whit this requirement? I have an additional domain hosted on my exchange. This domain has to use a smarthost with authentication. Now, only this two users should could use this connector. It would be cool, if there is a permission config to allow a group and deny the others or something like this... What could be a solution?
Thanks
Norbert

Hi,
Would help to know the version of the Exchange in your environment.
For Exchange 2003, please do the configuration on the send connector.
Expand ESM, Administrative Groups, Routing Groups, Connector, right click the send connector, select the Properties, in the Delivery Restrictions, please apply with the corresponding group.
For Exchange 2007, routing based on specific senders or a group is not supported in Exchange 2007 by design.
Thanks
Allen

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

Send connector in different costs

Hi,
All my exchange 2010 servers are in 1 single AD site.
It seems not working when I configured item no 2.
1. address => *, source server => hub A, cost => 1
2. address => *, source server => hub B, cost => 100
It is working if I joined Hub A & Hub B under send connector source server. This configuration will send via HUB A or HUB B.
My objective is to send to cost 1 as 1st proity. Any additon configurations are needed?
P/S: I was using this following for DR MBX and DR HUB
Set-MailboxServer -Id: mbxserverA-SubmissionServerOverrideList: htserverB,htserverC
Question: is it for all send and recived connectors?
Please advise. Thanks.
Kelvin Teang

Hi,
Exchange must bind the send connector to a specific hub transport server in your Exchange organization. By default, Exchange chooses the server that you are creating the connector on, but you do have the option of specifying a different hub transport server.
To meet your requirement, you should join both Hub A and Hub B under source server.
About SubmissionServerOverrideList, Exchange Hub transport Server will be automatically load balanced within the Active Directory Site. Hub Transport Servers are load balanced in Round robin fashion within the Site. If you want to force Exchange Mailbox
server to use specific Hub Server you need to make use of SUBMISSIONSERVEROVERRIDELIST.
"Set-MailboxServer -Id: mbxserverA-SubmissionServerOverrideList: htserverB,htserverC"
The command above will set Mailbox Server mbxserverA to use htserverB and htserverC for mailsubmission.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Send connector - e-mails from two domains to distinct anti-spam IPs

I have an Exchange enviroment that has two domains. I want that e-mails sent from a domain do the relay to an anti-spam, and e-mails sent from another domain do the relay to another anti-spam.
Example:
I need to config send connector to send the e-mails from "test1.com" to IP 10.160.190.66 and from "test2.com" to IP 10.160.190.69
How do I do?
I need this because each domain uses distincts anti-spam
Tks.

Hi,
Before going on, I would like to confirm the following information.
What's the version of the Exchange?
Whether the two domains have their own Exchange or share one Exchange?
Thanks
Allen

Disable Send Connector BareLinefeedRejection

Similar Messages

Maybe you are looking for