Hi folks, I have a send connector that is linked to a specific receive connector. But now I need to make sure the send connector does not allow mails to go to the internet (mails to the internet are allowed to be droped, we don't need to keep them) but only deliver mails sent to internal addresses. The receive connector can receive even mail from annonymous users (this is checked, it works) BUT only mails sent to the internal domain are allowed to go through, mails for external domains need to be droped / stoped. This question somewhat leans on to a previous question I posted, but I just wanted to re-phrase it. I hope my question is clear. If you have any tips to solve this problem, please let me know. tnx in advance. Greets, Stef

Let me make sure I understand. You do NOT want users to be able to send email TO the internet, just receive from the internet, correct? If this is the case then just delete the send connector. Send connectors and receive connectors are completely separated from each other. Let me know if I mis-understood you. Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

Hi Tim, Tnx for the quick reply. I think the situation is a bit more complicated. All the users are allowed to send mail to the internet BUT I created an extra receive connector that allows unauthenticated access, this receive connector is linked to an extra IP adress on the existing mail server. Our devolopers need to use this extra IP address as smtp server so their programs can send annonymous mails. ONLY the mails sent through that receive connector are not allow to leave to the internet. Only internal mails need to be delivered. So I can not delete all our send connectors , because then nobody can sent outgoing mail. But I'll give it a try by deleting the send connector that is linked to my receive connector. Tnx, Stef

Tim, I jus did a test when I deleted the linked send connector, I think the receive connector then falls back to our standard send connector (the one we need so our other users can send mail to the internet). As test I sent an anonymous mail to an internal and an external address. Both mails where delivered, even when the linked send connector was deleted and only the standard send connector exists. Stef

If normal routing would send mail through the send connector anyway, then there's no need to link a receive connector to a send connector. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "StefVH" wrote in message news:43c49595-e3b5-4cfb-ac4b-a9ab757474bc... Tim, I jus did a test when I deleted the linked send connector, I think the receive connector then falls back to our standard send connector (the one we need so our other users can send mail to the internet). As test I sent an anonymous mail to an internal and an external address. Both mails where delivered, even when the linked send connector was deleted and only the standard send connector exists. Stef Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I linked the receive connector to a separate send connector, hoping that the linked connector could "drop" all mails that have an external address and only deliver the mails that are intended for internal mail addresses. That's that whole point, all mails received through the specific receive connector is sent to that specific send connector. That specific send connector should only let internal mail address through and drop all mails with a mail address ouside the company. The specific receive connector is needed, because this is the only connector that allows annonymous mails. Our developers need to be able to send anonymous mails, but if by mistake, there is a mail address for outside our domain, that mail should not be allowed to be delivered. I can not use a rule for this because we do not know the "from" addres that is used, the "from" addres could even be an non-existing address. Hopefully this info helps to understand my problem. Tnx !! Stef

Hi Stef, There is no way to bind a send connector and receive connector together. However, you could use transport rule to do the job. Apply rule to messages | conditions: from users outside the organization and sent to users outside the organization | actions: silently drop the message. Thanks, Elvis

Tnx 4 the tip Elvis, that might also do the trick, did not have the possibility to test it. I think I found the solution : Created a new receive connector with the following settings : On the general tab make sure the FQDN is the one of your internal mail server. On the Authentication tab ONLY select - TLS (NOT Mutual Auth). - Basic Auth. (NOT Offer basic ...) - Exchange server auth. Permissions Groups - only Annonymous access Also Created an extra ip address on the Nic of the exchange server and added this address in the Use the local IP Address to receive mail in the Network Tab. On the same network tab, added the ip address of the workstation that would send the unauthenticated mail under the "Receive mail from remote server ..." window. No need to create an extra send connector. Tnx all for the tips and help.