<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>procmail vacation not working on Centos 3</title> 
  <pubDate>Fri, 10 Apr 2026 07:55:26 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7052</link> 
  <atom:link rel="self" type="application/rss+xml" title="procmail vacation not working on Centos 3" href="https://bugs.horde.org/ticket/7052/rss" /> 
  <description>procmail vacation not working on Centos 3</description> 
 
   
   
  <item> 
   <title>Centos (RHEL) 3.x, sendmail 8.12.11-4.RHEL3.6, procmail 3.22</title> 
   <description>Centos (RHEL) 3.x, sendmail 8.12.11-4.RHEL3.6, procmail 3.22-10.el3.centos.0 (e.g., a stock Centos 3.9

Final machine).



User has setup a vacation message via ingo using the procmail driver, and using a time period.  (I have not

tested without the time period; should try that sometime).



Using the stock vacation procmail recipe, it sends no vacation messages.  The message is delieved

normally to the recipient.  The procmail log shows:



procmail: Executing &quot;formail,-rD,8192,/u1/demkov/.vacation.demkov&quot;

procmail: Non-zero exitcode (1) from &quot;formail&quot;

procmail: Rescue of unfiltered data succeeded

procmail: Non-zero exitcode (-11) from &quot;procmail&quot;



If I change the recipe from using &quot;0: Whaf&quot; to use &quot;0: Wha&quot; then the vacation message is sent properly, but

the recipient gets two copies of the message in their inbox.  This is preferable to not sending a vacation

message, but still not good...



I tried using Whafi, but it didn&#039;t seem to help (still got the errors shown above).



Any ideas what is wrong?</description> 
   <pubDate>Wed, 09 Jul 2008 20:40:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47411</link> 
  </item> 
   
  <item> 
   <title>Can you attach the generated procmailrc?  Or email me privat</title> 
   <description>Can you attach the generated procmailrc?  Or email me privately if it has sensitive info?</description> 
   <pubDate>Wed, 09 Jul 2008 21:05:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47415</link> 
  </item> 
   
  <item> 
   <title>http://www.stimpy.net/procmail/tutorial/vacation.html sugges</title> 
   <description>http://www.stimpy.net/procmail/tutorial/vacation.html suggests that we should be using Whc:.  Can you try that?</description> 
   <pubDate>Mon, 14 Jul 2008 00:42:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47500</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.97&amp;r2=1.98&amp;ty=u</description> 
   <pubDate>Mon, 14 Jul 2008 00:53:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47501</link> 
  </item> 
   
  <item> 
   <title>A very quick check seems to indicate this change is better b</title> 
   <description>A very quick check seems to indicate this change is better but still not right.  I regenerated the .procmailrc

script with the change, emptied the .vacation.* database, then sent two messages from myself to the user.



 First message triggered an auto-response which I got fine, second didn&#039;t.  That is as expected.  But

the user (with the .procmailrc)  received  duplicate copies of each message...



Maybe there is something specific to my site causing the duplication, I don&#039;t know.  But I do prefer it with

this change, than without.  Since I&#039;d rather have them get a duplicate of everything, than have no vacation

reply sent out.



But either something else in my setup isn&#039;t right (causing the duplicate), or something else in this script isn&#039;t

right (causing the duplicate).



I&#039;ll try to investigate more later, and post more when/if I figure out what is going on...</description> 
   <pubDate>Mon, 14 Jul 2008 19:42:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47517</link> 
  </item> 
   
  <item> 
   <title>Can you post procmail debug logs for the first and second me</title> 
   <description>Can you post procmail debug logs for the first and second messages with clean databases.</description> 
   <pubDate>Mon, 14 Jul 2008 20:26:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47519</link> 
  </item> 
   
  <item> 
   <title>Matt, can you please review this ticket?</title> 
   <description>Matt, can you please review this ticket?</description> 
   <pubDate>Mon, 28 Jul 2008 07:16:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47829</link> 
  </item> 
   
  <item> 
   <title>We&#039;re seeing double-delivery because the {}&#039;s are causing pr</title> 
   <description>We&#039;re seeing double-delivery because the {}&#039;s are causing procmail to fork another copy and we get a delivery at the end of both }.  We either need to deliver the inner } to /dev/null, which looks weird, or we eliminate the inner {}.  Which method is preferred?</description> 
   <pubDate>Wed, 30 Jul 2008 05:50:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47904</link> 
  </item> 
   
  <item> 
   <title>I went with the /dev/null method for now.  Can you try this </title> 
   <description>I went with the /dev/null method for now.  Can you try this out?</description> 
   <pubDate>Wed, 30 Jul 2008 06:00:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t47905</link> 
  </item> 
   
  <item> 
   <title>Ping?</title> 
   <description>Ping?</description> 
   <pubDate>Thu, 14 Aug 2008 22:47:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48202</link> 
  </item> 
   
  <item> 
   <title>This patch doesn&#039;t apply to CVS HEAD.</title> 
   <description>This patch doesn&#039;t apply to CVS HEAD.</description> 
   <pubDate>Mon, 18 Aug 2008 09:35:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48259</link> 
  </item> 
   
  <item> 
   <title>Try this.</title> 
   <description>Try this.</description> 
   <pubDate>Mon, 18 Aug 2008 12:20:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48262</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.98&amp;r2=1.99&amp;ty=u</description> 
   <pubDate>Mon, 18 Aug 2008 12:28:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48263</link> 
  </item> 
   
  <item> 
   <title>Committed and merged, in absence of any feedback, thanks.</title> 
   <description>Committed and merged, in absence of any feedback, thanks.</description> 
   <pubDate>Mon, 18 Aug 2008 12:29:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48264</link> 
  </item> 
   
  <item> 
   <title>Hi,



the procmail vacation script isn&#039;t working in the new</title> 
   <description>Hi,



the procmail vacation script isn&#039;t working in the new ingo release (1.2.1).



It seems that the new /dev/null method breaks the script entirely: No

vacation message is being sent and, even worse, incoming mails are not being delivered to

the Inbox anymore. Seems they are copied to /dev/null!



When commenting these lines



:0

/dev/null



the script works fine again.



Seems that this fix has never been tested against other operating systems than Centos 3.



I&#039;m using standard packages on a Debian etch machine.



Bye



Volker



</description> 
   <pubDate>Fri, 12 Sep 2008 15:23:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t48886</link> 
  </item> 
   
  <item> 
   <title>Can anybody using Procmail provide a working and compatible </title> 
   <description>Can anybody using Procmail provide a working and compatible solution for this issue?</description> 
   <pubDate>Mon, 13 Apr 2009 16:04:08 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t53625</link> 
  </item> 
   
  <item> 
   <title>The 

:0 

/dev/null 



surely breaks things in lenny. The </title> 
   <description>The 

:0 

/dev/null 



surely breaks things in lenny. The patch we use and seems to solve most problems is attached. The {&#039;s shouldn&#039;t start a new copy at all reading the documentation:





{      Followed by at least one space, tab or newline will mark the start of a nesting block.  Everything up  till  the  next closing  brace  will depend on the conditions specified for this recipe.  Unlimited nesting is permitted.  The closing brace exists merely to delimit the block, it will not cause procmail to terminate in any way.  If the end of  a  block is  reached  processing will continue as usual after the block.  On a nesting block, the flags H and B only affect the conditions leading up to the block, the flags h and b have no effect whatsoever.</description> 
   <pubDate>Tue, 14 Apr 2009 13:09:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t53646</link> 
  </item> 
   
  <item> 
   <title>There was more wrong with the procmail vacation script that </title> 
   <description>There was more wrong with the procmail vacation script that was produced. Put some time in it and came up with the following diff. I think the resulting script is also easier to read </description> 
   <pubDate>Fri, 24 Apr 2009 09:59:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t53851</link> 
  </item> 
   
  <item> 
   <title>Volker, Eric, does this patch work for you?</title> 
   <description>Volker, Eric, does this patch work for you?</description> 
   <pubDate>Fri, 24 Apr 2009 10:27:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t53853</link> 
  </item> 
   
  <item> 
   <title>Ping?</title> 
   <description>Ping?</description> 
   <pubDate>Wed, 13 May 2009 16:11:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54117</link> 
  </item> 
   
  <item> 
   <title>Giving up. With the current support for the maildrop and pro</title> 
   <description>Giving up. With the current support for the maildrop and procmail drivers, we should consider dropping them.</description> 
   <pubDate>Tue, 26 May 2009 11:38:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54303</link> 
  </item> 
   
  <item> 
   <title>I&#039;ve provided patches which we have been testing for a lot o</title> 
   <description>I&#039;ve provided patches which we have been testing for a lot of our customers. If you dont mind,we would like to take over maintainership for this part of horde.



</description> 
   <pubDate>Tue, 26 May 2009 12:14:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54308</link> 
  </item> 
   
  <item> 
   <title>That would be great. We desperately need dedicated maintaine</title> 
   <description>That would be great. We desperately need dedicated maintainers for those drivers.</description> 
   <pubDate>Tue, 26 May 2009 12:19:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54309</link> 
  </item> 
   
  <item> 
   <title>That would be great indeed - how do you want to handle this?</title> 
   <description>That would be great indeed - how do you want to handle this? Submit patches, or commit access, or?



Thanks!</description> 
   <pubDate>Thu, 28 May 2009 03:30:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54317</link> 
  </item> 
   
  <item> 
   <title>Ping (once again)?</title> 
   <description>Ping (once again)?</description> 
   <pubDate>Sun, 07 Jun 2009 10:01:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54459</link> 
  </item> 
   
  <item> 
   <title>Sorry, you haven&#039;t heared from me, but i&#039;ve became a father </title> 
   <description>Sorry, you haven&#039;t heared from me, but i&#039;ve became a father for the second time ;-) We still use my patch on several customer servers without problems. I&#039;m unable to try it on CentoOS3 and I can&#039;t be botherd to install such an old version of CentOS, sorry.</description> 
   <pubDate>Mon, 29 Jun 2009 12:49:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54741</link> 
  </item> 
   
  <item> 
   <title>Uhm, what does this have to with our questions?</title> 
   <description>Uhm, what does this have to with our questions?</description> 
   <pubDate>Sat, 11 Jul 2009 17:13:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54907</link> 
  </item> 
   
  <item> 
   <title>&gt; Uhm, what does this have to with our questions?



Hmm, ma</title> 
   <description>&gt; Uhm, what does this have to with our questions?



Hmm, maybe a long way to say, please use my patches and close this case.</description> 
   <pubDate>Sat, 11 Jul 2009 19:10:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54914</link> 
  </item> 
   
  <item> 
   <title>So you are *not* longer interested in maintaining those driv</title> 
   <description>So you are *not* longer interested in maintaining those drivers? Is that what you are saying?</description> 
   <pubDate>Mon, 13 Jul 2009 09:49:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54935</link> 
  </item> 
   
  <item> 
   <title>Not at all, I was just trying to say why it to longer to rea</title> 
   <description>Not at all, I was just trying to say why it to longer to react to your request. I just mean to say: 

1. I&#039;ve fixed some issues, please import these. I think they will solve several issues.



2. I will not test this specific case (#7052) so if the o.p. doesn&#039;t react please close this case and let&#039;s go on to other issues.

</description> 
   <pubDate>Mon, 13 Jul 2009 09:55:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t54936</link> 
  </item> 
   
  <item> 
   <title>The patch doesn&#039;t apply to procmail.php.</title> 
   <description>The patch doesn&#039;t apply to procmail.php.</description> 
   <pubDate>Tue, 18 Aug 2009 13:10:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55358</link> 
  </item> 
   
  <item> 
   <title>The ingofix2.diff does apply I hope?</title> 
   <description>The ingofix2.diff does apply I hope?</description> 
   <pubDate>Tue, 18 Aug 2009 13:17:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55359</link> 
  </item> 
   
  <item> 
   <title>No, that&#039;s the patch I was trying.</title> 
   <description>No, that&#039;s the patch I was trying.</description> 
   <pubDate>Tue, 18 Aug 2009 13:22:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55360</link> 
  </item> 
   
  <item> 
   <title>I&#039;ll rewrite it for cvs then. Will take a day of two probabl</title> 
   <description>I&#039;ll rewrite it for cvs then. Will take a day of two probably</description> 
   <pubDate>Tue, 18 Aug 2009 13:49:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55373</link> 
  </item> 
   
  <item> 
   <title>Have you made any progress yet?</title> 
   <description>Have you made any progress yet?</description> 
   <pubDate>Tue, 01 Sep 2009 11:07:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55627</link> 
  </item> 
   
  <item> 
   <title>After enjoying my vacation, here is (finally) a patch agains</title> 
   <description>After enjoying my vacation, here is (finally) a patch against 1.100</description> 
   <pubDate>Wed, 16 Sep 2009 09:56:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55768</link> 
  </item> 
   
  <item> 
   <title>1.100 of what?</title> 
   <description>1.100 of what?</description> 
   <pubDate>Wed, 16 Sep 2009 10:33:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55769</link> 
  </item> 
   
  <item> 
   <title>$Horde: ingo/lib/Script/procmail.php,v 1.100 2008/11/07 06:2</title> 
   <description>$Horde: ingo/lib/Script/procmail.php,v 1.100 2008/11/07 06:28:03 chuck Exp $</description> 
   <pubDate>Wed, 16 Sep 2009 10:45:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55771</link> 
  </item> 
   
  <item> 
   <title>This is from an abandoned branch (see 1st.README). Either us</title> 
   <description>This is from an abandoned branch (see 1st.README). Either use the latest version from Git, or from the FRAMEWORK_3 CVS branch.</description> 
   <pubDate>Wed, 16 Sep 2009 11:01:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55773</link> 
  </item> 
   
  <item> 
   <title>Luckily the patch applies without any problems on

$Horde: i</title> 
   <description>Luckily the patch applies without any problems on

$Horde: ingo/lib/Script/procmail.php,v 1.46.10.31 2008/11/07 16:53:43 chuck Exp $



Btw. It&#039;s not easy to go to the FRAMEWORK_3 branche on http://cvs.horde.org/</description> 
   <pubDate>Wed, 16 Sep 2009 11:17:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55774</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

Fix procmail</title> 
   <description>Changes have been made in CVS for this ticket:

Fix procmail vacation rule (micha@kovoks.nl, Bug #7052).
http://cvs.horde.org/diff.php/ingo/docs/CHANGES?rt=horde&amp;r1=1.55.2.127&amp;r2=1.55.2.128&amp;ty=u
http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?rt=horde&amp;r1=1.46.10.32&amp;r2=1.46.10.33&amp;ty=u</description> 
   <pubDate>Wed, 16 Sep 2009 12:37:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55776</link> 
  </item> 
   
  <item> 
   <title>&gt; Luckily the patch applies without any problems on

&gt; $Hord</title> 
   <description>&gt; Luckily the patch applies without any problems on

&gt; $Horde: ingo/lib/Script/procmail.php,v 1.46.10.31 2008/11/07 16:53:43 

&gt; chuck Exp $



Great! Committed, many thanks!



&gt; Btw. It&#039;s not easy to go to the FRAMEWORK_3 branche on http://cvs.horde.org/



Yes, known problem, see bug #8561.</description> 
   <pubDate>Wed, 16 Sep 2009 12:38:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55778</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

MFB: Fix pro</title> 
   <description>Changes have been made in Git for this ticket:

MFB: Fix procmail vacation rule (micha@kovoks.nl, Bug #7052).

http://git.horde.org/diff.php/ingo/docs/CHANGES?rt=horde-hatchery&amp;r1=ae3dfa4f32a99ebaff33773bd40b822903867de8&amp;r2=19e4902b7388356321c589fd133a66046649fd52
http://git.horde.org/diff.php/ingo/lib/Script/Procmail.php?rt=horde-hatchery&amp;r1=9b22223f642b6ab65a71694ff34f709f06dfce9d&amp;r2=19e4902b7388356321c589fd133a66046649fd52</description> 
   <pubDate>Wed, 16 Sep 2009 12:54:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t55784</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

MFB: Fix pro</title> 
   <description>Changes have been made in Git for this ticket:

MFB: Fix procmail vacation rule (micha@kovoks.nl, Bug #7052).

http://git.horde.org/diff.php/ingo/docs/CHANGES?rt=horde-git&amp;r1=ae3dfa4f32a99ebaff33773bd40b822903867de8&amp;r2=19e4902b7388356321c589fd133a66046649fd52
http://git.horde.org/diff.php/ingo/lib/Script/Procmail.php?rt=horde-git&amp;r1=9b22223f642b6ab65a71694ff34f709f06dfce9d&amp;r2=19e4902b7388356321c589fd133a66046649fd52</description> 
   <pubDate>Wed, 13 Jan 2010 00:11:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7052#t57615</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
