<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="/h/themes/default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>bug with procmail forwarding recipe</title> 
  <pubDate>Thu, 23 May 2013 22:01:35 +0000</pubDate> 
  <link>http://bugs.horde.org/ticket/7201</link> 
  <atom:link rel="self" type="application/rss+xml" title="bug with procmail forwarding recipe" href="http://bugs.horde.org/ticket/7201/rss" /> 
  <description>bug with procmail forwarding recipe</description> 
 
   
   
  <item> 
   <title>The built-in forward recipe for procmail does not appear to </title> 
   <description>The built-in forward recipe for procmail does not appear to work 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 &quot;^BestServHost: crater\.dragonflybsd\.org&quot;

procmail: No match on &quot;^Sender: horde-&quot;

procmail: No match on &quot;^Subject: Logwatch for&quot;

procmail: No match on &quot;^Subject: rsnapshot hourly&quot;

procmail: No match on &quot;^List-Id: rsnapshot discussion&quot;

procmail: No match on &quot;^Subject: Cron&quot;

procmail: No match on &quot;^Subject: DenyHosts Report from&quot;

procmail: No match on &quot;^Subject: Virus Detected&quot;

procmail: No match on &quot;^From: .MailScanner&quot;

procmail: No match on &quot;^Sender: AirSet&quot;

procmail: No match on &quot;^X-Spam-Status: Yes&quot;

procmail: Assigning &quot;MATCH=&quot;

procmail: Matched &quot;xxxxxxxxxx+gmcfv4790c0e5c2cb0154@gmail.com&quot;

procmail: No match on ! &quot;^From *\/[^  ]+&quot;

procmail: Assigning &quot;OUTPUT=xxxxxxxxxx+gmcfv4790c0e5c2cb0154@gmail.com&quot;

procmail: No match on ! &quot;(^(((Resent-)?(From|Sender)|X-Envelope-From):|&gt;?From )([^&gt;]*[^(.%

@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]*)?[%@&gt;  ][^&lt;)]*(\(.*\).*)?)?$([^&gt;]|$))&quot;

procmail: Assigning &quot;LASTFOLDER=/home/tim/Maildir/new/1218663938.15047_0.xxxxx.xxxxx.com

&quot;

procmail: Notified comsat: &quot;tim@0:/home/tim/Maildir/new/1218663938.15047_0.xxxxx.xxxxx.com&quot;

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</description> 
   <pubDate>Wed, 13 Aug 2008 22:02:06 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t48180</link> 
  </item> 
   
  <item> 
   <title>Can you post the recipe that Ingo generated and what you cha</title> 
   <description>Can you post the recipe that Ingo generated and what you changed it to in order to get it to work?</description> 
   <pubDate>Fri, 29 Aug 2008 17:14:20 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t48567</link> 
  </item> 
   
  <item> 
   <title>Ping?</title> 
   <description>Ping?</description> 
   <pubDate>Fri, 12 Sep 2008 08:51:02 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t48878</link> 
  </item> 
   
  <item> 
   <title>&gt; Can you post the recipe that Ingo generated and what you c</title> 
   <description>&gt; Can you post the recipe that Ingo generated and what you changed it 

&gt; to in order to get it to work?



Top receipe is what I used (doesn't handle loops, I know, it was a 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&quot;X-Loop: to-fforwarded@email.com&quot; | $SENDMAIL -oi -f $OUTPUT forwarded@email.com

  :0 E

  $DEFAULT

  :0

  /dev/null

}

</description> 
   <pubDate>Sat, 13 Sep 2008 00:47:33 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t48900</link> 
  </item> 
   
  <item> 
   <title>Can anybody using Procmail provide a real solution/patch?</title> 
   <description>Can anybody using Procmail provide a real solution/patch?</description> 
   <pubDate>Mon, 13 Apr 2009 16:06:43 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t53627</link> 
  </item> 
   
  <item> 
   <title>Reposting, because email notifications didn't work:

Can any</title> 
   <description>Reposting, because email notifications didn't work:

Can anybody using Procmail provide a real solution/patch?

</description> 
   <pubDate>Thu, 16 Apr 2009 22:31:31 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t53719</link> 
  </item> 
   
  <item> 
   <title>I guess not.</title> 
   <description>I guess not.</description> 
   <pubDate>Tue, 18 Aug 2009 12:58:04 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t55355</link> 
  </item> 
   
  <item> 
   <title>I modified it as follows:

 58: ##### DEAKTIVIERT: Weiterl</title> 
   <description>I modified it as follows:

 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&quot;X-Loop: to-test@gmail.com&quot; | $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&quot;X-Loop: to-test@gmx.at&quot; | $SENDMAIL -oi test@gmx.at
 69: #   :0 
 70: #   /dev/null
 71: # }

kind regards
</description> 
   <pubDate>Tue, 15 Mar 2011 14:12:40 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t62326</link> 
  </item> 
   
  <item> 
   <title>Can you elaborate on your patch, what exactly it does any wh</title> 
   <description>Can you elaborate on your patch, what exactly it does any why? I mostly see large code segments simply being commented out, which rings an alarm for me.</description> 
   <pubDate>Wed, 30 Mar 2011 11:03:51 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/7201#t62843</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
