https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8211
tm86 <admin@threadmark-it.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |admin@threadmark-it.com.au
--- Comment #2 from tm86 <admin@threadmark-it.com.au> ---
(In reply to Bill Cole from comment #1)
> While multiple current and former PCCC associates (including myself) are
> heavily involved in supporting and maintaining SpamAssassin, PCCC is an
> independent commercial entity offering products that can be used with
> SpamAssassin but are NOT part of the ASF SpamAssassin Project. Their
> specific rules distributed as the "KAM rules channel" and their HashBLs are
> not distributed or supported here. The ASF SpamAssassin Project does not
> operate *any* HashBL. We provide the HashBL plugin so that users can
> configure their own systems to use 3rd-party HashBLs. There are NO specific
> HashBLs or HashBL rules configured in the code distribution or in the
> default rules channel maintained by the ASF SpamAssassin Project.
>
> You may also benefit from opening this discussion on the SpamAssassin Users
> mailing list and by re-reading the documentation of what HashBLs are for,
> how they work, and why they are fundamentally DIFFERENT from DNSBLs:
> 'perldoc Mail::SpamAssassin::Plugin::HashBL' will show you the internal
> documentation. If you believe there's something wrong with the PCCC HashBL
> or the rules in the KAM channel that reference it, contact PCCC for specific
> help with their products.
>
> There is no bug in SA described in this report.
Thank-you for letting me know this has absolutely nothing to to with SA. I
didnt know that ok.
As a previous associate of pccc.com you should be ashamed. The domain name inst
even signed? I think this may be specific to the email gateways im looking at.
Since this has nothing to do with SA and Apache, ill take the bug to ASD and
cyber.gov.au pccc.com have not replied to any questions.
Thanks for the help bud :)
--
You are receiving this mail because:
You are the assignee for the bug.
tm86 <admin@threadmark-it.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |admin@threadmark-it.com.au
--- Comment #2 from tm86 <admin@threadmark-it.com.au> ---
(In reply to Bill Cole from comment #1)
> While multiple current and former PCCC associates (including myself) are
> heavily involved in supporting and maintaining SpamAssassin, PCCC is an
> independent commercial entity offering products that can be used with
> SpamAssassin but are NOT part of the ASF SpamAssassin Project. Their
> specific rules distributed as the "KAM rules channel" and their HashBLs are
> not distributed or supported here. The ASF SpamAssassin Project does not
> operate *any* HashBL. We provide the HashBL plugin so that users can
> configure their own systems to use 3rd-party HashBLs. There are NO specific
> HashBLs or HashBL rules configured in the code distribution or in the
> default rules channel maintained by the ASF SpamAssassin Project.
>
> You may also benefit from opening this discussion on the SpamAssassin Users
> mailing list and by re-reading the documentation of what HashBLs are for,
> how they work, and why they are fundamentally DIFFERENT from DNSBLs:
> 'perldoc Mail::SpamAssassin::Plugin::HashBL' will show you the internal
> documentation. If you believe there's something wrong with the PCCC HashBL
> or the rules in the KAM channel that reference it, contact PCCC for specific
> help with their products.
>
> There is no bug in SA described in this report.
Thank-you for letting me know this has absolutely nothing to to with SA. I
didnt know that ok.
As a previous associate of pccc.com you should be ashamed. The domain name inst
even signed? I think this may be specific to the email gateways im looking at.
Since this has nothing to do with SA and Apache, ill take the bug to ASD and
cyber.gov.au pccc.com have not replied to any questions.
Thanks for the help bud :)
--
You are receiving this mail because:
You are the assignee for the bug.