gmane.mail.procmail

adding a missing Date: header

A. Lester Buck III — 2008-10-03T18:56:05

For obscure reasons, the Dilbert.com daily strip email does not include a Date: header. (It does include Delivery-date:, but I haven't tracked down where that is being added.) When I sort the folder by date, mh-e complains about unreadable dates, so I decided to add the date to any message missing that header in procmail. I didn't want to calculate the date string unless the Date: header was missing, so this is what I came up with: # Generate any missing Date: header :0 * ! ^Date: { :0 { DATE_=`ruby -e "require 'time'; print Time.now.rfc2822"`} :0 fhw: | formail -a "Date: ${DATE_}" -a "X-Date: added date header" } While this does add a Date: header to any message without it, it also ends up being evaluated as a delivering recipe. I've fiddled with it in different ways and I haven't been able to make it into a non-delivering recipe. Could someone fix this so it doesn't deliver? I really thought this would be a FAQ, but I couldn't find an example of calculating a value and inserting it into

Little doubt on receipts.

JoeL — 2008-10-03T08:37:09

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

Procmail stopped working? - update

Tolga — 2008-10-02T18:48:11

I just found out this in mail.log: Suspicious rcfile "/home/tolga/.procmailrc" -------- Orijinal Mesaj -------- Konu: Procmail stopped working? Tarih: Thu, 02 Oct 2008 20:44:20 +0300 Kimden: Tolga ozses.net> Kime: procmail< at >lists.RWTH-Aachen.DE Hi, I have the following recipes: LOGFILE = "procmail.log" MAILDIR = /var/mail/folders/tolga :0 * ^From.*procmail-bounces< at >lists.RWTH-Aachen.DE Procmail :0 * ^Sender.*kvirc-bounces< at >lists.omnikron.net KVIrc :0 * ^From.*noreply< at >couchsurfing.com * ^Subject:.*[CS msg:*\] { :0c CS :0 ! gokce.ozses< at >nielsen.com } :0 * ^From.*errors< at >hospitalityclub.org { :0c: HC :0 ! gokce.ozses< at >nielsen.com } :0 * ^From.*fatura< at >smileadsl.com * ^Subject:.*Smile Fatura ! tatlimcik< at >hotmail.com :0 * ^Subject:.*Anacron* /dev/null and the following .forward file: "|IFS=' ' && exec /usr/bin/procmail || exit 75 #tolga" But it suddenly stopped working. I don't know why. It just doesn't log, it just doesn't filter. Can you help me with that?

Intermittant procmail error

Kai Schaetzl — 2008-10-02T18:31:52

Hello, I haven't posted to the list for years, but I've now hit a problem with procmail that I can't find a fix for. I've been plagued by this obscure problem with one of my procmail recipes for a long time and thought it might have something to do with the old software/OS it was running on (SuSE 9.0, procmail 3.15.1). I just moved the script over to a newer OS (CentOS 5.2, procmail 5.22) and experience the same problem there :-( I hope that someone on this list can finally help me find the problem. The script takes a mail from a monitoring server (bigsister) as input and produces an output in the correct API format for an SMS provider and sends it to them. This has been working for years, I don't remember how long. However, after a while I recognized that I'm not getting all SMS that I should. Eventually I found out that on some of the mails an error happens and procmail "recovers" and sends the unprocessed mail body out. I tried quite a few changes (for instance I first catted most of the body

Procmail stopped working?

Tolga — 2008-10-02T17:44:20

Hi, I have the following recipes: LOGFILE = "procmail.log" MAILDIR = /var/mail/folders/tolga :0 * ^From.*procmail-bounces< at >lists.RWTH-Aachen.DE Procmail :0 * ^Sender.*kvirc-bounces< at >lists.omnikron.net KVIrc :0 * ^From.*noreply< at >couchsurfing.com * ^Subject:.*[CS msg:*\] { :0c CS :0 ! gokce.ozses< at >nielsen.com } :0 * ^From.*errors< at >hospitalityclub.org { :0c: HC :0 ! gokce.ozses< at >nielsen.com } :0 * ^From.*fatura< at >smileadsl.com * ^Subject:.*Smile Fatura ! tatlimcik< at >hotmail.com :0 * ^Subject:.*Anacron* /dev/null and the following .forward file: "|IFS=' ' && exec /usr/bin/procmail || exit 75 #tolga" But it suddenly stopped working. I don't know why. It just doesn't log, it just doesn't filter. Can you help me with that?

Problems with whitespace characters in procmail

Todd A. Jacobs — 2008-10-02T00:20:15

I want to use printf to use octal or hex characters to avoid ambiguity in a whitespace character class inside a procmailrc, but the following rule is not triggering: #SPC_CHAR=`printf \\\\040` #TAB_CHAR=`printf \\\\011` SPC_CHAR=`printf \\\\x20` TAB_CHAR=`printf \\\\x9` WHITESPACE="[${SPC_CHAR}${TAB_CHAR}]" :0 * ^Subject: Foo${WHITESPACE}bar { :0fW |formail -I "X-Local-Fubar: ${WHITESPACE}" :0: $DEFAULT } If I don't try to match against WHITESPACE in the recipe, then the character class appears to be passed along to formail just fine. What am I doing wrong here?

Adding to the body & forwarding

Shane — 2008-10-01T04:07:06

Hi All, I am effectively trying to add a string to an email body and forward the result. I am trying to stay within procmail/formail to do so if possible. I tried this: :0 | (formail -I "Subject: change" \ -I "To: test< at >test.com"; \ echo "change to $change") | $sendmail -t Here's what I observe: *Using formail - I To: as above didn't cause sendmail to send to that address *If I want to forward to several people I guess I can -I "To: email1, email2, email3 *I keep getting an error message (maybe because of the above) :executing echo - then the value of $change - then echo echo no such file or directory Thanks in advance for any thoughts. Shane

string search to exclude attachments

Nick Sharp — 2008-10-01T01:23:14

Forcing sendmail

Shane — 2008-09-27T15:23:24

Procmail and perl scripts

W. Thornton Martin — 2008-09-26T18:34:08

I want to call a perl script as a filter from procmail. The recipe is: #call perl filter :0f c |proctest.pl How do I pass the current mail document to proctest.pl and have proctest return information for Procmail to use? I would settle for a return code. Thank you Thornton

FROM_DAEMON on preventing loops

Skip Morrow — 2008-09-25T19:30:38

I am writing a recipe to forward mail to another account. Virtually every example I have seen includes use of the FROM_DAEMON conditional statement. Reviewing the recipe, it really looks to me that the real work is being done by the X-Loop: header being added. My question is, are the FROM_DAEMON (and FROM_MAILER) conditionals really necessary? :0 * ^TO_skip< at >pelorus\.org * !^FROM_DAEMON * !^FROM_MAILER * !^X-Loop: pelorus.org { :0fw | /usr/bin/formail -A "X-Loop: pelorus.org" :0c !skip.x.mobile< at >gmail.com } The reason why I ask is that I have seen some emails not get forwarded (namely from google itself, but they weren't in a loop) and I want to make sure that those conditionals aren't over aggressive and possibly prevent other emails from being forwarded. If all I am concerned about is looping, then couldn't I get rid of those two conditionals?

Problem on passing values from Procmail to Perl

Joyce Gutierrez — 2008-09-25T04:28:23

Changes on receipts

JoeL — 2008-09-24T08:25:20

two-language legal-mumbo-jumbo disclaimer footer

Richard Ball — 2008-09-23T16:27:03

Dallman, While I agree in principle, some of us don't have a choice about having this garbage appended to messages when we send them while we're working for our employer. Mine, for instance, blocks access to outside mail services so I couldn't even send from, e.g., gmail to get around the problem. No complaining to an IT dept. falls on anything other than deaf ears either. 'Tis a fact of corporate email life I'm afraid until such time as a strong legal precedence exists for the pointlessness of these disclaimers. Rich

Help with recipts.

Joel Serrano De Castro — 2008-09-23T15:18:24

Forcing permissions on mail files

Nigel Allen — 2008-09-23T03:01:35

Hi Having wrestled with procmail for the last few weeks, and with much appreciated assistance of this group, I have come up with the following recipe: and everything is perfect in the world. Except for one thing. All the mail messages that get put into $FLDR/ have the permissions set to 600 and I need them to be 660. I have set g+s on the Maildir and the Maildir/cur folder but it appears that procmail ignores this. Can anyone tell me what is the best way of having procmail create the messages as 660? I need them to be this way as they are shared folders with all users being members of the "group". Thanks and Regards Nigel.

Ammending Date-Time Stamps to a file

Shane — 2008-09-21T16:45:50

MarkMail search

Joe Smith — 2008-09-17T14:08:55

http://procmail.markmail.org very nice..

From list in a file

Joe Smith — 2008-09-17T03:56:13

I figured out my problem, sorry I jumped the gun. I swear I googled my eyeballs out for a while and was SO close.. but I tried again with a markmail search of this list and found an answer.

Appending FROM: headers only to a local file: Great Replies - Thanks.Why didn't my recipe work ??

Shane — 2008-09-16T03:39:25

changing MAILDIR not working[repost]

Robert Holtzman — 2008-09-16T00:49:06

Sent this the other day but it didn't show up. I am trying to change my MAILDIR from /var/spool/mail to $HOME/mail/ in ~/.procmailrc with no luck. Running "procmail -v" still shows Your system mailbox:/var/spool/mail/username This is in Fedora 9 and procmail 3.22. Google was no help and I went back a few years in the list archives with no hits. Any pointers appreciated.