Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

What is a receive connector used for?


  • Please log in to reply
3 replies to this topic

#1 David Ashcroft

David Ashcroft

  • Members
  • 169 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:45 PM

Posted 26 September 2014 - 10:32 AM

In simple terms, I am relating this to exchange.

 

Why would you need to add in custom receive connectors, we had to do this so that a printer could scan to email. I haven't done much with exchange myself so was just wondering why this is needed?

 

Thanks!! :)



BC AdBot (Login to Remove)

 


#2 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:09:45 AM

Posted 26 September 2014 - 03:52 PM

Does a scanner talk imap or pop?  Nope.  Exchange needs to know who is talking to it so Exchange can respond accordingly.



#3 sflatechguy

sflatechguy

  • BC Advisor
  • 2,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:45 PM

Posted 26 September 2014 - 09:50 PM

How you do this will depend on what version of Exchange you are using. In short, you'll create an SMTP receive connector on the server, using either the Exchange Management Console or PowerShell, then configure the device to route emails through that connector using SMTP. That's why you have to create the connector.



#4 x64

x64

  • Members
  • 352 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:London UK
  • Local time:05:45 PM

Posted 27 September 2014 - 12:56 AM

You  would use multiple receive connectors to handle different classes of email in different ways.

 

When an SMTP session to the Exchange server is started, the most appropriate Receive connectors is chosen to handle it.This is based on the Exchange server IP address and port the fledgling session is being received on and what the IP address the calling device is using (the most specific range of IP addresses on the Receive connectors bound to the listening port wins, and selects its parent connector). Although less common if the remote computer authenticates, the authenticated user can also help elect the chosen receive connector.

 

Once the Exchange server has selected the most specific connector, the settings on that connector govern the following SMTP conversation. You cold for example not allow SMTP authentication (and say what authentication methods are allowed) for a particular connector, allow (or enforce) TLS (encryption), turn on/off logging of the SMTP conversation, specify what classes of devices may authenticate (users, other exchange severs etc), even customise the server name inserted into the SMTP HELO banner message .

 

Exchange comes with one "one size fits all" connector what sort of just works, however there are distinct advantages in further customisation. For example. For example not allowing authentication (*) on smtp connections received from the internet, logging the conversations and logging it all; or (on a receive connector targeted at selected internal IP addresses) allowing anonymous (*) email sent from your domain. Whilst still allowing the normal authenticated SMTP chatter between multiple exchange servers. You could also set an internet facing receive connector to ensure email from (lets say) your banks mail server IP addresses has encryption enforced.

 

(* - Stops spammer poking at your server to try to find a login that allows email relaying) 

(** - just setting this on the connector is not enough by itself to enable anonymous email handling- but the connector setting is part of the equation)

 

x64






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users