Hi Marcus,

Do I understand it right and I just set home_Mailbox=Maildir/ and postfix will deliver to ~/Maildir in Maildir-format!? (Is it really tjat easy!?)

Yes, it really is that easy. I currently run bincimap on three servers. I use the IMAPdir mail folder structure and have the following in main.cf,

home_mailbox = .maildir/

This delivers all incoming mail to .maildir/ in each user's home
directory. This works just great for me. I also use,

another question on this:
does postfix deliver to the folder ~/.maildir/new or to ~/maildir/INBOX/new?
Since I'm going to use ImapDir, my folders won't be subfolders of INBOX. So what I want to have is the INBOX in ~/Maildir/INBOX and the other folders will be ~/Maildir/<someothers> on the same level as INBOX.
Does postfix work with

home_mailbox = Maildir/INBOX

in case if have to tell that explicit!?


mailbox_command = /usr/bin/procmail -t

By the way procmail:

---------------------------------------
MAILDIR=$HOME/Maildir
DEFAULT=$HOME/Maildir/INBOX/

:0
* ^Subject:.\[SPAM\?\].*
Spam/
---------------------------------------

Does this put Spam (recognized by spamassasin) into ~/Maildir/Spam/new and all the rest to ~/Maildir/INBOX ?? (That's what I want to have and that's how it worked with mbox)



Works great for me. You can also use 'maildirmake .maildir' to make the

To which package does this program belong?

initial maildir folder, and the perl scripts available to convert mbox
files as I did. I initially migrated from sendmail to postfix and

I tried mb2md-3.10.pl which put's all mails in "new". Can I move them to "cur" without getting into trouble?
(All messages have flag "S" and loook like this 1076238805.000037.mbox:2,RS)

Thanks for your help!!


For the archives:
I didn't get bincimap with inetd running. Probably it has something to do with wrong parameter passing (argv[]) in inetd - I've seen that in another thread in the archives.
I moved my stuff to xinetd and that works fine (it's used only for 2 or 3 things anyway, so it was a cakewalk)

Regards
Volker

Attachment: pgp00000.pgp
Description: PGP signature



Reply via email to