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 recipients as well. In my particular case the accounts are held in a mysql database, and it is replicated to the spare server
Wolfgang Hamann == Joshua 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 in most cases, spam goes to mail1 and got dropped. This is great. But then the spam tries to go ahead for mail2, and I did not enable mail2 for spamassassin (because it is mainly for redundancy, and not powerful enough). This makes mail2 extremely busy to send reply to the spammer of user unknown or other reporting messages. My question is, if I don't want mail2 to run spamassassin, just for relaying messages to mail1 (as it's main purpose--redundancy), how can I configure mail2 "NOT TO" reply the spammer for the undelivery?
