jonocodes/cypht container comments (latest/v2.0.1-wip)

[truthsword]

I was asked to try this image (originally I used sailfrog's image). In some ways this regressed for me. Rather than open multiple question posts, I have captured my initial impressions here.

I have used both jonocodes/cypht:latest and jonocodes/cypht:2.0.1-docker-wip image tags. The latest image gave me white screens when clicking the “Site” setting icon. The 2.0.1-docker-wip image displayed properly in the browser.

Findings:

• Create a profile seems missing
• No global Inbox, only global Unread
• No option to create multiple users. With the sailfrog image I was able to create multiple login credentials.
• Can't map folder sources to Trash, Sent, Junk, Drafts (maybe others). The resources are blank. There appear to be no means to map folders by email account as there is in the sailfrog image.
• Can't modify sources for the Flagged or Unread folders.
• The Sent folder does not show sources. It shows only an odd checkmark icon (if clicked, it reloads the Welcome page).
• Don't see Everything folder in left column. This appears in General settings, but there is no Everything folder in the left column.
• Don't see All Mail folder in left column. This appears in General settings, but there is no All Mail folder in the left column.
• IMAP subfolders do not appear. Same experience with the sailfrog image. This is a manually set up IMAP account from Charter Spectrum (mobile.charter.net:993).

[marclaporte]

Thank you @truthsword. This is very helpful.

I suspect all these issues come from 2 or 3 root causes.

@jonocodes is away from the keyboard for a few days and I am at Open Source events for the upcoming 2 weeks: https://tiki.org/TikiFestParis2024 so things will slow down a bit.

But @josaphatim will release Cypht 2.1.0 soon: #1050

And we will all make sure that https://hub.docker.com/u/cypht is as good as a manual install. We'll encourage the active developers to use it as much as possible.

[jonocodes]

Great info @truthsword . Thanks for testing.

Can you confirm that all these points are working with the old sailfrog image? And more importantly, if you have the resources, could you test to see if these are issues in master without docker?

@marclaporte what are the 2 or 3 causes guess?

[truthsword]

Can you confirm that all these points are working with the old sailfrog image

Some were, some weren't, some were “broken” in different ways. Going by memory… What worked in sailfrog, was

• the ability to create multiple logins
• the ability to define email account folders as Sent, Archive, Junk, Trash, Drafts... For example... mapping an email account folder “Sent Mail” to “Sent”.
• Designating email folders as resources for the combined folders (left column, top)... though not all worked as expected.
• profile creation worked; could create multiple sending profiles (alias?) for mail sending.
• The Everything folder was present, and seemingly functional.

What did not work in sailfrog,

• resource folder mappings were ignored and populated with seemingly random email folders. For example, Trash and Junk folder resources contained the draft folders from multiple email accounts.
• IMAP subfolders were not present for manually configured IMAP accounts.

could you test to see if these are issues in master without docker

I don't have a test machine to do that. Docker is simpler for me.

[marclaporte]

what are the 2 or 3 causes guess?

@truthsword compared legacy Docker recipe with 5 month old code from master vs new Docker recipe and latest code. Hypothesis: bugs emanate from either:

1- A side effect of #625 which is a massive revamp/cleanup 3 months ago in master. I expect breakage but things will be much easier to fix now because this new design is more robust.

2- Something needs an adjustment in the new Docker recipe. Ex.: something is hard-coded to off.

resource folder mappings were ignored and populated with seemingly random email folders. For example, Trash and Junk folder resources contained the draft folders from multiple email accounts.

I saw this and it was fixed. @truthsword was seeing because sailfrog Docker image has old code.

IMAP subfolders were not present for manually configured IMAP accounts.

I don't remember seeing this nor it being fixed, so I suspect it's just a regular bug. A good one for @Shadow243 to assign to one of the new devs as a training exercise :-)

[marclaporte]

@truthsword I expect some of the issues will be solved in Cypht 2.1.0 which should be available via Docker soon:
#1047 (comment)

[marclaporte]

@truthsword Please test with 2.1.0 https://hub.docker.com/r/cypht/cypht

I predict everything will be OK except #1046

[marclaporte]

@truthsword Please test with https://github.com/cypht-org/cypht/releases/tag/v2.2.0

[marclaporte]

@truthsword We are now at https://github.com/cypht-org/cypht/releases/tag/v2.4.0

[marclaporte]

• IMAP subfolders were not present for manually configured IMAP accounts.

Thank you @truthsword for #1046 so we can keep track on it independently.

[marclaporte]

could you test to see if these are issues in master without docker

I don't have a test machine to do that. Docker is simpler for me.

It is on our wishlist: #1175