On 2 Nov, Joe Leske wrote:
| Hello,
|
| I have a question that seems difficult for me yet will probably seem like
| child's play to you experts out there. I would like to know how I can find
| out whether or not procmail is my LDA. I suspect it's not because I have no
| etc/procmailrc file.
|
| I've tried running procmail over a .forward file in my home folder but I do
| not wish to do that anymore because I get bypassed locking errors in my
| logfile. Since my user is initializing procmail, procmail is running under
| the users UID and can't gain the permissions to lock the mail spool file.
|
| But I know that if I run procmail as my LDA, this probably won't be a
| problem. So I'd like to know how I can find out if procmail is my LDA. If
| it's not how can I set it up as my LDA?
|
| Currently I'm running procmail version 3.14 and my locking strategies are
| dotlocking and fcnt1().
|
| Thank you for your consideration
|
Lack of /etc/procmailrc does not reliably tell you it is not LDA.
For example, procmail is configured as LDA out of the box w/ SuSE Linux
but no /etc/procmailrc is created IIRC. I'm sure that's true of other
systems too. After all, what goes in to /etc/procmailrc is up to the
owner.
Retrieve, *Read*, then run:
http://www.professional.org/procmail/procdiag.sh
It'll provide that information and much more. For example (again), it
will alert you to ownership/permissions issues that might be the real
cause of your problems.
--
Reply to list please, or append "8" to "procmail" in address if you must.
Spammers' unrelenting address harvesting forces me to this...reluctantly.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail