Does ClamAV and SpamAssasin make sense on Secondary Email Server?
Does it make sense to activate ClamAV and SpamAssasin on the Secondary Email Server?
They are active on the Main Email Server (even if they don’t seem to work, but I’ll open a separate post for this problem).
| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Debian 12 |
| Webmin version | 2.111 |
| Virtualmin version | 7.10.0 |
| Related packages |
Decades ago I set up a second machine, ie, higher MX record. It seemed ONLY spammers hit that one while the primary was up so I tightened up what it considered spam.
I did not understand.
Is your advice to activate ClamAV and SpamAssassin as well?
Yes. I’m not sure but I think spammers will hit ANY open port 25 they can find. I got the impression they believed that would get them around checking since, at least back then, the secondary was only supposed to be a ‘disaster’ stand by.
At that point, both my MX servers were on a separate machine from the actual user email boxes. Our original server had 5 seat license. In the early days of dial up, email messages weren’t being used to send large files and other content so that was enough. Once spamming started to take off, the 5 seats wasn’t nearly enough concurrent connections so I had to put up a machine to do filtering. I did a pair. Watching the logs, I NEVER saw a valid email hit the secondary MX so I cranked down the controls pretty hard on that one.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.