HOW TO USE SMTP RELAY SERVICES TO KEEP SPAMMERS AWAY
A legitimately arranged SMTP relay can protect your Email Server by averting untrusted SMTP servers on the Internet from specifically speaking with your Email server. A SMTP relay doesn't require a lot of framework resources and you can introduce the SMTP service without acquiring the resource or security overhead you would have if you introduced the IIS W3SVC (World Wide Web service).
A SMTP relay is a machine that can acknowledge incoming and outgoing SMTP messages and forward them to their fitting area. The machine is a SMTP relay since it is not the endpoint of the SMTP message. You can think about the SMTP relay as a SMTP switch. The SMTP relay courses SMTP messages to the fitting location. No messages are stored on the SMTP relay as it is not definitive for any SMTP mail domains.
A great many people who execute a SMTP relay consider using it for incoming mail. The SMTP relay machine acknowledges mail just for the domains you host. For instance, if you host an email domain named maildomain.com, then the relay acknowledges messages for that domain and courses them to the suitable location. The appropriate location might be an Email Server on the interior system, or it might be another SMTP relay that is in charge of spam catching and infection checking. Mail bound to domains you don't host is dropped by the SMTP relay. This keeps spammers from using your Email Server to relay spam to other mail domains on the Internet.
One of the significant preferences of the outgoing SMTP relay is that it can likewise be designed as a message screener that can evacuate attachments. Numerous pervasive infections and worms incorporate attachments and surge the Internet with sham mail with viral payload. The outgoing SMTP relay can strip the attachments or block the messages from leaving your system. You can use a full highlighted email antivirus application like GFI's MailSecurity or you can use the implicit ISA Server 2004 SMTP Message Screener.
The test in this whole plan is designing the SMTP service on the SMTP relay machine to support both inbound and outgoing relay. There are a few pre-requisites for our SMTP relay:
• Inbound SMTP relay is permitted just for domains you host
• Outgoing SMTP relay is permitted to any domain
• The machine must not be an open SMTP relay that can be used by criminal spammers
• Remote clients can forward mail to domains you don't host by confirming with the SMTP relay machine
Inbound SMTP Relay is Allowed Only to Domains You Host
The SMTP relay machine ought to just acknowledge mail for relay to domains you host. For instance, in the event that you host the domain maildomain.com, the SMTP relay ought to just acknowledge mail for that domain and reject mail for whatever other domain. (In any event, this ought to be the situation for unauthenticated connections). The explanation behind this is if external SMTP servers and customers can send mail to different domains through your SMTP relay, then those machines will have the capacity to relay spam through your SMTP server. You need to reject mail sent to the SMTP relay for domains you don't host.
Outgoing SMTP Relay is Allowed to Any Domain
If you exploit outgoing SMTP relay, you have to set the SMTP relay PC to permit outgoing relay to any to any mail domain. You should permit relay to any mail domain since you can't foresee what domains your inner system clients will send mail to. You can design the Email Server with a rundown of domains to which you don't need clients to send mail to in the event that you need to make an outgoing mail list. In any case, by and large, the SMTP relay machine ought to have the capacity to send outgoing mail to any domain.
One imperative capacity the outgoing SMTP relay must complete is determining names of Internet mail domains incorporated into the outgoing SMTP messages. For instance, when a client sends an outgoing message to email@example.com, the outgoing SMTP relay must have the capacity to determine the microsoft.com email domain to the IP address of a server that can acknowledge incoming mail for the microsoft.com domain. This requires the SMTP relay have outgoing access to the DNS (UDP) question and DNS (TCP) zone exchange protocol. The SMTP relay will use these protocols to question DNS servers when determining the MX domain name for the destination mail server.