headers
Mutt | 1 Feb 2009 01:30

[Mutt] #3180: mutt does not set the From: header by default

#3180: mutt does not set the From: header by default
------------------------------+---------------------------------------------
 Reporter:  antonio <at> dyne.org  |       Owner:  mutt-dev
     Type:  defect            |      Status:  new     
 Priority:  minor             |   Milestone:          
Component:  mutt              |     Version:          
 Keywords:                    |  
------------------------------+---------------------------------------------
 Hi guys,
 I'm forwarding a bug opened to the debian team, we have the intention to
 close the bug because for us it is not a problem but the person who cut
 the bug keeps reopening it.

 What I'm looking here is a *clear* response from you about this behavior,
 do you want to add the From header by default or do you want to let the
 MTA manage it?

 This is the first bug report, done 8 years ago (sic).

 ---

 With the default configuration of mutt and exim, bounced messages may end
 up with no From: headers.  This can be reproduced by sending a message
 while
 saving a copy in =sent.  If that copy is then bounced, then mutt doesn't
 add a From: header since the default Muttrc doesn't do so, and exim
 doesn't
 add one since Resent-From is present.

 Something's got to give here.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mutt | 2 Feb 2009 10:22

Re: [Mutt] #3173: Mutt with gmail crashes after IMAP timeout

#3173: Mutt with gmail crashes after IMAP timeout
-----------------------+----------------------------------------------------
  Reporter:  cycykewl  |       Owner:  mutt-dev        
      Type:  defect    |      Status:  new             
  Priority:  major     |   Milestone:                  
 Component:  mutt      |     Version:  1.5.18          
Resolution:            |    Keywords:  gmail crash imap
-----------------------+----------------------------------------------------
Changes (by pietro):

 * cc: pbinetti <at> gmail.com (added)

Comment:

 I have the same problem with Mutt 1.5.18 on Debian (Testing) Linux 2.6.26.
 Not only with Gmail-IMAP, but also with the IMAP mail server at work.

 Last lines of .muttdebug0 after a crash:

 tls_socket_read (A TLS packet with unexpected length was received.)
 imap_cmd_step: Error reading server response.
 imap_exec: command failed:
 Error polling mailboxes
 Error queueing command
 Mailbox closed
 mutt_socket_close: Attempt to close closed connection.
 mx_check_mailbox: null or invalid context.

 And my Mutt is (mutt -v):
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 3 Feb 2009 21:19

Re: [Mutt] #3177: mutt wish: send_charset default "us-ascii:utf-8"

#3177: mutt wish: send_charset default "us-ascii:utf-8"
-------------------------------+--------------------------------------------
  Reporter:  antonio <at> dyne.org  |       Owner:  mutt-dev
      Type:  enhancement       |      Status:  new     
  Priority:  minor             |   Milestone:          
 Component:  mutt              |     Version:  1.5.19  
Resolution:                    |    Keywords:          
-------------------------------+--------------------------------------------

Comment(by myon):

 As much as I like utf-8, I think the current default makes sense.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3177#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 4 Feb 2009 16:22

Re: [Mutt] #3179: Attach: pseudoheader doesn't work with files with

#3179: Attach: pseudoheader doesn't work with files with spaces
-----------------------+----------------------------------------------------
  Reporter:  edgewood  |       Owner:  mutt-dev
      Type:  defect    |      Status:  new     
  Priority:  minor     |   Milestone:          
 Component:  mutt      |     Version:  1.5.17  
Resolution:            |    Keywords:          
-----------------------+----------------------------------------------------

Comment(by chrisbra):

 I have created an experimental patch for that issue. My C-skills are
 rusty, but it seems to work for me. This patch is against 1.5.18.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3179#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Matthias Andree | 4 Feb 2009 16:41
Picon
Picon

current mutt on Cygwin fails to compile.

Greetings,

mutt cannot currently be compiled on Cygwin (1.5), as it uses  
unimplemented functions in a handful of places, namely fputws, fgetws,  
ungetwc [1]. It appears as though Cygwin 1.7 test versions implement these  
[2], however, 1.7 is not supposed to be used in production.

Reverting to the changeset shown below allows me to build mutt on Cygwin.

changeset:   5479:95a11c7f677d
branch:      HEAD
user:        Vincent Lefevre <vincent <at> vinc17.org>
date:        Mon Aug 18 13:08:43 2008 -0700
summary:     Updated French translation.

So what's the view on Cygwin portability of mutt? Ignore? Wait for Cygwin  
to provide interfaces? Implement portability later?

Thanks & best regards
MA

[1] http://dev.mutt.org/trac/changeset/3e850c6e43fd by Rocco to fix ticket  
#3033, Aug 2008
[2] http://www.cygwin.com/ml/cygwin-announce/2008-12/msg00023.html

--

-- 
Matthias Andree
Permalink | Reply | 1 comment |
headers
Dan Fandrich | 4 Feb 2009 20:13
Favicon

Re: current mutt on Cygwin fails to compile.

On Wed, Feb 04, 2009 at 04:41:40PM +0100, Matthias Andree wrote:
> mutt cannot currently be compiled on Cygwin (1.5), as it uses  
> unimplemented functions in a handful of places, namely fputws, fgetws,  
> ungetwc [1]. It appears as though Cygwin 1.7 test versions implement these 
> [2], however, 1.7 is not supposed to be used in production.

There's a bug open on this: http://dev.mutt.org/trac/ticket/3148
I'll attach my half-baked patch to the bug entry.

>>> Dan
--

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved
Permalink | Reply | 0 comments |
headers
Derek Martin | 4 Feb 2009 20:50

Next week's anniversary...

The last non-security-fix stable release of Mutt (Mutt-1.4.2) was
released on Feb 11, 2004, 5 years ago next Wednesday.  Should we have
a celebration? ;-)

--

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.
Permalink | Reply | 9 comments |
headers
Brendan Cully | 4 Feb 2009 20:54
Gravatar

Re: Next week's anniversary...

On Wednesday, 04 February 2009 at 13:50, Derek Martin wrote:
> The last non-security-fix stable release of Mutt (Mutt-1.4.2) was
> released on Feb 11, 2004, 5 years ago next Wednesday.  Should we have
> a celebration? ;-)

A party sounds like a great idea. How about a bug hunting party?

http://dev.mutt.org/trac/query?status=infoneeded&status=started&status=assigned&status=infoneeded_new&status=new&status=accepted&group=status&milestone=1.6
Permalink | Reply | 7 comments |
headers
Derek Martin | 4 Feb 2009 21:04

Re: bug hunting party

On Wed, Feb 04, 2009 at 11:54:16AM -0800, Brendan Cully wrote:
> On Wednesday, 04 February 2009 at 13:50, Derek Martin wrote:
> > The last non-security-fix stable release of Mutt (Mutt-1.4.2) was
> > released on Feb 11, 2004, 5 years ago next Wednesday.  Should we have
> > a celebration? ;-)
> 
> A party sounds like a great idea. How about a bug hunting party?
> 
> http://dev.mutt.org/trac/query?status=infoneeded&status=started&status=assigned&status=infoneeded_new&status=new&status=accepted&group=status&milestone=1.6

I have a thought about the approach to fix #2560:

  http://dev.mutt.org/trac/ticket/2560

The first time Mutt needs to call iconv, it should get (and cache) the
list of available encodings (the equivalent of iconv -l from the
command line).  If the message's encoding is not listed, display an
error indicating that mutt will be unable to display the message.

Alternately (perhaps configurably), Mutt could use the assumed charset
to attempt to display the message.

Thoughts?

--

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.
(Continue reading)

Permalink | Reply | 6 comments |
headers
John J. Foster | 5 Feb 2009 01:38

Re: Next week's anniversary...

On Wed, Feb 04, 2009 at 01:50:38PM -0600, Derek Martin wrote:
> The last non-security-fix stable release of Mutt (Mutt-1.4.2) was
> released on Feb 11, 2004, 5 years ago next Wednesday.  Should we have
> a celebration? ;-)
> 
Up until about a year or so ago, I would have had some stupid*** comment
to make, but I am extremely happy with all the progress lately. I really
wish I could code (especially with an understanding of IMAP, which I
don't have), but 1.6 doesn't really seem too far off.

festus

P.S. To answer the question you posed though, yeah - where do we meet
for drinks. I'm in Fort Collins, CO.
Permalink | Reply | 0 comments |

Gmane