| Summary | bug with procmail forwarding recipe |
| Queue | Ingo |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | tim (at) sig (dot) msstate (dot) edu |
| Created | 08/13/2008 (6169 days ago) |
| Due | |
| Updated | 12/30/2014 (3839 days ago) |
| Assigned | 03/30/2011 (5210 days ago) |
| Resolved | 12/30/2014 (3839 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
Version ⇒ Git master
Milestone ⇒
Taken from Matt Selsky
State ⇒ Feedback
mostly see large code segments simply being commented out, which rings
an alarm for me.
New Attachment: procmail.patch
58: ##### DEAKTIVIERT: Weiterleitung #####
59: # :0 cw
60: # {
61: # :0 c
62: # * !^(From|Sender|X-Envelope-From):.*(Postmaster|MAILER-DAEMON)@
63: # * !^X-Loop: to-test@gmail.com
64: # | formail -A"X-Loop: to-test@gmail.com" | $SENDMAIL -oi
test@gmail.com
65: # :0 c
66: # * !^(From|Sender|X-Envelope-From):.*(Postmaster|MAILER-DAEMON)@
67: # * !^X-Loop: to-test@gmx.at
68: # | formail -A"X-Loop: to-test@gmx.at" | $SENDMAIL -oi test@gmx.at
69: # :0
70: # /dev/null
71: # }
kind regards
State ⇒ Stalled
Can anybody using Procmail provide a real solution/patch?
State ⇒ Feedback
to in order to get it to work?
quick work around). Bottom was Ingo generated.
##### Forward All #####
:0 D
* ^Received: .
! forwarded@email.com
##### Forwards #####
:0
{
:0
*$ ! ^From *\/[^ ]+
*$ ! ^Sender: *\/[^ ]+
*$ ! ^From: *\/[^ ]+
*$ ! ^Reply-to: *\/[^ ]+
{
OUTPUT = `formail -zxFrom:`
}
:0 E
{
OUTPUT = $MATCH
}
:0 c
* !^FROM_MAILER
* !^X-Loop: to-forwarded@email.com
| formail -A"X-Loop: to-fforwarded@email.com" | $SENDMAIL -oi -f
$OUTPUT forwarded@email.com
:0 E
$DEFAULT
:0
/dev/null
}
State ⇒ Feedback
in order to get it to work?
State ⇒ Assigned
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ bug with procmail forwarding recipe
Type ⇒ Bug
correctly in all cases. I was forwarding an e-mail address to gmail
and the confirmation e-mail wasn't forwarded. See the logs below. As
a work around, I just built a regular recipe.
procmail: [15047] Wed Aug 13 16:45:38 2008
procmail: No match on "^BestServHost: crater\.dragonflybsd\.org"
procmail: No match on "^Sender: horde-"
procmail: No match on "^Subject: Logwatch for"
procmail: No match on "^Subject: rsnapshot hourly"
procmail: No match on "^List-Id: rsnapshot discussion"
procmail: No match on "^Subject: Cron"
procmail: No match on "^Subject: DenyHosts Report from"
procmail: No match on "^Subject: Virus Detected"
procmail: No match on "^From: .MailScanner"
procmail: No match on "^Sender: AirSet"
procmail: No match on "^X-Spam-Status: Yes"
procmail: Assigning "MATCH="
procmail: Matched "xxxxxxxxxx+gmcfv4790c0e5c2cb0154@gmail.com"
procmail: No match on ! "^From *\/[^ ]+"
procmail: Assigning "OUTPUT=xxxxxxxxxx+gmcfv4790c0e5c2cb0154@gmail.com"
procmail: No match on !
"(^(((Resent-)?(From|Sender)|X-Envelope-From):|>?From )([^>]*[^(.%
@a-z0-9])?(Post(ma(st(er)?|n)|office)|(send)?Mail(er)?|daemon|mmdf|n?uucp|ops|r(esponse|oo
t)|(bbs\.)?smtp(error)?|s(erv(ices?|er)|ystem)|A(dmin(istrator)?|MMGR))(([^).!:a-z0-9][-_a
-z0-9]*)?[%@> ][^<)]*(\(.*\).*)?)?$([^>]|$))"
procmail: Assigning
"LASTFOLDER=/home/tim/Maildir/new/1218663938.15047_0.xxxxx.xxxxx.com
"
procmail: Notified comsat:
"tim@0:/home/tim/Maildir/new/1218663938.15047_0.xxxxx.xxxxx.com"
From xxxxxxxxxx+gmcfv4790c0e5c2cb0154@gmail.com Wed Aug 13 16:45:38 2008
Subject: Gmail Confirmation - Send Mail as tim@xxxxx.xxxxx.com
Folder: /home/tim/Maildir/new/1218663938.15047_0.xxxxx.xxxxx.com 4134