Precedence in SMTP connection control

pbeddy

posted Jul 21 '16 at 4:55 am

Good day all.

I am investigating the possibility of using a paid filtering

service offered by DuoCircle to run as our MX, which then in turn delivers

legitimate mail to our local Mercury32 server. I already have all users required to

authenticate over SMTP in order to send out email from phones, tablets etc. I

will now add the list of DuoCircle servers to the allowed connection list,

followed by a “deny all” rule which will block any other direct delivery to our

server. My question is as follows: What do I need to do so that my users who

may be connecting from outside our network (from home ADSL or 3G data or

similar) are still able to use our Mercury SMTP as their outgoing server? Will

an authenticated user’s rights trump a connection refusal rule?

Any information would be much appreciated.

Good day all. I am investigating the possibility of using a paid filtering service offered by DuoCircle to run as our MX, which then in turn delivers legitimate mail to our local Mercury32 server. I already have all users required to authenticate over SMTP in order to send out email from phones, tablets etc. I will now add the list of DuoCircle servers to the allowed connection list, followed by a “deny all” rule which will block any other direct delivery to our server. My question is as follows: What do I need to do so that my users who may be connecting from outside our network (from home ADSL or 3G data or similar) are still able to use our Mercury SMTP as their outgoing server? Will an authenticated user’s rights trump a connection refusal rule?Any information would be much appreciated.&nbsp;&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history