ports/134347: spamlogd's whitelist expiration period is hardcoded

R. Schulze rs at bytecamp.net
Thu May 7 22:00:10 UTC 2009


>Number:         134347
>Category:       ports
>Synopsis:       spamlogd's whitelist expiration period is hardcoded
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 07 22:00:09 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     R. Schulze
>Release:        7.1-RELEASE-p5
>Organization:
>Environment:
>Description:
Spamlogd's whiteexp should not be hardcoded in grey.h.
Instead there should be a configurable whitelist expiration like stated in the docs.
>How-To-Repeat:
Configure spamd_flags "-G 4:4:192" and have a look of whitelisted entries, they do not expire after 192 hours, but after 36 days, like defined in spamd/grey.h.
>Fix:
Just add a parameter.

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list