headers
Todd Hoffmann | 1 Feb 06:19
Picon

Re: Trying to patch mutt to use gmail imap extension


On Tue, Jan 31, 2012 at 10:54:43AM -0600, David Champion wrote:
> Todd, thanks for looking into this.  Would you be willing to look at the
> keywords patch located here: https://bitbucket.org/dgc/mutt-dgc/qseries
> and adapt your fix to that patch queue?  I'd love for this new approach
> to keyword handling to fully support Google's labels as well.

I read the keywords patch description and it definitely sounds useful. One
reminder is that gmail labels are not in the headers and can only be accessed
using the imap fetch command.  Users of offlineimap or some other mechanism to
retrieve the messages and put them in mboxes or a maildir structure will not be
able to extract them from headers, in general. Of course, a patched version of
offlineimap or an imap proxy (see https://github.com/zmughal/gmail-imap-label)
that assigns the labels to a header could be used also.

> 
> If you can't do this I'll see about integrating it when I have a chance.
> But if you can do it I can just add your patch to my series.

My implementation just takes the labels and puts them in the X-LABEL header, so
it _may_ play nicely the existing keywords patch just by setting
$xlabel_delimiter. I'll compile in the keywords patch along with mine and give
it a try.

One obvious problem with my patch is header caching. Mutt has no way of knowing
if the labels have changed so it can't automatically refresh the cache if they
do change. I haven't made any real efforts to fix this. For now I'm just not
using header caching and close/reopen the mailbox to force a refresh.

cheers!
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Feb 09:51

Re: [Mutt] #3555: Mutt ASCII signatures in figlet font sent (received) distorted

#3555: Mutt ASCII signatures in figlet font sent (received) distorted
------------------------+---------------------------------------------------
  Reporter:  riderplus  |       Owner:  mutt-dev        
      Type:  defect     |      Status:  closed          
  Priority:  minor      |   Milestone:                  
 Component:  mutt       |     Version:  1.5.21          
Resolution:  wontfix    |    Keywords:  ascii; signature
------------------------+---------------------------------------------------
Changes (by riderplus):

  * status:  new => closed
  * resolution:  => wontfix

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3555#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 1 Feb 10:02

[Mutt] #3563: NO Beep for New Messages, but "beep_new" is set

#3563: NO Beep for New Messages, but "beep_new" is set
-----------------------------------------+----------------------------------
 Reporter:  riderplus                    |       Owner:  mutt-dev
     Type:  defect                       |      Status:  new     
 Priority:  major                        |   Milestone:          
Component:  mutt                         |     Version:  1.5.21  
 Keywords:  beep; set beep_new; no beep  |  
-----------------------------------------+----------------------------------
 I use mutt on xterm, konsole and urxvt. I have "set beep_new=yes" in my
 ~/.muttrc, but there's no beep upon receiving new messages. I also have
 "set beep=yes", which works fine, as I get a beep when an error is
 encountered. I always get a notification "New message in inbox" when a new
 message is received, but no beep. It should have worked I think, since the
 variable is set. I have tried on a different computer with gnome-terminal,
 and no luck.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3563>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 2 Feb 07:56

[Mutt] #3564: can't choose certain public keys for encryption even when specifying the keyID

#3564: can't choose certain public keys for encryption even when specifying the
keyID
----------------------+-----------------------------------------------------
 Reporter:  likkk     |       Owner:  mutt-dev
     Type:  defect    |      Status:  new     
 Priority:  critical  |   Milestone:          
Component:  mutt      |     Version:  1.5.21  
 Keywords:            |  
----------------------+-----------------------------------------------------
 I get stuck when trying to send an encrypted mail after entering
 0xbc8002f3 as keyID... mutt keeps asking me for keyID. The key is in my
 keyring but it is not listed when entering nothing. You can fetch the key
 from the keyservers. Please help! Thank you!

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3564>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 2 Feb 10:10

Re: [Mutt] #3562: with exchange 2010 IMAP -- tls_socket_read (A TLS packet with unexpected length was received)

#3562: with exchange 2010 IMAP  -- tls_socket_read (A TLS packet with unexpected
length was received)
---------------------------+------------------------------------------------
 Reporter:  jreidthompson  |       Owner:  mutt-dev
     Type:  defect         |      Status:  new     
 Priority:  major          |   Milestone:          
Component:  mutt           |     Version:  1.5.21  
 Keywords:                 |  
---------------------------+------------------------------------------------
Changes (by berni):

 * cc: berni@… (added)

Comment:

 I have the same problem, but I'm pretty sure superflous mailboxes are not
 the cause.

 {{{
 mailboxes =INBOX
 }}}

 I'll try to get a debug log when it happens. Also against Exchange 2010
 SP1.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3562#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 2 Feb 10:25

Re: [Mutt] #3562: with exchange 2010 IMAP -- tls_socket_read (A TLS packet with unexpected length was received)

#3562: with exchange 2010 IMAP  -- tls_socket_read (A TLS packet with unexpected
length was received)
---------------------------+------------------------------------------------
 Reporter:  jreidthompson  |       Owner:  mutt-dev
     Type:  defect         |      Status:  new     
 Priority:  major          |   Milestone:          
Component:  mutt           |     Version:  1.5.21  
 Keywords:                 |  
---------------------------+------------------------------------------------

Comment(by berni):

 {{{
 [2012-02-02 10:15:55] Sorting mailbox...
 [2012-02-02 10:15:55] 5123 kept, 65 deleted.
 [2012-02-02 10:15:56] 4> a0022 IDLE
 [2012-02-02 10:15:56] 4< + IDLE accepted, awaiting DONE command.
 [2012-02-02 10:21:49] Search wrapped to top.
 [2012-02-02 10:21:49] No unread messages.
 [2012-02-02 10:21:49] tls_socket_read (A TLS packet with unexpected length
 was received.)
 [2012-02-02 10:21:53] imap_cmd_step: Error reading server response.
 [2012-02-02 10:21:53] mutt_free_body: not unlinking service_pickup.html.
 [2012-02-02 10:21:53] Mailbox closed
 [2012-02-02 10:21:54] Error reading IDLE response
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3562#comment:8>
Mutt <http://www.mutt.org/>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 2 Feb 15:35

Re: [Mutt] #3562: with exchange 2010 IMAP -- tls_socket_read (A TLS packet with unexpected length was received)

#3562: with exchange 2010 IMAP  -- tls_socket_read (A TLS packet with unexpected
length was received)
---------------------------+------------------------------------------------
 Reporter:  jreidthompson  |       Owner:  mutt-dev
     Type:  defect         |      Status:  new     
 Priority:  major          |   Milestone:          
Component:  mutt           |     Version:  1.5.21  
 Keywords:                 |  
---------------------------+------------------------------------------------

Comment(by berni):

 Argh ... it looks like my problem was self-induced.

 Our Exchange CAS (Client-Access servers) are loadbalanced behind a pair of
 F5 BigIP SLBs. These boxes have a default idle timeout of just 300s, which
 is way lower than the 30 minutes the RFC mandates and also lower than the
 15 minutes mutt uses for idle_timeout.

 {{{
 set imap_keepalive = 60
 }}}

 works around the problem, increasing the timeout on the SLB fixes it. At
 least it looks like, will take a few days until I can be sure.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3562#comment:9>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olaf Hering | 3 Feb 21:02
Picon

[PATCH] add real prototype for re_match_2_internal in regex.c

# HG changeset patch
# User Olaf Hering <olaf <at> aepfle.de>
# Date 1328299312 -3600
# Branch HEAD
# Node ID 8743a4a6bd37bd5c1b873c7758046fdbc47f4021
# Parent  c26dbc7021f4ec56c0e41d43019e43dd0be666de
add real prototype for re_match_2_internal in regex.c

regex.c: In function 're_search_2':
regex.c:3584:6: warning: call to function 're_match_2_internal' without a real prototype [-Wunprototyped-calls]
regex.c:384:12: note: 're_match_2_internal' was declared here
regex.c: In function 're_match':
regex.c:3706:9: warning: call to function 're_match_2_internal' without a real prototype [-Wunprototyped-calls]
regex.c:384:12: note: 're_match_2_internal' was declared here
regex.c: In function 're_match_2':
regex.c:3751:9: warning: call to function 're_match_2_internal' without a real prototype [-Wunprototyped-calls]
regex.c:384:12: note: 're_match_2_internal' was declared here

Signed-off-by: Olaf Hering <olaf <at> aepfle.de>

diff -r c26dbc7021f4 -r 8743a4a6bd37 regex.c
--- a/regex.c
+++ b/regex.c
@@ -381,7 +381,9 @@ typedef char boolean;
 #define false 0
 #define true 1

-static int re_match_2_internal ();
+static int re_match_2_internal (struct re_pattern_buffer *bufp,
+	const char *string1, int size1, const char *string2, int size2, int pos,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 9 Feb 22:16

Re: [Mutt] #3300: mutt-1.5.20: mutt terminates with >=gpgme-1.2.0

#3300: mutt-1.5.20: mutt terminates with >=gpgme-1.2.0
----------------------+-----------------------------------------------------
 Reporter:  grobian2  |       Owner:  mutt-dev
     Type:  defect    |      Status:  new     
 Priority:  major     |   Milestone:          
Component:  crypto    |     Version:          
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by idl0r):

 * cc: idl0r@… (added)

Comment:

 *push*

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3300#comment:6>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 9 Feb 22:46

Re: [Mutt] #3337: [Bcc header showing] Mutt + Exim

#3337: [Bcc header showing] Mutt + Exim
-----------------------+----------------------------------------------------
 Reporter:  will177    |       Owner:  mutt-dev
     Type:  defect     |      Status:  new     
 Priority:  major      |   Milestone:          
Component:  mutt       |     Version:  1.5.18  
 Keywords:  bcc, exim  |  
-----------------------+----------------------------------------------------
Changes (by idl0r):

 * cc: idl0r@… (added)

Comment:

 *push*

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3337#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |

Gmane