Re: Procmail+qmail
Seby [EMAIL PROTECTED] wrote: How can i make this work fine, i don't want procmail to write there how can i disable this behavior... success: procmail:_Couldn't_create_/var/spool/mail/linux/did_0+0+1/ Try asking on a procmail list, or see the procmail documentation. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Procmail
Xavier Pegenaute [EMAIL PROTECTED] wrote: Please, i need that Qmail exec procmail for every user in mine system, this procmail is a little different than normal procmail, this one, zip all messages and store the messages in his own folder ... A better solution to your problem, which is How do I keep a copy of all messages is contained in the FAQ: http://cr.yp.to/qmail/faq/admin.html#copies You can make your special procmail the default delivery method, but users can override that with their .qmail files. And, yes, you can prevent users from using .qmail files using qmail-users, as Charles suggested, but why not just do it right and not have to worry about diddling with qmail-users? You want your users to be able to create .qmail files, don't you? -Dave
Re: Procmail
I can do it only if i put ".qmail-default" in ../alias/ ? I think its right .. Thanks for all ...:-) - Original Message - From: Xavier Pegenaute To: [EMAIL PROTECTED] Sent: Thursday, July 19, 2001 5:16 PM Subject: Procmail Hi all... Please, i need that Qmail exec "procmail" for every user in mine system, this procmail is a little different than normal procmail, this one, zip all messages andstore the messages in his own folder ... But i'm not sure about how i can do it .., anyone know ..? Thanks.
Re: Procmail
Xavier Pegenaute [EMAIL PROTECTED] wrote: Please, i need that Qmail exec procmail for every user in mine system, this procmail is a little different than normal procmail, this one, zip all messages and store the messages in his own folder ... Make it your default delivery instruction (i.e., argument to qmail-start). See Life with qmail for an example of setting up your default delivery instruction, if the qmail documentation isn't clear enough. Beware that users who can create files in their home directories can override this instruction -- if that's a problem, you can use qmail-users to disallow .qmail access. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Procmail
On Thu, Jul 19, 2001 at 05:35:02PM +0200, Xavier Pegenaute wrote: I can do it only if i put .qmail-default in ../alias/ ? I think its right .. Thanks for all ...:-) - Original Message - From: Xavier Pegenaute To: [EMAIL PROTECTED] Sent: Thursday, July 19, 2001 5:16 PM Subject: Procmail Hi all... Please, i need that Qmail exec procmail for every user in mine system, this procmail is a little different than normal procmail, this one, zip all messages and store the messages in his own folder ... But i'm not sure about how i can do it .., any one know ..? Thanks. No, you do not need .qmail-default anywhere. A quick google search returned: 1. Dan's own instructions, _contained in the qmail-1.03 distribution_. 2. Numerous other sources. Just hit www.google.com with 'qmail procmail' and you will find your answers. -- Greg White
Re: Procmail
On Thu, Jul 19, 2001 at 05:35:02PM +0200, Xavier Pegenaute wrote: I can do it only if i put .qmail-default in ../alias/ ? Nonsense. Edit /var/qmail/rc, the sample scripts in /var/qmail/boot/ will help. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Procmail + Maildir
Fábio Gomes [EMAIL PROTECTED] wrote: Does Procmail work with Qmail maildir format? Newer versions of procmail have Maildir support built-in, but they don't adhere to djb's naming convention -- you could run into problems. You'd be better off to use maildrop, or if you must use procmail, use safecat to deliver into maildirs. See qmail.org for links. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: procmail and spambouncer
Charles Cazabon([EMAIL PROTECTED])@2001.05.18 13:04:03 +: I don't know anything about spambouncer, but purely based on the name, I'd say it's useless. I've seen some systems which generate late bounces to suspicious mail to try to get your name removed from spammers' lists, but the basic idea is flawed because spammers universally use forged envelope sender addresses and therefore never see the bounces. even worse with spambouncer which appears to create mails from templates and sends them to other adresses like contacts of the providers and so on. i doubt that this can be done effectively with a set of scripts without annoying overworked admins all over the world... *sigh* seems like we all will get another wave of spam complaining about spam like it was when netmedic came out and complained about high latency or not enough bandwidth at some providers technical mail accounts. and that just because some web server out there in the net served it's objects with 6kbit/s and the backbone companies got the annoy-me-mail here's an excerpt from the web page http://www.spambouncer.org/: --- The SpamBouncer is a set of procmail recipes, or instructions, which search the headers and text of your incoming email to see if it meets one or more of the following conditions: - Originates from an email address known to belong to a spammer. - Originates from known spam source sites, domains or hosts -- internet sites which exist solely or primarily to spam or provide services to spammers. - Originates from irresponsible, or rogue, Internet Service Providers (ISPs), who permit spamming from their sites and fail to take appropriate action against spammers. - Was sent using a bulk email program whose only or primary purpose is to send large quantities of junk email. - Contains headers which match the filter's profile of definite or probable spam. - Contains body text strings which match the filter's profile of probable spam. The SpamBouncer sorts suspected spam into two categories -- mail from known spam sources which is definitely spam, and other mail which is probably spam, but might also be legitimate. It then tags this email with appropriate headers giving the spam classification, and responds according to the parameters you have set. Depending on how you set it up, it will: - Simply tag the suspected spam and return it to your main incoming mailbox, allowing you to set up Eudora, Pegasus Mail, or another POP mail program to retrieve and sort your mail. - Tag the suspected spam, delete spam from known spam sources, and file suspected spam in a separate folder. - Send a simulated MAILER-DAEMON daemon bounce to known spammers in hopes that they will think your email address is invalid and remove you from their spam lists. - Complain to the upstream providers of known spammers or spam sites/domains, asking that they disconnect the internet service of the spammers. - Notify senders of email tagged as probable spam that their email was intercepted, and give them a password to resend their email and bypass spam filtering if their email was legitimate. (Spammers almost never try to bypass filtering when warned this way -- in most cases, they don't even read replies to their mail.) --- -- Nothing is better than Sex. Masturbation is better than nothing. Therefore, Masturbation is better than Sex. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
Re: procmail and spambouncer
Gawain Reifsnyder [EMAIL PROTECTED] wrote: I want to implement spam filtering for several users. My ISP recently installed qmail and vpopmail on our colocated Yellow Dog Linux server. The machine already has procmail 3.14 installed, although I've never used it. I installed spambouncer http://www.spambouncer.org (which uses procmail) according to the directions, but it doesn't seem to be doing anything. Are there any known gotchas with this setup? I don't know anything about spambouncer, but purely based on the name, I'd say it's useless. I've seen some systems which generate late bounces to suspicious mail to try to get your name removed from spammers' lists, but the basic idea is flawed because spammers universally use forged envelope sender addresses and therefore never see the bounces. If you do want to use this, you'll probably have to modify either the users' .qmail files or the default delivery instruction to call procmail. Typically this means setting it to something like: |preline procmail [.procmailrcfile] Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Procmail headaches
On Sun, Apr 15, 2001 at 03:20:10AM +0200, David Gmez wrote: The qmail-start script (the default one which comes with qmail) ? There are a set of possible start-up scripts in /var/qmail/boot. None are named qmail-start. qmail-start is a program in /var/qmail/bin. man qmail-start "qmail-start '|preline procmail' splogger qmail" Apparently your distribution or your chosen RPM is using .../boot/proc as the start-up script. to avoid a defaultdelivery action, without modifying the log stuff ?. I You can certainly use one of the other ones in .../boot or edit the one you currently have. Look at .../boot/home if you want delivery to a traditional Un*x mailbox named "Mailbox" in the user's home directory, or .../boot/maildir if you want delivery to a maildir named "Maildir" in the user's home directory. Tim
Re: procmail
With best regards, Shishir K. Singh [EMAIL PROTECTED] - Original Message - From: MOkondo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 26, 2001 7:51 PM Subject: procmail I am trying to filter email using procmail. what i was doing put a line below on ~/.qmail file: | preline procmail The result is filtered emails delivered to ~/Mail/anyfile (one file) but unfiltered email delivered to /var/spool/mail/ my question is: How to make procmail work with Maildir and as reliable as Maildir? what i have to write on ~/.qmail file ? -- MOkondo i am an atheist, thank god !
Re: procmail
* MOkondo [EMAIL PROTECTED] [20010326 21:21]: I am trying to filter email using procmail. what i was doing put a line below on ~/.qmail file: | preline procmail The result is filtered emails delivered to ~/Mail/anyfile (one file) but unfiltered email delivered to /var/spool/mail/ my question is: How to make procmail work with Maildir and as reliable as Maildir? what i have to write on ~/.qmail file ? Read man procmail, there's an environment variable that tells what do do with all mail after all rules has been completed and none of them matched. -- MOkondo i am an atheist, thank god ! -- Kirill
Re: procmail
With best regards, Shishir K. Singh [EMAIL PROTECTED] - Original Message - From: MOkondo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 26, 2001 7:51 PM Subject: procmail I am trying to filter email using procmail. what i was doing put a line below on ~/.qmail file: | preline procmail The result is filtered emails delivered to ~/Mail/anyfile (one file) but unfiltered email delivered to /var/spool/mail/ my question is: How to make procmail work with Maildir and as reliable as Maildir? what i have to write on ~/.qmail file ? -- MOkondo i am an atheist, thank god !
Re: procmail
With best regards, Shishir K. Singh [EMAIL PROTECTED] - Original Message - From: MOkondo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 26, 2001 7:51 PM Subject: procmail I am trying to filter email using procmail. what i was doing put a line below on ~/.qmail file: | preline procmail The result is filtered emails delivered to ~/Mail/anyfile (one file) but unfiltered email delivered to /var/spool/mail/ my question is: How to make procmail work with Maildir and as reliable as Maildir? what i have to write on ~/.qmail file ? -- MOkondo i am an atheist, thank god !
Re: procmail problems (RH6.2) SOLVED (?)
I made some modifications to the homedir files: $HOME/.qmail now has | preline /usr/bin/procmail -m /home/joe/.procmailrc (the -m file was previously mis-named) and $HOME/.procmailrc has PATH=/bin:/usr/bin:/usr/bin:$PATH ORGMAIL=$HOME/Mailbox MAILDIR=$HOME/mail DEFAULT=$HOME/Mailbox #completely optional LOGFILE=$MAILDIR/procmail.log Does this mean I have to have these two files in every home directory!? And does it also mean that any user can screw his mail up by accidentally deleting these files? I have to say, though this works, I'm not particularly comfortable with it... Joe --- Joe Janitor [EMAIL PROTECTED] wrote: I'm having trouble with qmail and procmail. I've read the FAQ and the list archives, but am still unsure what to do. I'm using a Linux RedHat 6.2 system. installed qmail. outgoing mail works. incoming mail (from outside) bounces (unknown user) local mail won't be delivered, i.e when I try (from the machine in question): $ mail joe Subject: testing testing . Cc: $ I end up with /var/spool/mail/joe (a symlink to /home/joe/Mailbox) being renamed as BOGUS.joe.1jLB and a new FILE called /var/spool/mail/joe containing the "testing" message. I read in INSTALL.mbox the following: A few mail programs are unable to handle symbolic links, so you will have to configure them to look at ~user/Mailbox directly: * procmail: Change SYSTEM_MBOX in config.h and recompile; or, with recent versions, define MAILSPOOLHOME in src/authenticate.c. but I don't know where to find config.h or authenticate.c... do I have to download the procmail source and recompile after these edits? (There has to be an easier way!) I tried adding ~joe/.qmail-test1 containing: |preline procmail -m /home/awilber/.procmailrc and ~joe/.procmail containing PATH=/bin:/usr/bin:/usr/bin:$PATH ORGMAIL=$HOME/Mailbox MAILDIR=$HOME/mail DEFAULT=$HOME/Mailbox #completely optional LOGFILE=$MAILDIR/procmail.log this didn't work. I'm lost. Thanks, Joe __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: procmail problems (RH6.2) SOLVED (?)
Joe Janitor [EMAIL PROTECTED] wrote: I made some modifications to the homedir files: $HOME/.qmail now has | preline /usr/bin/procmail -m /home/joe/.procmailrc (the -m file was previously mis-named) and $HOME/.procmailrc has PATH=/bin:/usr/bin:/usr/bin:$PATH ORGMAIL=$HOME/Mailbox MAILDIR=$HOME/mail DEFAULT=$HOME/Mailbox #completely optional LOGFILE=$MAILDIR/procmail.log Does this mean I have to have these two files in every home directory!? No. First, procmail doesn't need the -m flag. See the procmail section in LWQ: http://www.lifewithqmail.org/lwq.html#procmail Also, if you want delivery via procmail to be the default, specify that on the qmail-start command line, or in the control/defaultdelivery file if you installed using LWQ. Finally, you can specify a systemwide default procmailrc in /etc/procmailrc. And does it also mean that any user can screw his mail up by accidentally deleting these files? I have to say, though this works, I'm not particularly comfortable with it... You can't really save your users from themselves... -Dave
Re: procmail problems (RH6.2) SOLVED (?)
--- Dave Sill [EMAIL PROTECTED] wrote: Joe Janitor [EMAIL PROTECTED] wrote: I made some modifications to the homedir files: $HOME/.qmail now has | preline /usr/bin/procmail -m /home/joe/.procmailrc (the -m file was previously mis-named) and $HOME/.procmailrc has PATH=/bin:/usr/bin:/usr/bin:$PATH ORGMAIL=$HOME/Mailbox MAILDIR=$HOME/mail DEFAULT=$HOME/Mailbox #completely optional LOGFILE=$MAILDIR/procmail.log Does this mean I have to have these two files in every home directory!? No. First, procmail doesn't need the -m flag. See the procmail section in LWQ: http://www.lifewithqmail.org/lwq.html#procmail Also, if you want delivery via procmail to be the default, specify that on the qmail-start command line, or in the control/defaultdelivery file if you installed using LWQ. I think I was already doing this, my /etc/rc.d/init.d/qmail script called qmail-start '|preline procmail' splogger qmail Finally, you can specify a systemwide default procmailrc in /etc/procmailrc. I read about that, but since that file didn't already exist on my system, I wondered if it would be looked for at all (if I created it). I never got around to testing it. And does it also mean that any user can screw his mail up by accidentally deleting these files? I have to say, though this works, I'm not particularly comfortable with it... You can't really save your users from themselves... But you can make it harder for them to auto-hank... In any case, I've since downloaded the procmail source, edited src/authenticate.c to include #define MAILSPOOLHOME "/Mailbox" and recompiled. Now it works great without any $HOME/.qmail or $HOME/.procmailrc or /etc/procmailrc Thanks for writing. Joe __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: procmail and formail problem..
[EMAIL PROTECTED] wrote: MAILFROM=`/usr/bin/formail -xFrom:` :0 c |(/usr/bin/formail -X "" \ -I "To: [EMAIL PROTECTED]" -X "To:" \ -I "Cc: " -X "Cc:" \ -I "Bcc: " -X "Bcc:" \ -I "From: [EMAIL PROTECTED]" -X "From:"; \ echo "Email from:$MAILFROM "; \ echo " " ) | $MAILMAIL and the qmail log.. is that @40003a77ed5f35833224 delivery 15: success: procmail:_Error_while_writing_to_"(/usr/bin/formail_-X_""_\/_-I_"To:_123456@ pager.icq.com"_-X_"To:"_\/__-I_"Cc:_"__-X_"Cc:"_\/__-I_"Bcc:_"__-X_" Bcc:"_\/_-I_"From:[EMAIL PROTECTED]"_-X_"From:";_\/_echo_"Email_from:$MAI LFROM_";_\/__echo_"_"_)_|_$MAILMAIL_"/did_0+0+1/did_0+0+1/ so any idea??? First problem is that qmail considers this a successful delivery, but procmail thinks it was unsuccessful. See: http://www.lifewithqmail.org/lwq.html#procmail for some qmail/procmail tips. Second problem is that procmail didn't like your recipe. That's really a procmail problem, and should be directed to a procmail forum. -Dave
Re: Procmail weirdness
Here they go. Thanks. 1) $HOME/.qmail: |/usr/sbin/qmail-procmail ./Maildir/ 2) $HOME/.procmail: SHELL=/bin/sh MAILDIR=$HOME/Maildir LOGFILE=$HOME/.procmaillog VERBOSE=yes :0 HB * ! ^From:.*postmaster@xxx * ^Content-Type:.*multipart * ^.*name=.*.(avi|mp3|com|exe|sys|bat|bin|pcx|gif|jpg|jpeg|bmp|pps|mpg|mpeg|pi f|scr) /dev/null 3) /usr/sbin/qmail-procmail: #!/bin/sh # Copyright (c) 1998 Software in the Public Interest http://www.debian.org/ # Written by Philip Hands phil@x. Distributed under the GNU GPL # $Id: qmail-procmail,v 1.2 1998/03/24 19:31:27 phil Exp $ /var/qmail/bin/preline /usr/bin/procmail -m -p .procmailrc exit 0 # check if procmail returned EX_TEMPFAIL (75) [ $? = 75 ] exit 111 # otherwise return a permanent error exit 100 4) sample .procmaillog: procmail: [27698] Thu Dec 7 00:06:38 2000 procmail: Match on ! "^From:.*postmaster@xxx" procmail: Match on "^Content-Type:.*multipart" procmail: Match on "^.*name=.*.(avi|mp3|com|exe|sys|bat|bin|pcx|gif|jpg|jpeg|bmp |pps|mpg|mpeg|pif|scr)" procmail: Assigning "LASTFOLDER=/dev/null" procmail: Opening "/dev/null" From [EMAIL PROTECTED] Thu Dec 07 02:06:38 2000 Subject: Fw: CUIDADO com os Clubes de Nudismo.. Folder: /dev/null 42135 procmail: Notified comsat: "abc@0:/dev/null" - Original Message - From: "Timothy Legant" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 08, 2000 1:38 AM Subject: Re: Procmail weirdness On Thu, Dec 07, 2000 at 11:25:39PM -0200, Francisco Jen Ou wrote: The weirdness is just this: procmail says recipies OK (forwarded to [EMAIL PROTECTED]), but qmail-local delivers a copy to original recipient. How are you calling procmail? In a .qmail file? From the qmail-start command line? Please show us the whole file. -thl
Re: Procmail weirdness
"Francisco Jen Ou" [EMAIL PROTECTED] writes: Here they go. Thanks. 1) $HOME/.qmail: |/usr/sbin/qmail-procmail ./Maildir/ You have two lines here. One which calls procmail and one which makes a local delivery. Remove the ./Maildir/ line if you don't want local delivery. -- "I live in the heart of the machine. We are one."
Re: Procmail weirdness
That's it! Now it's working flawlessly! Thanks a lot. - Original Message - From: "Jenny Holmberg" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 08, 2000 8:01 AM Subject: Re: Procmail weirdness "Francisco Jen Ou" [EMAIL PROTECTED] writes: Here they go. Thanks. 1) $HOME/.qmail: |/usr/sbin/qmail-procmail ./Maildir/ You have two lines here. One which calls procmail and one which makes a local delivery. Remove the ./Maildir/ line if you don't want local delivery. -- "I live in the heart of the machine. We are one."
Re: Procmail weirdness
Thanks for your feedback. Tried out your suggestion, but the problem continues. The weirdness is just this: procmail says recipies OK (forwarded to [EMAIL PROTECTED]), but qmail-local delivers a copy to original recipient. - Original Message - From: "Peter Green" [EMAIL PROTECTED] To: "Francisco Jen Ou" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 07, 2000 1:27 AM Subject: Re: Procmail weirdness * Francisco Jen Ou [EMAIL PROTECTED] [001206 21:59]: Procmail log reports no problems executing recipies, but the messages that are supposed to be dumped to /dev/null continue to get delivered by qmail-local. I haven't seen your particular problem. However, you might try setting up a dummy user; put just ``#'' (that's a hash with nothing else) in ~alias/.qmail-nobody. Then, instead of ``delivering'' to /dev/null, forward the offending e-mails to [EMAIL PROTECTED] where example.com is your domain. That will effectively throw those messages into the bitbucket. /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- Oh, and this is another kernel in that great and venerable "BugFree(tm)" series of kernels. So be not afraid of bugs, but go out in the streets and deliver this message of joy to the masses. (Linus, in the announcement for 1.3.27)
Re: Procmail weirdness
On Thu, Dec 07, 2000 at 11:25:39PM -0200, Francisco Jen Ou wrote: The weirdness is just this: procmail says recipies OK (forwarded to [EMAIL PROTECTED]), but qmail-local delivers a copy to original recipient. How are you calling procmail? In a .qmail file? From the qmail-start command line? Please show us the whole file. -thl
Re: Procmail weirdness
* Francisco Jen Ou [EMAIL PROTECTED] [001206 21:59]: Procmail log reports no problems executing recipies, but the messages that are supposed to be dumped to /dev/null continue to get delivered by qmail-local. I haven't seen your particular problem. However, you might try setting up a dummy user; put just ``#'' (that's a hash with nothing else) in ~alias/.qmail-nobody. Then, instead of ``delivering'' to /dev/null, forward the offending e-mails to [EMAIL PROTECTED] where example.com is your domain. That will effectively throw those messages into the bitbucket. /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- Oh, and this is another kernel in that great and venerable "BugFree(tm)" series of kernels. So be not afraid of bugs, but go out in the streets and deliver this message of joy to the masses. (Linus, in the announcement for 1.3.27)
Re: Procmail and maildir format
Subba Rao [EMAIL PROTECTED] wrote: I am in the process of moving from maildrop to procmail. The MTA on my system is Qmail, therfore I chose to use Maildir format for my mail. Procmail has been compiled to point to my spool at $HOME/Maildir [...] The fetchmailrc is invoking procmail fine, but it does not write to the $HOME/Maildir/new directory. Instead it is dropping the mail in the literal $HOME/Maildir/ directory. The LOGFILE too is written to $HOME/Maildir/ directory. [...] Procmail variables are as follows, PATH=$HOME/bin:/usr/bin:/usr/ucb:/bin:/usr/local/bin:. MAILDIR=$HOME/Maildir The MAILDIR variable doesn't mean q qmail-style Maildir. Instead, it's more lie a chroot, which is what you're seeing. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Procmail and maildir format
On Sat, Sep 30, 2000 at 06:05:56PM +, Subba Rao wrote: I am in the process of moving from maildrop to procmail. The MTA on my system is Qmail, therfore I chose to use Maildir format for my mail. Procmail has been compiled to point to my spool at $HOME/Maildir The fetchmailrc is invoking procmail fine, but it does not write to the $HOME/Maildir/new directory. Instead it is dropping the mail in the literal $HOME/Maildir/ directory. The LOGFILE too is written to $HOME/Maildir/ directory. [snip...] How can I make Procmail deliver mail in maildir format? The version of procmail on my system is v3.15 You must specify a '/' at the end of the name of the maildir to alert procmail that your desired delivery mailbox is, in fact, a maildir. For example, my .procmailrc includes the following recipe to process messages to this list: :0 * ^TO_qmail Qmail/ Qmail is the name of the maildir in MAILDIR ($HOME/Mail, in my case). Procmail automatically delivers to the new/ directory within the specified mailbox. Procmail variables are as follows, PATH=$HOME/bin:/usr/bin:/usr/ucb:/bin:/usr/local/bin:. MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR LOGFILE=procmail.log LOCKFILE=$HOME/.lockmail VERBOSE=yes You probably will need to change DEFAULT to say DEFAULT=$MAILDIR/ if you plan on some mail falling off the end of your processing and getting delivered to the default drop. Thanks for any pointers or info. Hope this helped. Subba Rao [EMAIL PROTECTED] http://pws.prserv.net/truemax/ Tim -- Timothy Legant [EMAIL PROTECTED]
Re: Procmail and maildir format
Quoted from Subba Rao: The MTA on my system is Qmail, therfore I chose to use Maildir format for my mail. I've never heard of an MTA called Qmail. Perhaps you meant qmail? (This distinction is noted in Dave Sill's ``life with qmail'', which every qmail user is advised to read.) The fetchmailrc is invoking procmail fine, but it does not write to the $HOME/Maildir/new directory. Instead it is dropping the mail in the literal $HOME/Maildir/ directory. The LOGFILE too is written to $HOME/Maildir/ directory. [...] MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR As mentioned by someone else, MAILDIR in procmail actually specifies the default directory to use when a relative (not starting with a slash) filename is given as a folder. You must, nonetheless, end the folder name with a slash to tell procmail that you're delivering to a maildir. Try ``DEFAULT=./'', if you have ``MAILDIR=$HOME/Maildir'' as you have. Not tested, but should work. Hope it helps, ---Chris K. -- Chris, the Young One |_ If you can't afford a backup system, you can't Auckland, New Zealand |_ afford to have important data on your computer. http://cloud9.hedgee.com/ |_ ---Tracy R. Reed
Re: procmail error
Ramzi Abdallah [EMAIL PROTECTED] wrote: Sep 28 11:16:54 intranet qmail: 970100214.227272 delivery 2: success: procmail:_Lock_failure_on_"/var/spool/mail/rsa.lock"/did_0+0+2/ any idea what might be causing this?? 1) That's really a procmail question, but... 2) Permissions? Stale lock? Already locked by another instance of procmail? I'm just guessing. -Dave
Re: procmail and qmail, exitcode, stdout
Ronny Haryanto [EMAIL PROTECTED] writes:
I'm trying to discard emails from somebody and have procmail return a
hard error code (like 67, 77 or 100) *with* my own brief error message.
The MTA is qmail. Currently I have "|preline procmail" in my .qmail file.
I have tried this following recipe with partial success (email is
discarded and bounced, but my brief error message is not there):
:0
* ^From:.*abuser@example\.com
{
EXITCODE=100
:0
| echo "Permission denied"
}
:0
* ^From:.*abuser@example\.com
{
EXITCODE=100
:0 f
| echo "Piss off."
:0 r
|
}
In procmailese, the f flag on the first recipe inside the braces means
"filter", which makes procmail pipe the message through the specified
command, and replace the current message content with the output of the
pipe. For instance:
:0 f
| sed 's/expletive/[expletive deleted]/g'
would be a nice start at sanitizing all email passing through your
.procmailrc. :) In our instance, however, we're piping our message to echo,
which ignores the input it has been offered, and simply outputs our
message, which procmail now takes to be the message body.
The pipe with no argument makes procmail emit the current message to
standard output, with the desired effect. The r flag prevents procmail from
trying to add extraneous \r or \n characters to the output, which are
inappropriate in this context, but appropriate for normal procmail
operation. I added it mostly for aesthetic reasons on the output; try it
both ways and see for yourself.
--
[EMAIL PROTECTED] (Michael Handler) washington, dc
Re: procmail/vpopmail
Chester Chee wrote: Hi, Does anyone has an experience using procmail with vpopmail (virtual domain)? I am trying to setup procmail to filter "junk" mail to specific mail folder for vpopmail user. And it does not seem to work at all. My vpopmail users access their mail via IMAP instead of Maildir. Am I using the right approach to taggle this problem? Any pointer or help is greatly appreciated. Thanks in advance. Here is my .procmailrc:- :0: * ^X-JunkMail: Yes junk-mail Take a look at the development version of vpopmail, 4.8.6. It contains a new filtering module. Ken Jones inter7
Re: procmail preline acting like a local user (fwd)
I tried the suggestion [thanks John] below but alas. Jul 22 13:46:42 adsl-63-201-55-218 qmail: 964298802.949315 starting delivery 86: msg 79379 to local _|[EMAIL PROTECTED] Jeff local _|_/var/qmail/bin/preline_/usr/local/bin/procmail@adsl-6etc. etc later I get no_mailbox as to be expected. Advice please. Try deleting the space in front of the vertical bar. -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Re: procmail preline acting like a local user - again, sorry
My apologies for sending this again but I could not receive mail responses for a bit because silly me, I forgot to remove the .qmail before sending the note below. If anyone was good enought to repsond as yet please also be so good as to send again. Thanks Jeff --- I tried the suggestion [thanks John] below but alas. Jul 22 13:46:42 adsl-63-201-55-218 qmail: 964298802.949315 starting delivery 86: msg 79379 to local _|[EMAIL PROTECTED] Jeff local _|_/var/qmail/bin/preline_/usr/local/bin/procmail@adsl-6etc. etc later I get no_mailbox as to be expected. Advice please. Try deleting the space in front of the vertical bar. -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Re: procmail preline acting like a local user - again, sorry
From: Jeff Gray [EMAIL PROTECTED] I tried the suggestion [thanks John] below but alas. _|[EMAIL PROTECTED] Ah, the Americisms... :) Jeff, note the underline before the pipe ( _| ). Delete the space at the *start* of the line, *before* the pipe. Armando
Re: procmail preline acting like a local user - again, sorry
Thanks, this was, of course, the fix. This post is now mostly for the archives so another will not fall into the 'American whitespace hole" g. With appreciation to a list that responds professionally and quickly. Hopefully in a bit I too will be able to contribute. Jeff On Sat, 22 Jul 2000, asantos wrote: From: Jeff Gray [EMAIL PROTECTED] I tried the suggestion [thanks John] below but alas. _|[EMAIL PROTECTED] Ah, the Americisms... :) Jeff, note the underline before the pipe ( _| ). Delete the space at the *start* of the line, *before* the pipe. Armando
Re: procmail/vpopmail
Hi, Does anyone has an experience using procmail with vpopmail (virtual domain)? I am trying to setup procmail to filter "junk" mail to specific mail folder for vpopmail user. And it does not seem to work at all. My vpopmail users access their mail via IMAP instead of Maildir. Am I using the right approach to taggle this problem? Any pointer or help is greatly appreciated. Thanks in advance. Here is my .procmailrc:- :0: * ^X-JunkMail: Yes junk-mail Chester Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: procmail vs. maildrop
On Tue, Mar 14, 2000 at 01:30:12AM -0600, Peter Schultz wrote: Hi, I'm just trolling for your opinion on which solution is the best match with qmail. Procmail 3.14 is said to be maildir compliant, yet on: http://www.procmail.org/todo.html you will find that they're admittedly still not totally up-to-date. No problem. Use procmail, and deliver with safecat. /magnus -- http://x42.com/
Re: procmail problems
Hey, Try something like this: :0: * /home/mordac/mailbox Check out the procmail docs for details. -Deke Eric LaLonde [[EMAIL PROTECTED]] wrote: I'm trying to set up procmail so that when a user emails another user locally using 'mail', it will go to ~/user/Mailbox. (mordac is my test user) to do this i put: "/home/mordac/Mailbox" (minus quotes) in /home/mordac/.procmailrc and in /home/mordac/.qmail i put: | preline procmail but it doesn't seem to work. I get this in the maillog: Jan 26 19:46:50 damacles qmail: 948934010.491702 new msg 40216 Jan 26 19:46:50 damacles qmail: 948934010.491977 info msg 40216: bytes 260 from [EMAIL PROTECTED] qp 8619 uid 0 Jan 26 19:46:50 damacles qmail: 948934010.495584 starting delivery 11: msg 40216 to local [EMAIL PROTECTED] Jan 26 19:46:50 damacles qmail: 948934010.495851 status: local 1/10 remote 0/20 Jan 26 19:46:50 damacles qmail: 948934010.525596 delivery 11: success: procmail:_Skipped_"/home/mordac/Mailbox"/did_0+0+1/ Jan 26 19:46:50 damacles qmail: 948934010.525854 status: local 0/10 remote 0/20 Jan 26 19:46:50 damacles qmail: 948934010.525958 end msg 40216 what's with "success: procmail:_Skipped_"/home/mordac/Mailbox"/did_0+0+1/" ??? What am I leaving out or doing wrong? any help is appreciated.
Re: Procmail.
On Tue, Nov 02, 1999 at 04:30:09PM -0600, eric wrote: Is there anyway to filter thru procmail and then write to a users Maildir ? The "patched" procmail from qmail.org site (and even the RPM) doesn't seem to do anything but deliver to /var/spool/mail/$USER. Hmmm... I use a plain and simple procmail, no patches at all. Try using this in your .procmailrc... DEFAULT=$HOME/Maildir/new/. It works for me! Regards; Ricardo Cerqueira -- +--- | Ricardo Cerqueira - [EMAIL PROTECTED] | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | FCCN/RCCN - Fundacao para a Computacao Cientifica Nacional | Av. Brasil, 101 / 1700-066 Lisboa / Portugal *** Tel: (+351) 1 8440100
Re: Procmail.
Thanks, but we have to make a slow migration for the stupid users. What I have working is ... $ cat .procmailrc PATH=/usr/bin:/usr/sbin:/bin:/sbin UMASK=077 # umask DATE=`date +%y%m` # date format SHELL=/bin/sh # a shell for exec MAILDIR=$HOME/Maildir :0 $MAILDIR/new/. Doesn't look to be anything wrong with this -- but it does not do exact time stamping on files in $MAILDIR/new -- only a numeric increase per file. Any other ideas are welcome. ; If you want a mail filter that supports maildirs natively, look here: ; http://www.flounder.net/~mrsam/maildrop/ ; ; -- ; Sam ; ; -- Eric D. Pancer @ "I don't give advice; geniuses don't [EMAIL PROTECTED] |need it, and amateurs don't want it." http://www.catastrophe.net | -- Vida Chenoweth
Re: Procmail.
eric [EMAIL PROTECTED] wrote on Tue, 02 Nov 1999: MAILDIR=$HOME/Maildir For procmail, $MAILDIR is the default location of mail folders. Typically this is ~/Mail, or ~/mail. You probably do not want it to be pointing to ~/Maildir, unless you plan to having actual mail folders (mbox style or maildir style, either) under the directory ~/Maildir You likely want to do this instead: DEFAULT=$HOME/Maildir :0 $MAILDIR/new/. Here's the second problem. With the maildir patch to procmail (at least the one I use), maildir folders are handled just like mbox folders. That means you do *not* specify the "new" in the folder name. I think you may place an ending / there, to make it obvious it's a maildir, but if the folder exists and is a maildir that isn't a requirement. I'm not sure how procmail behaves if the folder doesn't yet exist, the trailing / could have an effect then. Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / 2400 bps makes you want to get out and push!!
Re: Procmail.
On Tue, 2 Nov 1999, eric wrote: Any other ideas are welcome. How about "safecat"? See http://www.nb.net/~lbudney/linux/software/safecat.html, especially the "safecat one-liners" page http://www.nb.net/~lbudney/linux/software/safecat/one-liners.html. Eric -+ Eric Rahmig | "Merely having an open mind is nothing. The object of [EMAIL PROTECTED] | opening the mind, as of opening the mouth, is to shut it | again on something solid." -- G.K. Chesterton
Re: Procmail.
Apparently it is unclear that SOME people need procmail during the migration and the default delivery will be sent to the recipe posted before. jeez ; ; If all you're doing is delivering to $HOME/Maildir, I don't see why you ; need procmail. ; ; ;
Re: Procmail.
On Tue, Nov 02, 1999 at 04:48:02PM -0600, eric wrote: What I have working is ... $ cat .procmailrc PATH=/usr/bin:/usr/sbin:/bin:/sbin UMASK=077 # umask DATE=`date +%y%m` # date format SHELL=/bin/sh # a shell for exec MAILDIR=$HOME/Maildir You want DEFAULT=$HOME/Maildir/ here, and drop the following rule: :0 $MAILDIR/new/. Doesn't look to be anything wrong with this -- but it does not do exact time stamping on files in $MAILDIR/new -- only a numeric increase per file. The "/." at the end of the above recipe directs procmail to deliver into the named directory as a MH folder, which uses sequentially numbered files for storage. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
Re: procmail issues
On Mon, 10 May 1999, Peter van Dijk wrote: On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote: hey all, i recently tried going back to some procmail scripts i had before and am getting the follow error: none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir /var/spool/mail/$USER, it says it's a bogus file and renames it. Ofcourse it is. procmail doesn't do Maildir. Though there is a version on the qmail page that does and works well. andy
Re: procmail issues
On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote: hey all, i recently tried going back to some procmail scripts i had before and am getting the follow error: none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir /var/spool/mail/$USER, it says it's a bogus file and renames it. Ofcourse it is. procmail doesn't do Maildir. Greetz, Peter -- | 'He broke my heart,| Peter van Dijk | I broke his neck' | [EMAIL PROTECTED] | nognikz - As the sun |Hardbeat@ircnet - #cistron/#linux.nl | | Hardbeat@undernet - #groningen/#kinkfm/#vdh |
Re: procmail issues
ecuse me that should be $HOME/Mailbox end +-+ |Greg Albrecht KF4MKT [EMAIL PROTECTED]| |Safari Internetwww.safari.net| |Fort Lauderdale, FL1-888-537-9550| +-+ On Mon, 10 May 1999, Peter van Dijk wrote: On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote: hey all, i recently tried going back to some procmail scripts i had before and am getting the follow error: none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir /var/spool/mail/$USER, it says it's a bogus file and renames it. Ofcourse it is. procmail doesn't do Maildir. Greetz, Peter -- | 'He broke my heart,| Peter van Dijk | I broke his neck' | [EMAIL PROTECTED] | nognikz - As the sun |Hardbeat@ircnet - #cistron/#linux.nl | | Hardbeat@undernet - #groningen/#kinkfm/#vdh |
Re: procmail-~/Maildir
John Conover [EMAIL PROTECTED] writes: Is there a way of executing procmail do ~/.procmailrc, and if email is not rejected for a user, it is delivered into a ~/Maildir? BTW, eg., use my standard spam filter for users that want it, but want to fetch mail via POP3 in a Maildir. If I understand you correctly, you want mail to be pumped through procmail--and to be delivered to a maildir if it falls through all of your procmail filters. The qmail way to do that is to put something like this in your .qmail-ext file: |preline procmail ./Maildir/ To make this work, your "rejecting" recipes must return exit code 99, telling qmail to ignore the next instruction(s). Be aware that procmail itself has a default delivery instruction, for mails that "fall through", and you don't want to trigger it. A recipe like this, as your last recipe, should do the trick: :0 /dev/null On the other hand, there is an easier way (YMMV). You can use the patched procmail which can do maildir deliveries, and make your last recipe a maildir delivery--or set $DEFAULT appropriately in the rc file. If you'd rather not use a patched procmail (my preference), there is a program which does maildir delivery of messages posted on stdin--just what you need. It's called "safecat", and it's available at the URL: http://www.pobox.com/~lbudney/linux/software/safecat.html To use it, make your last recipe the following: :0w |safecat $HOME/Maildir/tmp $HOME/Maildir/new Used in this way, procmail+safecat should be as safe as qmail's own maildir delivery. Len. -- 45. Being to advise or reprehend any one, consider whether it ought to be in publick or in Private; presently, or at Some other time in what terms to do it in reproving Shew no Sign of Cholar but do it with all Sweetness and Mildness. -- George Washington, "Rules of Civility Decent Behaviour"
Re: Procmail and Maildir?
On Wed, Apr 28, 1999 at 09:23:47AM -0500, Andy Walden wrote: Is there anyway to fudge procmail into writing things to a Maildir? I would think that just giving each message a different name based on some variable that could be captured would work. Is anyone doing anything like this? Thanks, andy There are some patches available to make procmail deliver to maildirs. Try http://www.qcc.sk.ca/~bguenter/distrib/procmail-maildir/ A better choice might be to use maildrop instead of procmail: http://www.flounder.net/~mrsam/maildrop/ Maildrop knows about Maildir natively, and is superior to procmail in a lot of ways. Chris
Re: Procmail and Maildir?
On Apr 28 1999, Andy Walden wrote: Is there anyway to fudge procmail into writing things to a Maildir? I would think that just giving each message a different name based on some variable that could be captured would work. Is anyone doing anything like this? Thanks, andy I use basically two ways: 1 - get a patched version of procmail with support for Maildir; 2 - let's say your username is user and that you want to write your messages to the ~/list Maildir. Then, forward each message (that you'd like to write in the maildir) to user-list and let qmail do the rest of the work, putting ./list/ in the file ~user/.qmail-list. Hope this helps, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ (still an) Ugrad. Comp. Science student - "Windows? Linux and X!" Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Procmail and Maildir?
Chris Johnson [EMAIL PROTECTED] writes: On Wed, Apr 28, 1999 at 09:23:47AM -0500, Andy Walden wrote: Is there anyway to fudge procmail into writing things to a Maildir? There are some patches available to make procmail deliver to maildirs. If you like procmail, and don't want to patch it, then I recommend safecat. You can download it at my web page: http://www.pobox.com/~lbudney/linux/software/safecat.html. Safecat takes stdin and writes it to a file in a Maildir, using the same algorithm as qmail. You can invoke it from procmail (patched or not) with a rule like: :0w |safecat $HOME/Maildir/tmp $HOME/Maildir/new With the 'w' flag, above, procmail+safecat should be as reliable as qmail itself. ~~~ Len Budney | There are many good reasons to ignore Maya Design Group | this cipher...So why bother with [EMAIL PROTECTED]| nitpicks about the code style? | -- Prof. Dan Bernstein ~~~
Re: Procmail and assign?
Andy Walden [EMAIL PROTECTED] wrote: How can procmail be used with an assign db? Each entry in assign points to a directory where qmail looks for .qmail files. Put the "| procmail" line in the appropriate file. -Dave
Re: procmail problem
+ "Adam D. McKenna" [EMAIL PROTECTED]: | Sorry to post is here, but I am getting tons of messages in my logs | that look like this: | | status: local 10/10 remote 4/20 | delivery 64: deferral: |procmail:_Out_of_memory/buffer_0:_"13739"/buffer_1:_""/preline:_fatal:_unable_to_copy_input:_broken_pipe/ | | There is over 200 megs of memory free, so I don't know why it would | be out of memory. I checked the queue, and there aren't any | messages larger than 200 megs.. There may be over 200M free, but that does not help if the per process limit is set lower. procmail is notorious for reading the entire message into memory. - Harald
Re: procmail problem
On Sun, 11 Apr 1999, Adam D. McKenna wrote: Sorry to post is here, but I am getting tons of messages in my logs that look like this: What does the .qmail file which is being used for the delivery contain? then the procmail fans can tell what's up... Richard
Re: procmail problem
nevermind, I fixed the problem. Thanks to everyone who responded so quickly. The problem was a (totally) screwed up /var/mail heirarchy, (permissions and ownership had been changed, pretty much randomly). I still can't figure out why procmail would give an out of memory error for that though. --Adam On Sun, Apr 11, 1999 at 06:12:57PM +0100, Richard Letts wrote: On Sun, 11 Apr 1999, Adam D. McKenna wrote: Sorry to post is here, but I am getting tons of messages in my logs that look like this: What does the .qmail file which is being used for the delivery contain? then the procmail fans can tell what's up... Richard
Re: Procmail type rules?
Is there a way to get the qmail-smtpd to use some form of delivery rules, similar to procmail 'recipies'? I am using IMAP and would like to filter the mail on the server when it comes in. I think you mean "Is there a way to get qmail-local to use some form of delivery rules," because you want the rules to happen on local delivery. The answer is pretty simple: it depends on what you want to do :-) If you really want, you can use procmail as your local delivery agent (see /var/qmail/boot/proc), but unless you want to do some heavy processing I think it would be a lot easier for you to use qmail's own .qmail files. Perhaps you can tell us exactly what you want, and we can try to help? Evan
Re: Procmail type rules?
What I am trying to do is filter incoming mail... for example, for mail coming in from the qmail mailing list, move the mail to the 'Qmail Mailing List' IMAP folder in my directory. Also the same type of rule for the RedHat mailing list, or for mail from a paticular person. Assuming you're using uw-imapd, the easiest way to do it is to subscribe to the list as (say) [EMAIL PROTECTED] and then create a file called: .qmail-qmail containing something like: ./mail/qmail This will write mail to [EMAIL PROTECTED] to an mbox file ./mail/qmail. I use this for the 20 or so mailing lists I'm on, and it works very nicely. There are other ways you can tackle this problem. In fact, I'm almost sure that someone just posted something about this, so you should check the list archives. Definitely check out dot-qmail(5), qmail-command(8) and condredirect(1). If you have any further questions you can mail me. Evan
