https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8189
Sidney Markowitz <sidney@sidney.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|REOPENED |RESOLVED
CC| |sidney@sidney.com
--- Comment #3 from Sidney Markowitz <sidney@sidney.com> ---
From your comments, I see that you installed an old version of Spamassassin
(the current one is 4.0.0, with 4.0.1 to be released soon) and found that the
default configuration did not trigger SORBS rules when you think they should.
You were able to get it to trigger custom rules that you added to your
configuration. That proves that 1) The code in SpamAssassin does properly
handle using SORBS as an RBL; and 2) Your configuration after installing
SpamAssassin had a problem with SORBS, which you could work around by changing
the configuration.
You still have a problem, because even though your configuration seems to work,
it is doing so by running five different queries to SORBS nameservers instead
of just one query to the aggregate server and interpreting the results.
This is exactly the kind of problem that you can get help with on the users
mailing list. If after a discussion there you have an example of a specific
email message that demonstrates a bug in SpamAssassin, you can open a bug
report and attach the email along with the steps by which anyone can reproduce
the bug.
Until then, I am closing this issue again as "invalid". That doesn't mean that
your problem is invalid, only that it is not a valid issue for this forum and
is better taken to the user mailing list for help getting it resolved.
--
You are receiving this mail because:
You are the assignee for the bug.
Sidney Markowitz <sidney@sidney.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|REOPENED |RESOLVED
CC| |sidney@sidney.com
--- Comment #3 from Sidney Markowitz <sidney@sidney.com> ---
From your comments, I see that you installed an old version of Spamassassin
(the current one is 4.0.0, with 4.0.1 to be released soon) and found that the
default configuration did not trigger SORBS rules when you think they should.
You were able to get it to trigger custom rules that you added to your
configuration. That proves that 1) The code in SpamAssassin does properly
handle using SORBS as an RBL; and 2) Your configuration after installing
SpamAssassin had a problem with SORBS, which you could work around by changing
the configuration.
You still have a problem, because even though your configuration seems to work,
it is doing so by running five different queries to SORBS nameservers instead
of just one query to the aggregate server and interpreting the results.
This is exactly the kind of problem that you can get help with on the users
mailing list. If after a discussion there you have an example of a specific
email message that demonstrates a bug in SpamAssassin, you can open a bug
report and attach the email along with the steps by which anyone can reproduce
the bug.
Until then, I am closing this issue again as "invalid". That doesn't mean that
your problem is invalid, only that it is not a valid issue for this forum and
is better taken to the user mailing list for help getting it resolved.
--
You are receiving this mail because:
You are the assignee for the bug.