On Mon, Dec 27, 2004 at 10:10:22PM +1100, Adam Bogacki wrote:
Aha, something seems to be working ...
Looking at /home/adam/Mail I find I have two files
similarly named - 'procmaillog' and '.procmaillog'
which I have almost certainly been confusing.
Yes, thanks to Ruud for first proposing that confusion.
It was confirmed by the output you ran for me in diag.rc .
.. but the last entry in '.procmaillog' is Sun Dec 26 22:09:35 2004
with the previous being Sat Dec 11 14:57:39 2004
and then backwards on an almost daily basis which corresponds
with my usage pattern.
However, I'm stumped why it tells me there are no matches for
BRW, AFR, OECD .. etc., as I have been receiving these.
It's only telling you that that particular last message you logged
was not matching on those.
From root(_at_)paradise(_dot_)net(_dot_)nz Sat Dec 11 14:57:39 2004
Subject: Anacron job 'cron.daily' on Tux
Folder: backup
procmail: Executing "cd backup && rm -f dummy 'ls -t msg.* | sed -e 1,200d'"
/bin/bash: line 0: cd: backup: Not a directory
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This you've now fixed, you say. Good.
............<snip>............
procmail: No match on "^Subject:.*SEEK Job Mail"
procmail: No match on "^X-Mailing-List:
.*debian-\/[^]*(_at_)lists(_dot_)debian(_dot_)org"
procmail: Extraneous locallockfile ignored
procmail: No match on
"(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)debian-user-digest"
procmail: No match on
"(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)slug"
procmail: No match on
"(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)wellylug"
procmail: No match on "^Subject:.*Nature"
procmail: No match on "^From:.*BRW"
procmail: No match on "^From:.*AFR"
procmail: No match on "^From:.*OECD"
procmail: No match on "^Subject:.*SCOOP"
procmail: No match on "^From:.*CommonwealthFund"
procmail: No match on "^From:.*ABC Science"
procmail: No match on "^From:.*ABC Health"
procmail: No match on "^From:.*Medscape Psychiatry"
procmail: No match on "^From:.*science-mailer"
procmail: No match on "^From:.*mutt-users-digest"
Yes, it wouldn't match any of those. The message being logged in this extract
is the one from your cron-job!
From: Anacron <root(_at_)paradise(_dot_)net(_dot_)nz>
To: root(_at_)paradise(_dot_)net(_dot_)nz
Subject: Anacron job 'cron.daily' on Tux
You would not expect that message to match on any of the above regexes.
Are you confused about how the logs work? They are a linear, serial record
of each message that comes in. They are not some sort of summary report.
And when you look for problems, you need to *read* them linearly to see
what procmail did on each line. I suspect this bit of knowledge has been
missing for you.
procmail: Assigning "LOGFILE=/home/adam/procmail.log"
procmail: Opening "/home/adam/procmail.log"
So inside your $HOME/.procmailrc you reassign the $LOGFILE, or try to, to
the undotted file. Only nothing gets written there, because adam doesn't have
write permissions on that file, most likely because root created that file and
didn't give adam sufficient perms. This is also what the diagnostics rcfile
you ran told us.
procmail: Locking "msgid.lock"
procmail: Executing "-D,8192,.msgid.cache"
/bin/sh: 8192: No such file or directory
procmail: Non-zero exitcode (127) from "-D"
procmail: Assigning "LASTFOLDER=-D 8192 .msgid.cache"
procmail: Unlocking "msgid.lock"
procmail: Executing "-D,8192,.msgid.cache"
/bin/sh: 8192: No such file or directory
procmail: Non-zero exitcode (127) from "-D"
procmail: Assigning "LASTFOLDER=-D 8192 .msgid.cache"
procmail: Unlocking "msgid.lock"
This is probably symptomatic of the same sort of problem. Perhaps root
owns the dir and adam has no permission to create a file here?
If this dir is under adam's $HOME, you should chown it to adam.
procmail: No match on "^From:.*ABC Science"
procmail: No match on "^From:.*ABC Health"
procmail: No match on "^From:.*Medscape Psychiatry"
procmail: No match on "^From:.*science-mailer"
procmail: No match on "^From:.*mutt-users-digest"
procmail: Assigning "save_LOGFILE=/home/adam/Mail/.procmaillog"
procmail: Executing "env > /dev/tty"
procmail: Assigning "DUMMY="
procmail: Assigning "HOST=byebye"
procmail: HOST mismatched "Tux"
Well, that was the log output from the diag.rc of mine you ran.
Again, we wouldn't match on any of those other regexes, because
the mail procmail reacted to here did not have them in it. (In
fact, the "mail" was /dev/null!)
From foo(_at_)bar Sun Dec 26 22:09:35 2004
Folder: cd backup && rm -f dummy 'ls -t msg.* | sed -e 1,200d' 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. also of interest may be the last part of the file 'backup':
[I have now renamed backup as 'backup#2' and created *directory* 'backup'
- something I thought I had already done ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From root(_at_)paradise(_dot_)net(_dot_)nz Sat Dec 11 14:57:39 2004
Return-path: <root(_at_)paradise(_dot_)net(_dot_)nz>
How can you have a log entry from the 26th interspersed and showing up
earlier than a log entry from the 11th?
/etc/cron.daily/logrotate:
error: error accessing /var/log/freeb: No such file or directory
error: freeb:1 glob failed for /var/log/freeb/*.log
run-parts: /etc/cron.daily/logrotate exited with return code 1
These are more of a similar kind of permissions error. You really need
to get a handle on file perms and how they work between users, especially
users of different privileges.
Apparently /var/log/ is owned by root or the system; but you have user
adam trying to write to it. Or something like that.
/etc/cron.daily/mailscanner:
/etc/cron.daily/mailscanner: line 19: cd: /var/spool/MailScanner: No such
file or directoryrun-parts: /etc/cron.daily/mailscanner exited with return
code 1
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/ctags.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/etags.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/preline.1.gz is a dangling symlink
mandb: warning: /usr/share/man/man1/rzsh.1.gz is a dangling symlink
I don't know what that means, but it cries out to be fixed.
--
dman
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail