Procmail errors in log

Submitted by ADDISON74 on Wed, 03/09/2016 - 04:31

In my procmail.log file there are every day 3 errors. I am trying the figure out what is going on but without any luck.

Here is the message for today:

procmail: Unable to treat as directory "/var/list/Maildir"
procmail: Error while writing to "/var/list/Maildir"
procmail: Unable to treat as directory "/var/list/Maildir"
procmail: Lock failure on "/var/list/Maildir.lock"
procmail: Error while writing to "/var/list/Maildir"
From list@mydomain.com  Wed Mar  9 08:00:01 2016
Subject: Cron <list@server> [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/
  Folder: **Bounced**                                                       692
Time:1457503258 From:root@mydomain.com To:list@mydomain.com User:list Size:1374 Dest:/var/list/Maildir/ Mode:None
procmail: Unable to treat as directory "/var/list/Maildir"
procmail: Error while writing to "/var/list/Maildir"
procmail: Unable to treat as directory "/var/list/Maildir"
procmail: Lock failure on "/var/list/Maildir.lock"
procmail: Error while writing to "/var/list/Maildir"
From list@mydomain.com  Wed Mar  9 09:00:02 2016
Subject: Cron <list@server> [ -x /usr/lib/mailman/cron/disabled ] && /usr/lib/
  Folder: **Bounced**                                                       692
Time:1457506858 From:root@mydomain.com To:list@mydomain.com User:list Size:1377 Dest:/var/list/Maildir/ Mode:None

1) Mailman it is running but I am not using it with my vhost.

2) There is no /var/list directory in my system

3) Here is /etc/procmailrc file content

LOGFILE=/var/log/procmail.log
TRAP=/etc/webmin/virtual-server/procmail-logger.pl
:0wi
VIRTUALMIN=|/etc/webmin/virtual-server/lookup-domain.pl $LOGNAME
EXITCODE=$?
:0
* ?/usr/bin/test "$EXITCODE" = "73"
/dev/null
EXITCODE=0
:0
* ?/usr/bin/test "$VIRTUALMIN" != ""
{
INCLUDERC=/etc/webmin/virtual-server/procmail/$VIRTUALMIN
}
DEFAULT=$HOME/Maildir/
ORGMAIL=$HOME/Maildir/
DROPPRIVS=yes
:0
$DEFAULT

4) I don't have any errors in mail.log file. For vhost users emails are going/coming as normal.

5) Spamassassin, ClamAV both are running. Postfix too. This system has Virtualmin by default.

I guess this issue is related to system accounts. It needs a fix of paths. Also these are cron information for a list of users?

Status: 
Active

Comments

Submitted by ADDISON74 on Wed, 03/09/2016 - 04:40

Observation: There is a file named list in /var/mail. This file is owned by list and group is mail. The error procmail provides is a wrong communication between root and list. I don't know where to find the setting to route correctly the emails from root to list mailbox.

I will try to disable mailman service to see if tomorrow I will get the same errors in procmail log.

Submitted by andreychek on Wed, 03/09/2016 - 09:57

Ah, that does indeed appear to be related to Mailman.

It looks like it's a Mailman cron job trying to send an email to the "list" user.

Yeah, if you don't need Mailman, we'd recommend disabling that.

Submitted by ADDISON74 on Thu, 03/10/2016 - 07:57

Well mailman service was not running by default, it was disabled. Yesterday I started mailman service and qrunner process too. I don't get any errors in procmail.log with both running today.

In my opinion if someone is disabling Mailman freature in Virtualmin you should not kill qrunner process only. You should leave qrunner running. Mailman service running depends on it and I will check today this scenario, disabling qrunner. If someone doesn't need Mailman he should close both not only mailman because qrunner is still running in background. I will come back with information tomorrow.

How do I get cron jobs for mailman? I tried crontab -u mailman and it says user 'mailman' unknown. Those cron jobs mentioned in my first post are coming from a place.

Submitted by andreychek on Thu, 03/10/2016 - 10:12

Disabling the Virtualmin feature doesn't actually stop the processes from running. It only makes it so that the feature isn't available to the Virtual Servers on your system.

As far as where the cron job is -- Mailman runs as the "list" user, but system services such as that don't typically have cron jobs under their own users.

Instead, you'd want to look in the various cron directories in /etc, such as cron.daily, cron.weekly, cron.monthly, and cron.d.