On Thu, May 23, 2013 at 01:45:42AM +0930, Peter Gossner wrote:
> This issue has effected 
>   - at least 5 machines I have worked with. (and many virtuals)
>   - has remained across versions.
>   - blocks upgrades and even initial  _install on stable releases_.
>   - blocks sa-update (and others)

Can I ask why you are enabling 'options inet6' in resolv.conf? The
resolv.conf(5) documenation indicates that "Some programs behave
strangely when this option is turned on." I wonder what your use case
for it is?

> While solution(s) seem simple 
> ("nameserver s/::1/127.0.0.1/  and remove the options inet6 line from 
> /etc/resolv.conf)
> Its tricky getting to that solution on fresh installs.
> (without foreknowledge)

'options inet6' is not enabled on fresh installs. Just verified that.

> FWIW very similar IPv6 issues occur with cpan builds.
> Some weird perl dependency thing I expect.
> The existance of AAA::Mail::SpamAssassin is of note.
> So the real issue remain upstream.

Note that 'options inet6' is not required or IPv6 transport or DNS
resolution to work, generally.

> Do we need to run sa-update at install time ?

You never *need* to run sa-update. The spamassassin packages include a
collection of rules provided by upstream at the time that the package
was most recently updated. However, it is highly recommended that you
use sa-update in order to keep up with changing spam tactics. The
recommended way to do this is by setting CRON=1 in
/etc/default/spamassassin.

noah

Attachment: signature.asc
Description: Digital signature

Reply via email to