Re: Snapshot 20091109, queue disk partition sizing
Stefan F?rster: If I understood the release notes correctly, with smtpd_proxy_options = speed_adjust, each smtpd process will keep the message it's currently receiving in a temporary file. That seems to imply that there could be (number of smtpd processes) * message_size_limit bytes of queue space allocated in temporary files. I _think_ that this is not different from a setup without a content filter which would mean I don't have to increase the disk partition keeping the queue - is that assumption correct? By default, the Postfix requires 1.5*message_size_limit of free space before it accepts mail. Right now, the before-proxy scratch files are put in the incoming queue, but that may still chnage. I didn't change the formula (to 2.5*message_size_limit) for that reason. Wietse
Re: Snapshot 20091109, queue disk partition sizing
* Wietse Venema wie...@porcupine.org: Stefan Förster: (number of smtpd processes) * message_size_limit bytes of queue space allocated in temporary files. By default, the Postfix requires 1.5*message_size_limit of free space before it accepts mail. Right now, the before-proxy scratch files are put in the incoming queue, but that may still chnage. I didn't change the formula (to 2.5*message_size_limit) for that reason. Thank you for that clarification. Now, about logging - I'd be really grateful if the existing logging functionality could be extended in a way so that the pre-queue content filter's response is logged. I know that it is actually the content filter's job to log what it did during an ESMTP transaction, but I think if Postfix logged the filter's response, correlating logs would be much easier. Stefan
