procmail.log

10 posts / 0 new
Last post
#1 Wed, 08/02/2006 - 04:51
GrahamWatts

procmail.log

Hi Joe,

After my procmail-wrapper problem I'm now getting the following message in maillog : procmail[[19162]]: Error while writing to "/var/log/procmail.log"

The permissions on procmail.log are rw for the owner 'root' and group 'mem'.

Are these correct? I've just tried setting the file to world writable and indeed it does get updated but with the following error...

Failed to run /virtual-server/lookup-domain.pl : No such file or directory at /etc/webmin/virtual-server/lookup-domain.pl line 10. procmail: Error while writing to "/etc/webmin/virtual-server/lookup-domain.pl" procmail: Assigning "VIRTUALMIN=" procmail: Executing "/usr/bin/test,,!=," procmail: Non-zero exitcode (1) from "/usr/bin/test" procmail: No match on "/usr/bin/test != "

Is this caused by my unintentionally unistalling virtualmin-base as in the earlier procmail-wrapper thread? Can I force a re install of it?

Regards,

Graham

Thu, 08/03/2006 - 00:39
Joe
Joe's picture

Hey Graham,

<i>Is this caused by my unintentionally unistalling virtualmin-base as in the earlier procmail-wrapper thread?</i>

Probably not, since you've replaced it. Though we probably do want to get an up to date procmail-wrapper installed. I'm not actually sure what to make of the error you're getting...

<i>Can I force a re install of it?</i>

Please don't! (At least not without proper caution.)

It is only safe to install this package on a system that has no modifications at all (i.e. it may not blow up your system, but it'll probably cause some trouble that may sneak up on our when you least expect it), or if you use the --nopost option to RPM. So, don't install it using yum, but you can safely install it using &quot;rpm -i --nopost virtualmin-base-blah.blah.blah.rpm&quot; (obviously, you need to download the package first--use the serial number and license key as the username and password to download it, and you'll find the software repos on http://software.virtualmin.com/).

I'll try to get a procmail-wrapper package rolled up shortly, so you can install it safely and separately from the virtualmin-base package.

--

Check out the forum guidelines!

Thu, 08/03/2006 - 15:39
GrahamWatts

Hi Joe,

Thanks for your reply. I'm busy doing paying work at the moment so I'll leave the server alone as it's working (apart from procmail not calling clamav or spamassain). To save you wrapping up procmail-wrapper could I just ftp the binary from you? I'm running fc4 on a x86 based server.

Cheers,

Graham

Thu, 08/03/2006 - 15:53
Joe
Joe's picture

Hey Graham,

I've added a package for procmail-wrapper to the repository, so you can install it easily, without having to worry about issues with virtualmin-base running its post script again.

Just run:

yum install procmail-wrapper

Let us know if anything changes with the new binary. I'm not convinced we'll see any difference...I suspect something else is going wrong...but it's worth ruling it out.

--

Check out the forum guidelines!

Thu, 08/03/2006 - 16:18
GrahamWatts

Hi Joe,

Sorry to be a pain. Tried that but got...

[[root@ww3 ~]]# yum install procmail-wrapper
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
No Match for argument: procmail-wrapper
Nothing to do

I did run yum update procmail-wrapper in error first.

Cheers,

Graham

Thu, 08/03/2006 - 23:37
Joe
Joe's picture

Hey Graham,

I'm sure it's my fault. ;-)

Is this an x86_64 box, perchance? If so, try it again...I didn't add it for x86_64 to start with. Fixed now.

If not, try doing a &quot;yum clean all&quot; first...sometimes yum is a bit aggressive in its use of locally cached data.

--

Check out the forum guidelines!

Fri, 08/04/2006 - 05:28
GrahamWatts

Hi Joe,

That fixed it :). Permission are back to normal now on procmail.log and it all works. It did need the x86_64 version. I know I have a 64 bit box but I thought I had asked for the 32 bit version of fc4 to be installed as I didn't want to keep running into issues. I'm sure I installed an early virtualmin before you had made the _64 versions.
Ho hum.

I see evidence of spamassain in the headers of my emails. Should I see anything from clamav saying it has been scanned?

One last question off topic. Is there somewhere in virtuamin where I can set up re directing root emails to my normal email address?

Regards,

Graham

Tue, 04/24/2007 - 20:34
MarkThomas

If you see my ID all over your logs, it was me attempting to locate the software you had talked about in this thread.

I seem to be having the same type of difficulties with my procmail log file that Graham had mentioned.

Apr 23 23:47:22 ns1 procmail[[5552]]: Error while writing to &quot;/var/log/procmail.log&quot;
Apr 23 23:47:22 ns1 postfix/local[[5534]]: C198E2B8043:

When I look at the permissions on this file, owner 'root' has read and write, group 'root' has none, and the world has none.

Tue, 04/24/2007 - 22:15 (Reply to #8)
Joe
Joe's picture

Hey Mark,

<i>If you see my ID all over your logs, it was me attempting to locate the software you had talked about in this thread.</i>

Which software? It's impossible (or pretty close, anyway) to end up not having procmail-wrapper on a Virtualmin Professional system today. The bit you're probably missing is actually calling it--not the software itself.

Check your MTA configuration (Postfix, probably, which lives in /etc/postfix/main.cf) to be sure the mailbox_command directive is actually set to procmail-wrapper instead of procmail.

If that's true, then we'll need to go from there. But I'm really pretty certain your problem is not related to the one reported at the top of this thread--it was a pretty specific set of circumstances that led up to that (removing virtualmin-base, which took procmail-wrapper along with it...which would not result in this event today, because virtualmin-base and procmail-wrapper are wholly independent).

--

Check out the forum guidelines!

Wed, 04/25/2007 - 06:35 (Reply to #9)
MarkThomas

Hey Joe,

I was looking for the procmail-wrapper you were speaking of in message 2 of this thread. I assumed that it had already been incorporated into Virtualmin, but I just had to look ... just in case.

In main.cf, I see mailbox_command = /etc/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME
It appears to be set as required.

I appear to be able to send mail just fine. I just keep getting this pesky little message when I do it. If you have other more important things on your plate, this does not have to be a high-priority thing.

- Mark

Topic locked