[quote user="Devon P"]

I use a program called peerblock to create my own custom allow and block rule lists and just use notepad++ to edit the lists. Easy to setup on the fly once master it. My custom block list now over 17K lines long. Peerblock is just a glorified firewall program that works with windows firewalls and dont have to create custom rules every time as this program listens on text file lists and populates the block list itself.

We had a massive problem with spammers worldwide, so we had to block all country's world wide besides the US and just allow certain domains and ip addresses from outside the US.

[/quote]

Ah - this would not work for the OP as Peerblock blocks IP addresses. You'd need some sophisticated traffic analysis to successfully allow mail from one IP address to just one domain.

Hi Guys,

I have a mercury server handling multiple domains via synonym file.
domain1.com
domain2.com
domain3.com 

etc

Is it possible or any way to tell mercury to ONLY accept smtp mail for domain2.com if it comes from ip address 123.123.123.123?
but for domain1.com and domain3.com accept from anywhere (normal SMTP behavior).

Cheers
Adam

It may be easier to rely on firewall rules to control this instead of mercury settings. I found that it is so much easier to control spam and domains via firewalls that mercury

[quote user="Devon P"]It may be easier to rely on firewall rules to control this instead of mercury settings. I found that it is so much easier to control spam and domains via firewalls that mercury
[/quote]

How would you do that? I can understand how your answer would apply to incoming mail if just one domain was being used, but not how it would apply for just one domain out of three. Mind you, we use a basic firewall/router so it may simply be that our equipment does not have the functional complexity required. It would be good to know.

I use a program called peerblock to create my own custom allow and block rule lists and just use notepad++ to edit the lists. Easy to setup on the fly once master it. My custom block list now over 17K lines long. Peerblock is just a glorified firewall program that works with windows firewalls and dont have to create custom rules every time as this program listens on text file lists and populates the block list itself.

We had a massive problem with spammers worldwide, so we had to block all country's world wide besides the US and just allow certain domains and ip addresses from outside the US.

[quote user="Devon P"]It may be easier to rely on firewall rules to control this instead of mercury settings. I found that it is so much easier to control spam and domains via firewalls that mercury
[/quote]

This is wrong. The recipient domain is transferred in OSI layer 5 (session layer) and no regular firewall filters this. One needed a session layer firewall for this.

In other words: using a regular firewall you can block all or no mails (actually: connections to your SMTP servers listening port) coming from a specific host/net but you cannot block depending on the transferred data (RCPT TO:).