From: Wietse Venema (wietseporcupine.org)
Date: Sat Mar 01 2003 - 17:53:59 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Craig Sanders:
> On Sat, Mar 01, 2003 at 09:15:25AM -0500, Wietse Venema wrote:
> > > e.g. say i have a content filter running as user "filter", and that
> > > content filter runs spamassassin 2.50 (which has bayesian stuff built
> > > in) - do i have to worry about ~filter/.spamassassin/bayes_toks
> > > exceeding mailbox_size_limit?
> >
> > File size limits are inherited from parent process to child process.
> > What is the parent process of your content filter?
>
> master.
>
> i have the following in master.cf
>
> smtp inet n - n - - smtpd -o content_filter=bogofilter:
>
>
> bogofilter unix - n n - - pipe
> user=filter argv=/home/filter/bf.sh ${sender} ${recipient}

In that case, the file size limit is that of the master's parent
process (ultimately, inherited from /sbin/init). Master resets the
file size limit only when it can't make sense of the the inherited
value. In that case it sets the limit to the generous value of
MAX_INT, which is 2GB on 32-bit systems.

There's another limit you may want to be aware of. As of Postfix
2.0.4 the command time limit is enforced like it used to be many,
many, years ago. Mail that takes too much time is returned as
undeliverable (but the bounce is not run through the content
scanner).

        Wietse

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]