Re: IPv6 problem with sa-update

2010-08-08 Thread Andreas Schulze
On Sun, Aug 08, 2010 at 02:57:29PM -0500, Dave Funk wrote: > For some reason when you set that "options inet6" your system is not > willing to fall back to IPv4 mode (or a bug is preventing it). > That's what you need to look into (until such time as > spamassassin.apache.org gets v6 connected ;)

Re: IPv6 problem with sa-update

2010-08-08 Thread Michael Scheidell
On 8/8/10 2:46 PM, Andreas Schulze wrote: Hi, at my Debian Lenny /etc/resolv.conf contains "options inet6" sa-update failed with retruncode 4. I wonder if adding spamassassin.apache.org to your hosts file will help? as to my previous post, yes, I guess it doesn't have an record. and

Re: IPv6 problem with sa-update

2010-08-08 Thread Dave Funk
On Sun, 8 Aug 2010, Andreas Schulze wrote: Hi, at my Debian Lenny /etc/resolv.conf contains "options inet6" sa-update failed with retruncode 4. GET http://spamassassin.apache.org/updates/MIRRORED.BY request failed: 500 Can't connect to spamassassin.apache.org:80 (Bad hostname 'spamassassin.apa

Re: IPv6 problem with sa-update

2010-08-08 Thread Michael Scheidell
On 8/8/10 2:46 PM, Andreas Schulze wrote: Hi, at my Debian Lenny /etc/resolv.conf contains "options inet6" sa-update failed with retruncode 4. GET http://spamassassin.apache.org/updates/MIRRORED.BY request failed: 500 Can't connect to spamassassin.apache.org:80 (Bad hostname 'spamassassin.apach

IPv6 problem with sa-update

2010-08-08 Thread Andreas Schulze
Hi, at my Debian Lenny /etc/resolv.conf contains "options inet6" sa-update failed with retruncode 4. GET http://spamassassin.apache.org/updates/MIRRORED.BY request failed: 500 Can't connect to spamassassin.apache.org:80 (Bad hostname 'spamassassin.apache.org'): 500 Can't connect to spamassassin.a