Milter-greylist

Hello,

I am trying to install milter-greylist 2.1.3 on AIX .. with more or less
success.

On AIX 5.2 (no maintenance level) or AIX 4.3 (maintenance level 11),
I get the following error message at run time:

config error at line 32: syntax error

This concerns the first ACL whitelist of the file (the original sample
file in this case):

acl whitelist addr 127.0.0.0/8

Same problem if I uncomment a peer entry but then, it crashes with the
following message

Mar 13 08:59:42 xxxxxxx milter-greylist: cannot start MX sync, socket
failed: A file or directory in the path name does not exist.

On AIX 5.2, ML 7, both problems seem to be solved and the thing works well
(I couldn't test the MX sync yet).

Unfortunately, ML 11 is the lastest maintenance level for AIX 4.3 :-(

Would you have any idea where things could go wrong ? I'm using
bison-1.875 and flex-2.5.33 but I don't think the problem is there.
Actually, after upgrading from AIX 5.2 to AIX 5.2-ML7, the problems
disappeared without needing to recompile anything.


The config error problem is there for all the versions I tried (just in
case): 1.75, 1.4, 1.2, ...
The MX sync problem seems to disappear with 1.4 ...

Thanks in advance for any hint,

--
Alain Buys

Daniel Zachary <dan_zachary@...> wrote:

> I've noticed that milter-greylist seems to truncate the sender's name
> when there is an '=' sign as part of the username.  Is this a bug that
> needs to be fixed?

It's not a bug, it's a feature :-)

-- 
Emmanuel Dreyfus
Le cahier de l'admin BSD 2eme ed. est dans toutes les bonnes librairies
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...

--- In milter-greylist@yahoogroups.com, manu@... wrote:
>
> Daniel Zachary <dan_zachary@...> wrote:
> 
> > I've noticed that milter-greylist seems to truncate the sender's name
> > when there is an '=' sign as part of the username.  Is this a bug that
> > needs to be fixed?
> 
> It's not a bug, it's a feature :-)

I just noticed that same issue (in 2.0.2).

Will it be fixed sometime?


    Elrond

Elrond <yahoo.com@...> wrote:

> Will it be fixed sometime?

If you submit a patch for making it configurable, it will be integrated.

-- 
Emmanuel Dreyfus
Publicité subliminale: achetez ce livre!
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@netbsd.org

--- In milter-greylist@yahoogroups.com, manu@... wrote:
>
> Elrond <yahoo.com@...> wrote:
> 
> > Will it be fixed sometime?
> 
> If you submit a patch for making it configurable, it will be integrated.

Why exactly does it need to be configurable?

You don't want to tell me, that anyone depends on the broken behaviour?
--> If broken entries are in the autowhitelist: milter-greylist will
learn the correct ones and forget the old ones.

Or you don't want to tell me, that this is "by design"?

Or... Wait...

Is this for those broken MTAs, that send a unique envelope-sender per
attempt? No? Yes? If so, please let me know, where it's documented. It
should be documented.


    Elrond

--- In milter-greylist@yahoogroups.com, Dan Zachary <dan_zachary@...>
wrote:
>
> As pointed out previously by Manu, this is a FEATURE, not a bug. It's 
> intended to prevent too many listing in the greylist (remove the serial 
> numbers from list messages that use this pattern).

He only said, that it's a feature. Not what it is intended to do, that
confused me a bit. It sounded a bit like a joke. ;-)

This feature has it's confusing parts. When I first saw it in my db
file, I thought "Oh well, it's broken in the parser?".

As you can see in my previous mail, I finally found out, what it's
good for.

> If you don't like this feature, it could be configurable as an option, 
> but you'd have to write the code and submit it.

IF I find the time, I'd rather consider making this more obvious in
the logs / db dump. Like putting a * in front to show, that it was
trimmed to make it like a wildcard. Or "..." or something like that.
Something, so the admin sees "The software did not just drop/loose
something, it did something intended".
(And I preivously wrote patches for milter-greylist, so I know to
write patches.)


> Dan


    Elrond

> Elrond wrote:
> > --- In milter-greylist@yahoogroups.com, manu@ wrote:
> >   
> >> Elrond <yahoo.com@> wrote:
> >>
> >>     
> >>> Will it be fixed sometime?
> >>>       
> >> If you submit a patch for making it configurable, it will be
integrated.
> >>     
> >
> > Why exactly does it need to be configurable?
> >
> > You don't want to tell me, that anyone depends on the broken
behaviour?

> > --> If broken entries are in the autowhitelist: milter-greylist will
> > learn the correct ones and forget the old ones.
> >
> > Or you don't want to tell me, that this is "by design"?
> >
> > Or... Wait...
> >
> > Is this for those broken MTAs, that send a unique envelope-sender per
> > attempt? No? Yes? If so, please let me know, where it's documented. It
> > should be documented.
> >
> >
> >     Elrond
> >
> >
> >
> >
> >
> >
> >
> >  
> > Yahoo! Groups Links
> >
> >
> >
> >  
> >
> >
> >
>