Community Discussions and Support
Configure Mercury to accept mail relayed from another INTERNAL mail server

I saw a suggestion somewhere that to help mitigate the problem of spam senders looking for the secondary MX you could set up a 3rd MX that is the same as your first MX thus possibly causing the spam sender to really send to your primary MX.  Of course this does not guarantee that a spam sender won't figure out that you are trying to circumvent his attempt to send to your true secondary MX.

I saw a suggestion somewhere that to help mitigate the problem of spam senders looking for the secondary MX you could set up a 3rd MX that is the same as your first MX thus possibly causing the spam sender to really send to your primary MX.  Of course this does not guarantee that a spam sender won't figure out that you are trying to circumvent his attempt to send to your true secondary MX.

Hello,

We have two mailservers internally, a Mercury/32 4.61 server which is primary (with MX record priority 0) and a Zimbra server which is secondary (MX priority is 10). Some mail from outside gets to the secondary server first instead of Mercury and, since the user account isn't recognized on the secondary the mail gets rejected. I think I know how to make the secondary Zimbra server relay those messages to the Primary Mercury server but I don't know how to tell Mercury to accept them; or do I need to do anything at all. i.e. will Mercury happily accept them without any further configuration? Currently running modules S,P,E and I on Mercury.

Thanks, David Silsbee

 

 

<p>Hello,</p><p>We have two mailservers internally, a Mercury/32 4.61 server which is primary (with MX record priority 0) and a Zimbra server which is secondary (MX priority is 10). Some mail from outside gets to the secondary server first instead of Mercury and, since the user account isn't recognized on the secondary the mail gets rejected. I think I know how to make the secondary Zimbra server relay those messages to the Primary Mercury server but I don't know how to tell Mercury to accept them; or do I need to do anything at all. i.e. will Mercury happily accept them without any further configuration? Currently running modules S,P,E and I on Mercury. </p><p>Thanks, David Silsbee </p><p> </p><p> </p>

We have two mailservers internally, a Mercury/32 4.61 server which is

primary (with MX record priority 0) and a Zimbra server which is

secondary (MX priority is 10). Some mail from outside gets to the

secondary server first instead of Mercury and, since the user account

isn't recognized on the secondary the mail gets rejected. I think I

know how to make the secondary Zimbra server relay those messages to

the Primary Mercury server but I don't know how to tell Mercury to

accept them; or do I need to do anything at all. i.e. will Mercury

happily accept them without any further configuration? Currently

running modules S,P,E and I on Mercury.

If the Zimbra server is doing an MX function and the domain is not local to this host then it check to see if the Mercury host is online and if so will forward the mail.  If the host is not online it will queue the mail for later delivery and check on the status of the Mercury host every so often.  When it's online then it will forward the queued mail to the Mercury host and the Mercury host will accept it without any further configuration. 
<blockquote>We have two mailservers internally, a Mercury/32 4.61 server which is primary (with MX record priority 0) and a Zimbra server which is secondary (MX priority is 10). Some mail from outside gets to the secondary server first instead of Mercury and, since the user account isn't recognized on the secondary the mail gets rejected. I think I know how to make the secondary Zimbra server relay those messages to the Primary Mercury server but I don't know how to tell Mercury to accept them; or do I need to do anything at all. i.e. will Mercury happily accept them without any further configuration? Currently running modules S,P,E and I on Mercury.</blockquote>If the Zimbra server is doing an MX function and the domain is not local to this host then it check to see if the Mercury host is online and if so will forward the mail.  If the host is not online it will queue the mail for later delivery and check on the status of the Mercury host every so often.  When it's online then it will forward the queued mail to the Mercury host and the Mercury host will accept it without any further configuration. 

Thanks Thomas,

So I'll set up the Zimbra server to relay non-local incoming mail to the Mercury server. I'm a little curious why a significant number of messages seem to want to go to the Zimbra server first, even though its set up as the secondary MX destination with our authoritative DNS host.

<p>Thanks Thomas,</p><p>So I'll set up the Zimbra server to relay non-local incoming mail to the Mercury server. I'm a little curious why a significant number of messages seem to want to go to the Zimbra server first, even though its set up as the secondary MX destination with our authoritative DNS host. </p>

Some spam programs prefer using MX hosts with lower priority as they expect less effective anti-spam measures there. There is nothing you can do to force them to use a specific MX host.

/Rolf 

<p>Some spam programs prefer using MX hosts with lower priority as they expect less effective anti-spam measures there. There is nothing you can do to force them to use a specific MX host. </p><p>/Rolf </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft