Milter-greylist

Johann Klasek wrote:
> On Thu, Aug 30, 2007 at 07:29:47PM +0200, manu@... wrote:
>   
>> Jeff A. Earickson <jaearick@...> wrote:
>>
>>     
>>> I now get this with 4.0b1:
>>>
>>>     cannot write dumpfile "/var/milter-greylist/greylist.db-XXn4aOmb":
>>>     Error 0
>>>       
>> Hum... errno was not set after a failed fdopen? Any Solaris expert that
>> could explain what is going on?
>>     
>
> Just for completness:
>
> Solaris man page (eg. for fdopen) says (even on Sol 10):
>
>      The fdopen() function may fail and not set  errno  if  there
>      are no free stdio streams.
>
>
> This issue is addressed by
>
> http://jk.kom.tuwien.ac.at/~jklasek/software/milter-greylist/mg.stdio-handling.patch
>
> which seems not to interfere with other platforms but improves
> compatibility somehow.

I see that exact line in the man page on my Solaris 9 system. We are
still running the milter-greylist 1.6 that we installed over a year and
a half ago. At the time we had some issues with 2.0.2 and decided to
stick with 1.6. Since then, I've never bothered to update. Ahh,
remembering now, we are running poprelayd which creates popip.db from
the uw-imap.log and there is a patch to milter-greylist that looks up
the IP in popip.db and bypasses greylisting if it is found. The guy who
wrote that left just as 2.0.2 came out, and I hadn't had time to dig
into it yet when we went online.

We did have some issues with stability. I don't recall what we did to
make things better. It wasn't coding. Even so, we have a cron script
that runs every 15 minutes or so called greycheck. It checks to see that
greylist is still running; and, if it isn't, starts it up again and
sends us an email. It doesn't happen that often. Interesting thing is
that when it happened a couple of weeks ago, it happened on both of the
departmental servers we are responsible for. These servers are
independent, on different subnets, and with completely different users
and community of contacts.

I don't know if there is any connection between the code currently being
discussed and the version that we are running. It seems that a great
many of the features that have been added ought to have been pretty
independent of the db writing segment. Anyway, I just thought I would
throw this into the discussion.

One of my projects this fall is to update everything on our mail
servers. Up to now, we've been tuning and adjusting. But it seems time
to upgrade, especially if there seem to be some Solaris stability
improvements coming in.


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

Chris Hoogendyk

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

<hoogendyk@...>

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

Erd\ufffds 4