Mailtrain v3 - Development

[talheim-it]

We are going to start the development of Mailtrain V3.

Mailtrain v3 is focusing on the stability and updating all libraries to the latest versions.

ToDo:

• [ ] Update Mailtrain libraries to latest version
• [ ] Testing v3
• [ ] Write user and developer documentation for Maitrain v3

Feature Requests are collected in this issue: #1373

[fthobe]

Hey, I really appreciate the effort and would totally be up to sponsor features with my company giving development resources as I am infinitely sick and tired of mailchimp. Is there a feature list you plan to include? I saw all feature requests and bug reports have been closed, what's the new roadmap here?

[talheim-it]

@fthobe the list above will be adopted.

We initialize start to prepare the base to get all up to date and write the documentation so it is easier for developers starting with development for mailtrain.

We also plan to move to containers. OS packages maybe later. But to speed up the development containers are easier.

[fthobe]

So v3 will be an intermediate step basically adjusting some architecture and update libraries, correct?

[bures]

It would help us to know what features are essential for you. We would like to make Mailtrain a bit leaner in order to simplify it's maintenance. As the result, we would like to drop some functionality that probably no one ever used (such as Reports). In order not to remove stuff that is used, we would like to know which Mailtrain features our community uses (like LDAP, automation = triggered campaigns, RSS campaigns, list segmentation, GrapeJS, API - which functions).

[fthobe]

If you share some details I can contribute a full time developer for 2-4 weeks, but there must be a tangible outcome for us -> kill of mailchimp by integrating abandoned cart and purchase based triggers, if we on the way close your bucket list as well I am perfectly happy with that.

[bures]

@fthobe, can you create a separate ticket for the functionality you mentioned and describe it there in a bit more detail? If your developer know his/her business, I would be happy to supervise this effort a bit a then bring the functionality in. I just would like to see first, how it fits in. If it fits, I would let you know once Mailtrain v3 will be in a shape when contributions would be sensible.

[talheim-it]

@fthobe we can make an issue for feature requests to collect them for v3.

I can make one but the want to get mailtrain up to date first.

Two things I imagine is ldap / sso and 2FA.

[fthobe]

can you create a separate ticket for the functionality you mentioned and describe it there in a bit more detail?

Issue #1000 was testing the water and never received response ;) If the ticket is reopened I can elaborate and expand it.

If your developer know his/her business, I would be happy to supervise this effort a bit a then bring the functionality in.

We do have some capable people;)

I just would like to see first, how it fits in. If it fits, I would let you know once Mailtrain v3 will be in a shape when contributions would be sensible.

I totally agree that features that go beyond basic newsletter templates should remain a modular component.

We would like to make Mailtrain a bit leaner in order to simplify it's maintenance. As the result, we would like to drop some functionality that probably no one ever used (such as Reports). In order not to remove stuff that is used, we would like to know which Mailtrain features our community uses (like LDAP, automation = triggered campaigns, RSS campaigns, list segmentation, GrapeJS, API - which functions).

We do have capable people ;)

I think LDAP while a great technology, in times of Microsoft Entra and google workspace is becoming more and more redundant. Also considering the effort that now needs to put into Microsoft on premise installations to keep it running (certificates mostly).

Removing reports and segments would reduce mailtrain to an smtp frontend / mail editor, I just believe to get this thing to take off the approach should be more relevant for commercial use to result also in significant community contributions. I think there is a real case to be made (also communication wise) to establish an alternative to existing mass mail platforms.

I will find some time tomorrow to open up and create issues. Is there a demo running somewhere?

[talheim-it]

@fthobe let me create a new issue to collect the ideas :)

For PKI / Certificates I use freeipa or any other pki solution. MS is not dependable but thats because I implement wherever I can linux open source based solutions instead of proprietary software.

[talheim-it]

Feature Requests are collected here: #1373

[caloon]

Is v3 development still ongoing? The last comment on this thread was three months ago. I just tried to deploy Mailtrain on a new server, but since most VPS providers do no longer offer Ubuntu 18.04, Node.js 14, etc. it can't be (re-)installed right now.

[talheim-it]

@caloon yes, the situation that it relies on @bures at the moment. We are communicating but it is slow at the moment.

I hope that with v3 we can implement development guides to speed it up :)

[fillon]

I am in the same situation, our provider no longer offer Nodejs14... @talheim-it do you have a rough date for v3, is it for this month, 6 months.... Just to get an idea if we wait to build our server or move to another solution tx

[talheim-it]

@fillon thanks for your feedback.

I wrote @bures about it to make the process more transparent.

I completely agree that the silence here makes it abandoned and we need to improve the communication.

I will try to give you an update in approx a week :)

[fillon]

Thanks @talheim-it :)