16 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Greylisting and C...
FromSent OnAttachments
Marco BalmerNov 21, 2006 3:49 am 
Georg LutzNov 25, 2006 6:58 am 
Marco BalmerNov 28, 2006 10:39 am 
Milan ObuchNov 28, 2006 10:50 am 
Marco BalmerNov 28, 2006 11:14 am 
Marco BalmerNov 28, 2006 2:30 pm 
Georg LutzNov 28, 2006 2:36 pm 
Marco BalmerNov 28, 2006 2:41 pm 
Marco BalmerNov 28, 2006 3:02 pm 
Gordon MessmerNov 28, 2006 3:21 pm 
Marco BalmerNov 29, 2006 10:54 am 
Georg LutzNov 29, 2006 2:21 pm 
Marco BalmerNov 29, 2006 2:57 pm 
Gordon MessmerNov 29, 2006 3:53 pm 
Gordon MessmerNov 29, 2006 3:58 pm 
Marco BalmerNov 30, 2006 12:49 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Greylisting and Courier-MTAActions...
From:Georg Lutz (geor@georglutz.de)
Date:Nov 29, 2006 2:21:18 pm
List:net.sourceforge.lists.courier-users

On 2006-11-29 19:54, Marco Balmer wrote:

Hello

Seems to be that greylist.py has a problem with ipv6 addresses. Is that possible?

Nov 29 09:22:27 xxx courieresmtpd: error,relay=2001:xxx:xxx:xxx::2,from=<xy@domain.tld>: 451 Internal failure locating control files

This is true, greylist.py uses the IPv6 address directly without further network calculation like with IPv4 (it doesn't make much sense with IPv6 anyway at that time).

But I suppose the 451 error is triggered somewhere else, not in greylist.py . Perhaps in line 38 of whitelist.py .