Yahoo Groups archive

Milter-greylist

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

Message

Re: [milter-greylist] best stable version (conservative)

2007-09-26 by manu@netbsd.org

Chris Hoogendyk <hoogendyk@...> wrote:

> Because of some locally developed code that interfaces with poprelayd,
> we are still running milter-greylist 1.6. However, we've finally got 
> other things tuned and running in a way that this is no longer required.
> So, we need to upgrade. I figure we'll jump at least a whole version,
> and maybe two versions, but not leap into CVS or the latest beta.

4.0b2 is fairly stable. We have major trouble on Solaris, but on other
system, it should be okay.

> I'm guessing that 3.0 would be the way to go. However that's now 6 
> months back, and there have been code changes to that branch since then.
> What is 3.0nb2? I'm not familiar with the nb notation. Should I just 
> grab the 3.0 from the main site and not worry about it?

3.0nb2 is a notation from the NetBSD package system (pkgsrc). It's for
the second revision of the package, while the software is 3.0. There is
no reason you use that unless you use pkgsrc.

> We're going to run into all kinds of changes in the configuration files.
> Without immediately adding any of the many new features that have been
> put in through 2... and 3..., what are we going to have to do to get our
> configuration file in line? 

Some option have been deprecated, but backward compatibility is supposed
to have been maintained: you should be able to drop your config file
from a 1.0 installation on 4.0b2 and it should just work.

> And, should the new milter-greylist just 
> plug into our existing panoply of mail applications? We're running 
> Sendmail 8.13.6, mimedefang 2.54, spamassassin 3.2.1, and, well, I guess
> the rest of it doesn't matter much. It's on Solaris 9 on SPARC.

32 bit or 64 bit apps?

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

Attachments

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.