Your message dated Sat, 27 Jan 2007 20:17:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#365385: mutt: unable to send message if ~/sent directory
is not there (mutt does not create it)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mutt
Version: 1.5.11+cvs20060403-1
Severity: normal
DESCRIPTION
1. Install mutt
2. Start it for the first time
3. have ~/Maildir full of messages and ~/.muttrc
set spoolfile = ~/Maildir/
4. Start composing reply to someone
5. Send message with "y"
The program stop and displays:
Couldn't lock /home/foo/sent?
PROBLEM
The error message isn't very descriptive. Did the program try to lock
a file? Is there problem while locking .... The problem is not specified.
Looking at the default composed message reveals that there is field:
Fcc: ~/sent
added by default
SUGGESTION
1) Program shoudl not add Fcc by default, especially when directory does
not exist.
2) The error message should be clear enough to indicate the error reason.
In this case better erro rmessage would have been:
Cannot save message. Directory does not exist ~/sent. Check Fcc field
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Versions of packages mutt depends on:
ii exim4-daemon-heavy [mai 4.61-1 exim MTA (v4) daemon with extended
ii libc6 2.3.6-7 GNU C Library: Shared libraries
ii libdb4.4 4.4.20-4 Berkeley v4.4 Database Libraries [
ii libgnutls12 1.2.9-2 the GNU TLS library - runtime libr
ii libidn11 0.5.18-2 GNU libidn library, implementation
ii libncursesw5 5.5-1.1 Shared libraries for terminal hand
ii libsasl2 2.1.19.dfsg1-0.2 Authentication abstraction library
Versions of packages mutt recommends:
ii locales 2.3.6-7 GNU C Library: National Language (
ii mime-support 3.36-1 MIME files 'mime.types' & 'mailcap
-- no debconf information
--- End Message ---
--- Begin Message ---
Re: Jari Aalto 2007-01-27 <[EMAIL PROTECTED]>
> Not with the lastest mutt, but the error is still there in different
> situation. Suppose user already has "sent":
>
> 1. preparations
>
> mkdir ~/sent or chmod ugo-rwx ~/sent
>
> 2. Try to send message
>
> mutt
> <compose ..., select "y" to send>
>
> 3. Error is displayed, message is not sent.
>
> /home/foo/sent is not a mailbox.
Hi Jari,
thanks for the reply.
Sorry if you are deliberatly breaking things you get what you deserve
- an error. Your ~/sent is not an mbox folder, so the message is even
correct.
> >> [1] http://www.mutt.org/doc/devel/manual.html#record
>
> There should no Fcc: field inserted by default. The user to set in his
> ~/.muttrc if he needs one. Quoting Dave (from bugs previous's messages):
No. If you don't want the message saved, unset 'copy'. I very much
support upstream in that the've finally fixed the missing 'record'
default. Joe Average User expects that a MUA saves copies of outgoing
messages, the default is correct.
> ..if, for some reason, the folder ~/sent cannot be written to.
> Having a pre-existing directory called ~/sent might cause confusion, I
> suppose.
Yes, it will generate the proper error message.
We could put a note in NEWS.Debian that upstream changed defaults
here, but as I don't think having a non-mbox ~/sent file is likely to
be experienced by more users, it's probably not worth the trouble.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
