begin  Thorsten Haude quotation:
>
> Received: from pop.kundenserver.de [212.227.126.142]
>         by localhost with POP3 (fetchmail-5.8.0)
>         for yooden@localhost (single-drop); Sun, 14 Apr 2002 17:00:25 +0200
(CEST)

That's a really old fetchmail, with a lot of known bugs, including
problems with parsing usernames with spaces in them.  Try upgrading it,
and see if the problem persists.


--
Shawn McMahon                    | McMahon's Laws of Linux support:
http://www.eiv.com               | 1) There's more than one way to do it
AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong

begin  Will Yardley quotation:
>
> > And I cannot verify this one.
>
> perhaps it's time (past time???) to take this discussion off list?

Is this list no longer for solving Mutt-related problems?

Or is it just that you think no one else will possibly ever have this
problem, and only the people he'd communicate with off-list could
possibly solve it?


--
Shawn McMahon                    | McMahon's Laws of Linux support:
http://www.eiv.com               | 1) There's more than one way to do it
AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong

Hi,

* Shawn McMahon <smcmahon@...> [02-04-15 22:01]:
>begin  Thorsten Haude quotation:
>> Received: from pop.kundenserver.de [212.227.126.142]
>>         by localhost with POP3 (fetchmail-5.8.0)
>>         for yooden@localhost (single-drop); Sun, 14 Apr 2002 17:00:25 +0200
(CEST)
>That's a really old fetchmail, with a lot of known bugs, including
>problems with parsing usernames with spaces in them.  Try upgrading it,
>and see if the problem persists.
Done.

Thanks so far.

Thorsten
--
The fact that windows is one of the most popular ways to operate a computer
means that evolution has made a general fuckup and our race is doomed.

I recently changed configs - I'm now using fetchmail/procmail/mutt,
and when I compose a message in mutt, I get this message when
I try to send it:

    ~/.mutt/tmp/mutt-merrill-1234-0 [#1] modified. Update encoding? ([y]/n):

Am I doing something wrong, or have a forgotten something in the
config of mutt?

TIA.

--
Hardy Merrill
Senior Software Engineer
Red Hat, Inc.
hmerrill@...

Michal 'hramrach' Suchanek (hramrach_l@...) muttered:
> I found these problems for which I know *no* 100% workaround:

> - I'm unable to browse Maildirs reliably. They can contain both messages
>   and subfolders but when I enter a maildir the message index is
>   displayed automatically

This is perfect behaviour. A Maildir should not have subdirs other then
cur, new, tmp.
If you need subdirs, use normal directories.

  ~/Mail (dir)
  |
  `-lists (dir)
  | |
  | `-mutt-users (Maildir)
  | | `-cur
  | | `-new
  | | `-tmp
  | |
  | `-somelist (mbox)
  | |
  | `-yet_another_list (Maildir)
  |   `cur
  |   `new
  |   `tmp
  |
  `-what_the_heck
  [...]

> (should be handled the same way IMAP browsing is described in
> documentation).
> - subfolders in Maildirs arent displayed in browser - start with dot
>   (set mask to show .subforder and ignore new|cur|tmp) - suggest
>   maildir_mask

IMAP folder may have subdirs. Maildirs not.

> set folder=imaps://artax.karlin.mff.cuni.cz/mail
> # During previous experiments I discovered that I'm able to set browser
> # root using $folder exactly twice: first I set it to ~/Mail as a
> # default and then to an imap server using folder-hook. After that
> # browser starts on the imap server I used first.
> #set folder=~/Mail

If you use hooks to toggle variables make sure you have a default hook
to reset the values.

folder-hook . "set folder=~/Mail"
account-hook imap-account \
   "set folder=imaps://artax.karlin.mff.cuni.cz/mail"

HTH,

Michael
--

PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key

Hi,

* Patrik Modesto [04/15/02 20:28:12 CEST] wrote:
> On Mon, Apr 15, 2002 at 03:40:03PM +0200, Rocco Rutte wrote:
> > * Patrik Modesto [04/15/02 13:46:31 CEST] wrote:
> > > I'm having problems with pgp_strict_enc. I want mutt to not encode
> > > message to quoted-printable before pgp sign, so I set pgp_strict_enc to
> > > no in my .muttrc, but mutt still encode it before sign. What's wrong? Me
> > > or mutt? (Of course! Mutt can't be wrong, I know! :-)
> >
> > Why would someone want this? QP is chosen to ensure that the
> > body of a messages is not touched and can be safely
> > transported and delivered. Signing unencoded mail may cause
> > some MTA on the path to do encoding so that you can't verify
> > anything.

> Because my emails read users of MUA, that dont understand that =50=65
> messages.

In which character set do you send non-signed mail? Maybe your
$send_charset overides it?

> Anyway. Is the pgp_strict_enc setting working? Not for me.

I just noticed that it does not always work for me.

Cheers, Rocco.

Thorsten Haude wrote:
> * Thorsten Haude <mutt@...> [02-04-15 20:19]:

> >I cannot verify the first

> And I cannot verify this one.

perhaps it's time (past time???) to take this discussion off list?

--
Will Yardley
input: william < @ hq . newdream . net . >

Hi,

* Alain Bench [04/15/02 21:31:06 CEST] wrote:
>  On Monday, April 15, 2002 at 1:15:41 AM +0200, Rocco Rutte wrote:

> > So a message would have to be encoded correctly before handing it over
> > to an SMTP delivery process and should be deliverable without any
> > modifications.

>     BTW you seem to be nearly the only one here to use PGP/MIME sigs,
> and to *not* use QP encoding: why?

Well some are encoded QP. I know some basics about encryption,
so I wonder why I would want to change that? I let mutt decide
which character encoding to use.

Cheers, Rocco.

> Is it possible to read Mailinglist of public folders on a
> Exchange Server with Mutt
I manged to configure my mutt to read my mails from the exchange server, but
unfortunatly i cannot Browse lower than one level into the public folders.
I am running:
Debian Linux woddy kernel 2.4.7 with imaptool 0.9-4
Everything else is working perfectly > writing mails, browsing subfolders of my
Inbox etc. But when i start browsing the public folder of exchange (win2000
Server, Exchange 2000 SP2) I get timeouts, eg. No response.
The interessting thing is that i can browse some folder (with no subfolders
insinde) and read the mail in these folders.
All folders i have Problems with have subdirectories. In my pager they have IMAP
+ notation.
All with the + down´t work.

Any ideas ?

Michael Tatge wrote:
> Michal 'hramrach' Suchanek (hramrach_l@...) muttered:

> > I found these problems for which I know *no* 100% workaround:
>
> > - I'm unable to browse Maildirs reliably. They can contain both messages
> >   and subfolders but when I enter a maildir the message index is
> >   displayed automatically

> This is perfect behaviour. A Maildir should not have subdirs other then
> cur, new, tmp.
> If you need subdirs, use normal directories.
[...]
> > (should be handled the same way IMAP browsing is described in
> > documentation).
> > - subfolders in Maildirs arent displayed in browser - start with dot
> >   (set mask to show .subforder and ignore new|cur|tmp) - suggest
> >   maildir_mask
>
> IMAP folder may have subdirs. Maildirs not.

perhaps the OP is confusing courier's 'maildir++' documentation with
Maildir itself.  courier imapd does actually allow subfolders, and this
is the default. folders start with a '.' by default.

you can put:
set mask="^\\."
to show only folders starting with a leading dot.

personally, i've found that the better way to use both courier IMAP and
local Maildir folders is either to put your actual mail folders in
~/Mail/ and then create symlinks from ~/Mail/foo/ to ~/Maildir/.foo/, or
to do the opposite and link ~/Maildir/.foo/ to ~/Mail/foo/.

courier's strange way of doing things makes sense when the only access
to the system is via IMAP, but it's a pain to use with local folders.

--
Will Yardley
input: william < @ hq . newdream . net . >

On Monday 15 April 2002 22:41, Rocco Rutte wrote:
- Hmm, try replacing "\n" by "<enter>":
-
- macro compose i ":set ispell=...<enter>" "..."

Same old thing - a rapidly blinking cursor and what appears to be a freeze of
all Mutt functions.

Cheers,

Brian

On Mon, Apr 15, 2002 at 11:50:09PM +0200, Rocco Rutte wrote:
> Hi,
>
> * Patrik Modesto [04/15/02 20:28:12 CEST] wrote:
> > On Mon, Apr 15, 2002 at 03:40:03PM +0200, Rocco Rutte wrote:
> > > * Patrik Modesto [04/15/02 13:46:31 CEST] wrote:
> > > > I'm having problems with pgp_strict_enc. I want mutt to not encode
> > > > message to quoted-printable before pgp sign, so I set pgp_strict_enc to
> > > > no in my .muttrc, but mutt still encode it before sign. What's wrong? Me
> > > > or mutt? (Of course! Mutt can't be wrong, I know! :-)
> > >
> > > Why would someone want this? QP is chosen to ensure that the
> > > body of a messages is not touched and can be safely
> > > transported and delivered. Signing unencoded mail may cause
> > > some MTA on the path to do encoding so that you can't verify
> > > anything.
>
> > Because my emails read users of MUA, that dont understand that =50=65
> > messages.
>
> In which character set do you send non-signed mail? Maybe your
> $send_charset overides it?

I have
set send_charset="us-ascii:iso-8859-2:utf8"
in my muttrc file. How can send_charset overide pgp_strict_enc?

>
> > Anyway. Is the pgp_strict_enc setting working? Not for me.
>
> I just noticed that it does not always work for me.

Thanks.

Patrik

On aanother thread, Simon White writes:
> I always hit L to reply to lists, and hope that Mutt will reply as
> intended.

I'm generally very happy with mutt, but one thing I wish it would do,
which apparently pine and several of the Mac mailers can do, is
reply to lists without my having to update my .muttrc to tell it
about every mailing list I might ever subscribe to.  (I sub/unsub
to lots of lists and it's a chore to keep .muttrc up to date.)

Is there a way to tell mutt to just reply to the address in the To
line (or, perhaps, in the To or Cc line) and not to the sender?

99% of the time, that's what I want a list reply to do, and mutt's
so configurable that I figure there must be a way.  I'd love to
take all those "lists" lines out of my .muttrc and have mutt
"just work" for all mailing lists.  (I guessed "lists *" but it
didn't work, L said "No mailing lists found".)

Thanks!

	 ...Akkana

Akkana wrote:
> On aanother thread, Simon White writes:

> > I always hit L to reply to lists, and hope that Mutt will reply as
> > intended.

> I'm generally very happy with mutt, but one thing I wish it would do,
> which apparently pine and several of the Mac mailers can do, is reply
> to lists without my having to update my .muttrc to tell it about every
> mailing list I might ever subscribe to.

pine doesn't have this function. even in more recent versions, which
have support for rfc 2369 headers, you can't 'list-reply' or
'list-post'.  you can, of course, group-reply, but you can do this in
mutt too.

> Is there a way to tell mutt to just reply to the address in the To
> line (or, perhaps, in the To or Cc line) and not to the sender?

how would mutt pick which?  it's not psychic.

> 99% of the time, that's what I want a list reply to do, and mutt's so
> configurable that I figure there must be a way.  I'd love to take all
> those "lists" lines out of my .muttrc and have mutt "just work" for
> all mailing lists.  (I guessed "lists *" but it didn't work, L said
> "No mailing lists found".)

how is mutt supposed to know which addresses are mailing lists and which
aren't? if mutt had support for interpreting rfc 2369 style headers, i
suppose it would be possible to make a guess in some cases.

note that you probably want to use 'subscribe' rather than 'lists' for
lists that you're subscribed to.

--
Will Yardley
input: william < @ hq . newdream . net . >

Hi,

* Patrik Modesto [04/16/02 08:33:01 CEST] wrote:
> On Mon, Apr 15, 2002 at 11:50:09PM +0200, Rocco Rutte wrote:
> > In which character set do you send non-signed mail? Maybe your
> > $send_charset overides it?

> I have
> set send_charset="us-ascii:iso-8859-2:utf8"
> in my muttrc file. How can send_charset overide pgp_strict_enc?

Oops, my mistake. It must have too late. ;-)

Cheers, Rocco.

There is this

   Mail client test file v0.5 (55kb): This mbox file triggers some bugs
   and has very long field values to trigger buffer overflows.

at http://kmail.kde.org/mail-client-QA.gz . Mutt doesn't crash, but
shows only 18 mails whereas kmail shows 20. I guess that has to do with
different interpretation of From_. Is mutt supposed to behave as it
does?

Volker

--
Volker Kuhlmann 	 is possibly list0570 with the domain in header
http://volker.orcon.net.nz  Please do not CC list postings to me.

Hi,

* Brian Durant [04/16/02 08:39:12 CEST] wrote:
> On Monday 15 April 2002 22:41, Rocco Rutte wrote:
> - Hmm, try replacing "\n" by "<enter>":
> -
> - macro compose i ":set ispell=...<enter>" "..."

> Same old thing - a rapidly blinking cursor and what appears to be a freeze of
> all Mutt functions.

Hmm, then probably your ispell doesn' behave as expected.
Yours look like wrappers, so maybe they're wrong?

Cheers, Rocco.

Rocco Rutte (s1118644@...) muttered:
> Hi,
>
> * Brian Durant [04/16/02 08:39:12 CEST] wrote:
> > On Monday 15 April 2002 22:41, Rocco Rutte wrote:
> > - Hmm, try replacing "\n" by "<enter>":
> > -
> > - macro compose i ":set ispell=...<enter>" "..."
>
> > Same old thing - a rapidly blinking cursor and what appears to be a freeze
of
> > all Mutt functions.
>
> Hmm, then probably your ispell doesn' behave as expected.
> Yours look like wrappers, so maybe they're wrong?

Unlikely. Currently he's only setting vars. <enter-commnd>set ispell=lol<enter>
should always work!

HTH,

Michael
--
"I once witnessed a long-winded, month-long flamewar over the use of
mice vs. trackballs...It was very silly."
(By Matt Welsh)

PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key

On Tuesday 16 April 2002 15:11, Rocco Rutte wrote:
- Hmm, then probably your ispell doesn' behave as expected.
- Yours look like wrappers, so maybe they're wrong?

Umm sorry, I don't understand. My iSpell is a standard version that came with
the SuSE 7.3 Pro distro. Wrappers? What are you referring to? What are
wrappers? If it has something to do with my messages, I am using KMail until
I can get this and a couple of other issues with Mutt straightened out.

Cheers,

Brian

On Mon, Apr 15, 2002 at 04:09:25PM -0700, Will Yardley wrote:
> Michael Tatge wrote:
> > Michal 'hramrach' Suchanek (hramrach_l@...) muttered:
>
> > > I found these problems for which I know *no* 100% workaround:
> >
> > > - I'm unable to browse Maildirs reliably. They can contain both messages
> > >   and subfolders but when I enter a maildir the message index is
> > >   displayed automatically
>
> > This is perfect behaviour. A Maildir should not have subdirs other then
> > cur, new, tmp.
> > If you need subdirs, use normal directories.
Why? This is how courier-imap sets things and it causes no problems
except the subfolders arent easily accessible from mutt.
> [...]
> > > (should be handled the same way IMAP browsing is described in
> > > documentation).
> > > - subfolders in Maildirs arent displayed in browser - start with dot
> > >   (set mask to show .subforder and ignore new|cur|tmp) - suggest
> > >   maildir_mask
> >
> > IMAP folder may have subdirs. Maildirs not.
Is there anything that fobids it? Mine have and some of them were created
automagically.
> perhaps the OP is confusing courier's 'maildir++' documentation with
> Maildir itself.  courier imapd does actually allow subfolders, and this
> is the default. folders start with a '.' by default.
??? procmail happily sorts into subdirs of ~/Mail which is a maildir. As
I understand Maildirs they contain mail messages in cur, new and tmp.
Other directories arent affected in any way and my be used for more maildirs.
>
> you can put:
> set mask="^\\."
> to show only folders starting with a leading dot.
>
> personally, i've found that the better way to use both courier IMAP and
> local Maildir folders is either to put your actual mail folders in
> ~/Mail/ and then create symlinks from ~/Mail/foo/ to ~/Maildir/.foo/, or
> to do the opposite and link ~/Maildir/.foo/ to ~/Mail/foo/.
Thank you for your suggestions, I have tried both already. As I find
myself typing the folder names directly more often the link solution
seems superior to mask.
>
> courier's strange way of doing things makes sense when the only access
> to the system is via IMAP, but it's a pain to use with local folders.
Yes, it is weird. But if it didnt use the dots it wouldnt be that bad.

--
	 Michal Suchanek
	 Hramrach@...

Volker Kuhlmann (hidden@...) muttered:
>   Mail client test file v0.5 (55kb): This mbox file triggers some bugs
>   and has very long field values to trigger buffer overflows.
>
> at http://kmail.kde.org/mail-client-QA.gz . Mutt doesn't crash, but
> shows only 18 mails whereas kmail shows 20. I guess that has to do with
> different interpretation of From_. Is mutt supposed to behave as it
> does?

Mutt does not see the last two mails:

X-From_: dnaber@...  Fri Jun 16 00:15:22 2000
Subject: Date in 1975

From bla <bla@...> Sat Jul 15 20:37:05 2000
X-From_: bla@...  Sat Jul 15 20:36:34 2000
Subject: HTML only

Guess it does not recognize the two ^From_ lines because of the special
format. All other ^From_ lines look like this:

From aaa@aaa Mon Jan 01 00:00:00 1997

The other format is obviously the mailer test in this case. See X-From_:
Mutt failed.
Mutt also fails with Dates. If you sort by date/date the order is not
correct.

Michael
--
"Problem solving under linux has never been the circus that it is under
AIX."
(By Pete Ehlke in comp.unix.aix)

PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key

* Shawn McMahon <smcmahon@...> [Apr 16. 2002 15:12]:
> Alternately, just do the "To:", and ignore the "Cc:", because people
> shouldn't be Cc:ing lists.  But that may just be me.

But they do. A LOT.

--
Mads Martin Jørgensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
  and totally illogic, with just a little bit more effort?"
                                 -- A. P. J.

* mutt-users <mutt-users@...> [2002-04-16 00:26 +0200]:
> I manged to configure my mutt to read my mails from the exchange
> server,

via mapi or imap protocol?

> I am running: Debian Linux woddy kernel 2.4.7 with imaptool 0.9-4

$ apt-cache search imaptool
imaptool - A tool for creating client-side image maps

> All folders i have Problems with have subdirectories. In my
> pager they have IMAP + notation.  All with the + down´t work.

Have you tried both <space> and <enter> to select those folders?

--
Johannes Franken

Professional unix/network development
mailto:jfranken@...
http://www.jfranken.de/

Moin,

* David T-G <davidtg-muttusers@...> [02-04-16 15:30]:
>Maybe, but maybe not.  I don't think we've pinned it down to a not-mutt
>problem.  Frankly I don't know what the heck is going on.
It's not Fetchmail. I use 5.9.11 now, which seems to be the latest
version, but I cannot verify David's mail.

>Personally I hope it doesn't leave mutt-users unless someone (I volunteer)
>sets up a temporary mutt-and-gpg-verification-problems@ list to get to
>the bottom of it and keep me in the loop.  I certainly want to get it
>resolved.
This might be a good idea.

Thorsten
--
It is dangerous to be right when the government is wrong.
	 - Voltaire

begin  Thorsten Haude quotation:
>
> * David T-G <davidtg-muttusers@...> [02-04-16 15:30]:
> >Maybe, but maybe not.  I don't think we've pinned it down to a not-mutt
> >problem.  Frankly I don't know what the heck is going on.
> It's not Fetchmail. I use 5.9.11 now, which seems to be the latest
> version, but I cannot verify David's mail.

Well, it's not unusual to have an occasional unverifiable mail, but for
it to be so consistent for you, it almost has to be somewhere in your
MTA path, not your MUA, since nobody else is seeing it with this
frequency.

ALMOST has.  It could be Mutt, but I don't think anybody else is going
to find anything Mutt if they haven't yet.

Try making a copy of your mail spool, and then edit that copy to remove
everything but one of the messages you can't verify, then pump that
message through gpg and see what happens.  If it still doesn't verify,
it's not Mutt.


--
Shawn McMahon                    | McMahon's Laws of Linux support:
http://www.eiv.com               | 1) There's more than one way to do it
AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong

> > Is there a way to tell mutt to just reply to the address in the To
> > line (or, perhaps, in the To or Cc line) and not to the sender?
>
> how would mutt pick which?  it's not psychic.

If a message said:

From: Alice
To: A list

the request is for a command which will initiate a reply to "A list" but not
Alice.

What's not being suggested is that mutt handle something like:

From: Alice
To: Bob, A list

However, in both cases i'd say you should just group-reply to everyone, and
if the recipient is annoyed at getting two copies of the message, they
should just use the one-line procmail/formmail solution to remove duplicate
messages. And if their OS doesn't support that, it's a great incentive to
upgrade to one which does. :)


--
Mike Schiraldi
VeriSign Applied Research

begin  Will Yardley quotation:
>
> how is mutt supposed to know which addresses are mailing lists and which
> aren't?

IMHO, if you hit "list-reply" and Mutt doesn't recognize a list, it
should assume you know what you're talking about, and pop up the "To:"
address as a "yes/no" default.  Then if you say no, it should cycle
through the Cc: addresses until you say "yes" or "q".

Alternately, just do the "To:", and ignore the "Cc:", because people
shouldn't be Cc:ing lists.  But that may just be me.


--
Shawn McMahon                    | McMahon's Laws of Linux support:
http://www.eiv.com               | 1) There's more than one way to do it
AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong

Shawn, et al --

...and then Shawn McMahon said...
%
% begin  Thorsten Haude quotation:
% >
% > It's not Fetchmail. I use 5.9.11 now, which seems to be the latest
% > version, but I cannot verify David's mail.
%
% Well, it's not unusual to have an occasional unverifiable mail, but for
% it to be so consistent for you, it almost has to be somewhere in your
% MTA path, not your MUA, since nobody else is seeing it with this
% frequency.

I don't know that I'd say that.  I cannot verify my own messages in my
own =mutt-users fcc folder.


%
...
% everything but one of the messages you can't verify, then pump that
% message through gpg and see what happens.  If it still doesn't verify,
% it's not Mutt.

I had previously tried saving the body and the signature of a given
message and found that the signature was valid but not verified.

I tried this method, using my editor to write everything from the last
^From_ line down to the bottom of the folder out to a file, but couldn't
get gpg to do anything with it:

   [zero] [9:39am] ~>  cat /tmp/m | gpg --verify
   gpg: no signed data
   gpg: can't hash datafile: file open error
   [zero] [9:39am] ~>  gpg --verify /tmp/m
   gpg: no signed data
   gpg: can't hash datafile: file open error
   [zero] [9:39am] ~>  gpg --verify < /tmp/m
   gpg: no signed data
   gpg: can't hash datafile: file open error

What did you mean?


%
% --
% Shawn McMahon                    | McMahon's Laws of Linux support:
% http://www.eiv.com               | 1) There's more than one way to do it
% AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong


TIA & HAND

:-D
--
David T-G                      * It's easier to fight for one's principles
(play) davidtg@... * than to live up to them. -- fortune cookie
(work) davidtgwork@...
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

Michal --

...and then Michal 'hramrach' Suchanek said...
%
% On Mon, Apr 15, 2002 at 04:09:25PM -0700, Will Yardley wrote:
% > Michael Tatge wrote:
% > > Michal 'hramrach' Suchanek (hramrach_l@...) muttered:
% >
...
% > > > - I'm unable to browse Maildirs reliably. They can contain both messages
% > > >   and subfolders but when I enter a maildir the message index is
...
% >
% > > This is perfect behaviour. A Maildir should not have subdirs other then
...
% Why? This is how courier-imap sets things and it causes no problems
% except the subfolders arent easily accessible from mutt.

Just because Courier IMAP does that doesn't mean that Maildirs are
actually permitted to have subfolders therein.


...
% > > > (should be handled the same way IMAP browsing is described in
...
% > > > - subfolders in Maildirs arent displayed in browser - start with dot
...
% > > IMAP folder may have subdirs. Maildirs not.
% Is there anything that fobids it? Mine have and some of them were created
% automagically.

Please provide the Maildir spec which states that directories other than
cur, new, and tmp may be present in a Maildir.  I am sure that, given a
proper reference, the developers will fix the code so that Maildirs are
handled with full capabilities as they are designed.  You can count on
mutt to Do It Right.


% > perhaps the OP is confusing courier's 'maildir++' documentation with
...
% ??? procmail happily sorts into subdirs of ~/Mail which is a maildir. As

Sure; procmail will put mail wherever you tell it to.  That also doesn't
mean that Maildirs are permitted to have subfolders therein.


% I understand Maildirs they contain mail messages in cur, new and tmp.
% Other directories arent affected in any way and my be used for more maildirs.

I look forward to a pointer to the spec or an actual copy posted to the
list.


HTH & HAND

:-D
--
David T-G                      * It's easier to fight for one's principles
(play) davidtg@... * than to live up to them. -- fortune cookie
(work) davidtgwork@...
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

Hardy --

...and then Hardy Merrill said...
%
...
%    ~/.mutt/tmp/mutt-merrill-1234-0 [#1] modified. Update encoding? ([y]/n):
%
% Am I doing something wrong, or have a forgotten something in the
% config of mutt?

This just came up recently; you can check the archives for the full
discussion.  Is your home dir NFS mounted and are you experience clock
difference problems between machines?


%
% TIA.

HTH & HAND


%
% --
% Hardy Merrill
% Senior Software Engineer
% Red Hat, Inc.
% hmerrill@...


:-D
--
David T-G                      * It's easier to fight for one's principles
(play) davidtg@... * than to live up to them. -- fortune cookie
(work) davidtgwork@...
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!