headers
David J. Weller-Fahy | 1 Oct 05:33

Re: Sad news

* Brendan Cully <brendan <at> kublai.com> [2009-09-29 13:13 -0500]:
> On Tuesday, 29 September 2009 at 09:11, Thomas Roessler wrote:
> > On 29 Sep 2009, at 02:20, Brendan Cully wrote:
> > >I am deeply saddened to report that Rocco Rutte died of cancer last
> > >week. ... He was a huge part of the mutt community, and I know that
> > >he will be deeply missed here, and by all who knew him.
> >
> > I suggest that mutt 1.6 (when it eventually comes out!) be dedicated
> > to Rocco's memory.

+1 to the dedication.

Rocco, you will be missed.

--

-- 
dave [ please don't CC me ]
Permalink | Reply | 0 comments |
headers
Beifus Kobi-BKB015 | 1 Oct 14:05
Favicon

Portable Email Client

Hi,

I am looking for Portable Email Client for embedded system.
Can I use Mutt?

Regards,
Kobi
Permalink | Reply | 0 comments |
headers
Aron Griffis | 14 Oct 05:44
Favicon
Gravatar

Re: Sad news

I haven't been keeping up on mutt-dev for a while, so I hadn't
seen this news yet.  That's very sad and unexpected.  Rocco
remained vibrantly part of the community up until a couple months
before he died.  He struck me as exceedingly patient and
clear-minded.  His technical contributions were great, but we'll
certainly miss him more for the encouraging attitude he brought
to mutt development.

Regards,
Aron
Permalink | Reply | 2 comments |
headers
Derek Martin | 15 Oct 00:48
Gravatar

Re: Sad news

On Tue, Oct 13, 2009 at 11:44:05PM -0400, Aron Griffis wrote:
> I haven't been keeping up on mutt-dev for a while, so I hadn't
> seen this news yet.  That's very sad and unexpected.  Rocco
> remained vibrantly part of the community up until a couple months
> before he died.  He struck me as exceedingly patient and
> clear-minded.  His technical contributions were great, but we'll
> certainly miss him more for the encouraging attitude he brought
> to mutt development.

I have nothing to say that hasn't already been said, but I'd like to
echo those same sentiments.

--

-- 
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 | 1 comment |
headers
Mutt | 16 Oct 05:08

[Mutt] #3343: unset write_bcc removes BCC header in sent folder copy

#3343: unset write_bcc removes BCC header in sent folder copy
----------------------+-----------------------------------------------------
 Reporter:  chaoflow  |       Owner:  mutt-dev
     Type:  defect    |      Status:  new     
 Priority:  major     |   Milestone:          
Component:  mutt      |     Version:  1.5.20  
 Keywords:            |  
----------------------+-----------------------------------------------------
 When write_bcc is not set, mutt also removes the BCC header from the mail
 it stores in the sent folder. Most definitely not what a user wants.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3343>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 4 comments |
headers
Mutt | 16 Oct 05:10

[Mutt] #3344: set smtp_ehlo_name

#3344: set smtp_ehlo_name
-------------------------+--------------------------------------------------
 Reporter:  chaoflow     |       Owner:  mutt-dev
     Type:  enhancement  |      Status:  new     
 Priority:  major        |   Milestone:          
Component:  mutt         |     Version:  1.5.20  
 Keywords:               |  
-------------------------+--------------------------------------------------
 It would be great to have a configuration option to set the name used for
 EHLO regardless of my current hostname/domainname.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3344>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 2 comments |
headers
David J. Weller-Fahy | 19 Oct 04:47

BikINI protocol revival

Ladies and Gentlemen,

In 2003 Charles Cazabon started a project called BikINI (BikINI is not
IMAP).  With his blessing, I am continuing that project.

Specifically I am going to complete the specification, finalize the
reference implementation, request the use of a System port number (TCP
only), and submit an RFC.  The goal is to create a remote mail storage
protocol which avoids server-side message parsing, and is as simple as
possible to implement.  I've created a wiki [1] to document the work on
the both the specification and software.

[1]: http://bikini.caterva.org

I am posting this to all the mailing lists having members I believe
would have interest in this project (either helping or trying out the
server as it becomes viable).  I will post nothing else on this list
relating to BikINI except to announce a reference implementation
release.

If you are interested in helping with any part of this, please email me
directly (dave dash bikini at weller dash fahy dot com) or sign up for
the bikini <at> lists.caterva.org mailing list (see wiki for details).

Regards,
--

-- 
dave [ please don't CC me ]
Permalink | Reply | 0 comments |
headers
Mun | 20 Oct 01:43
Picon

Re: Threading representation within Index

Hi,

I apologize, but I am resurrecting an old e-mail I sent to the group (see
below).  My attempts to workaround Outlook have not been successful so I
am attempting to approach my issue in a different manner.

Please see my comments below.

On Mon, Aug 17, 2009 at 12:09 PM PDT, Mun Johl wrote:
MJ> Hi,
MJ> 
MJ> I'm running Mutt 1.5.20 on Red Hat 5.3 and I'm trying to understand how
MJ> Mutt ascertains how to represent e-mails in the threaded view within the
MJ> Index.
MJ> 
MJ> Here's my issue: I forward Outlook e-mails to my Linux box (IMAP/POP are
MJ> not supported--don't get me started).  When Outlook does the forwarding,
MJ> it alters some of the header.  Therefore, I process all of my e-mails
MJ> via a script on the Linux box in an attempt to reconstruct the important
MJ> header lines (e.g., from:, to:, and subject:).
MJ> 
MJ> It turns out that if the initial e-mail message is no longer in the
MJ> mbox, then all successive e-mails show the threading symbols
MJ> correctly but the entire subject text is depicted for each
MJ> successive message in the index for that thread.

I'm wondering now why Mutt is showing the subject text for each message
in the thread instead of only the "first" message of the sub-thread
still residing within my mbox?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 21 Oct 18:32

[Mutt] #3345: Mutt fails during SSL certificate checks

#3345: Mutt fails during SSL certificate checks
-----------------------+----------------------------------------------------
 Reporter:  forrie     |       Owner:  mutt-dev
     Type:  defect     |      Status:  new     
 Priority:  minor      |   Milestone:          
Component:  mutt       |     Version:  1.5.20  
 Keywords:  ssl check  |  
-----------------------+----------------------------------------------------
 I have trouble with Mutt 1.5.20 (2009-06-14) where the SSL certificate
 check and save does not function properly.  This is on CentOS 5.3.

 What happens is the SSL cert (self-generated) is saved to
 .mutt_certificates and subsequent actions continue to save/append the
 certificate to the file.  In either case, I'm constantly asked whether I
 want to save the certificate.

 I've posted on Google before and there seems to be a few other people who
 experience this.  Others don't.

 Previously, I had this on a FreeBSD-7.x system.  On CentOS 5.3, a fresh
 and updated install, I have the same problem.

 I have not yet checked out and compiled the latest development code - I
 will be happy to, if this bug has been addressed.

--

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

Permalink | Reply | 8 comments |
headers
Mutt | 21 Oct 18:58

Re: [Mutt] #3345: Mutt fails during SSL certificate checks

#3345: Mutt fails during SSL certificate checks
-----------------------+----------------------------------------------------
 Reporter:  forrie     |       Owner:  mutt-dev
     Type:  defect     |      Status:  new     
 Priority:  minor      |   Milestone:          
Component:  mutt       |     Version:  1.5.20  
 Keywords:  ssl check  |  
-----------------------+----------------------------------------------------

Comment(by forrie):

 I compiled 1.5.20h and it doesn't recognize the URI format:

 mutt -f imap://user:password <at> localhost

 So I'm going to revert back to the last release version for now.

--

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

Gmane