MailScanner users using latest Postfix

[Jason Williams]

-----Original Message-----
From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Glenn
Steen
Sent: Wednesday, November 08, 2006 1:26 AM
To: MailScanner discussion
Subject: Re: MailScanner users using latest Postfix

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":-).
>


Thanks for the help. I can't thank you enough.

Just so I am sure and have everything correct, let me put down what I
have here (still brewing my morning cup of java so bare with me :) ).


Incoming Queue Dir = /var/spool/postfix/hold
Outgoing Queue Dir = /var/spool/postfix/incoming
Incoming Work Dir = /var/spool/postfix/hold
Quarantine Dir = /var/spool/MailScanner/quarantine


Now, I should change Incoming Work Dir to:?

Incoming Work Dir = /var/spool/postfix/incoming


Still get those funny messages in maillog:

Nov  8 10:46:37 gammaflux2 postfix/showq[9478]: warning: incoming/9317:
uid 125: not a regular file
Nov  8 10:46:37 gammaflux2 postfix/showq[9478]: warning: incoming/9352:
uid 125: not a regular file
Nov  8 10:46:37 gammaflux2 postfix/showq[9478]: warning: incoming/9392:
uid 125: not a regular file
Nov  8 10:46:37 gammaflux2 postfix/showq[9478]: warning: incoming/9439:
uid 125: not a regular file
Nov  8 10:46:37 gammaflux2 postfix/showq[9478]: warning: incoming/9473:
uid 125: not a regular file


Doing a quick look at the directory (incoming)

gammaflux2# ls -la /var/spool/postfix/incoming/
total 14
drwx------   7 postfix  wheel  512 Nov  8 10:47 .
drwxr-xr-x  16 root     wheel  512 Nov  7 16:10 ..
drwx------   2 postfix  wheel  512 Nov  8 10:44 9317
drwx------   2 postfix  wheel  512 Nov  8 10:47 9352
drwx------   2 postfix  wheel  512 Nov  8 10:44 9392
drwx------   2 postfix  wheel  512 Nov  8 10:44 9439
drwx------   2 postfix  wheel  512 Nov  8 10:46 9473


Are those directories needed?


Thanks again everyone. Really appreciate your help and patience.

Cheers,

-Jason







-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.