[Tickets #10113] Re: Cannot create procmail rules with Maildir support

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10113
------------------------------------------------------------------------------
  Ticket             | 10113
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Cannot create procmail rules with Maildir support
  Queue              | Ingo
  Version            | 2.0.1
  Type               | Bug
-State              | Resolved
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Jan Schneider
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-06-20 14:14) wrote:

> Revert "Fix folder names in Procmail rules if using Maildir (Bug 10113)."

Yikes.  Not sure how I missed this commit originally, but this  
completely broke mail delivery for me, and I've lost a ton of messages  
since activating my new script yesterday.

Now mailboxes look are generated like:

[RULE DEFINITION]
".foo.bar/"

Which tells procmail to deliver to the foo.bar directory in the *base*  
home directory.  Which by default is the home directory (see $MAILDIR  
variable).

$MAILDIR can be used to change the base directory, but this is not  
documented in ingo and, worst of all, is a BC breaking change for  
existing scripts.

Not sure why we aren't delivering directly to the mailbox name itself anymore:

[RULE DEFINITION]
foo.bar

IIRC, this is the way we did it for years and it worked fine.

I've reverted the original change.  However, I am going to re-commit  
the original along with adding an explicit MAILDIR variable in  
backends.php and making both DEFAULT and MAILDIR active in the default  
backends configuration.