Re: Using maildir

2014-04-29 Thread Suvayu Ali
On Tue, Apr 29, 2014 at 11:27:38PM +0100, David Woodfall wrote:
> >On Tue, Apr 29, 2014 at 10:44:38PM +0100, David Woodfall wrote:
> >
> >>Well, I'm not quite out of the woods. Although mutt starts off in my
> >>Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
> >>I change folder, to say view all my mailboxes, then I can't get back
> >>into my Inbox. Inbox isn't listed anywhere that I can see, and the
> >>only way seems to be to restart mutt -f ~/Mail.
> >>
> >>If I hit 'c' to change folder it just lists all my folders minus
> >>Inbox. I guess I could make an Inbox folder and set that in procmail
> >>to be default. Is that the proper way? I expect I would need to point
> >>dovecot at it too.
> >>
> >>I tried commenting out the $folder as you suggested but it doesn't
> >>seem to help. I also noticed that $MAIL was set to
> >>/var/spool/mail/... so I also pointed that at ~/Mail.
> >
> >After pressing 'c', you can use '!' to go to what mutt considers your
> >"inbox" ($spoolfile), and '=' or '+' to go to $folder.
> >
> >If you have $folder set as ~/Mail, mutt will start there without you
> >passing '-f ~/Mail'. I've noticed you using ~/mail and ~/Mail at
> >different times, which is it? What does dovecot think it is? What does
> >mutt think it is?
> 
> I've set everything - mutt, dovecot, procmail to use ~/Mail now.
> 
> I'll checkout '!', thanks.

But did you follow David Champion's suggestion to have the maildir under
~/Mail and not have ~/Mail itself as a maildir.  Example from my setup:

  /home/user/Mail
  ├── archive
  │   ├── cur
  │   ├── new
  │   └── tmp
  ├── INBOX
  │   ├── cur
  │   ├── new
  │   └── tmp
  ├── sent
  │   ├── cur
  │   ├── new
  │   └── tmp
  └── templates
  ├── cur
  ├── new
  └── tmp


-- 
Suvayu

Open source is the future. It sets us free.


Re: Using maildir

2014-04-29 Thread David Woodfall

On Tue, Apr 29, 2014 at 10:44:38PM +0100, David Woodfall wrote:


Well, I'm not quite out of the woods. Although mutt starts off in my
Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
I change folder, to say view all my mailboxes, then I can't get back
into my Inbox. Inbox isn't listed anywhere that I can see, and the
only way seems to be to restart mutt -f ~/Mail.

If I hit 'c' to change folder it just lists all my folders minus
Inbox. I guess I could make an Inbox folder and set that in procmail
to be default. Is that the proper way? I expect I would need to point
dovecot at it too.

I tried commenting out the $folder as you suggested but it doesn't
seem to help. I also noticed that $MAIL was set to
/var/spool/mail/... so I also pointed that at ~/Mail.


After pressing 'c', you can use '!' to go to what mutt considers your
"inbox" ($spoolfile), and '=' or '+' to go to $folder.

If you have $folder set as ~/Mail, mutt will start there without you
passing '-f ~/Mail'. I've noticed you using ~/mail and ~/Mail at
different times, which is it? What does dovecot think it is? What does
mutt think it is?


I've set everything - mutt, dovecot, procmail to use ~/Mail now.

I'll checkout '!', thanks.

Dave


Re: Using maildir

2014-04-29 Thread Tom Furie
On Tue, Apr 29, 2014 at 10:44:38PM +0100, David Woodfall wrote:

> Well, I'm not quite out of the woods. Although mutt starts off in my
> Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
> I change folder, to say view all my mailboxes, then I can't get back
> into my Inbox. Inbox isn't listed anywhere that I can see, and the
> only way seems to be to restart mutt -f ~/Mail.
> 
> If I hit 'c' to change folder it just lists all my folders minus
> Inbox. I guess I could make an Inbox folder and set that in procmail
> to be default. Is that the proper way? I expect I would need to point
> dovecot at it too.
> 
> I tried commenting out the $folder as you suggested but it doesn't
> seem to help. I also noticed that $MAIL was set to
> /var/spool/mail/... so I also pointed that at ~/Mail.

After pressing 'c', you can use '!' to go to what mutt considers your
"inbox" ($spoolfile), and '=' or '+' to go to $folder.

If you have $folder set as ~/Mail, mutt will start there without you
passing '-f ~/Mail'. I've noticed you using ~/mail and ~/Mail at
different times, which is it? What does dovecot think it is? What does
mutt think it is?

Cheers,
Tom

-- 
He looked at me as if I were a side dish he hadn't ordered.
-- Ring Lardner


signature.asc
Description: Digital signature


Re: Using maildir

2014-04-29 Thread David Woodfall

Don't know if this helps with the problem, but I see a small "m" in
your .muttrc, but at command prompt, you type Mail with capital "M"
Two different directories.


Yep, I actually renamed the folder to Mail since I started this
thread. Seems to make it stand out more.


On Tue, Apr 29, 2014 at 1:44 PM, David Woodfall  wrote:

* On 29 Apr 2014, David Woodfall wrote:



Significant parts from .muttrc:

set mbox_type=maildir
set folder="$HOME/mail"
set mbox="$HOME/mail"
set spoolfile="$HOME/mail"



Your $folder may be the source of the problem.  My hypothesis: if you
change that (to anything else, pretty much) and open up ~/mail directly,
you'll see it as intended.  Since $folder is the directory in which
mailboxes are expected to be located -- i.e. there should be maildirs
*within* ~/mail -- mutt is searching it for mailboxes and unable to
treat it as a mailbox itself.



This helps:

set mask="!^\\.|^dovecot*|^tmp$|^new$|^cur$|^subscriptions$"

Now I just set my mailboxes and everything else is hidden.



Well, I'm not quite out of the woods. Although mutt starts off in my
Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
I change folder, to say view all my mailboxes, then I can't get back
into my Inbox. Inbox isn't listed anywhere that I can see, and the
only way seems to be to restart mutt -f ~/Mail.

If I hit 'c' to change folder it just lists all my folders minus
Inbox. I guess I could make an Inbox folder and set that in procmail
to be default. Is that the proper way? I expect I would need to point
dovecot at it too.

I tried commenting out the $folder as you suggested but it doesn't
seem to help. I also noticed that $MAIL was set to
/var/spool/mail/... so I also pointed that at ~/Mail.

Dave


--
Studioware. We provide the tools - You make the music.
http://www.studioware.org
irc.freenode.net #studioware
irc.oftc.net #studioware



Re: Using maildir

2014-04-29 Thread Michael
Don't know if this helps with the problem, but I see a small "m" in
your .muttrc, but at command prompt, you type Mail with capital "M"
Two different directories.

On Tue, Apr 29, 2014 at 1:44 PM, David Woodfall  wrote:
>>> * On 29 Apr 2014, David Woodfall wrote:


 Significant parts from .muttrc:

 set mbox_type=maildir
 set folder="$HOME/mail"
 set mbox="$HOME/mail"
 set spoolfile="$HOME/mail"
>>>
>>>
>>> Your $folder may be the source of the problem.  My hypothesis: if you
>>> change that (to anything else, pretty much) and open up ~/mail directly,
>>> you'll see it as intended.  Since $folder is the directory in which
>>> mailboxes are expected to be located -- i.e. there should be maildirs
>>> *within* ~/mail -- mutt is searching it for mailboxes and unable to
>>> treat it as a mailbox itself.
>>
>>
>> This helps:
>>
>> set mask="!^\\.|^dovecot*|^tmp$|^new$|^cur$|^subscriptions$"
>>
>> Now I just set my mailboxes and everything else is hidden.
>
>
> Well, I'm not quite out of the woods. Although mutt starts off in my
> Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
> I change folder, to say view all my mailboxes, then I can't get back
> into my Inbox. Inbox isn't listed anywhere that I can see, and the
> only way seems to be to restart mutt -f ~/Mail.
>
> If I hit 'c' to change folder it just lists all my folders minus
> Inbox. I guess I could make an Inbox folder and set that in procmail
> to be default. Is that the proper way? I expect I would need to point
> dovecot at it too.
>
> I tried commenting out the $folder as you suggested but it doesn't
> seem to help. I also noticed that $MAIL was set to
> /var/spool/mail/... so I also pointed that at ~/Mail.
>
> Dave


Re: Using maildir

2014-04-29 Thread David Woodfall

* On 29 Apr 2014, David Woodfall wrote:


Significant parts from .muttrc:

set mbox_type=maildir
set folder="$HOME/mail"
set mbox="$HOME/mail"
set spoolfile="$HOME/mail"


Your $folder may be the source of the problem.  My hypothesis: if you
change that (to anything else, pretty much) and open up ~/mail directly,
you'll see it as intended.  Since $folder is the directory in which
mailboxes are expected to be located -- i.e. there should be maildirs
*within* ~/mail -- mutt is searching it for mailboxes and unable to
treat it as a mailbox itself.


This helps:

set mask="!^\\.|^dovecot*|^tmp$|^new$|^cur$|^subscriptions$"

Now I just set my mailboxes and everything else is hidden.


Well, I'm not quite out of the woods. Although mutt starts off in my
Inbox (using mutt -f ~/Mail) and it shows everything correctly, when
I change folder, to say view all my mailboxes, then I can't get back
into my Inbox. Inbox isn't listed anywhere that I can see, and the
only way seems to be to restart mutt -f ~/Mail.

If I hit 'c' to change folder it just lists all my folders minus
Inbox. I guess I could make an Inbox folder and set that in procmail
to be default. Is that the proper way? I expect I would need to point
dovecot at it too.

I tried commenting out the $folder as you suggested but it doesn't
seem to help. I also noticed that $MAIL was set to
/var/spool/mail/... so I also pointed that at ~/Mail.

Dave


Re: Using maildir

2014-04-29 Thread Tom Furie
On Wed, Apr 30, 2014 at 05:08:17AM +1200, Chris Bannister wrote:
> On Tue, Apr 29, 2014 at 02:57:27PM +0100, Tom Furie wrote:

> > set mbox_type=maildir should let mutt know it's looking at a maildir
> > structure.
> 
> AFAIU, that setting, creates a maildir structure when creating a new
> mailbox to save to.
> 
> It can "see" mbox or maildir structures regardless of that setting.
> 
> Please enlighten me if I am wrong.

You are correct. I'm not sure what I was thinking about when I posted
that.

Cheers,
Tom

-- 
Prof:So the American government went to IBM to come up with a data
 encryption standard and they came up with ...
Student: EBCDIC!"


signature.asc
Description: Digital signature


Re: Using maildir

2014-04-29 Thread David Woodfall

* On 29 Apr 2014, David Woodfall wrote:


Significant parts from .muttrc:

set mbox_type=maildir
set folder="$HOME/mail"
set mbox="$HOME/mail"
set spoolfile="$HOME/mail"


Your $folder may be the source of the problem.  My hypothesis: if you
change that (to anything else, pretty much) and open up ~/mail directly,
you'll see it as intended.  Since $folder is the directory in which
mailboxes are expected to be located -- i.e. there should be maildirs
*within* ~/mail -- mutt is searching it for mailboxes and unable to
treat it as a mailbox itself.


This helps:

set mask="!^\\.|^dovecot*|^tmp$|^new$|^cur$|^subscriptions$"

Now I just set my mailboxes and everything else is hidden.

Dave


Re: Using maildir

2014-04-29 Thread David Champion
* On 29 Apr 2014, David Woodfall wrote: 
> 
> Significant parts from .muttrc:
> 
> set mbox_type=maildir
> set folder="$HOME/mail"
> set mbox="$HOME/mail"
> set spoolfile="$HOME/mail"

Your $folder may be the source of the problem.  My hypothesis: if you
change that (to anything else, pretty much) and open up ~/mail directly,
you'll see it as intended.  Since $folder is the directory in which
mailboxes are expected to be located -- i.e. there should be maildirs
*within* ~/mail -- mutt is searching it for mailboxes and unable to
treat it as a mailbox itself.

-- 
David Champion • d...@bikeshed.us


Re: Using maildir

2014-04-29 Thread David Woodfall

* On 28 Apr 2014, David Woodfall wrote:

I've just set up dovecot/procmail on a debian VPS and when using mutt
with maildir, as I navigate around, I see the new/ cur/ tmp/ folders
and inside the actual file names of the mail.


This should just work.  Maildir is tested first, before other mailbox
types, and it only checks whether there is a cur/ subdirectory to the
mailbox location.

Two questions: 1. are you sure that the permissions are correct (i.e.
that your user can read it, was not set up by root, etc)?  Clearly you
can read the mailbox directory, but what about cur?  2. How are you
referring to the mailbox?


The permissions look ok:

% ls -ld mail
drwx-- 7 dive dive 4096 Apr 29 03:30 mail/

% ls -l mail
total 52
drwx-- 2 dive dive  4096 Apr 29 03:04 cur/
-rw--- 1 dive dive 17408 Apr 29 03:04 dovecot.index.cache
-rw--- 1 dive dive  2008 Apr 29 03:30 dovecot.index.log
-rw--- 1 dive dive51 Apr 29 03:30 dovecot-uidlist
-rw--- 1 dive dive 8 Apr 29 03:05 dovecot-uidvalidity
-r--r--r-- 1 dive dive 0 Apr 29 01:43
dovecot-uidvalidity.535f03da
drwx-- 3 dive dive  4096 Apr 29 03:29 new/
-rw--- 1 dive dive   843 Apr 29 02:52 Sent
drwx-- 3 dive dive  4096 Apr 29 03:29 tmp/
drwx-- 5 dive dive  4096 Apr 29 03:05 Trash/



You might running in debug mode: mutt -d3 -f /path/to/mailbox


Output from that:

[2014-04-29 17:44:44] Mutt/1.5.21 (2010-09-15) debugging at level 3
[2014-04-29 17:44:44] Reading configuration file '/etc/Muttrc'.
[2014-04-29 17:44:44] Reading configuration file
'/usr/lib/mutt/source-muttrc.d|'.
[2014-04-29 17:44:44] Reading configuration file
'/etc/Muttrc.d/charset.rc'.
[2014-04-29 17:44:44] Reading configuration file
'/etc/Muttrc.d/colors.rc'.
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 1
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 2
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 3
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 4
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 5
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 6
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 7
[2014-04-29 17:44:44] mutt_alloc_color(): Color pairs used so far: 8
[2014-04-29 17:44:44] Reading configuration file
'/etc/Muttrc.d/compressed-folders.rc'.
[2014-04-29 17:44:44] Reading configuration file
'/etc/Muttrc.d/gpg.rc'.
[2014-04-29 17:44:44] Reading configuration file
'/etc/Muttrc.d/smime.rc'.
[2014-04-29 17:44:44] Reading configuration file
'/home/dive/.muttrc'.
[2014-04-29 17:44:44] mailbox '/home/dive/mail/Trash' already
registered as '/home/dive/mail/   Trash'
[2014-04-29 17:44:44] mailbox '/home/dive/mail/new' already
registered as '/home/dive/mail/new' [2014-04-29 17:44:44] mailbox
'/home/dive/mail/cur' already registered as '/home/dive/mail/cur'
[2014-04-29 17:44:44] mailbox '/home/dive/mail/tmp' already
registered as '/home/dive/mail/tmp' [2014-04-29 17:44:44] Reading
configuration file '/home/dive/.muttbinds'.
[2014-04-29 17:44:44] Reading mail...
[2014-04-29 17:44:44] Scanning mail... 0 
[2014-04-29 17:44:44] Reading mail... 0

[2014-04-29 17:44:44] Scanning mail... 0
[2014-04-29 17:44:44] Reading mail... 0
[2014-04-29 17:44:49] Mailbox is unchanged.

Significant parts from .muttrc:

set mbox_type=maildir
set folder="$HOME/mail"
set mbox="$HOME/mail"
set spoolfile="$HOME/mail"

sigificant parts from .muttbinds:

bindpager exit
bindbrowser   toggle-mailboxes
bindattachexit
bindpagerview-attachments
bindattach   view-attach
bindbrowser  select-entry
bindindexdisplay-message
bindcompose  view-attach

That allows me to use left and right to go pretty much anywhere.

Dave




Re: Using maildir

2014-04-29 Thread Chris Bannister
On Tue, Apr 29, 2014 at 02:57:27PM +0100, Tom Furie wrote:
> On Tue, Apr 29, 2014 at 04:00:07AM +0100, David Woodfall wrote:
> > I've just set up dovecot/procmail on a debian VPS and when using mutt
> > with maildir, as I navigate around, I see the new/ cur/ tmp/ folders
> > and inside the actual file names of the mail.
> > 
> > On my home box I connect locally to the imap server so I don't see
> > this, but is there a better way of viewing maildir without seeing
> > these folders and just seeing mail as normal?
> 
> set mbox_type=maildir should let mutt know it's looking at a maildir
> structure.

AFAIU, that setting, creates a maildir structure when creating a new
mailbox to save to.

It can "see" mbox or maildir structures regardless of that setting.

Please enlighten me if I am wrong.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


Re: dev.mutt.org has been down for days

2014-04-29 Thread Brendan Cully
It's back.

On Wednesday, 23 April 2014 at 12:47, Brendan Cully wrote:
> A sprinkler went off in the server room hosting it, and about $500K of
> hardware. We're still working through recovery.
> 
> On Wednesday, 23 April 2014 at 13:38, j...@forallx.net wrote:
> > Has anyone else been unable to reach dev.mutt.org for days now?  Safari, 
> > e.g., says "the server is not responding".
> > 
> > Plain old www.mutt.org is perfectly accessible, however.
> > 
> > Over the years I have found dev.mutt.org to be far less reliable than 
> > www.mutt.org.
> > 
> > -jack


Re: Using maildir

2014-04-29 Thread David Champion
* On 28 Apr 2014, David Woodfall wrote: 
> I've just set up dovecot/procmail on a debian VPS and when using mutt
> with maildir, as I navigate around, I see the new/ cur/ tmp/ folders
> and inside the actual file names of the mail.

This should just work.  Maildir is tested first, before other mailbox
types, and it only checks whether there is a cur/ subdirectory to the
mailbox location.

Two questions: 1. are you sure that the permissions are correct (i.e.
that your user can read it, was not set up by root, etc)?  Clearly you
can read the mailbox directory, but what about cur?  2. How are you
referring to the mailbox?

You might running in debug mode: mutt -d3 -f /path/to/mailbox

-- 
David Champion • d...@bikeshed.us


Re: Using maildir

2014-04-29 Thread Suvayu Ali
On Tue, Apr 29, 2014 at 07:54:24AM -0700, Will Yardley wrote:
> On Tue, Apr 29, 2014 at 12:52:29PM +0200, Suvayu Ali wrote:
> > On Tue, Apr 29, 2014 at 11:30:24AM +0100, David Woodfall wrote:
> 
> > > If I'm not using imap it won't matter will it? I'm just using mutt -f
> > > ~/mail.
> > 
> > What is the value of mbox_type in your mutt config?  It should be
> > `Maildir'.
> 
> mbox_type only affects the behavior of mailboxes you create. Mutt should
> correctly recognize mailboxes of any supported type regardless of the
> setting of this option.

I read the manual again, you are right!  I'm not sure from the OP's
description when he sees the cur, new, and tmp directories.

I tried navigating to a maildir outside of my regular mailstore from the
change-folder dialog, mutt correctly recognises it is a maildir and
shows the messages instead of the directory structure.

-- 
Suvayu

Open source is the future. It sets us free.


Re: Using maildir

2014-04-29 Thread Will Yardley
On Tue, Apr 29, 2014 at 12:52:29PM +0200, Suvayu Ali wrote:
> On Tue, Apr 29, 2014 at 11:30:24AM +0100, David Woodfall wrote:

> > If I'm not using imap it won't matter will it? I'm just using mutt -f
> > ~/mail.
> 
> What is the value of mbox_type in your mutt config?  It should be
> `Maildir'.

mbox_type only affects the behavior of mailboxes you create. Mutt should
correctly recognize mailboxes of any supported type regardless of the
setting of this option.

w



Re: Using maildir

2014-04-29 Thread Tom Furie
On Tue, Apr 29, 2014 at 04:00:07AM +0100, David Woodfall wrote:
> I've just set up dovecot/procmail on a debian VPS and when using mutt
> with maildir, as I navigate around, I see the new/ cur/ tmp/ folders
> and inside the actual file names of the mail.
> 
> On my home box I connect locally to the imap server so I don't see
> this, but is there a better way of viewing maildir without seeing
> these folders and just seeing mail as normal?

set mbox_type=maildir should let mutt know it's looking at a maildir
structure.

Cheers,
Tom

-- 
Go placidly amid the noise and waste, and remember what value there may
be in owning a piece thereof.
-- National Lampoon, "Deteriorata"


signature.asc
Description: Digital signature


Re: Change from-address according to recipient using send-hook

2014-04-29 Thread Erik Christiansen
On 29.04.14 14:01, Karl Voit wrote:
> I've got a special requirement of setting the From-address according
> to the To-address of emails I am sending.

That's a pretty standard thing to do. For description of how easy it
is in mutt, please read sections:

19. Change Settings Based Upon Message Recipients
5.1. Message Matching in Hooks

The latter includes an example which exactly matches your requirement.
Just bang in one for each To-address, and you're done. If you have a
bunch of recipients for whom a common return address would do, then I'd
use Groups.

Since the manual seems to be a stranger, it may not be out of place to
remind that pressing  in mutt is normally all that is required to
bring it up.

...

> I've read about send-hook and found [1] but I am not able to apply
> this to get the result I want to achieve.

It is worth reading the abovementioned sections, and searching in the
manual for definitions and explanations of anything not understood, such
as:

Table 4.4. Pattern modifiers

where you might decide whether to use ~t (as in the example) or ~C.

You might also like to read:

Example 4.3. Specifying a ?default? hook

Maybe strong coffee, prior to reading, then a few experiments? ;-)

Erik

-- 
It's always sad when the fleas leave, because that means your dog is dead.
  - Wesley T. Williams



Change from-address according to recipient using send-hook

2014-04-29 Thread Karl Voit
Hi!

I've got a special requirement of setting the From-address according
to the To-address of emails I am sending.

Due to the fact that I am using dozens of different email addresses,
I want to automate the setting of my From-address. For this reason,
I've got a text file "addresses.txt" in my home folder, which looks
like this:

recipie...@example.com o...@example.com 
 
recipie...@example.com sec...@example.com
...

Thus, when I write an email to recipie...@example.com, I want the
From-address changed to o...@example.com. When I write an email to
recipie...@example.com, I want the From-address changed to
sec...@example.com accordingly.

My plan is to write a Python script which gets somehow the
From-addresses (I don't know how to do this yet), looks up the
matching To-address (I can do that), and returns it to mutt somehow
(I don't know yet). 

I've read about send-hook and found [1] but I am not able to apply
this to get the result I want to achieve.

Can you please help me?
Thanks very much!

  1. 
http://dev.mutt.org/trac/wiki/ConfigTricks#Generatingsend-hooksfromaddressesinaflattextfile

-- 
Karl Voit


Re: Using maildir

2014-04-29 Thread Suvayu Ali
On Tue, Apr 29, 2014 at 11:30:24AM +0100, David Woodfall wrote:
> >Dear David,
> >
> >Are you sure that you installed mail_location variable in Dovecot correctly?
> >
> >http://wiki2.dovecot.org/MailLocation
> 
> If I'm not using imap it won't matter will it? I'm just using mutt -f
> ~/mail.

What is the value of mbox_type in your mutt config?  It should be
`Maildir'.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.


Re: Using maildir

2014-04-29 Thread David Woodfall

Dear David,

Are you sure that you installed mail_location variable in Dovecot correctly?

http://wiki2.dovecot.org/MailLocation


If I'm not using imap it won't matter will it? I'm just using mutt -f
~/mail.


Best regards,
Roman Kravets


On Tue, Apr 29, 2014 at 7:00 AM, David Woodfall  wrote:

I've just set up dovecot/procmail on a debian VPS and when using mutt
with maildir, as I navigate around, I see the new/ cur/ tmp/ folders
and inside the actual file names of the mail.

On my home box I connect locally to the imap server so I don't see
this, but is there a better way of viewing maildir without seeing
these folders and just seeing mail as normal?

Thanks for any help.

dave