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 2007/06/06 13:40:31 UTC

[Bug 5499] New: can't change spamc max-size

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

           Summary: can't change spamc max-size
           Product: Spamassassin
           Version: 3.2.0
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: frank.urban@commerzbank.com


Does Bug 4616 come back? 

mail1:/etc/mail/spamassassin # spamc -V
SpamAssassin Client version 3.2.0

mail1:/etc/mail/spamassassin # mv spamc.conf.old spamc.conf
mail1:/etc/mail/spamassassin # spamc -V
^c

The spamc.conf file is empty. I tried to turn the --max-size down to 350k again,
but that doesnt work. Now I found this old Bug 4616.
When I call "spamc --max-size=350000 < mail" I work well as lon no spamc.conf
file exists.



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

[Bug 5499] can't change spamc max-size

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


sidney@sidney.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE




------- Additional Comments From sidney@sidney.com  2007-06-06 05:23 -------
Argghh... Yes, that's exactly right. The comments in bug 4616 talk about the
need to check the fix into trunk but it never was.

I'm going to reopen bug 4616, close this one as a duplicate of it, and document
the checkin of the fix there.

Thank you!


*** This bug has been marked as a duplicate of 4616 ***



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