MailScanner users using latest Postfix

[Glenn Steen]

On 08/11/06, Jason Williams <jwilliams at courtesymortgage.com> wrote:
>
>
>  > Don't think so from the top of my head. There are a few extras that you
> can play with in your own time (Like milter support in PF) but providing you
> have set your queue depths correctly You   will  > know if you haven't, it
> won't work!) both sides of MailScanner nothing much else has changed really.
>
>
> Drew
> --------
>
> Thanks. I appreciate.
> Well, it is accepting and delivering mail, so that is a good thing.
>
> Looks like I need to go through a just comb through the config file again
> and set all my settings as needed.
> I was not planning on this today, so I apologize for sounding and being very
> rushed.
> If I can ask a quick question. Is this correct, for settings in
> MailScanner.conf?
>
> Should:
> Incoming Work Dir = /var/spool/MailScanner/incoming
>
>
> Thar right?


Jason, from am earlier mail by you, I couldn't help noticing that you
had set the Incoming Work Dir to the postfiox hold queue directory...
This is, simply put, wrong.

Set it to something like /var/spool/MailScanner/incoming ... This is
the directory where the MailScanner children "plays" all by their
lonesome selves... There will be a subdirectory/process ID (with the
PID as name). These subdirectories could potentially confuise the hell
out of things, if placed in an active postfix queue. As it is now,
when set to the hold queue, the only postfix commands that are
affected are postqueue -p (mailq for short:-) and postsuper, and
probably rather mildly.

Simply stop MailScanner, adjust MailScanner.conf and fire it up again.

So the quick answer is "yes":-).

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se