Yahoo Groups archive

Milter-greylist

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

Thread

Can't get it working

Can't get it working

2007-11-27 by Bust Ed

Hi,
I've installed milter-greylist on my FreeBSD from ports. It worked,
but there were some problems, so i decided to upgrade it. Downloaded
from homepage latest version, went through readme... And it won't
launch. Just reading config file and quits without any message. Is
there any log, to know, why it works such way?


-- 
Best regards,
 Bust Ed                          mailto:bust_ed@...

Re: [milter-greylist] Can't get it working

2007-11-27 by Emmanuel Dreyfus

On Tue, Nov 27, 2007 at 02:06:55PM +0300, Bust Ed wrote:
> I've installed milter-greylist on my FreeBSD from ports. It worked,
> but there were some problems, so i decided to upgrade it. Downloaded
> from homepage latest version, went through readme... And it won't
> launch. Just reading config file and quits without any message. Is
> there any log, to know, why it works such way?

Yes, there are logs, they go to the mail facility.
You can also start milter-greylist in the foreground and in verbose mode:
milter-greylist -Dv

-- 
Emmanuel Dreyfus
manu@...

Re[2]: [milter-greylist] Can't get it working

2007-11-27 by Bust Ed

Hello Emmanuel,


Thanks,


Here what i've got:


su-2.05b# milter-greylist -Dv

... skipped

Access list dump:

racl 126 whitelist net_list "my network"

racl 127 whitelist net_list "broken mta"

racl 136 greylist rcpt_list "grey users" [delay 1800] [aw 259200]

racl 137 whitelist default

cannot read dumpfile "/var/milter-greylist/greylist.db"

starting with an empty greylist

smfi_main() returned -1

Final database dump: no change to dump

su-2.05b#


What's the problem?



>

On Tue, Nov 27, 2007 at 02:06:55PM +0300, Bust Ed wrote:

> I've installed milter-greylist on my FreeBSD from ports. It worked,

> but there were some problems, so i decided to upgrade it. Downloaded

> from homepage latest version, went through readme... And it won't

> launch. Just reading config file and quits without any message. Is

> there any log, to know, why it works such way?


Yes, there are logs, they go to the mail facility.

You can also start milter-greylist in the foreground and in verbose mode:

milter-greylist -Dv


--

Emmanuel Dreyfus

manu@...





--

Best regards,

Bust mailto:bust_ed@...

Re: [milter-greylist] Can't get it working

2007-11-27 by Nerijus Baliunas

On Tue, 27 Nov 2007 14:06:55 +0300 Bust Ed <bust_ed@...> wrote:

> I've installed milter-greylist on my FreeBSD from ports. It worked,
> but there were some problems, so i decided to upgrade it. Downloaded
> from homepage latest version, went through readme... And it won't
> launch. Just reading config file and quits without any message. Is
> there any log, to know, why it works such way?

Please check permissions - is the user which runs milter-greylist
able to access config, socket and *.db file?

Regards,
Nerijus

Re[2]: [milter-greylist] Can't get it working

2007-11-28 by Bust Ed

Hello Nerijus,


There's no socket and *.db file. I've created new empty, chowned to smmsp. No change:


loaded config file "/etc/mail/greylist.conf" in 0.002246s

Access list dump:

racl 126 whitelist net_list "my network"

racl 127 whitelist net_list "broken mta"

racl 136 greylist rcpt_list "grey users" [delay 1800] [aw 259200]

racl 137 whitelist default

smfi_main() returned -1

Final database dump: no change to dump


That's all.


>

On Tue, 27 Nov 2007 14:06:55 +0300 Bust Ed <bust_ed@...> wrote:


> I've installed milter-greylist on my FreeBSD from ports. It worked,

> but there were some problems, so i decided to upgrade it. Downloaded

> from homepage latest version, went through readme... And it won't

> launch. Just reading config file and quits without any message. Is

> there any log, to know, why it works such way?


Please check permissions - is the user which runs milter-greylist

able to access config, socket and *.db file?


Regards,

Nerijus





--

Best regards,

Bust mailto:bust_ed@...

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.