Yahoo Groups archive

Milter-greylist

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

Thread

"milter-greylist" under Solaris SPARC

"milter-greylist" under Solaris SPARC

2007-12-06 by Matthias Scheler

Hello,

is anybody using "milter-greylist" under Solaris SPARC? Does it work stable?

	Kind regards

P.S. See <http://mail-index.netbsd.org/port-sparc64/2007/12/04/0000.html>
     for the background.

-- 
Matthias Scheler                                  http://zhadum.org.uk/

Re: [milter-greylist] "milter-greylist" under Solaris SPARC

2007-12-06 by shuttlebox

On Dec 6, 2007 2:04 PM, Matthias Scheler <tron@...> wrote:
>  Hello,
>
>  is anybody using "milter-greylist" under Solaris SPARC? Does it work
> stable?

4.0 is very stable for me. Lots of work was put in to making it stable
though. Read more here too:
http://developers.sun.com/solaris/articles/stdio_256.html.

As a Solaris user you might also be interested in using
milter-greylist packaged from Blastwave with dependency handling much
like apt/yum.

http://www.blastwave.org/packages.php/miltergreylist

-- 
/peter

Re: [milter-greylist] "milter-greylist" under Solaris SPARC

2007-12-06 by Chris Hoogendyk

shuttlebox wrote:
> On Dec 6, 2007 2:04 PM, Matthias Scheler <tron@...> wrote:
>   
>>  Hello,
>>
>>  is anybody using "milter-greylist" under Solaris SPARC? Does it work
>> stable?
>>     
>
> 4.0 is very stable for me. Lots of work was put in to making it stable
> though. Read more here too:
> http://developers.sun.com/solaris/articles/stdio_256.html.
>
> As a Solaris user you might also be interested in using
> milter-greylist packaged from Blastwave with dependency handling much
> like apt/yum.
>
> http://www.blastwave.org/packages.php/miltergreylist

I recently upgraded from 1.6 to 4.0 after seeing the exchanges regarding 
Solaris fixes.

Fingers crossed, I have had no instability problems so far -- about a 
week. Previously, with 1.6, my cron script would see milter-greylist 
down periodically and restart it. Unfortunately, there was often a dead 
period when it wasn't down but was not functioning properly, and my cron 
wouldn't catch that.

I'm running it on three servers. Probably handle a few hundred thousand 
messages a day. Solaris 9. Sun E250s. Sendmail 8.13.6.

I don't mess with blastwave on this stuff. Just get the source. It's an 
easy one anyway.



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

Chris Hoogendyk

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

<hoogendyk@...>

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

Erd\ufffds 4

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.