https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518
Dirk <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |REOPENED --- Comment #6 from Dirk <[email protected]> --- (In reply to Benny Pedersen from comment #4) > http://postfix.1071664.n5.nabble.com/Split-multiple-recipient-mail-td48458. > html > > its multirecipient limit > > <transport>_destination_recipient = 1 > > mta stage is no limit, but content filter transport should hae this in > main.cf > > sorry for write after its declared invalid :=) A last post to maybe help understanding why this is truely a bug in spamc: First of all, i am not only an administrator, i am a programner too! I know what i am talking about and i hate quick answers "your are stupid, shut up and go home" without further reading and just trying to understand if the user could be right! I can fix the code by myself, but i am not responsible! So please read the text below, think about it and than do what ever you want. After analysing the error in detail (the args-exceeded comes from spamc) the problem relies in the argument-parser of spamc. The switch "-e" has only ONE argument up to EOL (as stated in the code and manpage). The code of SPAMC counts ALL arguments until EOL, so all arguments passed to sendmail (in my example) will increase the arg-counter in spamc. This results in an ARGC-overflow with emails with more than 16 recipients (spamc counts "-s VALUE" in the configfile and "-e", "SENDMAIL", "-oi", "-t", "SENDER" and "ALL recipients"! This results in 25 counted arguments with 17 recipients which causes spamc to abort! Reducing the number of arguments by multiplying the email within the MTA is definitly just a workaround! This leads into scanning the same email more than once, leading to a much higher load for the server. If you further think this is not a bug, you should mention this in the manpage, because the text Note that this must be the LAST command line option, as everything after the -e is taken as arguments to the command (it's like rxvt or xterm)." says that "-e" has only ONE argument. Regards Dirk -- You are receiving this mail because: You are the assignee for the bug.
