On Saturday 28 Jan 2006 20:21, Markus Dobel wrote:
Anne Wilson 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 procmail recipe should read
- ^To:.*design@lydgate.org ${MAILDIR}.Design/
Regards, Markus
Unfortunately it just doesn't work.
Anne
Registered Linux User No.293302 (http://counter.li.org/)
On 01/28/2006 05:52:43 PM, Anne Wilson wrote:
On Saturday 28 Jan 2006 20:21, Markus Dobel wrote:
Anne Wilson 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 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
...
# Dovecot :0
- ^X-BeenThere.*dovecot@dovecot.org .Dovecot/
...
Success, Willem Riede.
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:
Anne Wilson 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 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/new
I 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
-----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-----
On Monday 30 Jan 2006 07:57, Alan Premselaar wrote:
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.
It doesn't seem to be doing that. Take, for instance the folder
INBOX.Fedora.Users - there are 14 individual messages in cur, 0 in new.
All are visible over the lan. It is noticeable, though, that the
messages that came in when I was using /new are named differently from
the ones accepted without /new, whatever that implies.
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.
I'm using that now. I did try both those formats before without success. It's almost as though it needed one message to be accepted into /new to kick-start things, after which they can work without it.
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.
Helpful explanation, thanks.
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.
I used to use subfolders on the old mbox system. I thought that the difference was accounted for by version, so I'm pleased that this has helped me understand more.
anyways, I hope you find this useful.
Very. But still a little puzzled about that 'new' thing. I'm trying to decide whether to leave it on for the little-used boxes that have not yet received any mail. The problem as I see it, is that before things were kick-started it was writing mbox-style to the right place. Now I don't know whether the system is correctly taking care of things, or whether the need is still folder-status-specific. If it *is* needed for those folders, leaving it off will result in lost, invisible messages.
Anne
Registered Linux User No.293302 (http://counter.li.org/)
On Mon, 2006-01-30 at 10:24 +0000, Anne Wilson wrote:
On Monday 30 Jan 2006 07:57, Alan Premselaar wrote:
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.
It doesn't seem to be doing that. Take, for instance the folder INBOX.Fedora.Users - there are 14 individual messages in cur, 0 in new.
All are visible over the lan. It is noticeable, though, that the messages that came in when I was using /new are named differently from the ones accepted without /new, whatever that implies.
If you say ".INBOX.Design/new", procmail writes the messages in "MH" format, which kind of works with maildir, but it behaves slightly differently so that if you leave it on, you'll start getting "expunged mail reappeared" errors from Dovecot.
So, ".INBOX.Design/" is the right way to do it for maildir..
On Monday 30 Jan 2006 11:32, Timo Sirainen wrote:
If you say ".INBOX.Design/new", procmail writes the messages in "MH" format, which kind of works with maildir, but it behaves slightly differently so that if you leave it on, you'll start getting "expunged mail reappeared" errors from Dovecot.
I think that has happened, during the various tests I've done.
So, ".INBOX.Design/" is the right way to do it for maildir..
Thanks. All seems to be well now. I'm down to the fine details, like checking that I haven't missed any necessary procmail filters.
Thanks to all who helped
Anne
Registered Linux User No.293302 (http://counter.li.org/)
participants (4)
-
Alan Premselaar
-
Anne Wilson
-
Timo Sirainen
-
Willem Riede