Yahoo Groups archive

Milter-greylist

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

Thread

Volume

Volume

2004-10-12 by Sutherland, James

Anyone have experience with milter-greylist on a high volume server?  By
high volume I mean 250k incoming mail connections per day?  I've had
some problems in the past with milter falling apart under loads like
this when trying to use MPP and a virus scanner.
    -James

Re: [milter-greylist] Volume

2004-10-12 by Emmanuel Dreyfus

On Tue, Oct 12, 2004 at 09:55:01AM -0700, Sutherland, James wrote:
> Anyone have experience with milter-greylist on a high volume server?  By
> high volume I mean 250k incoming mail connections per day?  I've had
> some problems in the past with milter falling apart under loads like
> this when trying to use MPP and a virus scanner.

There are two scallability problems in milter-greylist
1) RAM usage. But if you have a big mail server you can afford to buy more
memory
2) time to dump the database to disk. This could be improved by using
several buckets and dumping to disk bucket by bucket. Or by using an
external database. Or by not dumping at all, which cause the greylist to
be lost on power outtage.

I don't see any other problem you can hit on a bigger setup.

-- 
Emmanuel Dreyfus
manu@...

RE: Volume

2004-10-12 by Sutherland, James

Well I've got it installed and it's running.  I'm worried the db file
may grow to large to be sustained.  We'll see
 
Stats so far.
 
Unique triplets in the first ten minutes: 3796
Message deliveries stopped in the first ten minutes: 5365
 
Pretty crazy.
    -James
 

________________________________
Show quoted textHide quoted text
From: Sutherland, James 
Sent: Tuesday, October 12, 2004 9:55 AM
To: 'milter-greylist@yahoogroups.com'
Subject: Volume


Anyone have experience with milter-greylist on a high volume server?  By
high volume I mean 250k incoming mail connections per day?  I've had
some problems in the past with milter falling apart under loads like
this when trying to use MPP and a virus scanner.
    -James

Statistics

2004-10-12 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Unique triplets in the first ten minutes: 3796
> Message deliveries stopped in the first ten minutes: 5365

It might be interesting to gather statistics. At mine:
11245 greylisted entries, 1099 autowhitelisted entries. Runs fine: load
is always below 1. The server is an Apple XServe G4 running NetBSD.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] Statistics

2004-10-12 by Sutherland, James

At 1hr 30 minutes I've got 38,744 greylisted and two whitelisted.
 
greylist.db is 3.6meg, and wow does graylist take some time to start.
Takes a while for it read all that data in I guess.

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Tuesday, October 12, 2004 2:53 PM
To: milter-greylist@yahoogroups.com
Subject: [milter-greylist] Statistics


Sutherland, James <jsutherl@...> wrote:

> Unique triplets in the first ten minutes: 3796
> Message deliveries stopped in the first ten minutes: 5365

It might be interesting to gather statistics. At mine:
11245 greylisted entries, 1099 autowhitelisted entries. Runs fine: load
is always below 1. The server is an Apple XServe G4 running NetBSD.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...g


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129j646v3/M=294855.5468653.6549235.3001176/
D=groups/S=1707281942:HM/EXP=1097704451/A=2376776/R=0/SIG=11ldm1jvc/*htt
p://promotions.yahoo.com/ydomains2004/index.html> 	
 
<http://us.adserver.yahoo.com/l?M=294855.5468653.6549235.3001176/D=group
s/S=:HM/A=2376776/rand=490347758> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] Statistics

2004-10-12 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> At 1hr 30 minutes I've got 38,744 greylisted and two whitelisted.

For how long do you greylist? The default is 5 days, you'll have 3
millions of entries at that time, that's huge. You might want to adjust
that delay to a shorter value.

Or you can just let it go and see if you hit some limit :-)

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] Statistics

2004-10-12 by Sutherland, James

Right now it's set like this.  Yea, I think you're right I may need to
turn these down.
 
greylist 15m
autowhite 5d
timeout 10d
 
 
________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Tuesday, October 12, 2004 3:35 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Statistics


Sutherland, James <jsutherl@newedgenetworks.com> wrote:

> At 1hr 30 minutes I've got 38,744 greylisted and two whitelisted.

For how long do you greylist? The default is 5 days, you'll have 3
millions of entries at that time, that's huge. You might want to adjust
that delay to a shorter value.

Or you can just let it go and see if you hit some limit :-)

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129v4cloe/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097706940/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=806242465> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] Statistics

2004-10-13 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Right now it's set like this.  Yea, I think you're right I may need to
> turn these down.
>  
> greylist 15m
> autowhite 5d
> timeout 10d

I'm not sure a 10 days timeout makes any sense. No mail server will wait
10 days before sending a second time. Most are configured to try during
3 or 5 days, hence the default. You probably want one or two days, not
more.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] Statistics

2004-10-13 by Sutherland, James

Yea, thinking along those same lines I set the timeout to 1d last night.
I'll try to post some more statistics later today.

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Tuesday, October 12, 2004 11:26 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Statistics


Sutherland, James <jsutherl@...> wrote:

> Right now it's set like this.  Yea, I think you're right I may need to
> turn these down.
>  
> greylist 15m
> autowhite 5d
> timeout 10d

I'm not sure a 10 days timeout makes any sense. No mail server will wait
10 days before sending a second time. Most are configured to try during
3 or 5 days, hence the default. You probably want one or two days, not
more.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=1290ar192/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097735218/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=577769510> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

RE: Volume

2004-10-13 by Sutherland, James

Well Milter seems to have given up after four hours or so of that load.
 
It started reporting reported this:
Oct 12 17:44:31 hns1 sendmail[5004]: [ID 801593 mail.info]
i9D0iLB5005004: Milter (greylist): to error state
 
then lots of these:
Oct 12 18:56:11 hns1 sendmail[16658]: [ID 801593 mail.error]
i9D1u0m8016658: Milter (greylist): timeout before data read
 
and later on lots of these:
Oct 13 03:29:00 hns1 sendmail[29937]: [ID 801593 mail.error]
i9DAT0qw029937: Milter (greylist): error connecting to filter:
Connection refused by /var/milter-greylist/milter-greylist.sock

and some of these (6500 of these):
Oct 13 03:29:21 hns1 sendmail[173]: [ID 801593 mail.error]
i9DATB5L000173: Milter (greylist): init failed to open
 
Don't forget these:
Oct 13 08:23:48 hns1 sendmail[28793]: [ID 801593 mail.error]
i9DENm0R028793: Milter (greylist): write(Q) returned -1, expected 5:
Broken pipe
 
 
When I try to start milter-greylist now it throws these, with lots of
line numbers:
Oct 13 14:17:15 hns1 milter-greylist: [ID 861475 mail.error] error at
line 83054: syntax error

I zeroed the greylist.db file and it started right up and is working
fine.  The size of the greylist file was:
43391130 Oct 13 07:46 /var/milter-greylist/greylist.db
    
Anyone have any thoughts?    
        -James
 
________________________________
Show quoted textHide quoted text
From: Sutherland, James 
Sent: Tuesday, October 12, 2004 9:55 AM
To: 'milter-greylist@yahoogroups.com'
Subject: Volume


Anyone have experience with milter-greylist on a high volume server?  By
high volume I mean 250k incoming mail connections per day?  I've had
some problems in the past with milter falling apart under loads like
this when trying to use MPP and a virus scanner.
    -James

Re: [milter-greylist] RE: Volume

2004-10-13 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Well Milter seems to have given up after four hours or so of that load.

I have ideas about it (see at the end of the mail).
  
> It started reporting reported this:
> Oct 12 17:44:31 hns1 sendmail[5004]: [ID 801593 mail.info]
> i9D0iLB5005004: Milter (greylist): to error state

Yes, it does that when it crashes.
  
> When I try to start milter-greylist now it throws these, with lots of
> line numbers:
> Oct 13 14:17:15 hns1 milter-greylist: [ID 861475 mail.error] error at
> line 83054: syntax error

Old problem: the code that reloads the dump is more picky about the
addresses than the code that do the dump. Someone really have to fix
that.

But it shoulnd't prevent you from reloading, that just makes a lot of
spurious errors. 
 
> I zeroed the greylist.db file and it started right up and is working
> fine.  The size of the greylist file was:
> 43391130 Oct 13 07:46 /var/milter-greylist/greylist.db

Your system probably has resource limits, haven't it? On your setup, you
need a huge amount of memory. Did you make sure that milter-greylist was
able to use all the memory it needs? what ulimit -a says (in sh/ksh) in
the shell where you launch milter-greylist.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] RE: Volume

2004-10-13 by Sutherland, James

ulimit -a shows
 
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     unlimited
nofiles(descriptors) 256
vmemory(kbytes)      unlimited
 
I really appricate any insight because WOW did this take a lot of load
off the system.
 
In the time it was running "Greylisting" was seen in the log file
470,408 times.  And "autowhitelisting" was seen only 1,215 times.

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@netbsd.org] 
Sent: Wednesday, October 13, 2004 2:54 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


Sutherland, James <jsutherl@...> wrote:

> Well Milter seems to have given up after four hours or so of that
load.

I have ideas about it (see at the end of the mail).
  
> It started reporting reported this:
> Oct 12 17:44:31 hns1 sendmail[5004]: [ID 801593 mail.info]
> i9D0iLB5005004: Milter (greylist): to error state

Yes, it does that when it crashes.
  
> When I try to start milter-greylist now it throws these, with lots of
> line numbers:
> Oct 13 14:17:15 hns1 milter-greylist: [ID 861475 mail.error] error at
> line 83054: syntax error

Old problem: the code that reloads the dump is more picky about the
addresses than the code that do the dump. Someone really have to fix
that.

But it shoulnd't prevent you from reloading, that just makes a lot of
spurious errors. 

> I zeroed the greylist.db file and it started right up and is working
> fine.  The size of the greylist file was:
> 43391130 Oct 13 07:46 /var/milter-greylist/greylist.db

Your system probably has resource limits, haven't it? On your setup, you
need a huge amount of memory. Did you make sure that milter-greylist was
able to use all the memory it needs? what ulimit -a says (in sh/ksh) in
the shell where you launch milter-greylist.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@netbsd.org


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129mr5ttf/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097790896/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=912031013> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@...m
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-13 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> I really appricate any insight because WOW did this take a lot of load
> off the system.

Do you have a core dump? A last message from the milter in the log?

Maybe consider running it in the foreground (with -Dv for instance), so
that you can see a particular message when it dies. 

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] RE: Volume

2004-10-13 by Sutherland, James

No dump was written.
 
The first errors (really .warning)  in the log set "setsock opt() failed
(Invalid argument)"
 
However after that it keeps logging .info's about messages that where
delayed.  So it's still working at this point.
 
Then hours later it reports this ( a bunch of times all the same file
names):
Oct 13 08:16:56 hns1 milter-greylist: [ID 653641 mail.error]
mkstemp("/var/milter-greylist/greylist.db-XX1Daq3G") failed: Too many
open files
 
Then:
Oct 13 08:16:56 hns1 milter-greylist: [ID 421540 mail.info] Final
database dump:  no change to dump
Oct 13 08:16:56 hns1 milter-greylist: [ID 146194 mail.info] Exitting
 


________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Wednesday, October 13, 2004 3:05 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


Sutherland, James <jsutherl@...> wrote:

> I really appricate any insight because WOW did this take a lot of load
> off the system.

Do you have a core dump? A last message from the milter in the log?

Maybe consider running it in the foreground (with -Dv for instance), so
that you can see a particular message when it dies. 

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129icdkm3/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097791552/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=546946602> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Then hours later it reports this ( a bunch of times all the same file
> names):
> Oct 13 08:16:56 hns1 milter-greylist: [ID 653641 mail.error]
> mkstemp("/var/milter-greylist/greylist.db-XX1Daq3G") failed: Too many
> open files

Now, that's interesting: you hit a file descriptor limit. That suggests
a file descriptor leak. Nobody ever reported that, but your setup is
quite heavyweight.

In dump.c, after the mkstemp call, add

        syslog(LOG_INFO, "dumpfd = %d", dumpfd);

Run milter-greylist, and check in the log if dumpfd increases as time
goes. If it does, check the open files for milter-greylist (with a tool
such as lsof) and look for similar pool of open files that keeps
growing. Is it a file (which one)? Is it a socket?  
  
> Then:
> Oct 13 08:16:56 hns1 milter-greylist: [ID 421540 mail.info] Final
> database dump:  no change to dump

That's okay, it just means that milter-greylist was terminated because
of a resource limit (file descriptors), and that there was no change to
flush to disk at that time. It didn't crashed, it quitted safely.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

OK, that code is in. I recompiled and it's running.  I haven't seen any
output from it yet.  However I'm a C nincompoop, so let me know if the
syntax is correct here:
 
    if ((dumpfd = mkstemp(newdumpfile)) == -1) {
                syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
                    newdumpfile, strerror(errno));
                syslog(LOG_INFO, "dumpfd = %d", dumpfd);
                exit(EX_OSERR);
        }


________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Wednesday, October 13, 2004 11:11 PM
To: milter-greylist@...m
Subject: Re: [milter-greylist] RE: Volume


Sutherland, James <jsutherl@newedgenetworks.com> wrote:

> Then hours later it reports this ( a bunch of times all the same file
> names):
> Oct 13 08:16:56 hns1 milter-greylist: [ID 653641 mail.error]
> mkstemp("/var/milter-greylist/greylist.db-XX1Daq3G") failed: Too many
> open files

Now, that's interesting: you hit a file descriptor limit. That suggests
a file descriptor leak. Nobody ever reported that, but your setup is
quite heavyweight.

In dump.c, after the mkstemp call, add

        syslog(LOG_INFO, "dumpfd = %d", dumpfd);

Run milter-greylist, and check in the log if dumpfd increases as time
goes. If it does, check the open files for milter-greylist (with a tool
such as lsof) and look for similar pool of open files that keeps
growing. Is it a file (which one)? Is it a socket?  
  
> Then:
> Oct 13 08:16:56 hns1 milter-greylist: [ID 421540 mail.info] Final
> database dump:  no change to dump

That's okay, it just means that milter-greylist was terminated because
of a resource limit (file descriptors), and that there was no change to
flush to disk at that time. It didn't crashed, it quitted safely.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=12906lk6q/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097820693/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=890033913> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by Emmanuel Dreyfus

On Thu, Oct 14, 2004 at 08:51:12AM -0700, Sutherland, James wrote:
> OK, that code is in. I recompiled and it's running.  I haven't seen any
> output from it yet.  However I'm a C nincompoop, so let me know if the
> syntax is correct here:
>  
>     if ((dumpfd = mkstemp(newdumpfile)) == -1) {
>                 syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
>                     newdumpfile, strerror(errno));
>                 syslog(LOG_INFO, "dumpfd = %d", dumpfd);
>                 exit(EX_OSERR);
>         }

I should have been more precise. I meant this:

     if ((dumpfd = mkstemp(newdumpfile)) == -1) {
                 syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
                     newdumpfile, strerror(errno));
                 exit(EX_OSERR);
     }
     syslog(LOG_INFO, "dumpfd = %d", dumpfd);

Because, you know, I'm not really interested into learning that dumpfs == -1
when mkstemp fails, I know that without running the code :)


-- 
Emmanuel Dreyfus
manu@...

Re: [milter-greylist] RE: Volume

2004-10-14 by Cyril Guibourg

"Sutherland, James" <jsutherl@...> writes:

> OK, that code is in. I recompiled and it's running.  I haven't seen any
> output from it yet.  However I'm a C nincompoop, so let me know if the
> syntax is correct here:
>  
>     if ((dumpfd = mkstemp(newdumpfile)) == -1) {
>                 syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
>                     newdumpfile, strerror(errno));
>                 syslog(LOG_INFO, "dumpfd = %d", dumpfd);
>                 exit(EX_OSERR);
>         }

James,

The syntax is correct but you will not see anything until milter-greylist
reaches the error condition. I suggest to put the the syslog() call suggested
by Emmanuel out of the if { ... } block.

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

Done and done.  So this way it should dump that to the log each time the
DB file gets dumped, correct?
        -James
 

________________________________
Show quoted textHide quoted text
From: Cyril Guibourg [mailto:cg+milter-greylist@...] 
Sent: Thursday, October 14, 2004 9:01 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


"Sutherland, James" <jsutherl@newedgenetworks.com> writes:

> OK, that code is in. I recompiled and it's running.  I haven't seen
any
> output from it yet.  However I'm a C nincompoop, so let me know if the
> syntax is correct here:
>  
>     if ((dumpfd = mkstemp(newdumpfile)) == -1) {
>                 syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
>                     newdumpfile, strerror(errno));
>                 syslog(LOG_INFO, "dumpfd = %d", dumpfd);
>                 exit(EX_OSERR);
>         }

James,

The syntax is correct but you will not see anything until
milter-greylist
reaches the error condition. I suggest to put the the syslog() call
suggested
by Emmanuel out of the if { ... } block.



Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=1290krfrf/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097856096/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=695104259> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@...m
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by Cyril Guibourg

"Sutherland, James" <jsutherl@...> writes:

> Done and done.  So this way it should dump that to the log each time
> the DB file gets dumped, correct?

Correct.

If the fd number increases there is a file descriptor leak to fix.

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

Worked great:
 
Oct 14 09:51:56 hns1 milter-greylist: [ID 799890 mail.error] dumpfd =
116
Oct 14 09:51:56 hns1 milter-greylist: [ID 799890 mail.error] dumpfd =
116
Oct 14 09:51:56 hns1 milter-greylist: [ID 799890 mail.error] dumpfd =
116
Oct 14 09:51:56 hns1 milter-greylist: [ID 799890 mail.error] dumpfd =
116
 
 

________________________________
Show quoted textHide quoted text
From: Sutherland, James 
Sent: Thursday, October 14, 2004 9:38 AM
To: 'milter-greylist@yahoogroups.com'
Subject: RE: [milter-greylist] RE: Volume


Done and done.  So this way it should dump that to the log each time the
DB file gets dumped, correct?
        -James
 

________________________________

From: Cyril Guibourg [mailto:cg+milter-greylist@...] 
Sent: Thursday, October 14, 2004 9:01 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


"Sutherland, James" <jsutherl@...> writes:

> OK, that code is in. I recompiled and it's running.  I haven't seen
any
> output from it yet.  However I'm a C nincompoop, so let me know if the
> syntax is correct here:
>  
>     if ((dumpfd = mkstemp(newdumpfile)) == -1) {
>                 syslog(LOG_ERR, "mkstemp(\"%s\") failed: %s", 
>                     newdumpfile, strerror(errno));
>                 syslog(LOG_INFO, "dumpfd = %d", dumpfd);
>                 exit(EX_OSERR);
>         }

James,

The syntax is correct but you will not see anything until
milter-greylist
reaches the error condition. I suggest to put the the syslog() call
suggested
by Emmanuel out of the if { ... } block.



Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=1290krfrf/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097856096/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=695104259> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Worked great:
>  
> Oct 14 09:51:56 hns1 milter-greylist: [ID 799890 mail.error] dumpfd =
> 116

116 is quite large. Does it increase?
It could crash even without a file descriptor leak: if you get 140
connexions at a time, you hit the limit (256 on your system) and you are
toasted. 

> Done and done.  So this way it should dump that to the log each time the
> DB file gets dumped, correct?

Yes.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

Well it's certainly growing:
Thu 9:59am {root@hns1:[/var/milter-greylist]} lsof | grep 10919 | wc -l
    118
Thu 10:01am {root@hns1:[/var/milter-greylist]} lsof | grep 10919 | wc -l
    137
Thu 10:10am {root@hns1:[/var/milter-greylist]} lsof | grep 10919 | wc -l
    152
Thu 10:24am {root@hns1:[/var/milter-greylist]} lsof | grep 10919 | wc -l
    187
 
LSOF output below.  Looks like sockets:
COMMAND     PID   USER   FD   TYPE        DEVICE  SIZE/OFF      NODE
NAME
milter-gr 10919   root  cwd   VDIR         246,0       512         2 /
milter-gr 10919   root  txt   VREG         246,0    276846    144602
/usr/local/bin/milter-greylist
milter-gr 10919   root  txt   VREG         246,0    138560    227440
/usr/lib/libthread.so.1
milter-gr 10919   root  txt   VREG         246,0    867088    227722
/usr/lib/libc.so.1
milter-gr 10919   root  txt   VREG         246,0    743856    227773
/usr/lib/linsl.so.1
milter-gr 10919   root  txt   VREG         246,0     21676    227413
/usr/lib/libmp.so.2
milter-gr 10919   root  txt   VREG         246,0     37620    227423
/usr/lib/libpthread.so.1
milter-gr 10919   root  txt   VREG         246,0    316468    227793
/usr/lib/libresolv.so.2
milter-gr 10919   root  txt   VREG         246,0     58504    227437
/usr/lib/libsocket.so.1
milter-gr 10919   root  txt   VREG         246,0     16768    325636
/usr/platform/sun4u/lib/libc_psr.so.1
milter-gr 10919   root  txt   VREG         246,0      3984    227381
/usr/lib/libdl.so.1
milter-gr 10919   root  txt   VREG         246,5       120    218258
/var/ld/ld.config
milter-gr 10919   root  txt   VREG         246,0    212624    227273
/usr/lib/ld.so.1
milter-gr 10919   root    0r  VCHR          13,2       0t0    590231
/devices/pseudo/mm@0:null
milter-gr 10919   root    1r  VCHR          13,2       0t0    590231
/devices/pseudo/mm@0:null
milter-gr 10919   root    2r  VCHR          13,2       0t0    590231
/devices/pseudo/mm@0:null
milter-gr 10919   root    3u  unix        105,16       0t0    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a177430) (Vno
de=0x305b96603c0)
milter-gr 10919   root    4w  VCHR          21,0       0t0    590227
/devices/pseudo/log@0:conslog->LOG
milter-gr 10919   root    5u  unix        105,18     0t370    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a1547c8)
milter-gr 10919   root    6u  unix        105,26     0t378    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d733b88)
milter-gr 10919   root    7u  unix        105,22     0t157    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a154270)
milter-gr 10919   root    8u  unix        105,24     0t289    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fce60)
milter-gr 10919   root    9u  unix        105,34     0t678    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07a3490)
milter-gr 10919   root   10u  unix        105,75     0t143    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d77573d8)
milter-gr 10919   root   11u  unix        105,33     0t469    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc204900)
milter-gr 10919   root   12u  unix        105,37     0t133    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da669798)
milter-gr 10919   root   13u  unix        105,43    0t4936    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da669b28)
milter-gr 10919   root   14u  unix        105,56    0t1495    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da668eb0)
milter-gr 10919   root   15u  unix        105,50    0t2015    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37de798)
milter-gr 10919   root   16u  unix        105,48     0t580    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37d0248)
milter-gr 10919   root   17u  unix        105,59    0t2994    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fd910)
milter-gr 10919   root   18u  unix        105,73    0t4229    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1f11f8)
milter-gr 10919   root   19u  unix        105,55     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc2063a0)
milter-gr 10919   root   20u  unix        105,52     0t277    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fd3b8)
milter-gr 10919   root   21u  unix        105,42     0t195    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7747938)
milter-gr 10919   root   22u  unix        105,78     0t682    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x30638754258)
milter-gr 10919   root   23u  unix        105,54    0t1661    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d6b78)
milter-gr 10919   root   24u  unix        105,68    0t1718    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fc908)
milter-gr 10919   root   25u  unix        105,62     0t763    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a1770a0)
milter-gr 10919   root   26u  unix        105,77     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37bed00)
milter-gr 10919   root   27u  unix        105,95     0t401    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x30638755428)
milter-gr 10919   root   28u  unix        105,71     0t296    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc2041e0)
milter-gr 10919   root   29u  unix       105,108     0t137    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e078f498)
milter-gr 10919   root   30u  unix        105,84     0t460    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3000221a1d0)
milter-gr 10919   root   31u  unix        105,76     0t146    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fc578)
milter-gr 10919   root   32u  unix       105,136     0t191    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fd1f0)
milter-gr 10919   root   33u  unix        105,88     0t144    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1f1588)
milter-gr 10919   root   34u  unix        105,66     0t311    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305a9d5b3d0)
milter-gr 10919   root   35u  unix        105,83     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc207738)
milter-gr 10919   root   36u  unix        105,90     0t498    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37bf7b0)
milter-gr 10919   root   37u  unix        105,99     0t563    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da668400)
milter-gr 10919   root   38u  unix       105,100     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d723b90)
milter-gr 10919   root   39u  unix        105,80     0t149    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d77473e0)
milter-gr 10919   root   40u  unix        105,93     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1f0910)
milter-gr 10919   root   41u  unix       105,106    0t1076    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da68b3f8)
milter-gr 10919   root   42u  unix        105,97     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306427050b8)
milter-gr 10919   root   43u  unix        105,86     0t388    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc205740)
milter-gr 10919   root   44u  unix       105,157     0t145    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37bf090)
milter-gr 10919   root   45u  unix       105,114     0t999    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da669240)
milter-gr 10919   root   46u  unix       105,113     0t133    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306427040b0)
milter-gr 10919   root   47u  unix       105,115    0t2375    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07a39e8)
milter-gr 10919   root   48u  unix       105,135     0t196    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc207570)
milter-gr 10919   root   49u  unix       105,111     0t299    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7757930)
milter-gr 10919   root   50u  unix       105,131     0t782    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37de960)
milter-gr 10919   root   51u  unix       105,133    0t2343    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da68a5b8)
milter-gr 10919   root   52u  unix       105,117     0t129    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37be970)
milter-gr 10919   root   53u  unix       105,134     0t409    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a154438)
milter-gr 10919   root   54u  unix       105,129    0t1945    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f79a8)
milter-gr 10919   root   55u  unix       105,128     0t385    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d7332a0)
milter-gr 10919   root   56u  unix       105,123     0t763    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a154600)
milter-gr 10919   root   57u  unix       105,143     0t131    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d77243e8)
milter-gr 10919   root   58u  unix       105,150     0t304    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da68b950)
milter-gr 10919   root   59u  unix       105,148     0t154    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1df038)
milter-gr 10919   root   60u  unix       105,124     0t360    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37d0410)
milter-gr 10919   root   61u  unix       105,119     0t477    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1fd028)
milter-gr 10919   root   62u  unix       105,154     0t612    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a167600)
milter-gr 10919   root   63u  unix       105,138     0t131    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da678068)
milter-gr 10919   root   64u  unix       105,142     0t131    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a1550b0)
milter-gr 10919   root   65u  unix       105,153     0t131    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37dfcf8)
milter-gr 10919   root   67u  unix       105,146     0t389    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc205c98)
milter-gr 10919   root   68u  unix       105,147     0t369    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d79b8)
milter-gr 10919   root   69u  unix       105,158     0t662    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d7229c0)
milter-gr 10919   root   70u  unix       105,127     0t154    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d77465a0)
milter-gr 10919   root   71u  unix       105,213    0t1390    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d6620)
milter-gr 10919   root   72u  unix       105,161     0t193    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37beb38)
milter-gr 10919   root   73u  unix       105,112     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1dfae8)
milter-gr 10919   root   74u  unix       105,173     0t195    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d733468)
milter-gr 10919   root   75u  unix       105,166    0t5486    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a167270)
milter-gr 10919   root   76u  unix       105,168     0t147    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d7329b8)
milter-gr 10919   root   77u  unix       105,266     0t901    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x30638755260)
milter-gr 10919   root   78u  unix       105,179    0t2931    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d733630)
milter-gr 10919   root   79u  unix       105,170     0t785    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f70c0)
milter-gr 10919   root   80u  unix       105,171     0t571    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f7288)
milter-gr 10919   root   81u  unix       105,177     0t193    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426e6450)
milter-gr 10919   root   82u  unix       105,174     0t947    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07c0f28)
milter-gr 10919   root   83u  unix       105,184    0t1030    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306a5293808)
milter-gr 10919   root   84u  unix       105,182     0t996    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da678ce0)
milter-gr 10919   root   85u  unix       105,190     0t372    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07c1480)
milter-gr 10919   root   86u  unix       105,203     0t133    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a1670a8)
milter-gr 10919   root   87u  unix       105,186     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7725b10)
milter-gr 10919   root   88u  unix       105,230     0t139    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da68a780)
milter-gr 10919   root   89u  unix       105,187     0t157    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d7330d8)
milter-gr 10919   root   90u  unix       105,275     0t659    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3000221a728)
milter-gr 10919   root   91u  unix       105,205     0t489    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d722d50)
milter-gr 10919   root   92u  unix       105,195    0t1204    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1deca8)
milter-gr 10919   root   93u  unix       105,199     0t194    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a176ed8)
milter-gr 10919   root   94u  unix       105,200     0t834    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37be088)
milter-gr 10919   root   95u  unix       105,197     0t579    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d733d50)
milter-gr 10919   root   96u  unix       105,206     0t306    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7736050)
milter-gr 10919   root   97u  unix       105,207    0t3749    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a155278)
milter-gr 10919   root   98u  unix       105,209     0t483    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7756760)
milter-gr 10919   root   99u  unix       105,220     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7757768)
milter-gr 10919   root  100u  unix       105,218     0t377    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f6448)
milter-gr 10919   root  102u  unix       105,215     0t476    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da678788)
milter-gr 10919   root  103u  unix       105,226     0t312    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07a2f38)
milter-gr 10919   root  104u  unix       105,243     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d7298)
milter-gr 10919   root  105u  unix       105,234     0t843    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37df248)
milter-gr 10919   root  106u  unix       105,236     0t368    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3064d732460)
milter-gr 10919   root  107u  unix       105,225     0t148    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d77363e0)
milter-gr 10919   root  108u  unix       105,219     0t133    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da68a3f0)
milter-gr 10919   root  109u  unix       105,246     0t387    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7756040)
milter-gr 10919   root  110u  unix       105,233     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306a5292638)
milter-gr 10919   root  111u  unix       105,244     0t139    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d77f0)
milter-gr 10919   root  112u  unix       105,231     0t131    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426d7d48)
milter-gr 10919   root  113u  unix       105,191     0t857    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a154b58)
milter-gr 10919   root  114u  unix       105,240     0t152    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1f0580)
milter-gr 10919   root  116u  unix       105,250     0t212    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3000221a560)
milter-gr 10919   root  117u  unix       105,222    0t2117    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305a9d5bcb8)
milter-gr 10919   root  118u  unix       105,248     0t407    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305a9d5b598)
milter-gr 10919   root  119u  unix       105,251     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f69a0)
milter-gr 10919   root  120u  unix       105,252     0t170    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07b0648)
milter-gr 10919   root  122u  unix       105,257    0t2046    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a166268)
milter-gr 10919   root  123u  unix       105,259    0t1516    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a177b50)
milter-gr 10919   root  124u  unix       105,254     0t382    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305da668238)
milter-gr 10919   root  128u  unix       105,272     0t622    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426e6b70)
milter-gr 10919   root  129u  unix       105,274     0t311    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305a9d5a920)
milter-gr 10919   root  130u  unix       105,279    0t1404    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306a52920e0)
milter-gr 10919   root  131u  unix       105,277     0t596    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07c19d8)
milter-gr 10919   root  133u  unix       105,284     0t733    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426f7b70)
milter-gr 10919   root  134u  unix       105,286     0t314    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305a9d5a758)
milter-gr 10919   root  135u  unix       105,288    0t1325    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37deeb8)
milter-gr 10919   root  136u  unix       105,281     0t133    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc2071e0)
milter-gr 10919   root  137u  unix       105,302     0t155    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07b12c0)
milter-gr 10919   root  138u  unix       105,292    0t1668    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37dfb30)
milter-gr 10919   root  140u  unix       105,295     0t148    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3063a1775f8)
milter-gr 10919   root  141u  unix       105,189     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305e37be250)
milter-gr 10919   root  142u  unix       105,296     0t135    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306426e67e0)
milter-gr 10919   root  143u  unix       105,299     0t628    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07a22c0)
milter-gr 10919   root  144u  unix       105,301     0t192    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc204c90)
milter-gr 10919   root  145u  unix       105,303    0t1926    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7724cd0)
milter-gr 10919   root  146u  unix       105,305     0t406    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07b0ba0)
milter-gr 10919   root  147u  unix       105,307    0t1312    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc207ac8)
milter-gr 10919   root  148u  unix       105,314     0t303    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
<mailto:eudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock>
(0x306e07c0d60)
milter-gr 10919   root  149u  unix       105,311     0t508    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x3000221a8f0)
milter-gr 10919   root  150u  unix       105,313    0t1571    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7737058)
milter-gr 10919   root  151u  unix       105,315     0t318    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07a3820)
milter-gr 10919   root  152u  unix       105,317     0t521    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e07b0480)
milter-gr 10919   root  153u  unix       105,319    0t1686    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x30642704440)
milter-gr 10919   root  154u  unix       105,321     0t377    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7757cc0)
milter-gr 10919   root  156u  unix       105,325    0t2117    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1deae0)
milter-gr 10919   root  158u  unix       105,329     0t324    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x306e078f2d0)
milter-gr 10919   root  160u  unix       105,341     0t473    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305cc1f0ca0)
milter-gr 10919   root  186u  unix       105,385     0t146    590240
/devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
(0x305d7747cc8)
 

________________________________
Show quoted textHide quoted text
From: Cyril Guibourg [mailto:cg+milter-greylist@...] 
Sent: Thursday, October 14, 2004 9:51 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


"Sutherland, James" <jsutherl@...> writes:

> Done and done.  So this way it should dump that to the log each time
> the DB file gets dumped, correct?

Correct.

If the fd number increases there is a file descriptor leak to fix.


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129k3vhv6/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097859400/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=587194881> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> milter-gr 10919   root    9u  unix        105,34     0t678    590240
> /devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
> (0x306e07a3490)
[repeated many times]

It seems there are dead connexions between sendmail and milter-greylist.
Do you have junk sendmail processes lying around? Maybe awaiting for DNS
resolution?

By using lsof you should be able to find who is connected at the other
end of the socket. Are there alive processes?

Given an entry of socket used by milter-greylist in the lsof output,
will it disapear after some time, or does it stay there forever?

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Re: [milter-greylist] RE: Volume

2004-10-14 by Ethan Burnside

I think you two may have stumbled onto our problem as well:

We have a cluster of 5 incoming servers, all using milter-greylist.  I
have a script run out of cron I was using to check milter-greylist's
status to restart automagically after a crash.

A random lsof spot-check shows the following:

root@xxxx:~# lsof | grep milter-gr | wc
    924    7876   94006


so based on this:


root@xxxx:~# ulimit -a
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) 7168
virtual memory        (kbytes, -v) unlimited


I guess we're not crashing until we hit 1024?  Which seems to happen
somewhat frequently.

I'll try setting the ulimit open files to 2048 and see how things go.

for what it's worth, I don't think they're leaking, as the count tends
to fluxuate up and down quite a bit.  I'm also thinking that it's partly
our fault for giving sendmail's milter setup a much longer timeout.
(trying to work around possible DNS latency with libspf support, etc.)

Cheers,

~Ethan B.

-- 
----------------------------------
 Ethan Burnside - Founding Member
 Kattare Internet Services
 WWW: http://www.kattare.com
 E-mail: burnside@...
----------------------------------



Quoting manu@...:
Show quoted textHide quoted text
> 
> Sutherland, James <jsutherl@...> wrote:
> 
> > milter-gr 10919   root    9u  unix        105,34     0t678   
> 590240
> >
> /devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
> > (0x306e07a3490)
> [repeated many times]
> 
> It seems there are dead connexions between sendmail and
> milter-greylist.
> Do you have junk sendmail processes lying around? Maybe awaiting for
> DNS
> resolution?
> 
> By using lsof you should be able to find who is connected at the
> other
> end of the socket. Are there alive processes?
> 
> Given an entry of socket used by milter-greylist in the lsof output,
> will it disapear after some time, or does it stay there forever?
> 
> -- 
> Emmanuel Dreyfus
> Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
> le binaire et ceux qui ne le comprennent pas.
> manu@...
> 
> 
> ------------------------ Yahoo! Groups Sponsor
> --------------------~--> 
> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
> Now with Pop-Up Blocker. Get it for free!
> http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/W4wwlB/TM
> --------------------------------------------------------------------~->
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
>

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

They disappear, and when the box isn't taking much mail it gets a lot
lower.  A little while ago it got down to 40 then down to 21, then back
up to 116 again.  So I wonder if these are legit and I just happened to
have a bunch of sendmail grandchildren.
 
Sure enough, look at this:
 
$ ps -ef | grep -c sendmail
124
$ lsof | grep 10919 | wc -l  \\ 10919 is milter-greylist
    128
 
So I guess I need to increase the number of file descriptors.

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...g] 
Sent: Thursday, October 14, 2004 11:42 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


Sutherland, James <jsutherl@...> wrote:

> milter-gr 10919   root    9u  unix        105,34     0t678    590240
> /devices/pseudo/tl@0:ticots->/var/milter-greylist/milter-greylist.sock
> (0x306e07a3490)
[repeated many times]

It seems there are dead connexions between sendmail and milter-greylist.
Do you have junk sendmail processes lying around? Maybe awaiting for DNS
resolution?

By using lsof you should be able to find who is connected at the other
end of the socket. Are there alive processes?

Given an entry of socket used by milter-greylist in the lsof output,
will it disapear after some time, or does it stay there forever?

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129q0dvg6/M=315388.5497957.6576270.3001176/
D=groups/S=1707281942:HM/EXP=1097865731/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5497957.6576270.3001176/D=group
s/S=:HM/A=2372354/rand=256250453> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] RE: Volume

2004-10-14 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> So I guess I need to increase the number of file descriptors.

Yes, that's the bottom line. I'm pretty sure I did hit that already on
my systems, but as I could not reproduce the problem, I never looked
into it further. 

I'll document the problem in the README file.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] RE: Volume

2004-10-14 by Sutherland, James

I've increased the soft limit to 2048, which should be more then enough.
However I think that there may be another problem.  If try to use the
large greylist.db file from when the crash happened milter almost
immediately exits.  However, maybe the file was corrupted.  So I'm
letting the new file run and I'll let you know how it goes. 
        -James
 

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Thursday, October 14, 2004 3:19 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] RE: Volume


Sutherland, James <jsutherl@newedgenetworks.com> wrote:

> So I guess I need to increase the number of file descriptors.

Yes, that's the bottom line. I'm pretty sure I did hit that already on
my systems, but as I could not reproduce the problem, I never looked
into it further. 

I'll document the problem in the README file.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=1295n3g0o/M=315388.5500238.6578046.3001176/
D=groups/S=1707281942:HM/EXP=1097878759/A=2372354/R=0/SIG=12id813k2/*htt
ps://www.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21
004SS> 	
 
<http://us.adserver.yahoo.com/l?M=315388.5500238.6578046.3001176/D=group
s/S=:HM/A=2372354/rand=818357369> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] Volume

2004-11-12 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> Anyone have experience with milter-greylist on a high volume server?

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 le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

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 waiting with my fingers crossed that somebody would
make the change.  
 
I have no way to compile a 64bit binary since Sun charges an arm and a
leg for it's 64bit compiler and we don't have a copy here.
 
>    From: Emmanuel Dreyfus [mailto:manu@...] 
>    Sent: Friday, October 29, 2004 1:08 AM
>    To: milter-greylist@yahoogroups.com
>    Subject: Re: [milter-greylist] Volume 2
>       Okay... I guess we could book a low file descriptor for dumping
the
>   database. Something stored in a static. The problem is that we'll   
>   need to do the same thing for MX sync, which uses a number of
>   file descriptor which depends on the number of MX peers.
>
>   But as I understood, building a 64 bit binary automagically fixes
>   everything... 
>
>    -- 
>    Emmanuel Dreyfus
>    manu@...

    

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@netbsd.org] 
Sent: Friday, November 12, 2004 4:55 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Volume


Sutherland, James <jsutherl@...> wrote:

> Anyone have experience with milter-greylist on a high volume server?

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 le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...


Yahoo! Groups Sponsor	
ADVERTISEMENT
click here
<http://us.ard.yahoo.com/SIG=129rohif1/M=298184.5584357.6650215.3001176/
D=groups/S=1707281942:HM/EXP=1100350512/A=2426685/R=0/SIG=11eslo8dq/*htt
p://www.netflix.com/Default?mqso=60185401> 	
 
<http://us.adserver.yahoo.com/l?M=298184.5584357.6650215.3001176/D=group
s/S=:HM/A=2426685/rand=248854082> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [milter-greylist] Volume

2004-11-12 by Cyril Guibourg

"Sutherland, James" <jsutherl@...> writes:

> I have no way to compile a 64bit binary since Sun charges an arm and a
> leg for it's 64bit compiler and we don't have a copy here.

You can download a trial copy with an evaluation license valid for one month.

Re: [milter-greylist] Volume

2004-11-12 by Matthias Scheler

On Fri, Nov 12, 2004 at 08:30:27AM -0800, Sutherland, James wrote:
> I have no way to compile a 64bit binary since Sun charges an arm and a
> leg for it's 64bit compiler and we don't have a copy here.

You can build a GCC which creates 64Bit binaries. Instructions
are available here:

http://www.well.com/~jax/rcfb/solaris_tips/build_gcc_3.0_64bit.html#2004-10-10

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Re: [milter-greylist] Volume

2004-11-12 by Dan Hollis

On Fri, 12 Nov 2004, Cyril Guibourg wrote:
> "Sutherland, James" <jsutherl@...> writes:
> > I have no way to compile a 64bit binary since Sun charges an arm and a
> > leg for it's 64bit compiler and we don't have a copy here.
> You can download a trial copy with an evaluation license valid for one month.

gcc supports 64bit?

-Dan

Re: [milter-greylist] Volume

2004-11-12 by Cyril Guibourg

Dan Hollis <goemon@...> writes:

> gcc supports 64bit?

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

Re: [milter-greylist] Volume

2004-11-12 by manu@netbsd.org

Sutherland, James <jsutherl@...> wrote:

> 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 waiting with my fingers crossed that somebody would
> make the change.

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 dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Re: [milter-greylist] Volume

2004-11-13 by Matthias Scheler

On Fri, Nov 12, 2004 at 10:59:35PM +0100, Cyril Guibourg wrote:
> I wasn't speaking about gcc. The trial copy I was referring to is for a
> product called Sun One (aka Forte C).

I know. That's why I suggested GCC which is available for free.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Re: [milter-greylist] Volume

2004-11-13 by Matthias Scheler

On Fri, Nov 12, 2004 at 01:39:39PM -0800, Dan Hollis wrote:
> > "Sutherland, James" <jsutherl@...> writes:
> > > I have no way to compile a 64bit binary since Sun charges an arm and a
> > > leg for it's 64bit compiler and we don't have a copy here.
> > You can download a trial copy with an evaluation license valid for one month.
> gcc supports 64bit?

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

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Re: Volume

2004-11-14 by Klas Heggemann

> I have no way to compile a 64bit binary since Sun charges an arm and a
> leg for it's 64bit compiler and we don't have a copy here.

If you just want a 64 -bit build using Suns compilers, I can build
one and make it avaliable. Cc me the answer, as I am only
sporadically checking activity on this list.


/klas

RE: [milter-greylist] Re: Volume

2004-11-15 by Sutherland, James

That would be wonderful if you could do that.  I haven't had time to
mess with 64-bit gcc yet.  Or to download a trial copy of Sun's
compiler.
    -James
 


________________________________
Show quoted textHide quoted text
From: Klas Heggemann [mailto:klas@...] 
Sent: Sunday, November 14, 2004 6:53 AM
To: milter-greylist@yahoogroups.com
Subject: [milter-greylist] Re: Volume




> I have no way to compile a 64bit binary since Sun charges an arm and a
> leg for it's 64bit compiler and we don't have a copy here.

If you just want a 64 -bit build using Suns compilers, I can build
one and make it avaliable. Cc me the answer, as I am only
sporadically checking activity on this list.


/klas





Yahoo! Groups Sponsor	
 
<http://us.ard.yahoo.com/SIG=12982fefj/M=296572.5585671.6651487.3001176/
D=groups/S=1707281942:HM/EXP=1100530376/A=2343726/R=0/SIG=12i9kndg9/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=11004439767
83891>
<http://us.ard.yahoo.com/SIG=12982fefj/M=296572.5585671.6651487.3001176/
D=groups/S=1707281942:HM/EXP=1100530376/A=2343726/R=1/SIG=12i9kndg9/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=11004439767
83891> 

Get unlimited calls to

U.S./Canada

 
<http://view.atdmt.com/VON/view/yhxxxvon01900091von/direct/01/&time=1100
443976783891> 
 
<http://us.adserver.yahoo.com/l?M=296572.5585671.6651487.3001176/D=group
s/S=:HM/A=2343726/rand=538146585> 	

________________________________

Yahoo! Groups Links


*	To visit your group on the web, go to:
	http://groups.yahoo.com/group/milter-greylist/
	  
*	To unsubscribe from this group, send an email to:
	milter-greylist-unsubscribe@yahoogroups.com
<mailto:milter-greylist-unsubscribe@yahoogroups.com?subject=Unsubscribe>

	  
*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

RE: [milter-greylist] Re: Volume

2004-11-16 by klas@nada.kth.se

> That would be wonderful if you could do that.  I haven't had time to
> mess with 64-bit gcc yet.  Or to download a trial copy of Sun's
> compiler.
>     -James
>

It is now ftpable from
       ftp://ftp.nada.kth.se/Sysgr/milter-greylist-64

This is built on Solaris 9 using Forte Developer 7 C 5.4 2002/03/09.

Statistics

2004-12-11 by Alexander Waller

Hi!
I want to count the IPs milter-greylisting drops. And I want to count the good ones.
As I understand tubles will be in greylist.db until "timeout" is reached.
Is it possible to have the ones wich are cleaned out to be logged via syslog or to a file with the info if the IP was a good one or a bad one?
My Idea is to collect the IP-Adresse of mailers comming just one time. If such an IP comes several times only once for a email, that IP must be a Spam-Server.
Maybe it makes sense to collect and share such IPs for actively block such IPs with firewall-rules.
Alex.

Re: [milter-greylist] Statistics

2004-12-11 by Cyril Guibourg

"Alexander Waller" <walleralexander@...> writes:

[1. text/html]...

You should consider that other people may use plain text only mail clients.
Thanks.

Re: [milter-greylist] Statistics

2004-12-11 by manu@netbsd.org

Alexander Waller <walleralexander@...> wrote:

> <div style='background-color:'><DIV class=RTE>Hi!</DIV>

Please don't post in HTML. My MUA is not a browser, HTML is painful to
read

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

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.