https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6939
--- Comment #39 from Kip <[email protected]> --- (In reply to Karsten Bräckelmann from comment #38) > Spamc *could* check for a valid socket or listening process on the TCP port, > before processing STDIN at all. Yes, that's what the patch solves in the case of a UNIX socket. > That it does not is pretty much desired and documented behavior. Desired? Speak for yourself. > Spamc will not pass the message to spamd, if it exceeds a max-size > threshold. To know the message's size, spamc needs to process STDIN. See man > spamc: That has nothing to do with the substance of my comment. I'm not concerned with the max-size. > $ echo -n | spamc -U ""; echo $? > 74 Great, now model the problem accurately by repeating the same test again, but without piping the newline into it. > Please feel free to move the more general discussion parts to the dev list. I'm afraid you don't seem to understand how an issue tracker works. Sometimes people disagree with one another, and we don't restort to stasis of place out of desperation when it is convenient. -- You are receiving this mail because: You are the assignee for the bug.
