Traplists do not go into tables. (for this exact reason) only the
whitelisted
hosts go into tables guys.
Bob
* Peter N. M. Hansteen [2009-07-28 15:31]:
> Renaud Allard writes:
>
> > It happened to me also with servers with huge white/black lists. If
> > it's happening for new
On 7/24/09 3:03 PM, Peter N. M. Hansteen wrote:
setting up a new spamd plus various content filtering at a client site
we were kind of baffled to see that apparently manually setting an
address to TRAPPED with spamdb, ie
spamdb -a -t 211.49.57.32
for some reason seems porous, in that messages r
Renaud Allard writes:
> It happened to me also with servers with huge white/black lists. If
> it's happening for new connections, ensure that pf is configured with
> enough maximum table entries (set limit table-entries).
That's interesting. Hitting table size limits would explain the
symptoms.
Trapping an address only affects new connections that are looked up in
the
database. it does not affect existing passed connections. spamd only updates
the
tables on it's scan of the database so these will not take effect immediately.
-Bob
* Peter N. M. Hansteen [2009-07-24
On Fri, Jul 24, 2009 at 03:03:51PM +0200, Peter N. M. Hansteen wrote:
> setting up a new spamd plus various content filtering at a client site
> we were kind of baffled to see that apparently manually setting an
> address to TRAPPED with spamdb, ie
>
> spamdb -a -t 211.49.57.32
>
> for some reaso
setting up a new spamd plus various content filtering at a client site
we were kind of baffled to see that apparently manually setting an
address to TRAPPED with spamdb, ie
spamdb -a -t 211.49.57.32
for some reason seems porous, in that messages received from that IP
address still hits the conten
6 matches
Mail list logo
