Yahoo Groups archive

Milter-greylist

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

Thread

geoiplookup6

geoiplookup6

2015-07-02 by BERTRAND Joël

Hello,

	I use milter-greylist for a long time with geoip and I have seen this 
morning that ipv6 are sent to geoiplookup, not to geolookup6. Is a known 
issue ?

	Regards,

	JB

Re: [milter-greylist] geoiplookup6

2015-07-02 by manu@...

BERTRAND Joël joel.bertrand@... [milter-greylist]
<milter-greylist@yahoogroups.com> wrote:

>       I use milter-greylist for a long time with geoip and I have seen this
> morning that ipv6 are sent to geoiplookup, not to geolookup6. Is a known
> issue ?

Not until you raised it. Will you craft a fix?


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

Re: [milter-greylist] geoiplookup6

2015-07-03 by Hajimu UMEMOTO

Hi,

>>>>> On Thu, 2 Jul 2015 17:15:09 +0200
>>>>> "manu@... [milter-greylist]" <milter-greylist@yahoogroups.com> said:

>       I use milter-greylist for a long time with geoip and I have seen this
> morning that ipv6 are sent to geoiplookup, not to geolookup6. Is a known
> issue ?

milter-greylist> Not until you raised it. Will you craft a fix?

How about this?
Sorry but I'm not testing it by my self.

Sincerely,

Re: [milter-greylist] geoiplookup6 [1 Attachment]

2015-12-03 by BERTRAND_Jo=c3=abl

Manuel Badzong manuel@... [milter-greylist] a \ufffdcrit :
> [Attachment(s) <#TopText> from Manuel Badzong included below]
>
> On Fri, Jul 03, 2015 at 01:58:04PM +0900, Hajimu UMEMOTO
> ume@... [milter-greylist] wrote:
>  > How about this?
> Unfortunately it's not that simple. GeoIP uses a different database for IPv6
> lookups.
>
> I just recently added GeoIP support to mopher using milter-greylist code as
> a blueprint. By courtesy I attached a quick backport ;)
>
> Warning, this patch is untested.

	Hello,

	With a lot of delay, I have applied your patch against 4.5.16. It seems 
to run as expected.

	Regards,

	JKB

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.