Confuguration Error when setting up DeltaChat #9

Open
opened 2026-04-01 19:05:53 +00:00 by fabby · 9 comments
Owner

Image: raspi4_new_portal_changes_v0.0.2_010426.img.tar.gz
After scanning the QR Code I get "IMAP failed to connect" error when I try to log in.

Image: raspi4_new_portal_changes_v0.0.2_010426.img.tar.gz After scanning the QR Code I get "IMAP failed to connect" error when I try to log in.
Owner

What device/OS were you using, did you try both delta chat desktop and mobile and was the behaviour the same?

And just to double check, did you first complete the configuration steps and let the box reboot? The madmail service only gets configured and started after the operator has chosen a hostname and completed the configuration steps (and only after the subsequent reboot).

What device/OS were you using, did you try both delta chat desktop and mobile and was the behaviour the same? And just to double check, did you first complete the configuration steps and let the box reboot? The madmail service only gets configured and started after the operator has chosen a hostname and completed the configuration steps (and only after the subsequent reboot).
Owner

I was able to reproduce this error on both iPhone and Android. Didn't test on desktop.

Via root shell, can see madmail is not running, even after going through admin/service setup.

I was able to reproduce this error on both iPhone and Android. Didn't test on desktop. Via root shell, can see madmail is not running, even after going through admin/service setup.
Owner

If i try to run python3 /home/pi/butter-portal/install_madmail.py manually I get an error:

import pexpect
ModuleNotFoundError: No module named 'pexpect'

If i try to run python3 /home/pi/butter-portal/install_madmail.py manually I get an error: import pexpect ModuleNotFoundError: No module named 'pexpect'
Owner

systemctl status madmail - showed "inactive"
was able to then > systemctl restart madmail
to make it run.

DeltaChat then gets to "60%" on login attempt, but stuck there.

systemctl status madmail - showed "inactive" was able to then > systemctl restart madmail to make it run. DeltaChat then gets to "60%" on login attempt, but stuck there.
Owner

after a reboot, madmail service was now "disabled". Had to manually "restart".

it then shows that it is listening on various "0.0.0.0" ports like 587, 993, 143, and also 8443

after a reboot, madmail service was now "disabled". Had to manually "restart". it then shows that it is listening on various "0.0.0.0" ports like 587, 993, 143, and also 8443
Owner

oooo now everything is working. maybe the datetime issue is related?

From chat: "also realized, the box doesn't have the accurate time... which makes sense given it doesn't have an internet connection.
it started with an "April 1 2026" time, maybe from the image? and then after a reboot, I saw it had a Sept 2025 time on some files.
I manually set it to the correct time.... maybe we need a feature in the admin console to manually set the date and time?
that could be important for any crypto opertions of madmail?"

oooo now everything is working. maybe the datetime issue is related? From chat: "also realized, the box doesn't have the accurate time... which makes sense given it doesn't have an internet connection. it started with an "April 1 2026" time, maybe from the image? and then after a reboot, I saw it had a Sept 2025 time on some files. I manually set it to the correct time.... maybe we need a feature in the admin console to manually set the date and time? that could be important for any crypto opertions of madmail?"
Owner

setting up a pi3 right now fresh, and using incognito mode, and it properly walked me through the wizard.
Nathan GP (he)
okay that was a lot easier.

setup the box with the new portal wizard
waited for reboot (changed hostname and wifi)
once new wifi appeared, i connected to it from laptop
from laptop, I ssh'd in root@theotherbox.local (the name i called it)
set the date "date -s '2026-04-02 16:40:00' just in case
checked madmail 'systemctl status madmail' - it was in "disabled" state
restarted madmail 'systemctl restarted madmail' - worked!
laptop and phone could now connect / login on deltachat

setting up a pi3 right now fresh, and using incognito mode, and it properly walked me through the wizard. Nathan GP (he) okay that was a lot easier. setup the box with the new portal wizard waited for reboot (changed hostname and wifi) once new wifi appeared, i connected to it from laptop from laptop, I ssh'd in root@theotherbox.local (the name i called it) set the date "date -s '2026-04-02 16:40:00' just in case checked madmail 'systemctl status madmail' - it was in "disabled" state restarted madmail 'systemctl restarted madmail' - worked! laptop and phone could now connect / login on deltachat
Author
Owner

I manage to login on Delta Chat but:
The last step shoud be restarted madmail 'systemctl restart madmail' instead of restarted madmail 'systemctl restarted madmail'
And I was not able to send messages from one device to another because the QR codes didn't work. I got a loop between screenshots 1 and 2. So I added contacts manually and I wasn't allowed to send messages because E2EE wasn't set up yet. Screenshot 3.

I manage to login on Delta Chat but: The last step shoud be restarted madmail 'systemctl restart madmail' instead of restarted madmail 'systemctl restarted madmail' And I was not able to send messages from one device to another because the QR codes didn't work. I got a loop between screenshots 1 and 2. So I added contacts manually and I wasn't allowed to send messages because E2EE wasn't set up yet. Screenshot 3.
203 KiB
729 KiB
738 KiB
Owner

Testing the April 4 image, I no longer had to manually restart madmail, so great progress there.

The QR code issue remained, but we determined that was addressed by setting the date/time on the box.

This will be fixed with this ticket, as part of the wizard/setup: butter/butter-portal#15

Testing the April 4 image, I no longer had to manually restart madmail, so great progress there. The QR code issue remained, but we determined that was addressed by setting the date/time on the box. This will be fixed with this ticket, as part of the wizard/setup: https://guardianproject.dev/butter/butter-portal/issues/15
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: butter/churn#9
No description provided.