Milter-greylist

Hello,

I've just installed milter-greylist on a Tru64 computer (first 2.0.2, then
I've tried 1.6 and 2.1.3) and I've always the same problem.

In the header I get the following line :

X-Greylist: Message not sent from an IPv4 address, not delayed by
milter-greylist-x.y .

As far as I understand from the source code, it seems to me that the AF_INET
is not recognized but perharps I'm wrong.

On another Linux mail server we get : 

X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by
milter-greylist-x.y

Some idea on this problem ?

Thanks and Regards

Daniel Clar
Supelec

Hi,

>>>>> On Sat, 18 Mar 2006 12:42:30 +0100
>>>>> "Daniel Clar" <Daniel.Clar@...> said:

Daniel> I've just installed milter-greylist on a Tru64 computer (first 2.0.2, then
Daniel> I've tried 1.6 and 2.1.3) and I've always the same problem.

Daniel> In the header I get the following line :

Daniel> X-Greylist: Message not sent from an IPv4 address, not delayed by
Daniel> milter-greylist-x.y .

Daniel> As far as I understand from the source code, it seems to me that the AF_INET
Daniel> is not recognized but perharps I'm wrong.

It seems to me that sendmail doesn't pass sockaddr to milter-greylist
correctly, or sendmail doesn't set sa_family correctly.  I suspect
your sendmail configuration, perhaps confMILTER_MACROS_CONNECT doesn't
have {if_addr} macro?

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@...  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/

Several things have been tried following 2 e-mails :

- Run milter-greylist alone without clamav and spamassassin

- Trying a newer libmilter.a

- running with -v option to have more information in mail.log but nothing is
coming after starting.

- verify the milter config : yes {if_addr} is here

- I have no "smfi_getsymval failed for ..." error messages or I doon't find
them in any log file.

Regards

Daniel

Hello,

In fact, the problem is not there but in the creation of greylist.db .

On Tru64 there is no greylist.db file when the software runs for the 
first time and the result is this strange message with non IPV4 address.
So nothing comes in the greylist.db file.

The solution I've found was to copy a greylist.db file from a Linux box 
and now evrything works fine.

So the remaining question is : was something written somewhere on how 
to create a greylist.db file for the first time ?

Regards

Daniel

dc91190 <Daniel.Clar@...> wrote:

> So the remaining question is : was something written somewhere on how
> to create a greylist.db file for the first time ?

A blank file should do it.

I'm very suprised it does not create it when it's missing. The file
should be created using mkstemp(). Is there something special on Tru64
with mkstemp()?

-- 
Emmanuel Dreyfus
Un bouquin en français sur BSD:
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...

wrote on Thu, 23 Mar 2006 18:46:34 +0100:

> I'm very suprised it does not create it when it's missing.

Hm, now that you say it, I'm missing the file on my new CentOS 
installation as well. There's a pid and a socket but not db in 
/var/milter-greylist. However, I don't see it complaining (other than on 
startup where it says "empty db"). At the moment this machine gets only 
test mail from pre-whitelisted machines. Could this be the reason why it 
didn't create the db yet?

Kai

-- 
Kai Sch\ufffdtzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

Kai Schaetzl <maillists@...> wrote:

> Hm, now that you say it, I'm missing the file on my new CentOS 
> installation as well. There's a pid and a socket but not db in 
> /var/milter-greylist. 

Does the UID running milter-greylist has the right to write the dump
file?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

wrote on Thu, 23 Mar 2006 23:50:10 +0100:

> Does the UID running milter-greylist has the right to write the dump 
> file?

sure, at the moment it's running as root, see my other posting about 
"cannot change supplementary groups".

Kai

-- 
Kai Sch\ufffdtzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

On Sat, Mar 18, 2006 at 12:42:30PM +0100, Daniel Clar wrote:
> X-Greylist: Message not sent from an IPv4 address, not delayed by
> milter-greylist-x.y .

Did you disable the IPv6 support in Milter Greylist?

True64 has a dual network stack and "sendmail" might be using an IPv6
socket even for IPv4 connections.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Kai Schaetzl wrote on Thu, 23 Mar 2006 19:45:15 +0100:

> At the moment this machine gets only 
> test mail from pre-whitelisted machines. Could this be the reason why it 
> didn't create the db yet?

I can confirm this now. As long as incoming messages are whitelisted by 
greylist.conf or SPF, there's no need to write to greylist.db and it 
doesn't exist. First time the milter issues "Greylisting in action" it 
creates the db.

Kai

-- 
Kai Sch\ufffdtzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

> > X-Greylist: Message not sent from an IPv4 address, not delayed by
> > milter-greylist-x.y .
> 
> Did you disable the IPv6 support in Milter Greylist?
> 
> True64 has a dual network stack and "sendmail" might be using an IPv6
> socket even for IPv4 connections.

The attached patch removes some code asymmetry in the IPv4 - IPv6 relation.
There is no functionality changes. The most important part that it may produce more
accurate error messages such as instead of
"Message not sent from an IPv4 address"
it gives
"Message not sent from an IPv4 neither IPv6 address"
if IPv6 support is compiled in.

Bests,
Attila

I've looked inside the source code and I've found that the problem was
coming from the dump_dirty variable initialized to 0. So dump_perform was
not executed, the file was not created and the message about IPV4 address
was sent and no modification took place so even at the end the file was not
created.

So I've put the variable to 1 and everything was OK.

I don't know why it's just on Tru64.

Daniel

> -----Message d'origine-----
> De : milter-greylist@yahoogroups.com 
> [mailto:milter-greylist@yahoogroups.com] De la part de 
> attila.bruncsak@...
> Envoyé : mercredi 29 mars 2006 15:18
> À : milter-greylist@yahoogroups.com
> Objet : RE: [milter-greylist] Problem with AF_INET 
> recognition on Tru64
> 
> > > X-Greylist: Message not sent from an IPv4 address, not delayed by
> > > milter-greylist-x.y .
> > 
> > Did you disable the IPv6 support in Milter Greylist?
> > 
> > True64 has a dual network stack and "sendmail" might be 
> using an IPv6
> > socket even for IPv4 connections.
> 
> The attached patch removes some code asymmetry in the IPv4 - 
> IPv6 relation.
> There is no functionality changes. The most important part 
> that it may produce more
> accurate error messages such as instead of
> "Message not sent from an IPv4 address"
> it gives
> "Message not sent from an IPv4 neither IPv6 address"
> if IPv6 support is compiled in.
> 
> Bests,
> Attila
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
>

> I've looked inside the source code and I've found that the problem was
> coming from the dump_dirty variable initialized to 0. So 
> dump_perform was
> not executed, the file was not created and the message about 
> IPV4 address
> was sent and no modification took place so even at the end 
> the file was not
> created.
> 
> So I've put the variable to 1 and everything was OK.
> 
> I don't know why it's just on Tru64.
> 
> Daniel
> 

Surely my patch does not solve your problem,
but at least gives more precise error message
so it is worth to apply to the source code.

I found this small thing during the time I tried to
find the source of your problem via reading the code.

Bests,
Attila

--- In milter-greylist@yahoogroups.com, <attila.bruncsak@...> wrote:
> 
> The attached patch removes some code asymmetry in the IPv4 - IPv6 
relation.
> There is no functionality changes. The most important part that it 
may produce more
> accurate error messages such as instead of
> "Message not sent from an IPv4 address"
> it gives
> "Message not sent from an IPv4 neither IPv6 address"
> if IPv6 support is compiled in.
> 
> Bests,
> Attila
>

Hi

Where can I get these patches? It says "Not stored" with this message.

Sincerely
Seppo