gmane.mail.procmail

Beginner help

tolga — 2008-08-26T12:45:33

Hi, I am trying to start using procmail again, so please bear with my questions :) I have "|IFS=' ' && exec /usr/bin/procmail || exit 75 #tolga" in my .forward and LOGNAME=/var/log/procmail.log :0 * ^From.*mtozses< at >sabanciuniv.edu * ^Subject:.*compilers test in my ~/.procmailrc. I can't receive any e-mail that is from mtozses< at >sabanciuniv.edu and with the subject compilers. I mean, I don't receive it but it's not rejected either. How can I make it work? Also, logging is not done either. Regards,

padding a string

Nigel Allen — 2008-08-25T10:16:17

Hi I'm struggling with a procmail recipe - as a complete newbie to procmail I should add. Basically the pseudo code for what I want is as follows: extract string from header. if length($string) < 6 pad $string left spaces to 6; if test -d $string file the email into the folder $string else forward to bad_folders alias; What I have so far is: :0 * ^X-My-Header:[ \t]*\/$ { STRING=${MATCH} :0 * ? test ! -d $MATCH { ! bad_folder } $MATCH } I've managed to fudge my way so far with lot's of help from the Search Engine Gods, but I'm stuck on the "pad" problem. I know I could write this as a shell script or a perl snippet and then pipe the value of the variable out to it but how do I get it back in again (or alternatively how do I do it within procmail? P.S. I'll also happily accept any criticism, suggestions or advice. TIA Nigel

procmail and postfix aliases

Andreas Moroder — 2008-08-25T07:54:39

Hello, is it possible to use procmail to filter who can send a mail to a postfix alias ? Thanks Andreas

Procmail filter sometimes failed...

josias gonçalves — 2008-08-19T15:47:48

Hi for all, In my procmailrc i have this lines in the file. :0 H *^Content-type: (multipart/mixed) { :0 B *^Content-Disposition: (attachment|inline) *filename=".*\.(ocx|ade|adp|bas|bat|chm|cmd|com|cpl|crt|dll|exe|eml|hlp|hta|htt|inf|ins|isn|isp|js|jse|lnk|mdb|mde|msc|msi|msp|mst|pcd|pif|reg|sc|scr|sct|shb|shs|vb|vbe|vbs|pps|pptx|ppsx|ppt|wsc|wsf|wma|wmv|avi|mp3|mp4|mpeg|mpg|mov|qiv|asf|mpe|wsh)" { :0 /var/mail/attach } } if something attach is found, the e-mail will to /var/mail/attach so, some e-mails, like one today (one with pps extension), pass trought this rule. is something wrong ? with this rule... thanks.

recipe suddenly failing

Robert Holtzman — 2008-08-17T06:50:43

Running procmail v3.22 2001/09/10 on ubuntu 8.04. The following recipe has been unchanged and working well since I ran RedHat 7.3 (yeah, *that* long) until yesterday. :0 c /home/holtzm/mail/backup :0 ic | cd /home/holtzm/mail && rm -f dummy `ls -t msg.* | sed -e As of now it no longer delivers any copies to my backup file, even tho I have received 600+ emails in the last day or two. As an experiment I tried :0 c: /home/holtzm/mail/backup which didn't work either. What completely snows me is why after working all these years, would it suddenly give up the ghost. Any help, pointers, suggestions appreciated.

Which grep match?

Scott Moseman — 2008-08-13T20:53:42

Let's start from this very basic grep recipe... * ? formail -x Subject: | fgrep -is -f /etc/procmail/subjects.txt I will know it matched an entry in the file, but I will not know *which* entry (from subjects.txt) was matched. Is there an *easy* way to process this type of query *and* get the match output? I suppose in a worst case I could pipe to a script and go through the subjects.txt file line by line looking for a match, but there must be an easier way? My goal is that I desire to start collecting a "hit count" on the matches, so I see which ones are matched often and which ones are rarely matched, if ever. Thanks, Scott

Add X-Header to see which filter greps

Remien, Carsten — 2008-08-08T07:06:39

Hi, I would like to see, which procmail filter has moving my mail to a special IMAP folder. Is it possible to set a X-Header in each filter? Or is there any other soultion? Regards, Carsten

Mailing list handler

Jake Di Toro — 2008-08-05T18:01:16

Didn't see this come through, appoligies if this is posted twice: I've had some recent changes to my mail handling and wanted to streamline some more. Dug through the archives for the mailing list handlers and came up with this as the latest: http://www.xray.mpe.mpg.de/mailing-lists/procmail/2007-11/msg00028.html Was wondering is a) there's been any "upgrades" in the last 9ish months, and b) if anyone had a file available for download as the archive has munged up a few lines etc. I'm sure with a little testing I'd work out the kinks, but it might be eaiser to have a clean copy to start testing with.

dynamci filters

George Crum — 2008-07-30T22:39:29

Calling all procmail gurus here. I have searched and can not find any info on how to do this and I'm not sure if this is something that procmail can handle. I would like to setup a filter that would catch a subject line that has 2 variations, but change where the email will be forwarded to depending on this subject it matches. 1. All emails are forwarded to email-address1. 2. Receive email with "Subject: PROBLEM ..." for the first time, forward to email-address1. Any consecutive times afterwards I want to forward the email to email-address2. 3. When email with "Subject: RECOVERY..." is received I want the email to go to email-address1 and change the filter for "Subject: PROBLEM ..." back to forwading to email-address1. Is this possible with procmail? -george

help with procmail rules

Adam Williams — 2008-07-29T14:59:50

I have a user, rmiller< at >mdah.state.ms.us who wants all of his To: and Cc: email to go to his millerono< at >gmail.com as well as keeping a copy of the email on our mdah.state.ms.us mail server in his inbox. However, when he sends mail from millerono< at >gmail.com he will Bcc: the email to rmiller< at >mdah.state.ms.us so that we have a a copy of his email. Are the following procmail rules below correct to accomplish this? :0: * $ ^Bcc:.*rmiller< at >mdah.state.ms.us ${DEFAULT} :0 * ^Cc.*rmiller< at >mdah.state.ms.us { :0c ! millerono< at >gmail.com :0 ${DEFAULT} } :0 * ^To.*rmiller< at >mdah.state.ms.us { :0c ! millerono< at >gmail.com :0 ${DEFAULT} }

procmail X-Recipient:

josias gonçalves — 2008-07-28T17:58:33

____________________________________________________________ procmail mailing list Procmail homepage: http://www.procmail.org/ procmail< at >lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

new recipe filter...

Jim Seavey — 2008-07-26T18:17:26

Hi, I have several users who receive email from one or more specific person(s) who think it is their appointed task in life to send out the absolute largest email's that they possibly can. The vast majority of the stuff that is sent are jokes and other such trivia. All email on our system is filtered using procmail to remove spam. We have a global archiving of a copy of each incoming email that is the first thing that happens in the global procmail process. The second thing the global procmail process does is send large email's directly to the users default incoming mail box; larger being greater than 2MB so they do not cause procmail problems. The following is the filter to move large email's into the users home directory. :0 f * > 2048000 | ${FORMAIL} -A"X-Note: Oversize/Not Filtered" Works a treat. This recipe is run prior to the individual users procmail recipes. I would like to be able add a condition to this recipe that allows me to include specific From: email addresses that will send the large email being sent by specific email addresses to /dev/null and any others to be sent to the users default mail box. This way I can police the continual offenders who eat up disk space with this type of stuff. How do I code this? I already remove the messages on a daily basis from the users backup file based on the From: email address. This may sound Draconian to some but we do not have the luxury of allowing this kind of stuff eat up disk space; especially when people are out of the office and do not check their email for some time. Thanks. Jim

"cannot determine current working directory" Error

Matthew G. Saroff — 2008-07-25T13:19:11

I get a cannot determine current working directory" in my log. Procmail works fine, but it's kind of annoying. Here are some excerpts of the log file in question: ================================================================= procmail: Executing " cat - $BACKGFILE | formail -${maxgbackup}s > $TEMPGFILE ;\ mv -f $TEMPGFILE $BACKGFILE" sh: Cannot determine current working directory procmail: Executing " (formail -xFrom:) | fgrep -i -f $HOME/Procmail/jobs" sh: Cannot determine current working directory procmail: Executing " (formail -xFrom:) | fgrep -i -f $GOLIST" sh: Cannot determine current working directory ================================================================= I'm missing something apparently.

Getting the MATCH

Skip — 2008-07-22T03:45:18

I want to save the match from the following recipe, but this obviously isn't working. Any ideas of a way to fix it? I know I need to use the \/ operator, but I don't know where to put it in this type of expression. FGREP=/bin/grep IPBLACKLIST=/home/peloruso/ipblacklist FORMAIL = /usr/bin/formail FROM=`$FORMAIL -x"From" -x"From:" -x"Reply-To:" -x"Received:" -x"Return-Path:"` :0fw:ipblacklist.lock * ? (echo "$FROM" | $FGREP -i -f $IPBLACKLIST) | $FORMAIL -A "X-IP-Blacklist: Mail originated from a previous source of spam--$MATCH" Skip

Recipe not working

Rem P Roberti — 2008-07-21T22:01:45

Hi Everyone... I wrote this recipe hoping that it would take care of the silly email that you get from folks---you know, they think they have a funny joke and decide to send it to four hundred of their closest friends. Anyway, here is the recipe: :0 * ^(To|Cc):.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at >.*< at > /dev/null To my thinking, if either to or cc contains more than 12 < at >s then it should delete the post. But it doesn't. What am I doing wrong? Rem

Cyrus and procmail

Steve Webb — 2008-07-21T20:51:27

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. I just switched our company over to Cyrus pop/imap recently and I've found an issue where procmail is not detecting the "From" header properly and even in the log file, procmail is getting confused. I think that it's mis-interpreting the "Return-Path:" header as the "From:" header. Is there a way to have procmail be smarter about the From: header? Currently, all emails now get processed as if they're from "cyrus< at >mail". Is this a known problem? Should I be contacting the Cyrus people about this instead? - - Steve - -- Steve Webb - Lead System Administrator for Pronto.com Email: swebb< at >pronto.com (Please send any work requests to: rt< at >pronto.com) Cell: 303-564-4269, Office: 303-497-9367, YIM: scumola -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFIhPbPbhtJr2D5JAsRAtlEAJ4vWajakNGf1i0LxV2ZfB/hexyTQgCdFbZK cBT4tHHQ4Qky08ZRtRDS6e0= =Rqcj -----END PGP SIGNATURE-----

Need to clear out inbox with procmail

Nathan Brown — 2008-07-21T17:53:57

Is this list active?

Alex Rodriguez — 2008-07-21T17:25:08

procmail and user's mail-file permissions

Alex Rodriguez — 2008-07-18T22:52:01

expiring SPAM in Maildirs?

LuKreme — 2008-07-15T16:14:55

Not sure where to post this, so thought I'd start here. I have a postfix server with virtual (mysql) users who use maildir. I have procmail working for those users, and one of the things procmail does is filter out the spam and put it in a .SPAM maildir. Trouble is, some users never check this folder, and I've a couple where the .SPAM is over a gig in size, and growing. What I would like to do is figure out some way to auto-delete messages in there that are, say, 30 days old or older.

"mailbox as soft link" problem

Markus Krause — 2008-07-09T12:45:08