Solved

Separate SMTP and POP3 Server

Posted on 2006-07-24
7
580 Views
Last Modified: 2006-11-18
Hi All,

My current configuration as follows:
- Exchange Server, public IP for incoming mail (let's say mail.mydomain.com). For outgoing mail, users still send email through mail.mydomain.com, but we configure to forward all outgoing mail to another mail server that using MDaemon (which i will decribe below)
- MDaemon, no public IP (using NAT), for outgoing email only (receive outgoing mail from Exchange Server). faked domain (let's say mail.fakedomain.com).
- Internal Linux DNS Server (our own build)

Current Problem :
- Some domain can't be found, even though i have set DNS server directly to our ISP
- Some domain reject/refuse our mail (perhaps considered as a spammer or others).

Questions/Solutions:
- Change MDaemon to public IP (this one i can do it)
- I am planning to separate SMTP and POP3 server, Exchange Server still have the same functions and configurations as stated above, MDaemon will functions as SMTP (real domain, let's say SMTP.mydomain.com), how do i configure this ? Will it solve my problem ?

Thanks for your kind attention and sharing.

Regards,
Andy
0
Comment
Question by:andysk
  • 3
  • 2
7 Comments
 
LVL 22

Expert Comment

by:cj_1969
ID: 17170728
intermittant rejections could be caused by remote servers doing a reverse lookup on yur "faked" domain and then rejecting it if it does not resolve to a known/legitimate address ... basically, yes, they are treating you as a spammer.

If you put your outgoing mail server on a public IP with a domain that is resolvable then this could very well take care of your problem.

Some domains can't be found ... from a command prompt run nslookup and see if you can resolve them manually ... this will rule out the DNS.  If you do have problems here, check your DNS server settings ... typically it will have forwarding addresses wich point to your ISPs DNS servers for resolving "other" domains ... while running nslookup, enter server <next ISP DNS server IP> and hit enter ... now try resolving the domain again.  Do this for each IP address listed as a forwarding address ... you could just have one bad DNS server that is causing the problem.
0
 

Author Comment

by:andysk
ID: 17173127
Hi CJ, Thanks for your sharing. I think you misunderstood my point. Basically i am aware that our SMTP servers might be suspected as a spammer due to the "faked" domain. Now i will make it the real domain with the configuration as follows:
- Exchange Server will become our POP3 server. (pop.mydomain.com)
- MDaemon Server will become our SMTP server. (smtp.mydomain.com)

The question is, how do i configure that design ? since those two servers contains same domain with different function, one is incoming mail, the other is outgoing mail.

About the DNS things, the problem is on our DNS server, seems it can't handle massive query (our users is around 400). I will redirect our DNS Server on SMTP Server to our ISP DNS for better resolve name.
0
 
LVL 22

Expert Comment

by:cj_1969
ID: 17176039
Leave your Exchange server set up to receive incoming mail, just forward the MX record IP address in to the Exchange server, nothing needs to change for this ... I'm assuming this is what you already have.
For sending emails, you will need to configure the MDaemon server with a legitimate name and IP address so that it is in DNS, this is all that is required for a server doing a reverse lookup.  Then all you have to do is forward your mail from your Exchange server through the MDaemon server using the SMTP Connector option.

I'm not familiar with MDaemon so I don't know what needs to be done for it to be configured as a relay but it seems like a robust app (I looked at their website) so I'm sure you can set this up.
0
 

Author Comment

by:andysk
ID: 17181297
Hi CJ, i got and agree your point. the problem i am asking is Exchanger Server and MDaemon can have same domain ?
0
 
LVL 22

Accepted Solution

by:
cj_1969 earned 200 total points
ID: 17236571
If mDaemon is for outgoing only then yes ... your DNS mail records will refer to your SMTP server to delivery everything to Exchange ... as long as your MDaemon server has a ligitimate name (such as pop.<yourdomain.com>) and IP address then this should not be an issue and it should work.
0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
PDF to Word 25 157
How does your business securely share, sync and collaborate with external partners 7 90
Magic Software info 18 131
CD-RW/DVD-ROM DRIVE 3 45
This article describes how to use the timestamp of existing data in a database to allow Tableau to calculate the prior work day instead of relying on case statements or if statements to calculate the days of the week.
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
Using Adobe Premiere Pro, the viewer will learn how to set up a sequence with proper settings, importing pictures, rendering, and exporting the finished product.
An overview on how to enroll an hourly employee into the employee database and how to give them access into the clock in terminal.

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question