Sergei Senin <ss(_at_)ee(_dot_)port(_dot_)ac(_dot_)uk> wrote:
On Thu, 26 Oct 1995, NA/EBC/FB/TV Rabbe Fogelholm +46 8 422 0059 wrote:
I then prepared a .forward file as explained in the procmail(1) man
pages, and made it world readable.
It looks just fine.
I then prepared a simple .procmailrc file with no recipes at all.
Also excellent.
I'm a newbie myself but it looks like that a "simple .procmailrc file
with no recipes at all" wouldn't work at all. You should at least have
Well, you're mistaken there. A simple .procmailrc with no content at
all (empty file) should do just fine. It should almost seem as if procmail
isn't doing anything at all (mail should be delivered as usual, albeit now
by procmail).
I then tried to send mail to myself. No mail was delivered to my usual
mailbox (/usr/spool/mail/qbcholm).
Maybe your mail is being delivered on a different machine than where
procmail has been installed. This will cause problems since the procmail
binary may not exist or exist in a different place on the mailserver, thereby
causing your mail to become undeliverable.
And one other thing: when I first started procmail it changed permissions
on my /usr/mail/ss file: -rw-------- (used to be -rw-rw---). After a
short agony (as my knowledge of computers in general and mail in
particular is infinitely small) and using practical engineering approach
(trying....trying...trying....argh....trying...etc) I changed permissions
to -rwxrw---- and now procmail works just fine or probably even better
(ask me in a few years).
This may be related to his problem, but most likely isn't, since I believe
it happened on SunOS, which normally doesn't exhibit this problem.
FYI, this last feature (yes, it is/was intended as a security feature) has
been severely clipped in the upcoming version of procmail since too many
people tended to be taken by surprise by it.
--
Sincerely,
srb(_at_)cuci(_dot_)nl
Stephen R. van den Berg (AKA BuGless).
WARNING: Do not look into laser with remaining eye