Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Sun May 3 16:35:16 UTC 2015

Hm – that’s configured ..

Incoming Queue Dir = /var/spool/postfix/hold
Outgoing Queue Dir = /var/spool/postfix/incoming
Incoming Work Dir = /var/spool/MailScanner/incoming
Quarantine Dir = /var/spool/MailScanner/quarantine
SpamAssassin User State Dir = /var/spool/MailScanner/spamassassin

Processing Attempts Database = /var/spool/MailScanner/incoming/Processing.db
SpamAssassin Cache Database File = /var/spool/MailScanner/incoming/SpamAssassin.cache.db

SpamAssassin Temporary Dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp
SpamAssassin User State Dir = /var/spool/MailScanner/spamassassin

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 12:21 PM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Are you using the hold directory as a work directory? If so, this would be causing the problem.

Incoming Queue Dir = /var/spool/postfix/hold
Incoming Work Dir = /var/spool/MailScanner/incoming
Outgoing Queue Dir = /var/spool/postfix/incoming
Processing Attempts Database = /var/spool/MailScanner/incoming/Processing.db
Quarantine Dir = /var/spool/MailScanner/quarantine
SpamAssassin Cache Database File = /var/spool/MailScanner/incoming/SpamAssassin.cache.db
SpamAssassin Temporary Dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp
SpamAssassin User State Dir = /var/spool/MailScanner/spamassassin

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com>

On May 3, 2015, at 12:03 PM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

The package are from EPL

SPF outside MailScanner seems to work too

May  3 11:47:34 demo3 policyd-spf[6461]: spfcheck: pyspf result: "['Pass', 'sender SPF authorized', 'mailfrom']"
May  3 11:47:34 demo3 policyd-spf[6461]: Pass; identity=mailfrom; client-ip=209.85.223.169; helo=mail-ie0-f169.google.com<http://mail-ie0-f169.google.com/>;

But directories still back

[root at demo3 hold]# date
Sun May  3 11:57:41 EDT 2015
[root at demo3 hold]# ls
32669  32693

May  3 11:58:20 demo3 postfix/showq[10306]: warning: hold/32693: uid 89: not a regular file
May  3 11:58:20 demo3 postfix/showq[10306]: warning: hold/32669: uid 89: not a regular file

-->hold/32693: uid 89: not a regular file

I appreciate your help

Thank you.

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 11:11 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

The TNEF package you are using should be fine. That is the one the MailScanner install script installed. (Either from the repo or from the one hosted by MailScanner.)

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 3, 2015, at 11:07 AM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Thank you.

Policyd – should be only used for quota  spf and greylisting is disabled -- hm
SQL Grey  should be used for it ..

check_policy_service inet:127.0.0.1:2501, check_policy_service unix:private/policyd-spf

just some historic  stuff ESVA did years ago …

so what package you suggest for tnef ?

[root at demo3 ~]# rpm -qa | grep -i tnef
perl-Convert-TNEF-0.17-10.el6.noarch
tnef-1.4.12-1.x86_64

to prevent others running into this ..

thank you.

Mike

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 10:49 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Regarding the error you were seeing:

After I restarted postfix and mailscanner, the directories disappeared from the hold directory and the notices went away. The error you were seeing is typically related to tnef. You have the latest version of the internal decoder with MailScanner, but the binary you are using should also work correctly. I can’t reproduce the error now.

I logged in and checked your server and sent a couple of test emails. None of these items are related to your problem but I thought I would point them out:

- Your policyd seems broken. Pretty sure the mailborder.com<http://mailborder.com/> SPF records are correct but your system failed them.
- Policyd also failed gmail.com<http://gmail.com/> on SPF. Pretty sure their stuff is correct as well.
- Just my opinion, but you should consider just using the Spamassassin module for SPF checks and adjust the spam score for failing records. You can also create custom chains based on scores, etc.
- Not sure how you installed Postgrey, but there are no configuration files that I could find. You should have a whitelist somewhere.

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 3, 2015, at 10:14 AM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Ok

ssh mail.sentinelbox.net<http://mail.sentinelbox.net/>

root: MailBorder

thx

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 9:44 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Email me the credentials and I will take a look if you like.

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 3, 2015, at 9:41 AM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Hm

Still the same …

[root at demo3 ~]# sed -i "s/pickup    unix/pickup    fifo/g" /etc/postfix/master.cf
[root at demo3 ~]# sed -i "s/qmgr      unix/qmgr      fifo/g" /etc/postfix/master.cf

pickup    fifo  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr

--
May  3 09:33:24 demo3 MailScanner[32417]: Using locktype = flock
May  3 09:33:31 demo3 MailScanner[32451]: Using locktype = flock
May  3 09:36:51 demo3 postfix/showq[663]: warning: hold/32451: uid 89: not a regular file
May  3 09:36:51 demo3 postfix/showq[663]: warning: hold/32417: uid 89: not a regular file

For me it looks like mailq can not handle both directories created by  MailScanner in postfix  hold ->32451 and 32417 --> MailScanner[32417]: Using locktype = flock

[root at demo3 hold]# ls -l
total 8
drwxr-xr-x 2 postfix mtagroup 4096 May  3 09:33 32417
drwxr-xr-x 2 postfix mtagroup 4096 May  3 09:33 32451

May I am wrong ?

Thank you!

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 9:20 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Also:

# fix for postfix
# fix postfix unix -> fifo

sed -i "s/pickup    unix/pickup    fifo/g" /etc/postfix/master.cf
sed -i "s/qmgr      unix/qmgr      fifo/g" /etc/postfix/master.cf

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 3, 2015, at 9:00 AM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Quarantine Permissions = 0660

[root at demo3 postfix]# pwd
/var/spool/postfix
[root at demo3 postfix]# ls -la
total 72
drwxr-xr-x. 18 postfix mtagroup 4096 Apr 29 11:12 .
drwxr-xr-x. 13 root    root     4096 Apr 29 11:11 ..
drwx------.  2 postfix root     4096 May  3 08:36 active
drwx------.  2 postfix root     4096 May  3 03:40 bounce
drwx------.  2 postfix root     4096 Feb 20  2014 corrupt
drwx------.  2 postfix root     4096 Feb 20  2014 defer
drwx------.  2 postfix root     4096 Feb 20  2014 deferred
drwx------.  2 postfix root     4096 Feb 20  2014 flush
drwxrwxr-x.  2 postfix mtagroup 4096 May  3 08:40 hold
drwxr-x---.  2 postfix mtagroup 4096 May  3 08:36 incoming
drwx-wx---.  2 postfix postdrop 4096 May  3 08:35 maildrop

[root at demo3 spool]# pwd
/var/spool
[root at demo3 spool]# ls -l
total 44
drwxr-xr-x.  2 root      root      4096 Apr  6 10:17 anacron
drwx------.  2 root      root      4096 Nov 23  2013 cron
drwxr-xr-x.  2 root      root      4096 Sep 23  2011 lpd
drwxrwxr-x.  2 root      mail      4096 Apr 29 11:13 mail
drwxr-xr-x.  5 postfix   mtagroup  4096 Apr 29 11:08 MailScanner
drwx------.  2 root      mail      4096 Nov 11  2010 mqueue
drwx------.  2 root      root      4096 Apr 13 10:27 mqueue.in
drwxr-xr-x.  2 root      root      4096 Apr 30 12:31 plymouth
drwxr-xr-x. 18 postfix   mtagroup  4096 Apr 29 11:12 postfix

-->
[root at demo3 hold]# pwd
/var/spool/postfix/hold

It looks like that MailScanner creates both files in the hold queue<http://dict.leo.org/ende/index_en.html#/search=queue&searchLoc=0&resultOrder=basic&multiwordShowSingle=on> each per child after stopping both are disappeared by stopping the MailScanner Service

May  3 08:46:46 demo3 MailScanner[21903]: Using locktype = flock
May  3 08:46:50 demo3 MailScanner[21919]: Using locktype = flock

[root at demo3 hold]# ls -l
total 8
drwxr-xr-x 2 postfix mtagroup 4096 May  3 08:46 21903
drwxr-xr-x 2 postfix mtagroup 4096 May  3 08:46 21919

[root at demo3 ~]# date
Sun May  3 08:52:36 EDT 2015
[root at demo3 ~]# service MailScanner stop
ConfigSQL QuickPeek for mta found postfix
ConfigSQL QuickPeek for incomingworkdir found /var/spool/MailScanner/incoming
ConfigSQL QuickPeek for incomingqueuedir found /var/spool/postfix/hold
ConfigSQL QuickPeek for quarantinedir found /var/spool/MailScanner/quarantine
ConfigSQL QuickPeek for runasuser found postfix
Shutting down MailScanner daemons:
         MailScanner:                                      [  OK  ]
         incoming postfix:                                 [  OK  ]
         outgoing postfix:                                 [  OK  ]
[root at demo3 ~]#

[root at demo3 hold]# date
Sun May  3 08:52:55 EDT 2015
[root at demo3 hold]# ls -l
total 0
[root at demo3 hold]#

-->
[root at demo3 ~]# date
Sun May  3 08:54:00 EDT 2015
[root at demo3 ~]# service MailScanner start
ConfigSQL QuickPeek for mta found postfix
ConfigSQL QuickPeek for incomingworkdir found /var/spool/MailScanner/incoming
ConfigSQL QuickPeek for incomingqueuedir found /var/spool/postfix/hold
ConfigSQL QuickPeek for quarantinedir found /var/spool/MailScanner/quarantine
ConfigSQL QuickPeek for runasuser found postfix
Starting MailScanner daemons:
         incoming postfix:                                 [  OK  ]
         outgoing postfix:                                 [  OK  ]
         MailScanner:                                      [  OK  ]
[root at demo3 ~]#

[root at demo3 hold]# date
Sun May  3 08:54:27 EDT 2015
[root at demo3 hold]# ls -l
total 8
drwxr-xr-x 2 postfix mtagroup 4096 May  3 08:54 23962
drwxr-xr-x 2 postfix mtagroup 4096 May  3 08:54 23983

May  3 08:54:24 demo3 MailScanner[23962]: Using locktype = flock
May  3 08:54:24 demo3 MailScanner[23983]: Using locktype = flock

Never seen that before … is this supposed to do to create an separate folder each per child in hold?

Thank you.

Mike

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 8:37 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Your permissions in MailScanner.conf should also be 0660. You may also have to manually remove the offending file or directory that is hanging up MailScanner.

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 3, 2015, at 8:31 AM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Hi Jerry,

I did this but same issue with the postfix user id.

[root at demo3 incoming]# rm Processing.db
rm: remove regular empty file `Processing.db'? y
[root at demo3 incoming]# cd ..
[root at demo3 MailScanner]# chmod g+w /var/spool/MailScanner/*
[root at demo3 MailScanner]# chmod 0775 /var/spool/postfix/hold
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/MailScanner
chown postfix:mtagroup /var/spool/MailScanner/incoming
chown postfix:mtagroup /var/spool/MailScanner/quarantine
chown postfix.mtagroup /var/spool/MailScanner/spamassassin
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/MailScanner/incoming
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/MailScanner/quarantine
chown postfix:mtagroup /var/spool/postfix
[root at demo3 MailScanner]# chown postfix.mtagroup /var/spool/MailScanner/spamassassin
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/postfix
chown postfix:mtagroup /var/spool/postfix/incoming
chown postfix:mtagroup /var/spool/postfix/hold
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/postfix/incoming
[root at demo3 MailScanner]# chown postfix:mtagroup /var/spool/postfix/hold
[root at demo3 MailScanner]# service MailScanner start

May  3 07:49:09 demo3 MailScanner[9648]: Config: calling custom init function MailWatchLogging
May  3 07:49:09 demo3 MailScanner[9648]: Started SQL Logging child
May  3 07:49:09 demo3 MailScanner[9648]: Config: calling custom init function SQLWhitelist
May  3 07:49:09 demo3 MailScanner[9648]: Starting up SQL Whitelist
May  3 07:49:09 demo3 MailScanner[9648]: Read 0 whitelist entries
May  3 07:49:10 demo3 MailScanner[9648]: Using SpamAssassin results cache
May  3 07:49:10 demo3 MailScanner[9648]: Connected to SpamAssassin cache database
May  3 07:49:10 demo3 MailScanner[9648]: Enabling SpamAssassin auto-whitelist functionality...
May  3 07:49:20 demo3 MailScanner[9648]: Using locktype = flock
May  3 07:49:20 demo3 MailScanner[9628]: Using locktype = flock

[root at demo3 hold]# ls -l
total 8
drwxr-xr-x 2 postfix mtagroup 4096 May  3 07:49 9628
drwxr-xr-x 2 postfix mtagroup 4096 May  3 07:49 9648
[root at demo3 hold]#

May  3 08:15:12 demo3 postfix/showq[15437]: warning: hold/9648: uid 89: not a regular file
May  3 08:15:12 demo3 postfix/showq[15437]: warning: hold/9628: uid 89: not a regular file

id postfix
uid=89(postfix) gid=89(postfix) groups=89(postfix),12(mail),503(mtagroup)

mtagroup:x:503:apache,postfix,clam

MailScanner.conf
Run As User = postfix,
Run As Group = mtagroup
Incoming Queue Dir = /var/spool/postfix/hold
Outgoing Queue Dir = /var/spool/postfix/incoming
Quarantine Dir = /var/spool/MailScanner/quarantine
MTA = postfix

Thank you.
Mike

From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Sunday, May 03, 2015 4:19 AM
To: MailScanner Discussion
Subject: Re: Testing V 4.85.2 postfix/showq[31416]: warning: hold/3519: uid 89: not a regular file

Probably permissions. Fix them on those directories and then remove your Processing.db file from /var/spool/MailScanner. (Make sure you stop MailScanner first.)

chmod g+w /var/spool/MailScanner/*
chmod 0775 /var/spool/postfix/hold

I would suggest creating a group that has clamav and postfix as members and use that in your MailScanner settings. This prevents a lot of permissions issues. I use a group called mtagroup.

groupadd mtagroup
usermod -a -G mtagroup postfix
usermod -a -G mtagroup clamav
usermod -a -G mtagroup clam

(either clam or clamav depending on your distro and clam version)

chown postfix:mtagroup /var/spool/MailScanner
chown postfix:mtagroup /var/spool/MailScanner/incoming
chown postfix:mtagroup /var/spool/MailScanner/quarantine
chown postfix.mtagroup /var/spool/MailScanner/spamassassin
chown postfix:mtagroup /var/spool/postfix
chown postfix:mtagroup /var/spool/postfix/incoming
chown postfix:mtagroup /var/spool/postfix/hold

Start MailScanner running again.

-
Jerry Benton
www.mailborder.com<http://www.mailborder.com/>

On May 2, 2015, at 11:56 PM, michael pap <mike at sentinelbox.net<mailto:mike at sentinelbox.net>> wrote:

Did I something wrong ?

I am running 2 childs

[root at demo3 hold]# ls
3484  3519

By running the mailq command I get those errors?

[root at demo3 ~]# date
Sat May  2 23:44:19 EDT 2015
[root at demo3 ~]# mailq
Mail queue is empty
[root at demo3 ~]#

May  2 23:44:27 demo3 postfix/showq[32579]: warning: hold/3519: uid 89: not a regular file
May  2 23:44:27 demo3 postfix/showq[32579]: warning: hold/3484: uid 89: not a regular file

An postfix reload removes both files and then I get the next error …

[root at demo3 ~]# service postfix reload
Reloading postfix:                                         [  OK  ]
[root at demo3 ~]# ls /var/spool/postfix/hold/
[root at demo3 ~]#

May  2 23:48:53 demo3 MailScanner[3484]: Could not open file >/var/spool/postfix
/hold/3484/BF276E1B67.A91BF.header: No such file or directory
May  2 23:48:53 demo3 MailScanner[3484]: Cannot create + lock headers file /var/                              spool/postfix/hold/3484/BF276E1B67.A91BF.header,
May  2 23:48:56 demo3 MailScanner[3519]: Could not open file >/var/spool/postfix
/hold/3519/BF276E1B67.A91BF.header: No such file or directory
May  2 23:48:56 demo3 MailScanner[3519]: Cannot create + lock headers file /var/                                  spool/postfix/hold/3519/BF276E1B67.A91BF.header,

Sat May  2 23:51:33 EDT 2015
[root at demo3 ~]# ls /var/spool/postfix/hold/
1036  1093

Did somebody get the same result – or my configuration is wrong may there is a way to suppress the showq warnings?

Thank you,
mike

--
This email has been scanned by the EMFABox eMail service.