Fri, 10 Apr 2026 12:25:55 +0000 https://bugs.horde.org/ticket/8766 enabling of vacation option without specifying a date causes mail loss If a user enables the vacation option, and doesn't enter a start and end date, my expected behaviour of vacation would be to stay enabled until the user disables it. Instead, while the system does auto-reply with the users vacation message, the received message goes to /dev/null. There were other fixes applied to procmail in 1.2.2 and I'm concerned about upgrading because I know that procmail support isn't a high priority, our users aren't complaining about other functionality at this time, and I don't want to effect that by going to 1.2.2 where problems have been reported. If anyone could try this with 1.2.2 and let me know if it works, it would be appreciated. Without date the .procmailrc contains: :0 { --stuff that doesn't matter-- . . . :0 Whc: ${VACATION_DIR:-.}/vacation.lock -- more stuff that I don't think matters --- :0 /dev/null } With date: :0 { --stuff that doesn't matter--- . . . :0 Whc: ${VACATION_DIR:-.}/vacation.lock * ? test $DATE -gt $START && test $END -gt $DATE { :0 Whc . . . :0 /dev/null } } In the non-date case, the message is delivered to /dev/null which is verified by looking at procmail logs. Thu, 10 Dec 2009 21:37:01 +0000 https://bugs.horde.org/ticket/8766#t57112 > If anyone could try this with 1.2.2 > and let me know if it works, it would be appreciated. Anyone? Fri, 01 Jan 2010 16:27:05 +0000 https://bugs.horde.org/ticket/8766#t57388 Look at http://bugs.horde.org/ticket/8982 Wed, 28 Apr 2010 09:46:10 +0000 https://bugs.horde.org/ticket/8766#t58646