A smart host or smarthost is an email server via which third parties can send emails and have them forwarded on to the email recipients' email servers.[1]
Smarthosts were originally open mail relays,[1] but most providers now require authentication from the sender, to verify that the sender is authorised[1] – for example, an ISP might run a smarthost for their paying customers only.
YouTube Encyclopedic
-
1/3Views:1 5654721 531
-
SMTP Smart Host Server RHEL7
-
SMTP Server as a Smart Host in RED HAT ENTERPRISE LINUX 7
-
Send External Email From Exchange 2013 Through Jango SMTP smart host By Eng-Hany Abd El-Wahab
Transcription
Use in spam control efforts
In an effort to reduce email spam originating from their customer's IP addresses, some internet service providers (ISPs), will not allow their customers to communicate directly with recipient mailservers via the default SMTP port number 25. Instead, often they will set up a smarthost to which their customers can direct all their outward mail – or customers could alternatively use one of the commercial smarthost services.[2]
Sometimes, even if an outward port 25 is not blocked, an individual or organisation's normal external IP address has a difficulty in getting SMTP mail accepted. This could be because that IP was assigned in the past to someone who sent spam from it, or appears to be a dynamic address such as typically used for home connection. Whatever the reason for the "poor reputation" or "blacklisting", they can choose to redirect all their email out to an external smarthost for delivery.[3]
Reducing complexity
When a host runs its own local mail server, a smart host is often used to transmit all mail to other systems through a central mail server. This is used to ease the management of a single mail server with aliases, security, and Internet access rather than maintaining numerous local mail servers.
See also
References
- ^ a b c Moen, Rick (June 2005). "Mail Relaying/Authentication". Linux Gazette (115).
The term 'smarthost' harks back to the days before SMTP was universal and DNS reasonably reliable: The idea was that you assumed that your own host probably wasn't as well-connected and capable as, say, the UCBVAX machine at Berkeley. So, you would configure your local outbound mail processes to lob all outgoing mail over to UCBVAX via batched, dialed-up UUCP, or SMTP, or whatever, trusting to UCBVAX to perform necessary DNS lookups and redeliver the mail. UCBVAX was, in that sense, dubbed a "smarthost" for your site, in the sense that it's smarter about DNS and mail connections than yours is.
- ^ John, Chris. "When Using a Smart Host is the Smart Choice". SocketLabs. Retrieved 19 December 2018.
- ^ "Getting past email blocking". The National Bureau of Economic Research. Retrieved 19 December 2018.
This page was last edited on 19 June 2023, at 10:48