On 04/28/2014 10:15 AM, Tonix - Antonio Nati wrote:
Before I quitted my email service (I migrated to a collegue wich manages
a lot more accounts than me), I was considering to use this way to
capture spam on my servers.
Only problem I see this high priority MX may be active only if another
low level MX is active, otherwise it will classify everything as SPAM,
and a simple reboot of main MX may be troublesome.
So, the main problem is to keep this spam MX up only when lower priority
MX are up.
Tonino
That would be problematic. However, I'm thinking that the dummy MX
record would not be functional, but simply a host that doesn't answer
port 25 at all. I don't see this as being a problem.
I wonder though, if this would trap anything additional to what spamdyke
already rejects. I can do some observing/measuring to figure this out.
It's not a very high priority for me at this point though.
Thanks as always Tonino.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]