Yahoo Groups archive

Milter-greylist

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

Thread

Volume 2

Volume 2

2004-10-28 by Sutherland, James

Well I'm back at it again with that HUGE mx. I had to drop this issue for a while to work on some other stuff but now I'm back to it. Sorry for the delay.
Recap: this is the MX server that takes 200k+ messages per day and I'm having some trouble keeping milter-greylist running. It tends to exit on me. This is a Slaris 2.9 (SPARC) system. nofiles is set to 2048
I put the code into milter-greylist-1.5.10 to write dumpfd to syslog. Then I grepped all the normal-ish stuff out of the log leaving just the problems:
Anyone have any more ideas as to what to try?
$grep -i milter /var/log/mail.log | grep -v refused | grep -v "error state" | grep -v "syntax error" | grep -vi "delayed" | grep -v "Greylisting" | grep -vi "data read" | grep -vi "autowhitelisted" > /tmp/log1
-LOG FROM AROUND THE CRASH-
Oct 27 19:42:37 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 144
Oct 27 19:47:47 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 91
Oct 27 19:52:56 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 65
Oct 27 19:58:01 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 87
Oct 27 20:03:06 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 154
Oct 27 20:08:12 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 280
Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0
Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0
Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0
Oct 27 20:08:12 hns1 milter-greylist: [ID 421540 mail.info] Final database dump: no change to dump
Oct 27 20:08:12 hns1 milter-greylist: [ID 146194 mail.info] Exitting
Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0
Oct 27 20:08:12 hns1 sendmail[24863]: [ID 801593 mail.error] i9S386j7024863: milter_read(greylist): cmd read returned 0, expecting 5
Oct 27 20:08:12 hns1 sendmail[24863]: [ID 801593 mail.error] i9S386j7024863: milter_read(greylist): cmd read returned 0, expecting 5
-MANY OF THESE-
-SNIP-
; -AND THEN MANY Of THESE-
Oct 27 20:08:12 hns1 sendmail[24762]: [ID 801593 mail.error] i9S37uWg024762: Milter (greylist): write(D) returned -1, expected 23: Broken pipe
Oct 27 20:08:12 hns1 sendmail[24775]: [ID 801593 mail.error] i9S37vgP024775: Milter (greylist): write(R) returned -1, expected 32: Broken pipe
Oct 27 20:08:12 hns1 sendmail[24775]: [ID 801593 mail.error] i9S37vgP024775: Milter (greylist): write(R) returned -1, expected 32: Broken pipe
Those temp greylist.db-XXY* files are left in the directory after milter exits, they're always zero bytes.

Re: [milter-greylist] Volume 2

2004-10-28 by manu@netbsd.org

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

> Oct 27 19:42:37 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 144
> Oct 27 19:47:47 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 91
> Oct 27 19:52:56 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 65
> Oct 27 19:58:01 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 87
> Oct 27 20:03:06 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 154
> Oct 27 20:08:12 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 280
> Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot write
> dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0

Here is the code that causes this failure:

        if ((dump = fdopen(dumpfd, "w")) == NULL) {
                syslog(LOG_ERR, "cannot write dumpfile \"%s\": %s",
                    newdumpfile, strerror(errno));
                exit(EX_OSERR);
        } 

So your OS was not able to open that file, but doesn't tell us why
(errno says no error occured). You can add this before the syslog call:

                syslog(LOG_ERR, "dumpfd = %d, dump = %p, errno = %d\n",
                    dumpfd, dump, errno); 

to check that it's not strerror() that is misbehaving.

According to the X/Open spec:
http://www.opengroup.org/onlinepubs/007908799/xsh/fdopen.html
"Upon successful completion, fdopen() returns a pointer to a stream.
Otherwise, a null pointer is returned and errno is set to indicate the
error. "

So I'd say fdopen() does not behaves as expected. Is this a bug in your
OS?  

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

2004-10-28 by Sutherland, James

Geez, I can't keep milter-greylist running for more then ten minutes
this morning.  It starts into the "Milter read(greylist): timeout before
data read" almost at once after I start it.
 
I put that code in, here's what I got:
Oct 28 08:10:31 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 15
Oct 28 08:15:39 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 348
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 421540 mail.info] Final
database dump: no change to dump
Oct 28 08:15:39 hns1 milter-greylist: [ID 146194 mail.info] Exitting

________________________________
Show quoted textHide quoted text
From: manu@... [mailto:manu@...] 
Sent: Thursday, October 28, 2004 12:30 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Volume 2


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

> Oct 27 19:42:37 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
144
> Oct 27 19:47:47 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
91
> Oct 27 19:52:56 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
65
> Oct 27 19:58:01 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
87
> Oct 27 20:03:06 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
154
> Oct 27 20:08:12 hns1 milter-greylist: [ID 799890 mail.info] dumpfd =
280
> Oct 27 20:08:12 hns1 milter-greylist: [ID 525239 mail.error] cannot
write
> dumpfile "/var/milter-greylist/greylist.db-XXYsayUQ": Error 0

Here is the code that causes this failure:

        if ((dump = fdopen(dumpfd, "w")) == NULL) {
                syslog(LOG_ERR, "cannot write dumpfile \"%s\": %s",
                    newdumpfile, strerror(errno));
                exit(EX_OSERR);
        } 

So your OS was not able to open that file, but doesn't tell us why
(errno says no error occured). You can add this before the syslog call:

                syslog(LOG_ERR, "dumpfd = %d, dump = %p, errno = %d\n",
                    dumpfd, dump, errno); 

to check that it's not strerror() that is misbehaving.

According to the X/Open spec:
http://www.opengroup.org/onlinepubs/007908799/xsh/fdopen.html
"Upon successful completion, fdopen() returns a pointer to a stream.
Otherwise, a null pointer is returned and errno is set to indicate the
error. "

So I'd say fdopen() does not behaves as expected. Is this a bug in your
OS?  

-- 
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	
 
<http://us.ard.yahoo.com/SIG=129fkav8h/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099035081/A=2343726/R=0/SIG=12ieaqo3j/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989486810
60265>
<http://us.ard.yahoo.com/SIG=129fkav8h/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099035081/A=2343726/R=1/SIG=12ieaqo3j/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989486810
60265> 

Get unlimited calls to

U.S./Canada

 
<http://view.atdmt.com/VON/view/yhxxxvon01900091von/direct/01/&time=1098
948681060265> 
 
<http://us.adserver.yahoo.com/l?M=281955.5530326.6602771.3001176/D=group
s/S=:HM/A=2343726/rand=300270951> 	

________________________________

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 2

2004-10-28 by attila.bruncsak@itu.int

Hello,
Tru64 UNIX 'man atexit' writes among others: "It is not recommended to call exit() from within an atexit handler." I wonder that exit() was called for some reason before. All the messages you see is duplicated because the final_dump() is called now in a loop. Is the mkstemp() reentrant function?
Or you may exceeded the FOPEN_MAX or STREAM_MAX limits, and the fdopen() forget to set the errno = EMFILE.
Of course nothing is sure I am just thinking loudly.
Bests,
Attila
Show quoted textHide quoted text
Geez, I can't keep milter-greylist running for more then ten minutes this morning. It starts into the "Milter read(greylist): timeout before data read" almost at once after I start it.
I put that code in, here's what I got:
Oct 28 08:10:31 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 15
Oct 28 08:15:39 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 348
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd = 348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd = 348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd = 348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 180808 mail.error] dumpfd = 348, dump = 0, errno = 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 525239 mail.error] cannot write dumpfile "/var/milter-greylist/greylist.db-XXG7aOsh": Error 0
Oct 28 08:15:39 hns1 milter-greylist: [ID 421540 mail.info] Final database dump: no change to dump
Oct 28 08:15:39 hns1 milter-greylist: [ID 146194 mail.info] Exitting

Re: [milter-greylist] Volume 2

2004-10-28 by Matthias Scheler

On Thu, Oct 28, 2004 at 09:30:15AM +0200, Emmanuel Dreyfus wrote:
> So your OS was not able to open that file, but doesn't tell us why
> (errno says no error occured).

I couldn't open that file because you a passed file number larger than 255.
From Solaris's stdio(3C) manual page:

     The integer constant FOPEN_MAX specifies the minimum  number
     of  files  that  the  implementation  guarantees can be open
     simultaneously. Note that no more  than  255  files  may  be
     opened  using  fopen(),  and only file descriptors 0 through
     255 can be used in a stream.

That historic restricion does however only apply to 32Bit binaries.
The work arround is to use dup2(3C) to get a small file descriptor
number. But it will of course be difficult to find one which is
not occupied.

BTW: I wonder why Milter Greylist has so many file descriptors open at the
     same time. How many does it require to handle a single connection?

	Kind regards

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

RE: [milter-greylist] Volume 2

2004-10-28 by Sutherland, James

This is an interesting article I found on sunhelp about somebody else
having the same issue:
 
http://www.sunhelp.org/pipermail/sunhelp/2002-January/015005.html
 

________________________________
Show quoted textHide quoted text
From: Matthias Scheler [mailto:tron@...] 
Sent: Thursday, October 28, 2004 1:17 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Volume 2


On Thu, Oct 28, 2004 at 09:30:15AM +0200, Emmanuel Dreyfus wrote:
> So your OS was not able to open that file, but doesn't tell us why
> (errno says no error occured).

I couldn't open that file because you a passed file number larger than
255.
From Solaris's stdio(3C) manual page:

     The integer constant FOPEN_MAX specifies the minimum  number
     of  files  that  the  implementation  guarantees can be open
     simultaneously. Note that no more  than  255  files  may  be
     opened  using  fopen(),  and only file descriptors 0 through
     255 can be used in a stream.

That historic restricion does however only apply to 32Bit binaries.
The work arround is to use dup2(3C) to get a small file descriptor
number. But it will of course be difficult to find one which is
not occupied.

BTW: I wonder why Milter Greylist has so many file descriptors open at
the
     same time. How many does it require to handle a single connection?

      Kind regards

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


Yahoo! Groups Sponsor	
 
<http://us.ard.yahoo.com/SIG=12911i8ko/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099081043/A=2343726/R=0/SIG=12i0jiuvm/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989946431
86431>
<http://us.ard.yahoo.com/SIG=12911i8ko/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099081043/A=2343726/R=1/SIG=12i0jiuvm/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989946431
86431> 

Get unlimited calls to

U.S./Canada

 
<http://view.atdmt.com/VON/view/yhxxxvon01900091von/direct/01/&time=1098
994643186431> 
 
<http://us.adserver.yahoo.com/l?M=281955.5530326.6602771.3001176/D=group
s/S=:HM/A=2343726/rand=568887095> 	

________________________________

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 2

2004-10-28 by Sutherland, James

Looks pretty much the same on this latest failure.  handles open spikes
and milter can't write it's dump so it exits.
 
Oct 28 12:59:07 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 30
Oct 28 13:04:14 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 42
Oct 28 13:09:21 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 59
Oct 28 13:14:28 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 14
Oct 28 13:19:35 hns1 milter-greylist: [ID 799890 mail.info] dumpfd = 463
Oct 28 13:19:35 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
463, dump = 0, errno = 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
463, dump = 0, errno = 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
463, dump = 0, errno = 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 180808 mail.error] dumpfd =
463, dump = 0, errno = 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXKFaySc": Error 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXKFaySc": Error 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXKFaySc": Error 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 525239 mail.error] cannot
write dumpfile "/var/milter-greylist/greylist.db-XXKFaySc": Error 0
Oct 28 13:19:35 hns1 milter-greylist: [ID 421540 mail.info] Final
database dump: no change to dump
Oct 28 13:19:35 hns1 milter-greylist: [ID 146194 mail.info] Exitting
 
 

________________________________
Show quoted textHide quoted text
From: Matthias Scheler [mailto:tron@...] 
Sent: Thursday, October 28, 2004 1:17 PM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Volume 2


On Thu, Oct 28, 2004 at 09:30:15AM +0200, Emmanuel Dreyfus wrote:
> So your OS was not able to open that file, but doesn't tell us why
> (errno says no error occured).

I couldn't open that file because you a passed file number larger than
255.
From Solaris's stdio(3C) manual page:

     The integer constant FOPEN_MAX specifies the minimum  number
     of  files  that  the  implementation  guarantees can be open
     simultaneously. Note that no more  than  255  files  may  be
     opened  using  fopen(),  and only file descriptors 0 through
     255 can be used in a stream.

That historic restricion does however only apply to 32Bit binaries.
The work arround is to use dup2(3C) to get a small file descriptor
number. But it will of course be difficult to find one which is
not occupied.

BTW: I wonder why Milter Greylist has so many file descriptors open at
the
     same time. How many does it require to handle a single connection?

      Kind regards

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


Yahoo! Groups Sponsor	
 
<http://us.ard.yahoo.com/SIG=12911i8ko/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099081043/A=2343726/R=0/SIG=12i0jiuvm/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989946431
86431>
<http://us.ard.yahoo.com/SIG=12911i8ko/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099081043/A=2343726/R=1/SIG=12i0jiuvm/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10989946431
86431> 

Get unlimited calls to

U.S./Canada

 
<http://view.atdmt.com/VON/view/yhxxxvon01900091von/direct/01/&time=1098
994643186431> 
 
<http://us.adserver.yahoo.com/l?M=281955.5530326.6602771.3001176/D=group
s/S=:HM/A=2343726/rand=568887095> 	

________________________________

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 2

2004-10-29 by Emmanuel Dreyfus

On Thu, Oct 28, 2004 at 10:17:03PM +0200, Matthias Scheler wrote:
> I couldn't open that file because you a passed file number larger than 255.
> >From Solaris's stdio(3C) manual page:
> 
>      The integer constant FOPEN_MAX specifies the minimum  number
>      of  files  that  the  implementation  guarantees can be open
>      simultaneously. Note that no more  than  255  files  may  be
>      opened  using  fopen(),  and only file descriptors 0 through
>      255 can be used in a stream.

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

RE: [milter-greylist] Volume 2

2004-10-29 by Sutherland, James

Another option would be to spawn a child process to write the db dump.
Since each pid is limited.

________________________________
Show quoted textHide quoted text
From: Emmanuel Dreyfus [mailto:manu@...] 
Sent: Friday, October 29, 2004 1:08 AM
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Volume 2


On Thu, Oct 28, 2004 at 10:17:03PM +0200, Matthias Scheler wrote:
> I couldn't open that file because you a passed file number larger than
255.
> >From Solaris's stdio(3C) manual page:
> 
>      The integer constant FOPEN_MAX specifies the minimum  number
>      of  files  that  the  implementation  guarantees can be open
>      simultaneously. Note that no more  than  255  files  may  be
>      opened  using  fopen(),  and only file descriptors 0 through
>      255 can be used in a stream.

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


Yahoo! Groups Sponsor	
 
<http://us.ard.yahoo.com/SIG=1297egjff/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099123701/A=2343726/R=0/SIG=12ihitl4m/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10990373014
06077>
<http://us.ard.yahoo.com/SIG=1297egjff/M=281955.5530326.6602771.3001176/
D=groups/S=1707281942:HM/EXP=1099123701/A=2343726/R=1/SIG=12ihitl4m/*htt
p://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=10990373014
06077> 

Get unlimited calls to

U.S./Canada

 
<http://view.atdmt.com/VON/view/yhxxxvon01900091von/direct/01/&time=1099
037301406077> 
 
<http://us.adserver.yahoo.com/l?M=281955.5530326.6602771.3001176/D=group
s/S=:HM/A=2343726/rand=881399884> 	

________________________________

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 2

2004-10-29 by Emmanuel Dreyfus

On Fri, Oct 29, 2004 at 08:05:55AM -0700, Sutherland, James wrote:
> Another option would be to spawn a child process to write the db dump.
> Since each pid is limited.

On a system that doesn't fork using COW, that will cause a major memory 
copy. Otherwise it could be a good workaround.

-- 
Emmanuel Dreyfus
manu@...

Re: [milter-greylist] Volume 2

2004-11-01 by Matthias Scheler

On Fri, Oct 29, 2004 at 08:05:55AM -0700, Sutherland, James wrote:
> Another option would be to spawn a child process to write the db dump.

No, that won't work. After fork() you are only allowed to use
Async-Signal-Safe function until you have used exec(). And fdopen()
and many of the other functions used by the dumper routine are
only MT-safe but not Async-Signal-Safe.

We already had that problem in Milter Greylist, please don't
reintroduce it.

	Kind regards

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

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.