Hi all,
Here is my conclusion:
Many experts seem to have this same opinion: To enable 2nd, 3rd,,,etc
mail server the same defence (antivir, antispam) as the primary one.
Because the spamer knows the weak point/path to spam.
So I decide to 'join' all the experts that post the above idea.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua, C.S. Chen wrote:
> Looks like I have to enable SA in the 2nd server. It might be a spam
> hole if the spam sent to 2nd first, then forcily relayed to the primary.
>
>
Sorry for the late response, I'm just catching up on some backlog.
Here's
On 29-Mar-06, at 12:11 AM, Joshua, C.S. Chen wrote:
Looks like I have to enable SA in the 2nd server. It might be a spam hole if the spam sent to 2nd first, then forcily relayed to the primary.
If you are running postfix MTA on your 2nd server, you can map your email user list of main MTA serve
Looks like I have to enable SA in the 2nd server. It might be a spam
hole if the spam sent to 2nd first, then forcily relayed to the primary.
Thanks for all your opinions
Cheers
Joshua
martin wrote:
Joshua, C.S. Chen asiaa.sinica.edu.tw> writes:
Hi folks,
I am using spamassa
Joshua, C.S. Chen asiaa.sinica.edu.tw> writes:
>
> Hi folks,
> I am using spamassassin 3.1.0 and it works well. Now in my institute, we
> have 2 mx (mail servers) see it's dns record
>
> myinstitute.edu.tw. 300 IN MX 100 mail2.myinstitute.edu.tw.
> myinstitute.edu.tw. 300 IN MX 2 mail1.myinstit
"Bowie Bailey" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> 1) Get rid of the secondary
> 2) Make the secondary capable of rejecting messages based on spam,
> virus, unknown user, etc the same way the primary does.
> 3) Find a way to have the secondary only accept mail when the
Joshua, C.S. Chen wrote:
> Hi folks,
> I am using spamassassin 3.1.0 and it works well. Now in my institute,
> we have 2 mx (mail servers) see it's dns record
>
> myinstitute.edu.tw. 300 IN MX 100 mail2.myinstitute.edu.tw.
> myinstitute.edu.tw. 300 IN MX 2 mail1.myinstitute.edu.tw.
>
>
>
> Now
Hi,
I changed my first mailserver to not accept mail for non-existant accounts (so
these mails do not take SA resources either),
but a lot of spam seems to be sent to the 2nd MX anyway.
So the consequence was to make an account list available to the 2nd server, so
it can reject non-existent reci
Hi folks,
I am using spamassassin 3.1.0 and it works well. Now in my institute, we
have 2 mx (mail servers) see it's dns record
myinstitute.edu.tw. 300 IN MX 100 mail2.myinstitute.edu.tw.
myinstitute.edu.tw. 300 IN MX 2 mail1.myinstitute.edu.tw.
Now in most cases, spam goes to mail1 and got dro
