headers
Mutt | 2 Jun 09:45

Re: [Mutt] #3066: length of email

#3066: length of email

Changes (by pdmef):

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

Comment:

 (In [b2b844141ac1]) Allow for mail addresses longer than 256 characters
 (closes #3066).

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3066#comment:1>
Permalink | Reply | 0 comments |
headers
Rocco Rutte | 2 Jun 10:04
Picon

Re: [Mutt] #3064: Implement "show" menu to list various internal

Hi,

* Mutt wrote:

> Sounds really useful. Should I apply p1.2 or p1 to use this patch?

That was my fault when I attached them, they're identical.

Rocco
Permalink | Reply | 0 comments |
headers
Mutt | 2 Jun 10:05

Re: [Mutt] #3064: Implement "show" menu to list various internal

#3064: Implement "show" menu to list various internal configs as a nicely paged
menu

Comment (by Rocco Rutte):

 {{{
 Hi,

 * Mutt wrote:

 > Sounds really useful. Should I apply p1.2 or p1 to use this patch?

 That was my fault when I attached them, they're identical.

 Rocco
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3064#comment:>
Permalink | Reply | 0 comments |
headers
Brendan Cully | 3 Jun 09:00
Gravatar

mutt: 2 new changesets

2 new changesets in mutt:

http://dev.mutt.org/hg/mutt/rev/d6d04a7f5aea
changeset:   5416:d6d04a7f5aea
branch:      HEAD
tag:         tip
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Mon Jun 02 09:45:19 2008 +0200
summary:     Allow for printing variable values longer than 256 characters

http://dev.mutt.org/hg/mutt/rev/b2b844141ac1
changeset:   5415:b2b844141ac1
branch:      HEAD
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Mon Jun 02 09:44:44 2008 +0200
summary:     Allow for mail addresses longer than 256 characters (closes #3066).

--

-- 
Repository URL: http://dev.mutt.org/hg/mutt
Permalink | Reply | 0 comments |
headers
Mutt | 4 Jun 11:32

Re: [Mutt] #2897: message counts in mailbox view all zero (IMAP,

#2897: message counts in mailbox view all zero (IMAP, courier)

Comment (by sideshowbarker):

 Replying to [comment:15 knuta]:
 > I'm not arguing that dots should be valid directory separators in the
 configuration, that's not my point at all. I just wrote the patch this way
 to make it small and easy to read and understand. I's meant for
 demonstrating what the problem is and a way for others to verify if their
 symptoms are due to the same problem, not as a complete fix to be applied
 as-is :-)

 I'm the one who originally filed this particular bug, so I'll try to make
 time to apply the patch and report back about whether it eliminates the
 symptoms for my case.

   --Mike

 I guess I should note that this had become much less of an acute problem
 for me than it was when I first reported it. The reason being: After
 initially reporting -- more than a year ago now -- the regression that's
 the subject of this issue, I also took a little time to pinpoint the exact
 change that actually introduced it (r5052 -- see
 http://dev.mutt.org/trac/ticket/2897#comment:1 ). But I lacked the chops
 to productively try to figure out myself how to fix it, and for a long
 time after, saw little or no movement being made toward a fix.

 For the record, with the above comment I'm not trying to place blame --
 just saying that's the way things were. And as an open-source coder
 myself, I fully understand that the project committers have the right to
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 5 Jun 11:38

[Mutt] #3068: mutt -d 5 may crash

#3068: mutt -d 5 may crash

 Hi,

 If you look into mutt_addr_is_user, you will see twice dprint(5,
 "...%s\n", .... mutt_fqdn(X)); And mutt_fqdn may return NULL. I'm
 attaching diff which fixed this issue for me.

 Thank you

 --
   Vlad

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3068>
Permalink | Reply | 2 comments |
headers
Mutt | 5 Jun 11:42

[Mutt] #3069: smime crash when replying to mail

#3069: smime crash when replying to mail

 Hi,

 I have no idea how smime exactly works, but I guess that SmimeDefaultKey
 is NULL unless something is set in .muttrc. However this crashes mutt when
 replying to smime signed mail. I'm attaching patch which fixes this issue
 for me.

 Thank you

 --
   Vlad

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3069>
Permalink | Reply | 9 comments |
headers
Vladimir Marek | 5 Jun 11:49
Picon

Re: [Mutt] #3069: smime crash when replying to mail

>  I have no idea how smime exactly works, but I guess that SmimeDefaultKey
>  is NULL unless something is set in .muttrc. However this crashes mutt when
>  replying to smime signed mail. I'm attaching patch which fixes this issue
>  for me.

Thinking beyond the fix, would not be better to stop any smime
processing earlier, let's say somewhere in mutt_protect, if
SmimeDefaultKey is NULL ?

Thank you

--

-- 
	Vlad
Permalink | Reply | 0 comments |
headers
Mutt | 5 Jun 12:53

Re: [Mutt] #3069: smime crash when replying to mail

#3069: smime crash when replying to mail

Changes (by pdmef):

  * component:  mutt => crypto

Comment:

 Hmm, the code changes smime_sign_message() so first we need to know why it
 attempts to S/MIME sign the message at all. What are your pgp and s/mime
 settings ("mutt -D | grep crypt" and remove any private data)?

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3069#comment:2>
Permalink | Reply | 3 comments |
headers
Mutt | 5 Jun 13:17

Re: [Mutt] #3068: mutt -d 5 may crash

#3068: mutt -d 5 may crash

Changes (by pdmef):

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

Comment:

 (In [5ab92dd44ce2]) Wrap Fqdn in NONULL() to prevent crash with -d5 if
 Fqdn is NULL

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3068#comment:1>
Permalink | Reply | 1 comment |

Gmane