Milter-greylist

Hello!

I inserted some debug output into the peer_connect() function:

Entering peer_connect()
In function: peer_connect(), before fdopen()
In function: peer_connect(), before sync_waitdata()
Leaving function: peer_connect()
milter-greylist: Connection to 217.116.182.106 established
Entering peer_connect()
[Thread 1115703648 (LWP 29460) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 29520)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1115703648 (LWP 29520) exited]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: cannot sync with peer 213.235.245.178: Connection timed out
(0 entries queued)
[New Thread 1115703648 (LWP 29681)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j977DUrl029673: skipping greylist because address
209.132.176.167 is whitelisted,
(from==40netshadow.at-S1750704AbVJGHKi@...>,
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 29681) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 29776)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j977FXel029775: addr 66.35.250.225 from
<havp-users-admin@...> rcpt <unki@...>:
autowhitelisted for more 2160:00:00
Entering peer_connect()
[Thread 1115703648 (LWP 29776) exited]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: cannot sync with peer 213.235.245.178: Connection timed out
(1 entries queued)
[New Thread 1115703648 (LWP 30060)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1107310944 (LWP 28481) exited]
milter-greylist: greylist: mi_stop=2
milter-greylist: Final database dump: no change to dump
milter-greylist: Exiting

The first try to connect 213.235.245.178 didn't make problems. But after the
second one, milter-greylist exits.

So this happens somewhere around line 399 in sync.c, where peer_connect()
return -1.

Emmanuel Dreyfus (manu@...) schrieb:
>
> On Thu, Oct 06, 2005 at 07:57:30PM +0200, Andreas Unterkircher wrote:
> > So - it looks like my suspicion on the unreachable host was correct.
> >
> > On x86 v2.0.1 has no problem with a unreachable host as mx peer in the
> > config.
> > On x64 v2.0.1 exits after some random time with a unreachable host as mx
> > peer in the config.
> > (like showed in the mails before).
>
> An unreachable peer should trigger an error message in the log. Can you
> add some printf around the connect calls in sync.c and run milter-greylist
> in the foreground so that we know what happen when connect fails because the
> host is unreachable?
>
> --
> Emmanuel Dreyfus
> manu@...
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>