Yahoo Groups archive

Milter-greylist

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

Thread

milter-greylist 2.0 beta2 stops working after awhile.

milter-greylist 2.0 beta2 stops working after awhile.

2005-03-17 by iewebguy

Hello,

I just installed milter-greylist 2.0 beta2 and it works well for a
while, and then I get

Milter (greylist): error connecting to filter: Connection refused by
/var/milter-greylist/milter-greylist.sock

in the maillog.

How can I find out why it stops working? I am using the -v switch, but
I don't see any log entrys at the point of failure.

Is there a way to keep milter-greylist from forking so I can run it in
a terminal session?

I am on redhat 9

Any thoughts would be appreciated.

Mark

Re: [milter-greylist] milter-greylist 2.0 beta2 stops working after awhile.

2005-03-17 by manu@netbsd.org

iewebguy <mark@...> wrote:

[milter-greylist crashes]
Usual things to check
- if you have SPF support enabled, is your DNS resolver thread-safe? Run
nm on libspf (or libspf_alt), do you have res_init or nres_init in the
symbol table? If res_init then your DNS resolver is probably thread
unsafe, and this is why you crash. Disable SPF or rebuilt libspf{_alt}
linked with a thread safe DNS, and it will be alright.

- do you hit a resource limit? Try unlimiting the file descriptor limit
using ulimit (or limit if yo are a csh freak :-) 

> Is there a way to keep milter-greylist from forking so I can run it in
> a terminal session?

RTFM, there is a command line option for that.

If you don't get any clue by running in the foreground, you can try
running it in gdb. Add -g to CFLAGS in the Makefile, rebuild, and
run
gdb milter-greylist
(gdb) r -Dv

If it crashes, issue the bt command at the gdb prompt and send me the
backtrace. That will help understanding why it goes wrong? 

-- 
Emmanuel Dreyfus
Publicité subliminale: achetez ce livre!
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
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.