You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2008/02/19 00:10:26 UTC

[Bug 5832] New: mass-check --server seems to imply --all

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5832

           Summary: mass-check --server seems to imply --all
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Masses
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: spamassassin@dostech.ca


It seems that the mass-check --server is implying --all causing it to send large
(say 1MB) messages to the mass-check --client which won't scan them unless you
specify --all on the client.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5832] mass-check --server seems to imply --all

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5832





------- Additional Comments From spamassassin@dostech.ca  2008-02-18 16:06 -------
This may be a side effect of --cache.  Will look into it later.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5832] mass-check --server seems to imply --all

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5832


spamassassin@dostech.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Undefined                   |3.2.5






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5832] M::SA::AI ignores opt_all in its scan stage (it only applies opt_all in its run stage)

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5832


spamassassin@dostech.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Masses                      |Libraries






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5832] M::SA::AI ignores opt_all in its scan stage (it only applies opt_all in its run stage)

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5832


spamassassin@dostech.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|mass-check --server seems to|M::SA::AI ignores opt_all in
                   |imply --all                 |its scan stage (it only
                   |                            |applies opt_all in its run
                   |                            |stage)




------- Additional Comments From spamassassin@dostech.ca  2008-02-18 21:51 -------
It turns out that M::SA::AI doesn't limit the message size in the scan stage,
but rather the run stage.  So the mass-check --server will include any message
in its targets, regardless of size, and will send the message to its clients who
may or may not scan large messages depending on if they were run with the --all
option or not.

If none of the clients have the --all option and the mass-check --server has a
large message in its targets it'll keep retrying the large message without
success.  Prior to r628992 that I just committed to implement a limit to the
number of retries (--cs_max_retries=N, default 3) the server would retry these
large messages unsuccessfully forever.

r628992 solves the immediate problem of the mass-check --server never finishing,
but I think the message size limit in M::SA::AI should be moved to the scan
stage.  This would also require modifying the scan cache file format to include
the message size.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.