https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6939

--- Comment #78 from Karsten Bräckelmann <[email protected]> ---
> > Both swallow their input on STDIN.
> 
> Without a parameter to GNU cat, yes, it consumes input on stdin. With an
> empty string as a parameter, it bails with EXIT_FAILURE as all programs are
> expected to.

An empty string as a parameter (argument) to an option requiring an argument,
is an entirely valid case. Similar to this heavily perl-ish

  s/ anything Kip says / /x

> > Validating input comes *after* receiving input. Cannot validate while still
> > waiting.
> 
> The socket path is provided and available as input before the stdin stream
> needs to be accessed, therefore your argument is not valid.

Wrong. STDIN needs to be accessed, to decide whether to contact spamd at all.
See comment 38 for the max-size option you outright dismissed before. However,
this is entirely irrelevant.

 * Your recent arguing is about apparently hanging spamc processes, which
   can only happen with stalled STDIN.
 * Your patch does nothing in this regards.

So, is your bug report about idling on STDIN, while other options like a
possibly bad -U socket is not checked?

  Your patch does NOT fix this.

Or is your bug report about spamc not treating a bad -U socket as an error?

  It does.


Maybe there is a language barrier after all, between en_CA and en_DE.

Kip, can you coherently and in a single statement (unlike the squirming in the
previous 70+ comments) explain the issue again, please?

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

Reply via email to