Tag Info

Hot answers tagged

3

The alpine program does not support Maildir format mailboxes out of the box, although there is a patch floating around out there somewhere that adds this feature. If you're using Maildir, you can use mutt, which works great with maildir folders, or you can set an IMAP server (e.g., dovecot) that supports Maildir, and then configure alpine and other mail ...


3

Cristian's comment is correct: you need a trailing slash to make Postfix store incoming mail in Maildir format: home_mailbox = Maildir/ If you leave it off, it stores the mail in an mbox-style file of the same name. That is to say, this is not a setting where you are providing the name of a type of storage, you are providing the name of a file or ...


3

Its similar to how the data in a rm'd file will still be there until the disk space is reused. Thunderbird marks it free, but doesn't actually free it (which could involve moving later messages in the file, etc.). The way to make it actually free it is to compact the folder. Right-click the trash and select 'Compact'. That should do it. You can also select ...


3

By default Dovecot uses Maildir++ directory layout for organizing mailbox directories. This means that all the folders are directly inside ~/Maildir directory, and: ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. You can read more about the layout here Thus what you complain about is standard behavior. You can ...


3

No, Postfix has no way to configure this. As @HBruijn said, the Maildir format is a specification and it would be quite an effort to make the LDA and the MUA both agree on a different format. That said, if you don't like the filenames in your maildir, you could beautify them a bit when you look then up: $ ls | head -1 1325471944.27745_1.beta,S=10662:2,S $ ...


3

This is because you have set set mbox_type=Maildir which configures the default mail-box type for newly created mailboxes to maildir. And the maildir standard says that a maildir X must have sub-folders {cur,new,tmp}. A folder sent is not described by the maildir standard. Thus, when you specify as destination ~/.mail/sent mutt interprets it as maildir ...


2

Local email for multiple email cleints [IMAP] Have you considered using "maildir ready" IMAP server? It will allow you to access your maildir by many/most email clients. You may consider "maildir ready" Dovecot IMAP server as "an option zero". AFAIK two email clients (Evolution and Emacs/Gnus) can use Dovecot in server-less mode to access your personal ...


2

You can do this with something like Aufs or Unionfs. Both these filesystems are "union" filesystems. You would do something such as Mount the old NAS at /mnt/old Mount the new NAS at /mnt/new Mount the union filesystem at /mnt/nas with /mnt/new on top of /mnt/old. Any access to /mnt/nas/foo/bar will first look for /mnt/new/foo/bar, and if it's not there, ...


2

Modify your mail_location as follows. mail_location = maildir:~/Mail:LAYOUT=fs Ref: Dovecot Docs ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. ~/Maildir/.folder/ is a mailbox folder You can also optionally use the fs layout by appending :LAYOUT=fs to mail_location. This makes the folder structure look like: ...


1

Maildir store some data in the message filename. That data include message ID, sizes (with and w/o newlines) and flags. When unread message is opened, it is moved from new to cur and its name changes from 1406379300.M375059P35208.R93M.lan,S=679,W=699 to 1406379300.M375059P35208.R93M.lan,S=679,W=699:2,S IMAP server can track that changes cause it use ...


1

Fixing the variable If you'd like to make this change system wide I'd be inclined to add an entry in the directory /etc/profile.d for it. You can simply put a file in there with the contents as follows: # /etc/profile.d/mailenv.sh MAIL=$HOME/Maildir or MAILDIR=$HOME/Maildir This environment variable, $HOME, should be in scope when the user logs in. ...


1

The original specification of the Maildir format would be good start to answer your question. The requirement is that each new message will be stored with a unique name. Unless you're writing messages to a maildir, the format of a unique name is none of your business. A unique name can be anything that doesn't contain a colon (or slash) and ...


1

I found a shorter and simpler way to implement with Python. Sample code below. #!/usr/bin/python import mailbox import email.utils import os mbox = mailbox.Maildir(os.environ['HOME'] + "/Maildir" ) mbox.lock() spam = mbox.get_folder('INBOX.junk') print "INBOX:" for message in mbox: print "- [%s] %s: \"%s\"" % ( message['date'], message['from'], ...


1

It appears that Courier IMAP's architecture does not support Maildirs outside of $HOME.


1

What about offlineimap again? (running an imap server instance on the server).


1

you might be able to do it in place, like this: $ for m in Mail/{cur,new}/*; do echo $m; procmail <$m; rm $m; done You have to remove each original email afterwards, or else procmail will duplicate it. It will also record everything as new. I'm not sure of a good way to handle that.


1

I believe this will work. You need to run formail to reformat the mail and send it back through procmail. From the Maildir directory: cat * | formail -s procmail



Only top voted, non community-wiki answers of a minimum length are eligible