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/08/16 21:11:51 UTC

[Bug 5601] New: When SA is running, no one can send email

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

           Summary: When SA is running, no one can send email
           Product: Spamassassin
           Version: 3.2.1
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: spamassassin
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: sharmon@valuelinx.net


We have Spamassassin 3.2.1 running on Fedora Core 4 mail server. It has 2 2.8 Gb
Xeon processors and 3 Gb of RAM. We had SA running fine for over a year, and
then one day and ever since, it started causing smtp connections to time out
when sending mail. Turn of spamd and it sends just fine. Looking at the
smtpd\current file and the connections are maxed out. I restart Qmail, and we
can send just fine, but in about 5 seconds the connections are maxed out again,
and noone can send mail. I have tried turning it on with --round-robin, but it
is no help.
Not really sure if it is a bug or if something broke in the configuration.



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

[Bug 5601] When SA is running, no one can send email

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


felicity@apache.org changed:

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




------- Additional Comments From felicity@apache.org  2007-08-16 13:00 -------


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



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