| 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 ![]() procmail.txt ![]() procmail.diff ![]() procmail[1].diff ![]() |
| Milestone | 1.2.2 |
| Patch | No |
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
State ⇒ Resolved
http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.98&r2=1.99&ty=u
New Attachment: procmail[1].diff
New Attachment: procmail.diff
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?
Milestone ⇒ 1.2.1
with clean databases.
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...
http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.97&r2=1.98&ty=u
should be using Whc:. Can you try that?
Assigned to Matt Selsky
has sensitive info?
Patch ⇒
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ procmail vacation not working on Centos 3
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
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?