Yahoo Groups archive

Milter-greylist

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

Message

Re: [milter-greylist] peering problems on sun 8

2007-03-07 by An.H.Nguyen

Through my tests, it is confirmed that tcpdump does not show any sync activity between the peers. But telneting in port 5252 does work correctly.
I think version 3.1.6 code does not turn on sync. Please let me know which source file to check for enabling sync then I'll recompile from source code.
I swichted back to version 3.0 and sync works fine, but 3.0 does not dump the database when milter-greylist is killed and restarted.
Thanks,
An Nguyen
----- Original Message -----
Sent: Tuesday, March 06, 2007 10:32 AM
Subject: Re: [milter-greylist] peering problems on sun 8

It seems to get connected fine on port 5252 when telneting.
I have trouble with -Dv option and running tcpdump... Will keep trying.
Thanks
An
----- Original Message -----
Sent: Tuesday, March 06, 2007 12:07 AM
Subject: Re: [milter-greylist] peering problems on sun 8

On Mon, Mar 05, 2007 at 10:55:21PM -0800, aNguyen wrote:
> It does not give me any error. It simply does not synchronize to its peer and there's no mxsync in the message log. How do I find error?

First, run with -Dv
Then, try tcpdump to see if there are connexion attempts or not. Try to
telnet on port 5252 to see if the daemon answers to MX sync requests.

--
Emmanuel Dreyfus
manu@netbsd.org

Attachments

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.