a few questions about procmail


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers a few questions about procmail
# 1  
Old 04-28-2009
a few questions about procmail

Hello,

I am running a email server on Centos 5.3 (dovecot, postfix, with emails for a few domains) and I am wondering whether I am using procmail or not.

I know procmail is installed because
procmail -version
returns:
Locking strategies: dotlocking, fcntl()
Default rcfile: $HOME/.procmailrc
It may be writable by your primary group
Your system mailbox: /var/mail/root

But
(1) I cannot find the .procmailrc file anywhere.
find / -name .procmailrc returns nothing
Can procmail work properly without a .procmailrc file?
(2) The mailboxes are actually located in /var/mail/vhosts and not in /var/mail/root
Assuming procmail is on, why does it move the email to vhosts??

I would need to make changes to the .procmailrc file, should I create one in /root?

If I am not using procmail, how can I find out what I am using?

Thanks
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Procmail

Hi, I have a few questions. I am new to UNIX/Linux. At work I notice that our mail server uses sendmail. When I looked in the sendmail.cf file I see that it is using PROCMAIL as the Local Delivery Agent. Questions:- I looked for /etc/procmail to see its configuration file but I see none.... (0 Replies)
Discussion started by: mojoman
0 Replies

2. UNIX for Dummies Questions & Answers

Procmail or Spamassassin?

Hello, this is my first visit to your forum and I've searched previous threads for my answer but have not been able to find one. Apologies if there is one that I didn't discover. Is there a way of bouncing or deleting spam that contains non-existent addresses in TO: field but is delivered due... (1 Reply)
Discussion started by: WendyTinley
1 Replies

3. UNIX for Dummies Questions & Answers

procmail, backup, ftp

Hello, On a remote server with Centos 5.0, I am running procmail At /var/mail/vhosts/, I can find all the accounts and I was thinking of saving those files on my local machine using ftp. The structure is right and the files containing the emails (most of them stored in the cur folders) appear... (1 Reply)
Discussion started by: JCR
1 Replies

4. Shell Programming and Scripting

Procmail script

Hi, I need to write a procmail script such that: - incoming email is scanned to see if it is spam - if spam deliver to spam folder - otherwise deliver to inbox and send a copy to another address. So far I have: :0 * ^Subject:.*SPULK DUMB I can make a new recipe on to forward mail... (0 Replies)
Discussion started by: mojoman
0 Replies

5. UNIX and Linux Applications

procmail configuration pronblem?

Hi, I am using "procmail" for triggering an application job which is doing some database operations.The Home directory for my application script has the permissions 2771 which is a policy recommendation. As we know procmail won't accept it's default configuration file $HOME/.procmailrc if... (1 Reply)
Discussion started by: DILEEP410
1 Replies

6. UNIX for Dummies Questions & Answers

procmail code help

Hello, I was wondering if my code is correct on a procmail recipe I am trying to use. I am trying to set up custom filter for for my email address. What needs to happen is any email NOT addressed to me in the to: or cc: field is deleted. For the time being it is set it up to go to another... (0 Replies)
Discussion started by: Hexabah
0 Replies

7. Solaris

sendmail + procmail + spamassassin

Hello, I'm triying to install senmail + procmail + spamassassin, but i've been having trouble with the first part, i cant install procmail... im using solaris 9, i have already installed sendmail, then i tried to install procmail and everything goes right, , then edit the /etc/mail/sendmail.cf... (1 Reply)
Discussion started by: sx3v1l_1n51de
1 Replies

8. Email Antispam Techniques and Email Filtering

procmail rule

I can tell this is not a recently active formum, but here goes, "why doesn't this procmail rule block messages with víagra or v1agra appearing in the subject header :0 * ^Subject:.*(víagra¦v1agra¦pénis¦prescripti0n¦Medicati0n¦M0rtgage¦Xanaxz) { LOG="(THE 7 DIRTY WORDS) " :0 ... (4 Replies)
Discussion started by: jones
4 Replies

9. UNIX for Dummies Questions & Answers

Procmail filter

Hello, I want to make a filter with procmail, using the day of the week ant the hour to filter the message. If the day is Tuesday, the message is redirected to one address. On the other days, the message goes to another address. The messages will be redirected at 8 am to 17 pm. I tried... (1 Reply)
Discussion started by: luiz_fer10
1 Replies

10. UNIX for Dummies Questions & Answers

Procmail Tutorial

Hello, Somebody knows a good procmail tutorial in the net? Thanks!:) (1 Reply)
Discussion started by: luiz_fer10
1 Replies
Login or Register to Ask a Question
LOCKFILE(1)						      General Commands Manual						       LOCKFILE(1)

NAME
lockfile - conditional semaphore-file creator SYNOPSIS
lockfile -sleeptime | -r retries | -l locktimeout | -s suspend | -! | -ml | -mu | filename ... DESCRIPTION
lockfile can be used to create one or more semaphore files. If lockfile can't create all the specified files (in the specified order), it waits sleeptime (defaults to 8) seconds and retries the last file that didn't succeed. You can specify the number of retries to do until failure is returned. If the number of retries is -1 (default, i.e., -r-1) lockfile will retry forever. If the number of retries expires before all files have been created, lockfile returns failure and removes all the files it created up till that point. Using lockfile as the condition of a loop in a shell script can be done easily by using the -! flag to invert the exit status. To prevent infinite loops, failures for any reason other than the lockfile already existing are not inverted to success but rather are still returned as failures. All flags can be specified anywhere on the command line, they will be processed when encountered. The command line is simply parsed from left to right. All files created by lockfile will be read-only, and therefore will have to be removed with rm -f. If you specify a locktimeout then a lockfile will be removed by force after locktimeout seconds have passed since the lockfile was last modified/created (most likely by some other program that unexpectedly died a long time ago, and hence could not clean up any leftover lock- files). Lockfile is clock skew immune. After a lockfile has been removed by force, a suspension of suspend seconds (defaults to 16) is taken into account, in order to prevent the inadvertent immediate removal of any newly created lockfile by another program (compare SUSPEND in procmail(1)). Mailbox locks If the permissions on the system mail spool directory allow it, or if lockfile is suitably setgid, it will be able to lock and unlock your system mailbox by using the options -ml and -mu respectively. EXAMPLES
Suppose you want to make sure that access to the file "important" is serialised, i.e., no more than one program or shell script should be allowed to access it. For simplicity's sake, let's suppose that it is a shell script. In this case you could solve it like this: ... lockfile important.lock ... access_"important"_to_your_hearts_content ... rm -f important.lock ... Now if all the scripts that access "important" follow this guideline, you will be assured that at most one script will be executing between the `lockfile' and the `rm' commands. ENVIRONMENT
LOGNAME used as a hint to determine the invoker's loginname FILES
/etc/passwd to verify and/or correct the invoker's loginname (and to find out his HOME directory, if needed) /var/spool/mail/$LOGNAME.lock lockfile for the system mailbox, the environment variables present in here will not be taken from the environment, but will be determined by looking in /etc/passwd SEE ALSO
rm(1), mail(1), binmail(1), sendmail(8), procmail(1) DIAGNOSTICS
Filename too long, ... Use shorter filenames. Forced unlock denied on "x" No write permission in the directory where lockfile "x" resides, or more than one lockfile trying to force a lock at exactly the same time. Forcing lock on "x" Lockfile "x" is going to be removed by force because of a timeout (compare LOCKTIMEOUT in procmail(1)). Out of memory, ... The system is out of swap space. Signal received, ... Lockfile will remove anything it created till now and terminate. Sorry, ... The retries limit has been reached. Truncating "x" and retrying lock "x" does not seem to be a valid filename. Try praying, ... Missing subdirectories or insufficient privileges. BUGS
Definitely less than one. WARNINGS
The behavior of the -! flag, while useful, is not necessarily intuitive or consistent. When testing lockfile's return value, shell script writers should consider carefully whether they want to use the -! flag, simply reverse the test, or do a switch on the exact exitcode. In general, the -! flag should only be used when lockfile is the conditional of a loop. MISCELLANEOUS
Lockfile is NFS-resistant and eight-bit clean. NOTES
Calling up lockfile with the -h or -? options will cause it to display a command-line help page. Calling it up with the -v option will cause it to display its version information. Multiple -! flags will toggle the return status. Since flags can occur anywhere on the command line, any filename starting with a '-' has to be preceded by './'. The number of retries will not be reset when any following file is being created (i.e., they are simply used up). It can, however, be re- set by specifying -rnewretries after every file on the command line. Although files with any name can be used as lockfiles, it is common practice to use the extension `.lock' to lock mailfolders (it is ap- pended to the mailfolder name). In case one does not want to have to worry about too long filenames and does not have to conform to any other lockfilename convention, then an excellent way to generate a lockfilename corresponding to some already existing file is by taking the prefix `lock.' and appending the i-node number of the file which is to be locked. SOURCE
This program is part of the procmail mail-processing-package (v3.22) available at http://www.procmail.org/ or ftp.procmail.org in pub/proc- mail/. MAILINGLIST
There exists a mailinglist for questions relating to any program in the procmail package: <procmail-users@procmail.org> for submitting questions/answers. <procmail-users-request@procmail.org> for subscription requests. If you would like to stay informed about new versions and official patches send a subscription request to procmail-announce-request@procmail.org (this is a readonly list). AUTHORS
Stephen R. van den Berg <srb@cuci.nl> Philip A. Guenther <guenther@sendmail.com> BuGless 2001/06/23 LOCKFILE(1)

Featured Tech Videos