https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518
Bill Cole <sa-bugz-20080...@billmail.scconsult.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa-bugz-20080315@billmail.s
| |cconsult.com
--- Comment #14 from Bill Cole <sa-bugz-20080...@billmail.scconsult.com> ---
(In reply to Kevin A. McGrail from comment #12)
> I would recommend looking at other ways to call spamc from postfix. Your
> way seems odd. Why does it need to know the sender and all the recipient
> emails again, for example?
This is (unfortunately) a method documented on the SpamAssassin Wiki:
https://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix
> It's like instead of using a filter you are resending the email.
This is a documented and supported Postfix mechanism for after-queue filtering.
Messages being delivered locally are piped into the "content_filter" command
which typically also gets a trailing set of arguments like '-G -oi -f ${sender}
${recipient}' which are then handed off to sendmail for local re-injection &
delivery.
Since the spamc '-e' option is documented as accepting an unspecified plural
number of arguments to pass to the output command which is in fact limited by
an undocumented variable in an Autoconf input file, this seems like a
documentation bug, a misleading error message (since you cannot change
COMBO_ARGV_SIZE without reconfiguring the source and rebuilding,) and maybe an
ill-considered design choice.
The most obvious "fix" would be to note the COMBO_ARGV_SIZE limit in the spamc
man page and on the aforementioned Wiki page.
--
You are receiving this mail because:
You are the assignee for the bug.
