[Bug 3556] New: spamc shuts down socket too early, ISA server

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3556

           Summary: spamc shuts down socket too early, ISA server
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: jbrunette@excel.net


spamc clients are on public network, spamd is on private network behind an ISA 
server.  This part of libspamc.c (line 912):

    /* Send to spamd */
    if (flags & SPAMC_USE_SSL) {
#ifdef SPAMC_SSL
        SSL_write(ssl, buf, len);
        SSL_write(ssl, m->msg, m->msg_len);
#endif
    }
    else {
        full_write(sock, 0, buf, len);
        full_write(sock, 0, m->msg, m->msg_len);
        shutdown(sock, SHUT_WR);
    }

...gives our ISA server grief because the shutdown() call typically causes the 
FIN packet received by the spamd server to be ACK'd prior to spamd replying with 
the modified message.  The ISA server thinks the connection is now closed and, 
when spamd attempts to send the modified message, returns RST to spamd and the 
packet is never received by the spamc client.

Is there a reason why spamc closes the socket in this fashion so early?  
Commenting out that shutdown() call allows spamc/spamd communication to work 
while having no obvious negative side effects.



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