Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automx does not install correctly, Modoboa 2.2.0. #521

Closed
Aegis8 opened this issue Oct 5, 2023 · 2 comments
Closed

Automx does not install correctly, Modoboa 2.2.0. #521

Aegis8 opened this issue Oct 5, 2023 · 2 comments
Labels
stale Stale

Comments

@Aegis8
Copy link

Aegis8 commented Oct 5, 2023

Hello,

First off, thank you for modoboa and the installer! Getting a mail host up, has never been easier.

Now to the problem, after a migration and several test set ups, I found that automx was not installed correctly. I had assumed that it was working, for example Mozilla Thunderbird and Nextcloud automatically retrieved the server details. Only when inspecting the automx and syslogs, did I see that Thunderbird checked automx, received an error and continued with its own discovery methods.

The fix below works for Thunderbird and Outlook, this I tested using Postman. No other changes were made. I can not test IOS.

** Edit: corrected the commit link.

Impacted versions

modoboa 2.2.0 and I assume previous versions that incorporated d547d37

  • Distribution:
    Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-153-generic x86_64) and Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-86-generic x86_64)

  • Database: PostgreSQL

Steps to reproduce

Run the modoboa installer.
In the automx virtualenv, run pip list
Or run the installer with --debug and check the output for automx

image

results in:

image

I traced the problem to the changes made in d547d37

I updated the following section in the /scripts/automx.py with '"sqlalchemy < 2.0"'. Note I'm not a dev nor a python expert :)

def _setup_venv(self): """Prepare a python virtualenv.""" python.setup_virtualenv( self.venv_path, sudo_user=self.user, python_version=3) packages = [ "future", "lxml", "ipaddress", '"sqlalchemy < 2.0"', "python-memcached", "python-dateutil", "configparser" ] if self.dbengine == "postgres": packages.append("psycopg2-binary")

Ran the installer again and all the modules were installed for automx.

image

@hornikmichal
Copy link

Hello,

The same issue occurs in Debian 11/12 with PostgreSQL/MySQL. By applying the fix mentioned by Aegis8, I was able to complete the full installation and get automx working properly. Without this fix, I needed to install packages in a virtual environment manually.

Copy link

stale bot commented Mar 13, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale label Mar 13, 2024
@stale stale bot closed this as completed Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale
Projects
None yet
Development

No branches or pull requests

2 participants