Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

milter-greylist 4.1.1 Problem

milter-greylist 4.1.1 Problem

2008-04-13 by Jim Hermann

When I try to run milter-greylist version 4.1.1 with my existing
greylist.conf, I get this result:

# /usr/local/bin/milter-greylist-4.1.1 -v -c
loading config file "/etc/mail/greylist.conf"
load acl net 127.0.0.0/255.0.0.0
register acl last WHITELIST
[snip]
load acl net 64.12.136.0/255.255.255.0
load acl spf pass
unknown token """ line 208

My /etc/mail/greylist.conf line 208 is:

racl whitelist addr 64.12.136.0/24 spf report "SPF_OK From %f at IP %i
- Sender IP whitelisted, not delayed by %V" # AOL - confirmed - jwh

Is this format no longer supported?  It works fine with version 4.0.

Jim

Re: [milter-greylist] milter-greylist 4.1.1 Problem

2008-04-13 by manu@netbsd.org

Jim Hermann <hostmaster@...> wrote:

> racl whitelist addr 64.12.136.0/24 spf report "SPF_OK From %f at IP %i
> - Sender IP whitelisted, not delayed by %V" # AOL - confirmed - jwh
> 
> Is this format no longer supported?  It works fine with version 4.0.

Config file regression are bugs. Bugs shall be fixed.

I suspect recent spf changes to be the culprit, but I would like to be
sure. What happens if you replace "spf" by "spf pass"?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Re: milter-greylist 4.1.1 Problem

2008-04-14 by Jim Hermann

--- In milter-greylist@yahoogroups.com, manu@... wrote:
>
> Jim Hermann <hostmaster@...> wrote:
> 
> > racl whitelist addr 64.12.136.0/24 spf report "SPF_OK From %f at IP %i
> > - Sender IP whitelisted, not delayed by %V" # AOL - confirmed - jwh
> > 
> > Is this format no longer supported?  It works fine with version 4.0.
> 
> Config file regression are bugs. Bugs shall be fixed.
> 
> I suspect recent spf changes to be the culprit, but I would like to be
> sure. What happens if you replace "spf" by "spf pass"?
> 
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz
> manu@...
>

That works.

Jim

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.