I look with great fright upon the day that the format of that dbase will change. The mailflow on my private server will be completely undone!
Anyway. No worries, I'll check the code and see what I can come up with. It's just my silly wish to torture spambots a bit. On Fri, Nov 2, 2012 at 12:27 AM, Wietse Venema <wie...@porcupine.org> wrote: > Noel Jones: > > On 11/1/2012 8:55 AM, Han Boetes wrote: > > > I think you have a point there. Let's see what happens. Maybe later > > > on I will use spamd to annoy the zombies found by postscreen. To > > > keep the logfiles clean and for sadistic reasons. ;-) > > > > > > BTW how can I read this dbase? > > > > > > ~% postmap -s btree:/var/spool/postfix/postscreen/db > > > 1.2.3.4 1351857604;1351774804;1354363204;1354363204;1354363204;0 > > > 1.2.3.5 1351782475;1351699675;1354288075;1354288075;1354288075;0 > > > 1.2.3.6 1351718020;1351643615;1354223620;1354223620;1354223620;0 > > > _LAST_CACHE_CLEANUP_COMPLETED_ 1351766276 > > > > The internal postscreen database is intentionally not documented, > > and may change without warning. > > > > If you're curious about what the fields are, read the source code. > > That's about all the help you'll get on this. > > This correct. Postfix maintains forward and backward compatibility > with great effort, but this effort is limited to what is promised > by the documentation. > > Undocumented details WILL CHANGE without notice, without compatibility > safety nets, and without hand-holding. > > Wietse > -- # Han
