Created attachment 206946 [details]
The summary says it essentially. Attached trivial patch adds options for DRAC and SpamAssassin to milter-greylist. Neither of these currently can be enabled through the options menu, but is supported by milter-greylist and covered in the ports documentation.
Should these be added to OPTIONS_DEFAULT (for package users)
(In reply to Kubilay Kocak from comment #1)
I think it's better to not make these default, in order to maintain backward compatibility. Also, the appropriate configuration snippets are not included in the sample greylist.conf.
(In reply to Helge Oldach from comment #2)
I agree with keeping backward compatibility, but not necessarily on it's own, and that it should be weighed up with value of packages to users out of the box in the general case, which I believe should always be priority #1.
Obviously weighing those two considerations against dependency proliferation is important too.
It would be lovely to have our cake and eat it too (subpackages will help with this in the future).
With packages these days, the defacto is 'lean toward more by default out of the box, unless its ridiculous/exceptional'
(In reply to Kubilay Kocak from comment #3)
Got your point, though we might consider that SpamAssassin will pull in many more packages (in my case 115!) while the DRAC option is standalone. At the end of the day I don't have a strong opinion on this.
(In reply to Helge Oldach from comment #4)
Yeh SpamAssassin is fairly heavy. Alternative to defaulting the option ON, isa slave port to mail/milter-greylist for a spamassasin-enabled version (mail/milter-greylist-spamassasin)
No strong opinion here either, just wanted to make sure the questions/considerations were raised
The patch seems OK for me.
Speaking of enabling spamasassin by default I am with the submitter and I personally prefer to keep it disabled by default as it has toons of dependencies.
Although having a slave port seems totally reasonable