If that PF table is <spamd-white>, then it will get reset when you run spamd-setup(8) or reboot. Maybe a better way is to manually add this IP to the spamdb whitelist:
spamdb -a 207.126.144.121
In this case the grey entry will be ignored and stay in the database until it expires.

Or, even better, regularly add/update all OBSMTP addresses in your whitelist via SPF. Search the archives for people who made scripts for this kind of thing.

Greylisting is great, but some mail delivery networks need a little help in the form of manual whitelisting of their netblocks.


Op Wed, 14 Aug 2013 15:38:50 +0200 schreef ML mail <mlnos...@yahoo.com>:
This mail server has been somehow wrongly marked as grey and would stay stuck like in this state not allowing mails flowing in. Somehow after 3 attempts it should have whitelisted this IP so it didn't. What I now did is to manually add this IP my PF spamd whitelist. The final goal being simply to allow mail coming in from this mail server.

Regards,
M.L.
________________________________
 From: Boudewijn Dijkstra
<sp4mtr4p.boudew...@indes.com>
To: misc <misc@openbsd.org>
Sent: Wednesday,
August 14, 2013 12:39 PM
Subject: Re: remove entry from spamdb greylist

Op
Tue, 13 Aug 2013 17:49:51 +0200 schreef ML mail <mlnos...@yahoo.com>:
I am
using spamd in greylisting mode and would like to delete the
following entry:


GREY|207.126.144.121|eu1sys200aog106.obsmtp.com|<no_reply@sender>|<recipient@
domain>|1376398715|1376400232|1376413115|4|0

I tried the following command:

spamdb -d 207.126.144.121


Unfortunately it does not remove
the entry as it is still there. Any
ideas what could be wrong?

An IP
address can only be used as a key for WHITE and TRAPPED entries. The
spamdb(8)
utility was not designed to remove GREY entries, but if you are
clever, you might be able to use it for this purpose.

Anyway, the important question is:
what are you trying to accomplish?




--
Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/
(Remove the obvious prefix to reply privately.)

Reply via email to