I'd like to configure a Mercury for spam and virus protection so, that in
the very same network segment an other server (Postfix running on Linux) is
already existing.
According to my idea I would switch the external IP / port 25 in my router's
NAT option from the internal IP address of the Postfix server (192.168.0.3)
to
the IP address (192.168.0.5) of the "new" Mercury server onto port
25.
After the spam and virus check, I'd like to hand over all the "clean" mails
to the Postfix.
a.) do I have to use "Domain Mailbox" for this?
b.)
'admin' is enough as local user, isn't it?
c.) MercuryS and MercuryE enough
to do this?
To solve this issue what is the best solution?
1.) with 'mercfwd.dll
Daemon', or
2.) with 'Rewrite' (is it possible to use this option in case of
more (2) domains)?
Here comes a part from mercury.ini:
1st case:
[Domains]
prefilter: prefilter
prefilter:
mail.example-1.com
prefilter:
mail.example-2.com
daemon:c:\mercury\mercfwd.dll;[192.168.0.3]:
mail.example-1.com
daemon:c:\mercury\mercfwd.dll;[192.168.0.3]:
mail.example-2.com
2nd case:
[Rewrite]
mail.example-1.com: [192.168.0.3]
mail.example-2.com:
[192.168.0.3]
Note to the test case for the 1st option:
at the start
of Mercury the mercfwd.dll writes the following to the console:
Fri, 13:33:53 MercFwd Daemon is designed for MercuryAPI 3.01 - 4.198.
Fri,
13:33:53 Current version is 4.218,
Fri, 13:33:53 you may encounter some
compatibility problem.
Fri, 13:33:53 Daemon MercuryForward 0.03
started.
Despite all this it worked in case of local tests.
The version for testing: Mercury/32 v4.73 + SpamHalter, clamwall,
graywall.
Thank you in advance for all your help
Peter
<p>I'd like to configure a Mercury for spam and virus protection so, that in
the very same network segment an other server (Postfix running on Linux) is
already existing.</p>
<p>According to my idea I would switch the external IP / port 25 in my router's
NAT option from the internal IP address of the Postfix server (192.168.0.3)
to
the IP address (192.168.0.5) of the "new" Mercury server onto port
25.</p>
<p>After the spam and virus check, I'd like to hand over all the "clean" mails
to the Postfix.
a.) do I have to use "Domain Mailbox" for this?
b.)
'admin' is enough as local user, isn't it?
c.) MercuryS and MercuryE enough
to do this?</p>
<p>To solve this issue what is the best solution?
1.) with 'mercfwd.dll
Daemon', or
2.) with 'Rewrite' (is it possible to use this option in case of
more (2) domains)?</p>
<p>Here comes a part from mercury.ini:</p>
<p><strong>1st case:</strong></p>
<p>[Domains]
prefilter: prefilter
prefilter:
mail.example-1.com
prefilter:
mail.example-2.com
daemon:c:\mercury\mercfwd.dll;[192.168.0.3]:
mail.example-1.com
daemon:c:\mercury\mercfwd.dll;[192.168.0.3]:
mail.example-2.com</p>
<p><strong>2nd case:</strong></p>
<p>[Rewrite]
mail.example-1.com: [192.168.0.3]
mail.example-2.com:
[192.168.0.3]</p>
<p><strong>Note</strong> to the test case for the 1st option:
at the start
of Mercury the mercfwd.dll writes the following to the console:</p>
<blockquote>
<p>Fri, 13:33:53&nbsp;MercFwd Daemon is designed for MercuryAPI 3.01 - 4.198.
Fri,
13:33:53&nbsp;Current version is 4.218,
Fri, 13:33:53&nbsp;&nbsp;&nbsp; you may encounter some
compatibility problem.
Fri, 13:33:53&nbsp;Daemon MercuryForward 0.03
started.</p></blockquote>
<p>Despite all this it worked in case of local tests.</p>
<p>The version for testing: Mercury/32 v4.73 + SpamHalter, clamwall,
graywall.</p>
<p>Thank you in advance for all your help</p>
<p>Peter</p>