Milter-greylist

OK, I hope I don't get kicked around too much for this.

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.

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?

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? 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.

TIA


---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst 

<hoogendyk@...>

--------------- 

Erd\ufffds 4

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@...

manu@... wrote:
> 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.
>   

Since I'm on Solaris, then, I should stick with 3.0?


>> 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.
>   

Cool. That certainly eases the upgrade pains.


>> 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?
>   

You know, bad as it seems, I haven't paid too much attention to that. 
Since I haven't, and it seems gcc wants a -m64 flag to do 64 bit, I'm 
going to assume that my stuff is 32 bit.

I saw from the readme that that presents a problem with file descriptors 
and thus open sessions. How would I tell if that is a problem for us? 
We've set the connection timeout on Sendmail so that we rarely have 
above 20 sendmail processes at the same time. But I don't know how that 
correlates with the milter-greylist activity.

I'm also not totally clear on the compatibility issues between things 
that have been built 32bit and 64bit (shame on me for not knowing after 
all these years). In other words, if I choose to build milter-greylist 
64bit, where would the cascade of other required rebuilds end?


---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst 

<hoogendyk@...>

--------------- 

Erd\ufffds 4

On 9/26/07, manu@... <manu@...> wrote:
>  4.0b2 is fairly stable. We have major trouble on Solaris, but on other
>  system, it should be okay.

I run it on Solaris 10 and I have crashes when there's a lot of
connections due to the file descriptor problem. I'm trying a fixed
version but Chris is running Solaris 9 and Sun hasn't produced any
patches for anything other than Solaris 10. My best advice would be to
use Sendmails features like connection rate/throttling to keep it
happy combined with a restart script in cron.

I also have problems with the MX sync not working even in the latest
beta, I can connect to both servers on port 5252 without problems but
the daemon doesn't seem to even try, nothing is logged and the conf is
the same since it used to work. Maybe Chris doesn't use it on several
servers so he will be OK?

-- 
/peter

Chris Hoogendyk <hoogendyk@...> wrote:

> Since I'm on Solaris, then, I should stick with 3.0?

I don't know: we still have to understand how milter-greylist stopped
working on Solaris.

> > 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.
> Cool. That certainly eases the upgrade pains.

That's the goal: just upgrade and restart the milter and you are done. 

> > 32 bit or 64 bit apps?
> You know, bad as it seems, I haven't paid too much attention to that.
> Since I haven't, and it seems gcc wants a -m64 flag to do 64 bit, I'm
> going to assume that my stuff is 32 bit.
> 
> I saw from the readme that that presents a problem with file descriptors
> and thus open sessions. How would I tell if that is a problem for us?
> We've set the connection timeout on Sendmail so that we rarely have 
> above 20 sendmail processes at the same time. But I don't know how that
> correlates with the milter-greylist activity.

I don't know either, but I'm interested to know?

> I'm also not totally clear on the compatibility issues between things
> that have been built 32bit and 64bit (shame on me for not knowing after
> all these years). In other words, if I choose to build milter-greylist
> 64bit, where would the cascade of other required rebuilds end?

You need to have 64 bit versions of the libraries linked with
milter-greylist, but sendmail does not need to be 64 bits, for instance.

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

shuttlebox <shuttlebox@...> wrote:

> I also have problems with the MX sync not working even in the latest
> beta, I can connect to both servers on port 5252 without problems but
> the daemon doesn't seem to even try, nothing is logged and the conf is
> the same since it used to work. Maybe Chris doesn't use it on several
> servers so he will be OK?

MX sync also uses stdio's streams, so it may be the same problem.

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