>>> used 'it' for YEARS in production, (commercial product,)
>>> several
>>> platforms, i386, amd64, FreeBSD versions 6.4-7.4.
>>>
>>> ONE DAY, ONE BRAND NEW CLIENT was having real problems with their
>>> mailq. email was backing up.
>>> Two days to figure it out, I deleted the INET6
rpm -e --nodeps perl-IO-Socket-INET6
>>> By the way, is there a way to grep for the errant code? My
>>> feeble attempt didn't turn up much:
>>>
>> as in one of my previous emails:
>>
>> 'locate IO-Socket-INET6'
Sorry I missed that!
This gives only docs:
/usr/share/doc/perl-IO-Sock
On 1/9/12 1:33 PM, Juergen Edner wrote:
Hello,
I'm using SpamAssassin for years now to get rid of spam.
Now I wonder which sa-update channels you're using by
default to improve your scan results.
Are you sticking to the default 'updates.spamassassin.org'
Commercial product, maintainer of the Free
Hello,
I'm using SpamAssassin for years now to get rid of spam.
Now I wonder which sa-update channels you're using by
default to improve your scan results.
Are you sticking to the default 'updates.spamassassin.org'
channel only or would you recommend to use other channels
too. Unfortunately the SAR
On 1/9/12 6:25 AM, Michael Scheidell wrote:
On 1/8/12 9:52 PM, email builder wrote:
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
locate INET6
On 1/8/12 9:52 PM, email builder wrote:
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
