Getting Blacklist filtering to work on a New 2nd SMTP server

HCL Domino Domino Forum
1

I recently added a 2nd SMTP box and I’m having some trouble getting the Blacklist filtering to work. The new server is sending and receiving email ok, but the Blacklist filtering doesn’t seem to be working. We had cut down on our SPAM quite a lot, but now that we have the new server in place, it’s back!

I have one configuration document that’s for [ALL SERVERS] and filtering is still working on my original server…

So any of you got any ideas, that I could check on my config?

jer

2

Subject: getting Blacklist filtering to work on a New 2nd SMTP server

I have two SMTP boxes sharing an [ALL SERVERS] configuration, and blacklisting does work on both. Haven’t been on 6.0.2 CF2 for a while, but did run it at one point. The [ALL SERVERS] setting refers to servers in the same directory – do your servers share the same nab?Are these servers sharing anything at all on this config doc? You could test by changing or setting one of the INI settings and see if both servers pick it up.

3

Subject: RE: getting Blacklist filtering to work on a New 2nd SMTP server

Thanks for the reply Bob!

Both servers are listed in the same NAB and are part of the same network and Notes domains, if that’s what you mean… The actual NAB is a replica of another server though…

I tried adding an ini parameter to the config document. How long should that take to populate the individual server’s ini file?

4

Subject: getting Blacklist filtering to work on a New 2nd SMTP server

Well I finally found the issue. Too many wanna-be administrators! The network manager installed the new server and configured it. We ended up with a new config document (besides the ALL Servers doc) on that server’s NAB, specifically for that server. It didn’t have any of the Blacklist fields populated. AND, the NAB on that server wasn’t replicating with the NAB on the admin server.

5

Subject: RE: getting Blacklist filtering to work on a New 2nd SMTP server

Good outcome. For me it hsa been a good time saver to have the two boxes share a single config doc. Depending on the change it still means applying the changes twice, with “te smtp update config” or “te router update config” or “set rules”, but it eliminates duplicate entries and I never waste time chasing ghosts when a problem happens some times but not others.