[#7052] procmail vacation not working on Centos 3
Summary procmail vacation not working on Centos 3
Queue Ingo
Queue Version 1.2
Type Bug
State Assigned
Priority 2. Medium
Owners Matt Selsky <selsky (at) columbia (dot) edu>
Requester Eric Rostetter <eric (dot) rostetter (at) physics (dot) utexas (dot) edu>
Created 07/09/2008 (134 days ago)
Due
Updated 09/22/2008 (59 days ago)
Assigned 09/12/2008 (69 days ago)
Resolved
Attachments procmailrc Download
procmail.txt Download
procmail.diff Download
procmail[1].diff Download
Milestone 1.2.2
Patch No

History
09/22/2008 Jan Schneider Priority ⇒ 2. Medium
 
09/12/2008 Jan Schneider Milestone ⇒ 1.2.2
 
09/12/2008 Jan Schneider State ⇒ Assigned
 
09/12/2008 horde (at) volkerthen (dot) com Comment #15 Reply to this comment
Hi,

the procmail vacation script isn'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'm using standard packages on a Debian etch machine.

Bye

Volker


08/18/2008 Jan Schneider Comment #14
State ⇒ Resolved
Reply to this comment
Committed and merged, in absence of any feedback, thanks.
08/18/2008 CVS Commit Comment #13 Reply to this comment
08/18/2008 Matt Selsky Comment #12
New Attachment: procmail[1].diff Download
Reply to this comment
Try this.
08/18/2008 Jan Schneider Comment #11 Reply to this comment
This patch doesn't apply to CVS HEAD.
08/14/2008 Jan Schneider Comment #10 Reply to this comment
Ping?
07/30/2008 Matt Selsky State ⇒ Feedback
 
07/30/2008 Matt Selsky Comment #9
New Attachment: procmail.diff Download
Reply to this comment
I went with the /dev/null method for now.  Can you try this out?
07/30/2008 Matt Selsky Comment #8 Reply to this comment
We're seeing double-delivery because the {}'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?
07/28/2008 Jan Schneider Comment #7
Milestone ⇒ 1.2.1
Reply to this comment
Matt, can you please review this ticket?
07/26/2008 Jan Schneider State ⇒ Assigned
 
07/14/2008 Eric Rostetter New Attachment: procmail.txt Download
 
07/14/2008 Matt Selsky Comment #6 Reply to this comment
Can you post procmail debug logs for the first and second messages 
with clean databases.
07/14/2008 Eric Rostetter Comment #5 Reply to this comment
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'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't know.  But I do prefer it with
this change, than without.  Since I'd rather have them get a duplicate 
of everything, than have no vacation
reply sent out.

But either something else in my setup isn't right (causing the 
duplicate), or something else in this script isn't
right (causing the duplicate).

I'll try to investigate more later, and post more when/if I figure out 
what is going on...
07/14/2008 Jan Schneider State ⇒ Feedback
 
07/13/2008 CVS Commit Comment #4 Reply to this comment
07/13/2008 Matt Selsky Comment #3 Reply to this comment
http://www.stimpy.net/procmail/tutorial/vacation.html suggests that we 
should be using Whc:.  Can you try that?
07/12/2008 Jan Schneider State ⇒ Assigned
Assigned to Matt Selsky
 
07/11/2008 Eric Rostetter New Attachment: procmailrc Download
 
07/09/2008 Matt Selsky Comment #2 Reply to this comment
Can you attach the generated procmailrc?  Or email me privately if it 
has sensitive info?
07/09/2008 Eric Rostetter Comment #1
Patch ⇒
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ procmail vacation not working on Centos 3
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Reply to this comment
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 "formail,-rD,8192,/u1/demkov/.vacation.demkov"
procmail: Non-zero exitcode (1) from "formail"
procmail: Rescue of unfiltered data succeeded
procmail: Non-zero exitcode (-11) from "procmail"

If I change the recipe from using "0: Whaf" to use "0: Wha" 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't seem to help (still got the errors 
shown above).

Any ideas what is wrong?