http://blog.gmane.org/gmane.mail.procmail hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.mail.procmail/48118 <pre>Hi procmail&lt; at &gt;lists.RWTH-Aachen.de cc: bunsen&lt; at &gt;rz.rwth-aachen.de, Stefanie Scholten &lt;steffi&lt; at &gt;informatik.rwth-aachen.de&gt;, webmaster&lt; at &gt;www.procmail.org In http://www.procmail.org/era/lists.html Please Remove Obsolete references to procmail-request&lt; at &gt;informatik.RWTH-Aachen.de &amp; replace with reference to https://mailman.rwth-aachen.de/mailman/listinfo/procmail Thanks to Stefanie postmaster&lt; at &gt; Aachen who indentified the old address was overflowing &amp; obsolete &amp; will be deleted. Cheers, Julian </pre> Julian H. Stacey 2013-06-14T16:07:28 http://comments.gmane.org/gmane.mail.procmail/48114 <pre> Is there any method for having line numbers and script filenames printed in the procmail log files. Avoid brute force method of multiple LOG="foo" invocations. -- Eric Smith </pre> Eric Smith 2013-05-04T15:10:54 http://comments.gmane.org/gmane.mail.procmail/48113 <pre>I know we covered this several times many years ago, but at the time my solution was "If it's to my list account and it's not from a list, discard it" Sadly, that is no longer an option, so I need a way to do the following: If a message is TO me and ONLY to me, file it. If a message is to me and ALSO to a list, file it somewhere else (possibly /dev/null :) If a message is NOT to me, treat it as a list message (that is, let it fall through) I have all the recipes in place to deal with the list messages. I though that maybe this,a after all list processing might work: :0 * 9876543210^1 ! X-Original-To:.*kremels&lt; at &gt;kreme.com * 9876543210^1 ! TO_kremels&lt; at &gt;kreme\.com { TRAP='mv "$LASTFOLDER" "${LASTFOLDER}:2,S"' :0 .not-to-me/ } Which should let all the mail that is addressed to my list account fall through to $DEFAULT (the InBox) right? </pre> LuKreme 2013-03-06T18:44:30 http://comments.gmane.org/gmane.mail.procmail/48111 <pre>Hi all, I've been using Procmail for a bunch of years for various reasons. Currently I'm using it as an enterprise tool using a faceless account instead of a real user's account. We've tightly integrated Procmail with our support desk ticketing system. Messages come from various internal and external distribution lists, automated processes, faceless accounts, web based forms, and various IT devices. Based on our rules, we generate tickets that are auto-routed in the ticketing system pre-defined users/groups. Some messages get tickets, some get deleted etc. With this in mind, I have a couple questions for the group here. 1. Procmail seems to be typically used or end users to manage their own mail. I haven't really run across any sites discussing it being used in this way. Is this a novel approach or have others gone down this path before? It seems that with the way most folks use email today (not from a shell), using Procmail in this way may give it more value and exposure than it's had in the past. </pre> Peters, Ron 2013-02-01T19:04:53 http://comments.gmane.org/gmane.mail.procmail/48099 <pre> I got an email today with this paragraph in it: *** These new “post-Panamax” ships are the length of aircraft carriers. of the Lincoln Memorial. The ships can carry as many as 12,000 containers, or about a million flat-screen TVs. *** As you can see, the "From" is escaped. I'm not sure why this continues to happen, and it happens on an email that is delivered without a .procmailrc, which makes me think the issue is in the default procmailrc. The only part that modifies the original message is the formail to add the X-Hostname header. cat /usr/local/etc/procmailrc DATE=`date '+%Y%m%d%H%M%S'` LOGFILE=/var/log/procmail LOGABSTRACT=NO HOSTNAME=`hostname` NL=" " WS=" " :0c { :0 /backup/imap.backup/ } :0 { INCLUDERC=/usr/local/etc/furrin.rc LOG="SPAM:${NL} ${SPAMVAL}${NL} ${SPAMMISHNESS}${NL} ${SPAMNOTES}${NL}" } :0fw | formail -I"X-Hostname: $HOSTNAME" # from Sean B Straw # provide FROM_USER, FROM_DOMAIN, SUBJECT, TO, FROM, ENVTO, ENVFROM :0 { :0 * $ ^Subject:$</pre> LuKreme 2013-01-13T20:38:02 http://comments.gmane.org/gmane.mail.procmail/48095 <pre>I want all list mail to be saved to the appropriate list folder and if they match a pattern in a file, also save to $DEFAULT. This is what I am trying, multiple stanzas like these; :0: * ^x-mailing-list:([^ ]*\/\&lt;.*) { :0c $LISTDIR/`echo $MATCH|sed -e 's/[&lt; at &gt;\.&gt;].*//g' -e 's/.*[ &lt;]//' -e 's/.*://'` :0 * ? egrep -if /home/eric/serialised_subjects $DEFAULT } :0: * ^x-list:([^ ]*\/\&lt;.*) { :0c $LISTDIR/`echo $MATCH|sed -e 's/[&lt; at &gt;\.&gt;].*//g' -e 's/.*[ &lt;]//' -e 's/.*://'` :0 * ? egrep -if /home/eric/serialised_subjects $DEFAULT } The behaviour without the `c' in :0c is that the mail is only saved in the list dir. And with the `c' in :0c, the mail is saved MULTIPLE times in list dirs (as it matches more than one list regex condition) and one in the $DEFAULT. What would be the correct implementation? </pre> Eric Smith 2012-11-12T08:05:14 http://comments.gmane.org/gmane.mail.procmail/48090 <pre>How do I delete a folder before writing to it. Trying this but the folder `last' is not (apparently) written to :0c: { :0c: backup :0f | rm $MAILDIR/last :0: last } </pre> Eric Smith 2012-11-09T03:37:49 http://comments.gmane.org/gmane.mail.procmail/48088 <pre>I have blocks like these in my mailing list catcher INCLUDERC; :0: * ^list-post:([^ ]*\/\&lt;.*) { :0c $LISTDIR/`echo $MATCH|sed -e 's/[&lt; at &gt;\.&gt;].*//g' -e 's/.*[ &lt;]//' -e 's/.*://'` :0 * ? egrep -if /home/eric/serialised_subjects $DEFAULT } :0: * ^Mailing-list:([^ ]*\/\&lt;.*)&lt; at &gt; { ... When the mail matches the condition above the block, the block commands are processed but the problem is that procmail does not exit at this point but continues to the next condition. How could I change this behaviour? </pre> Eric Smith 2012-11-08T22:05:04 http://comments.gmane.org/gmane.mail.procmail/48080 <pre>I find it very sloppy that people send files attached to email, and I've always been disturbed that the available tools organize them poorly. When an email arrives with an attachment, sometimes the attachment should be deleted but not the message, or vice-versa. So it does not make sense to have files embedded inseperably with a message. Nor does it make sense to have multiple copies (one in the email, and the other saved separately). What do expert procmail users do? All files should probably be extracted as messages arrive, and be placed in a proper filesystem. The MIME object should then be removed from the message, but there should be a reference to the file on the filesystem. There should also be a back-reference from the file to the message, so that the linkage can be maintained when the file is moved or renamed. Seems like a job for procmail. </pre> Mike's unattended mail 2012-10-20T12:09:58 http://comments.gmane.org/gmane.mail.procmail/48077 <pre> Any stand alone DKIM programs for verification in ~/.procmailrc? Thanks, John </pre> John Conover 2012-10-10T00:17:11 http://comments.gmane.org/gmane.mail.procmail/48071 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On a new server I have ascertained that fetchmail is working. Dovecot is also working. Procmail isn't. I can't find anything to suggest that procmail actually sees the messages, so I assume that ~/.forward is the problem. Could someone please point out the things that I haven't checked? ls -l ~/.forward - -rw-r--r-- 1 anne anne 18 Sep 28 12:16 /home/anne/.forward cat ~/.forward |/usr/bin/procmail ls -al ~/.procmailrc - -rw-r--r-- 1 anne anne 1099 Sep 28 16:05 /home/anne/.procmailrc cat ~/.procmailrc PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin #Set user variable USER=`anne` #Set user Inbox directory MAILDIR=/home/anne/Maildir/ DEFAULT=$MAILDIR/ #Set logfile LOGFILE=/home/anne/pm.log VERBOSE=YES LOGABSTRACT=YES # LOG=" " :0 * ^From:.*magnatune $MAILDIR.INBOX.Magnatune/ .... * ^List-ID:.*procmail ${MAILDIR}.INBOX.MailSystems.Procmail/ The logfile ~/pm.log is not being written to. Where do I look next? Anne -----BEGIN PGP SI</pre> Anne Wilson 2012-09-28T16:30:18 http://comments.gmane.org/gmane.mail.procmail/48063 <pre> Does anyone have a recipe (patch?) for logging Date From To and CC when LOGABSTRACT is set?? steve -- </pre> rader< at >hep.wisc.edu 2012-09-12T13:10:50 http://comments.gmane.org/gmane.mail.procmail/48061 <pre>Hello all, I am trying to recover from a catastrophic system failure in which I also lost my backups (don't ask!). Before I attempt to bring my mail-chain back on line I wanted to recreate my procmail rules, and before I did that i wanted to test them. I have used Sean B. Straw's sandbox, and have as yet no /etc/procmailrc or even a $HOME/procmailrc. All I have is the sandbox.rc file and the recipe I am currently trying to test (the one that sorts my many mailing lists). I have fallen at the first hurdle. The recipe correctly identifies the correct mailing list, but then fails to write it to the mbox file in the testing area: =================8&lt;============================================================ procmail: Match on "^List-Id:.*mod-security-users" procmail: Locking "MLists/Mod-Security.lock" procmail: Error while writing to "MLists/__g.YRNOQB.mydomain.org" procmail: Terminating prematurely whilst waiting for lockfile "" From mod-security-users-bounces&lt; at &gt;lists.sourceforge.net Sat Aug 25 14:34:16 201</pre> Arthur Dent 2012-08-25T13:47:34 http://comments.gmane.org/gmane.mail.procmail/48050 <pre> Has anyone devised a recipe for checking to see if there is some match between the Received: header(s) and the From: and From headers? This could give a score to mail which could make a good contribution to filtering UCE. Thanks for any suggestions. Eric Smith </pre> Eric Smith 2012-07-26T12:15:05 http://comments.gmane.org/gmane.mail.procmail/48046 <pre>I'm trying to send an autoreply to senders who leave the Subject: field of their message blank, telling them that my server rejects messages with blank subjects (because in my experience, such no-subject messages are either spam or not worth reading). The autoreply works fine in test sends from Yahoo and from a mail client, but when I send from another host's webmail, I don't get the autoreply message. There is no spam folder on the webmail, so that's not the problem. I verified that I can send normal mail directly to the webmail, so I know the webmail is working properly. The procmail logs show that the autoreply was sent, but I notice that the logfile lines are in a different order than for the case in which the autoreply was received. (In the case where the autoreply wasn't received, "Folder:" precedes "Executing"). That's the only clue I have as to why messages from two different senders get the autoreply while messages from a webmail don't get the autoreply. Here are the logs and code: ---------</pre> Michael Bluejay 2012-07-24T15:31:46 http://comments.gmane.org/gmane.mail.procmail/48044 <pre>What are the best parameters to use with formail to force any piece of email to get enough proper headers on it so spamassassin catches the email when it goes into the probably-spam folder? I want to pass all incoming email through formail with these parameters first. Then if it's webmail that's just arrived I'd like to detect that and run it through lynx so lynx strips out the html and leaves it in a form alpine can read correctly. The system I use put a sample .procmailrc spamassassin file in my directory and I'm wondering when if at all any of that should be enabled and in what sequence with respect to the rest of what I want to do. ---------------------------------------------------------------- Windows Pants: made entirely of patches on patches each with a picture of a Microsoft Vacuum Cleaner; a computer mouse, or a dollar sign. Jude &lt;jdashiel-at-shellworld-dot-net&gt; &lt;http://www.shellworld.net/~jdashiel/nj.html&gt; </pre> Jude DaShiell 2012-07-04T17:58:04 http://comments.gmane.org/gmane.mail.procmail/48044 <pre>What are the best parameters to use with formail to force any piece of email to get enough proper headers on it so spamassassin catches the email when it goes into the probably-spam folder? I want to pass all incoming email through formail with these parameters first. Then if it's webmail that's just arrived I'd like to detect that and run it through lynx so lynx strips out the html and leaves it in a form alpine can read correctly. The system I use put a sample .procmailrc spamassassin file in my directory and I'm wondering when if at all any of that should be enabled and in what sequence with respect to the rest of what I want to do. ---------------------------------------------------------------- Windows Pants: made entirely of patches on patches each with a picture of a Microsoft Vacuum Cleaner; a computer mouse, or a dollar sign. Jude &lt;jdashiel-at-shellworld-dot-net&gt; &lt;http://www.shellworld.net/~jdashiel/nj.html&gt; </pre> Jude DaShiell 2012-07-04T17:58:04 http://comments.gmane.org/gmane.mail.procmail/48029 <pre> Hi, How it is possible to detect (and filter) an email written in Japanese characters (which I cannot read anyway)? The content-Type specifies charset="utf-8". The "From" field is apparently invalid, and may not necessarily contain .jp Regards, Konstantin. </pre> Konstantin 2012-05-21T18:59:41 http://comments.gmane.org/gmane.mail.procmail/48020 <pre>Hi guys, Is it possible to play a soundfile when procmail encounters mail from a certain e-mail address? Thank You Danny </pre> Danny 2012-04-17T19:27:32 http://comments.gmane.org/gmane.mail.procmail/48019 <pre>I have the following procmail recipe to auto-respond upon certain criteria. The recipe "works" in the way to match and to send reply email; however the sent email only has mail header without mail body (empty), that I could not get it why mail body is "not formed" or "not sent": SUBJADDR =`formail -xSubject: |perl -pe 's/.*sub.*\s+([^\s]+\&lt; at &gt;[^\s]+)/$1/sg;s/^\s+//g;s/\s+$//g;'` HISTMARK = `date +"%s"` :0 * ^TO.*watchdog&lt; at &gt;my.domain | (formail -i"Subject: Confirmation needed" \ -I "To: $SUBJADDR"; \ echo " "; \ echo " "; \ echo "Confirmation mark: $HISTMARK") | $SENDMAIL -oi $SUBJADDR I tried single or double 'echo " ";' lines to leave 1 or 2 space lines between mail header and body - that makes no difference. Any suggestion would be appreciated. Zhiliang </pre> Zhiliang 2012-02-09T20:32:22 http://comments.gmane.org/gmane.mail.procmail/48014 <pre>I’m thinking about taking a run at organizing, really organizing, all the procmail recipes for my several email accounts. I have, needless to say, code that is shared, duplicated, or nearly duplicated across my 4 primary accounts,a bout a half-dozen secondary accounts, and then a portion of that code is shared over to most of the user accounts on the system. Before I got started, I wanted some recommendations on how, exactly to go about this. I was considering something along these lines, with * items being things the are already done. * procmailrc file with basic variable extraction, mail backup * hand off processing to .procmailrc if user has one, otherwise process for spam In .procmailrc call external basicrc file for all users to process list messages, + addressing, and set default delivery locations (like .$ARG/ or .SPAM/) process local rc files (~/.procmail/.*rc) call a deliveryrc file that actually delivers the mail and logs to user’s log file (~/logs/pm.10-11-2011.log) I figure the deli</pre> LuKreme 2011-11-09T20:13:39 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.procmail