Milter-greylist

Hello all!

Has anyone seen following startup error messages like these:

Nov 16 00:27:18 tuvok milter-greylist: [ID 690954 mail.debug] unknown token "(" line 2070904, skipping
Nov 16 00:27:18 tuvok milter-greylist: [ID 663796 mail.debug] dump error at line 2070904: syntax error
Nov 16 00:27:18 tuvok milter-greylist: [ID 690954 mail.debug] unknown token ")" line 2070904, skipping
Nov 16 00:27:20 tuvok milter-greylist: [ID 690954 mail.debug] unknown token "(" line 2163466, skipping
Nov 16 00:27:20 tuvok milter-greylist: [ID 663796 mail.debug] dump error at line 2163466: syntax error
Nov 16 00:27:20 tuvok milter-greylist: [ID 690954 mail.debug] unknown token ")" line 2163466, skipping
Nov 16 00:27:20 tuvok milter-greylist: [ID 704145 mail.error] cannot start MX sync, bind failed: Address already in use
Nov 16 00:27:20 tuvok milter-greylist: [ID 829457 mail.error] cannot start MX sync, socket failed: Address already in use

milter-greylist left inoperable because the unix socket is missing ...
Just using milter-greylist 4.0rc1 - is this fixed any newer version?

The addresses which are the reason for the syntax errors have the form

<part1(part2)part2@domain>

I thing MG should accept "(" and ")" while reading the DB dump file if
these characters are dumped out sometimes before (regardless of RFC(2)822
compliance).


Johann

On Fri, Nov 16, 2007 at 01:11:19AM +0100, Johann E. Klasek wrote:
> Nov 16 00:27:18 tuvok milter-greylist: [ID 690954 mail.debug] unknown token "(" line 2070904, skipping

Theses are just harmless warnings. The tuple will not be reloaded, which 
will cause an extra delay in mail delivery, but that should not prevent
milter-greylist from launching.

> Nov 16 00:27:20 tuvok milter-greylist: [ID 704145 mail.error] cannot start MX sync, bind failed: Address already in use

That usually happen if you have another milter-greylist instance running.
It can also be that another process listen on MX sync port.

-- 
Emmanuel Dreyfus
manu@...