Xeams Home » Products » Xeams » Knowledge Base

Document information

Document ID:	347
Subject:	What is the difference between Smtp Server and Smtp Proxy Server
Creation date:	2/28/09 10:38 AM
Last modified on:	3/13/09 7:58 PM

Smtp Server and Smtp Proxy Server

Xeams offers two types of Smtp Servers:

1. Smtp Server
2. Smtp Proxy Server

Smtp Server The built-in Smtp server is the default mechanism in Xeams to accept new messages from a client. This Smtp Server accepts in-coming emails and stores the message in a local repository. If the message is bound for another SMTP server, the message gets queued and is finally delivered to the destination. If you decide to use Smtp authentication, you will have to create local users in Xeams. This Server can be used in all 3 operating modes (Stand-alone, Spam Firewall and Hybrid) of Xeams When should you use Smtp Server? Consider using Smtp Server when: Xeams is the final destination for all in-bound emails. You are using Xeams in Stand-alone mode. In this mode Xeams does not require any other email server and therefore, you cannot use the Smtp Proxy Server. You want to provide redundancy for your primary email server.

Smtp Proxy Server The built-in Smtp Proxy server can only be used if you have another server in your network that accepts emails. It sits in between a client and this other Smtp server. It does not have a local queue. Instead, when a client connects to send an email, the proxy server opens a TCP/IP connection to the actual server and simply watches what the client is sending. Besides watching the email, it can also modify and block the message. If the actual server goes down, so will Xeams. A proxy server requires less configuration in Xeams. You do not have to configure domain names and users in Xeams. This is because the primary server decides which emails to accept. This Server cannot be used in Stand-alone mode. It can only be used in Spam Firewall and Hybrid modes. When should you use Smtp Proxy Server? Consider using Smtp Proxy Server when: Xeams is NOT the final destination for in-bound emails. Consider the scenario where you are using Microsoft Exchange as your email server and want to use Xeams to filter spam. You are using Xeams in Spamwall or Hybrid mode. You have users on the Internet (outside your company's network) who want to use your email server to send their out-bound messages and you want to them to authenticate before accepting their message.

User comments

Add a comment to this document

Do you have a helpful tip related to this document that you'd like to share with other users? Please add it below. Your name and tip will appear at the end of the document text.

Your name:
Your email:	Hide my email address
Verification code:	Enter the verification code you see above more submitting your tip
Tip:	Please limit tips to 1000 characters