[Mulberry-discuss] Mulberry-discuss Digest, Vol 93, Issue 6

[Graziano Previato]

So, Mulberry is really wonderful, and I agree with this statement.

What I love is the straightforward use, the implementation of the standard,
the Sieve management, etc...
I've tried lot of competitors, but for a reason or another, no way to find
out a good enough...

I wonder why we are unable to keep it alive, as an Open Source project,
managed by ... Cyrus?..

I've already made an effort, some time ago, to display html mail in
Mulberry, and finally I got it... just because I cannot find out another
solution...
I've seen a lot of people working on the sources, for a reason or another,
but it's not enough to keep it alive...

Could be we can join our efforts?

-----------------------------
Ing. Graziano Previato
Mobile: [phone]

[Kenneth Porter]

Post by Graziano Previato
What I love is the straightforward use, the implementation of the
standard, the Sieve management, etc...
I've tried  lot of competitors, but for a reason or another, no way to
find out a good enough...

I missed the Sieve management. Where is that?

Post by Graziano Previato
I've already made an effort, some time ago, to display html mail in
Mulberry, and finally I got it... just because I cannot find out
another solution...

Do you have patches? Perhaps on Github?

My only real desire for better presentation is to display images. That's
why I run Thunderbird in parallel.

Hmm, I was going to suggest the other mailing list for developers but it
looks like Cyrus removed it from the list server. :( The archives have
some historical value.

I find the code too arcane to put serious effort into. I'd find it
easier to locate a good mail library and hook it up to a portability
layer like Qt or wxWidgets and recreate Mulberry from the ground up.
Modern tools and libraries have come a long way since Mulberry went into
mothballs, and I'd expect a rewrite would be a lot more stable and
secure. (Normally I'd vote against such an effort but most of the meat
of Mulberry has already been rewritten elsewhere and one would just have
to add back the things that make Mulberry unique.)

[Cyrus Daboo]

Hi Kenneth,

--On December 19, 2017 at 10:18:18 AM -0800 Kenneth Porter

Post by Kenneth Porter
Hmm, I was going to suggest the other mailing list for developers but it
looks like Cyrus removed it from the list server. :( The archives have
some historical value.

Mailing lists and archives are still available (though you may need to
accept the self-signed cert):

<https://lists.mulberrymail.com/mailman/listinfo>

The main website is woefully out of date. I should probably just replace it
and point to the trac site <http://trac.mulberrymail.com/mulberry/wiki>
(which also hasn't been update in a while).

As for any future development I would agree that trying to build off the
existing code base is not a good idea. As you noted, development tools and
technologies have come a long way and it would be much better to use modern
frameworks to build anything that you would want to keep usable for the
foreseeable future.

[Kenneth Porter]

--On Tuesday, December 19, 2017 1:37 PM -0500 Cyrus Daboo

Post by Cyrus Daboo
Mailing lists and archives are still available (though you may need to
<https://lists.mulberrymail.com/mailman/listinfo>

Aha. I'd used the link in a random list email and it used http, not https.
The most recent email has https in the headers. My bad for not noticing
that the folder wasn't sorted by date and I looked in an ancient email for
the list link.

You could put a redirect in the non-SSL server to 302 to the SSL one.

[Gleason]

Cyrus,

Post by Cyrus Daboo
Hi Kenneth,
--On December 19, 2017 at 10:18:18 AM -0800 Kenneth Porter

Post by Kenneth Porter
Hmm, I was going to suggest the other mailing list for developers but it
looks like Cyrus removed it from the list server. :( The archives have
some historical value.

Mailing lists and archives are still available (though you may need to
<https://lists.mulberrymail.com/mailman/listinfo>
The main website is woefully out of date. I should probably just replace it
and point to the trac site
<http://trac.mulberrymail.com/mulberry/wiki>
(which also hasn't been update in a while).
As for any future development I would agree that trying to build off the
existing code base is not a good idea. As you noted, development tools and
technologies have come a long way and it would be much better to use modern
frameworks to build anything that you would want to keep usable for the
foreseeable future.

The downside of that is that instead of rewriting the new tools and technologies, you would
be rewriting the well conceived and implemented unique features of Mulberry. Not necessarily
even an equal tradeoff, I suspect.

[Kenneth Porter]

Post by Gleason
The downside of that is that instead of rewriting the new tools and
technologies, you would be rewriting the well conceived and implemented
unique features of Mulberry. Not necessarily even an equal tradeoff, I
suspect.

Free software tends to be scratching an itch of the programmer that writes
it. I'd only be writing the parts that I used. I don't heavily customized
Mulberry the way I see you describe, so I wouldn't be rewriting that part.