-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anne Wilson wrote:
On Saturday 28 Jan 2006 23:37, Willem Riede wrote:
On 01/28/2006 05:52:43 PM, Anne Wilson wrote:
On Saturday 28 Jan 2006 20:21, Markus Dobel wrote:
- ^To:.*design@lydgate.org ${MAILDIR}.Design That just leaves the question of the procmail recipe. Will the messages end up in the right place? AFAIK, Maildir-folders have to end with a "/" in procmailrc. The
Anne Wilson wrote: procmail recipe should read
- ^To:.*design@lydgate.org ${MAILDIR}.Design/
Regards, Markus Unfortunately it just doesn't work. It does for me:
# .procmailrc setup file PATH=/bin:/usr/bin:/usr/bin/mh:/usr/lib/mh:/usr/local/bin SHELL=/bin/sh MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR/.Other/ LOGFILE=$HOME/.procmail.log
# to eliminate duplicates
:0 Wh : | formail -D 512000 $HOME/.msgid.cache
I do believe you. Others have said the same, but it didn't for me.
Late last night I got a result, but I had to define the folder as ${MAILDIR}/.INBOX.Design/newI can only think that there is a variable definition somewhere that is not set optimally. I'd like to identify it, but if I can't, at least I have something now that works.
Thanks to all for the input.
Anne
Anne,
it looks like you just have had some small typos or misunderstandings throughout this process. anyways, it looks like you're getting close.
the problem with the above "${MAILDIR}/.INBOX.Design/new" is that procmail will then write an mbox style file called "new" in ${MAILDIR}/.INBOX.Design/ which is not what you want.
to use procmail with maildir format (which is what I'm assuming you want to do with your setup, you need to end your destination directory with a /
simply having ${MAILDIR}/.INBOX.Design/ or ${MAILDIR}/.Design/ would have worked for you.
the different between [1]${MAILDIR}/.Design/ and [2]${MAILDIR}/.INBOX.Design/ is that the former will show up as a "root level" folder in your mailbox heirarchy, and the latter will show up as a subfolder of your INBOX.
[1] in uber ascii art representation:
*mail account name | -> INBOX -> Design -> Trash -> Sent -> Etc
[2] in uber ascii art representation
*mail account name | -> INBOX \-> Design -> Trash -> Sent -> Etc
you can actually achieve the same type of heirarchy with mbox format,although a primary difference is that in this case, .INBOX.Design/ can contain messages AND subfolders whereas mbox format will only allow .INBOX.Design to contain messages OR subfolders.
anyways, I hope you find this useful.
Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD3cblE2gsBSKjZHQRAhmUAKDNH55xAZ+YkmB8KXy0/4aVhkLyWwCghLan Tg6NI6fYoziijU8cOF/0yEw= =CbUl -----END PGP SIGNATURE-----