Yahoo Groups archive

Milter-greylist

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

Messages

Browse messages

Page 131 of 144 · 7199 messages matched

Re: [milter-greylist] Volume

2004-11-13 by Matthias Scheler

... Yes. NetBSD-sparc64 (the UltraSPARC port) is built with it. But you should at least use GCC 3.x (better 3.3.x) because at least 2.95.x has a lot of code

Thread view Attachments: 0

So far this milter has been amazing..

2004-11-13 by jtwoodstock

I was reading the email about how much of an impact this has on Spam.. I figured I d give it a try.. Within 24 hours, I was a believer.. I ve since loaded it

Thread view Attachments: 0

Re: [milter-greylist] Volume

2004-11-12 by manu@netbsd.org

... It s not an easy change. The limitation to 256 streams is difficult to workaround in a scallable way. -- Emmanuel Dreyfus Il y a 10 sortes de personnes

Thread view Attachments: 0

Re: [milter-greylist] Volume

2004-11-12 by Cyril Guibourg

... I wasn t speaking about gcc. The trial copy I was referring to is for a product called Sun One (aka Forte C).

Thread view Attachments: 0

RE: [milter-greylist] Volume

2004-11-12 by Sutherland, James

The last message from you led me to believe that a change was necessary to the was the DB is dumped to make the 32bit executable reliable on Solaris. So I was

Thread view Attachments: 0

Access-lists in milter-greylist

2004-11-12 by manu@netbsd.org

After some discussions behind the scene with Remy Card, I repost my last proposal about an ACL mecanism for milter-greylist, so that he can reply on this topic

Thread view Attachments: 0

libspf2

2004-11-12 by manu@netbsd.org

There have been no update on that front. Should we hold 1.6 release for libspf2 support? Anyone wants to contribute it? -- Emmanuel Dreyfus Il y a 10 sortes de

Thread view Attachments: 0

Re: [milter-greylist] Volume

2004-11-12 by manu@netbsd.org

... You gave no feedback after we discovered the file descriptor shortage. Does it works properly now? -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans

Thread view Attachments: 0

Re: [milter-greylist] parse / reload bug

2004-11-11 by manu@netbsd.org

... Thank you for that one, I committed it (with a man page update, please think about updating the doc next time). -- Emmanuel Dreyfus Il y a 10 sortes de

Thread view Attachments: 0

Re: [milter-greylist] parse / reload bug

2004-11-10 by Brent J. Nordquist

... Yeah; I discovered the same kind of thing. I m supposed to be working on a patch to change this behavior (see list archive, a few days ago); a few things

Thread view Attachments: 0

parse / reload bug

2004-11-10 by Klas Heggemann

We are running greylist-milter version 1.5.10 + some patches. Yesterday I added the extra ebay range to the config file, installed and checked the syslog file

Thread view Attachments: 0

Re: Another Ebay range

2004-11-09 by iewebguy

... How can I tell if I have a thread-safe resolver? I am running a raq 550 (cobalt linux)

Thread view Attachments: 0

Re: [milter-greylist] Another Ebay range

2004-11-09 by Enrico Scholz

... at several places. Really nothing, which I would use somewhere in the near of a productive system. ... A domain + TXT entry are much easier/cheaper to get

Thread view Attachments: 0

Re: [milter-greylist] Another Ebay range

2004-11-09 by Emmanuel Dreyfus

... lippf_alt works fine for me. Beside potential problems with libspf, the key point is to link with a thread safe resolver. libspf and libspf_alt make DNS

Thread view Attachments: 0

Re: [milter-greylist] Another Ebay range

2004-11-09 by manu@netbsd.org

... I ll add it to the default config file. -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et ceux qui ne le

Thread view Attachments: 0

Another Ebay range

2004-11-09 by Joseph Burford

Hi all, Just an FYI I added 216.33.244.0/24 to local whitelisting. It s another ebay range, they just keep trying every 20 seconds and give up before the

Thread view Attachments: 0

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.