Impacted versions

• Modoboa: 1.10.1
• installer used: Yes ?
• Webserver: Nginx

OS: centos 7.4

Steps to reproduce

Upgrade from 1.9.0

Current behavior

Can't open quarantine - Internal Error I have put Debug on, should open the debug log on modoboa ? can't see nothing on log files.

Impacted versions

• Modoboa: 1.8.2
• installer used: Yes
• Webserver: Nginx

When logging in to modoboa, for one particular domain I am unable to edit anything. For example, if I try to disable the domain and click update nothing happens. For that matter, any field I edit -- once I click update nothing happens. Changes are not saved and there are no error messages. However, I can go into the individual accounts within that domain and edit them without a problem. I can login to webmail without a problem. The accounts are able to send and receive email.

Impacted versions

• OS Type: Debian/Ubuntu
• OS Version: 20.0
• installer used: Yes
• Webserver: Nginx

Steps to reproduce

I installed my server Connect with admin and create simple user email Send my first email and it work Receive my first email and it work I connect my account to outlook with: mail server: mail.exemple.com username: [email protected] pass: pass Incoming port: 993 SSL Outgoing port: 587 STARTTLS I connected successfuly and I can see my email

Current behavior

When I try to send email from outlook I got an error I connected my account with node mailer and I got this error message: response: '451 4.3.5 [email protected]: Recipient address rejected: Server configuration problem'

Expected behavior

I should be able to send my mail from outlook as I do from my webmail

On my Modoboa server, the policyd upload limit is not reset every day.

So, my sending limit is lowered each time I send a mail, and never goes back up.

Hello everyone,

I don't think i'm the only one to have this issue. When I do all the configuration for domain and the DKIM box it's green, my mail don't pass dkim on gmail or other webmail, can someone help me to fix that please, i read some articles about openDKIM on mobodoa website or github but don't work for me, or I fail somewhere.

Thanks in advance for your answer.

Hi, I'm trying to install the Radicale module, but whenever I try to run python manage.py migrate it gives me this error:

Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 302, in execute
    settings.INSTALLED_APPS
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 55, in __getattr__
    self._setup(name)
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 43, in _setup
    self._wrapped = Settings(settings_module)
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 99, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/srv/modoboa/instance/instance/settings.py", line 255, in <module>
    from modoboa_amavis.settings import *
ImportError: No module named modoboa_amavis.settings

I got to say that this is a fresh installation.

Any idea what is missing?

Thanks.

I'm not experienced with Python, Postgre.

I have Modoboa 1.6.0 running on my mailserver . My install method was the 'easy', Python script method:

$ git clone https://github.com/modoboa/modoboa-installer $ cd modoboa-installer $ sudo ./run.py <mail server hostname>

I have read the docs describing how to update modoboa with new version, but I'm stuck on the deploy instructions.

Example from the docs: $ modoboa-admin.py deploy modoboa_example --collectstatic [--dburl default:database-url] [--extensions extensions]

What do I replace modoboa_example with?

How do I determine my --dburl values?

Any help is very appreciated!

Running the cronjobs (no matter under what account) triggers warning in syslog, like this

Dec 15 13:51:01 {hostname} mysqld: 141215 13:51:01 [Warning] Aborted connection {conn_id} to db: '{db_name}' user: '{db_user}' host: '{db_host}' (Unknown error)

example cronjob definition

0 0 * * * python /{modoboa_instance_path}/manage.py cleanlogs

Is this known issue, or problem of instance configuration? I'm not running it in virtualenv or anything special.

hi, i have new error without any reasson .. maybe restart or update any package .. but now have this :/

debian 10, maria 10.5 , nginx mainline, --

Mar 18 16:56:16 mail postfix/postscreen[20786]: CONNECT from [127.0.0.1]:57479 to [127.0.0.1]:25 Mar 18 16:56:16 mail postfix/postscreen[20786]: WHITELISTED [127.0.0.1]:57479 Mar 18 16:56:16 mail postfix/smtpd[20787]: connect from localhost[127.0.0.1] Mar 18 16:56:17 mail postfix/smtpd[20787]: warning: problem talking to server 127.0.0.1:9999: Success Mar 18 16:56:17 mail postfix/smtpd[20787]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.5 [email protected]: Recipient address rejected: Server configuration problem; from=[email protected] to=[email protected] proto=ESMTP helo=<email.domain1.net> Mar 18 16:56:17 mail postfix/smtpd[20787]: disconnect from localhost[127.0.0.1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6

thanks a lot !

I am considering switching from ASSP to modoboa and I was curious if it is possible to setup things up so that modoboa is configured as a mail gateway with all mail (and users) residing on another system (like xmail or hMailServer)?

I know that I can do this with postfix and setting up relay_domains, relay_receipients, and transport configuration files, The question is -- will modoboa continue to work with this confirmation (including support for quarantine)?

I'm recently having issues adding new users. Receiving this response

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data .parseJSON() jquery.min.js:3 Cwizard.prototype.post/<() creation_wizard.js:61 .proxy/i() jquery.min.js:3 b.Callbacks/c() jquery.min.js:3 b.Callbacks/p.fireWith() jquery.min.js:3 k() jquery.min.js:5 .send/r()

DKIM key in old admin interface shows both BIND and RAW versions of the DKIM key The new admin interface only shows the BIND variety, which is not helpful for hosted DNS

Modoboa 2.0.3 When using the old admin interface the suggested format for a DNS TXT entry is: modoboa._domainkey The new admin suggests: domain._domain_key One of the examples in which the new admin reports things differently, but also troublesome as testing tools expect the standard format as suggested by the old admin interface. The new suggestion seems wrong. Another example is the fact that new and old admin interfaces report differently on if dmarc, dnsbl, spf, mx, dkim are supported/configured per domain or not (properly).

Impacted versions

• OS Type: Ubuntu
• OS Version: 22.04
• Database Type: PostgreSQL
• Database version: 14.5
• Modoboa: 2.0.3
• installer used: Yes
• Webserver: Lighttpd

Steps to reproduce

1. Run the installer once, it creates installer.cfg
2. Edit that and adjust to your needs (specifically set the dovecot mailboxes_owner to vmail)
3. Run the installer again to install everything
4. Check /etc/dovecot/conf.d/mail/conf. Notice that mail_uid and mail_gid are commented out
5. Check /etc/dovecot/dovecot-sql.conf.ext and notice that both user_query and password_query return the uid and gid of the user dovecot not vmail

Current behavior

Webmail fails, IMAP fails ... and it turns out because the home_dir set in installer.cfg is owned by vmail/vmail and dovecot is trying to create Mailboxes in there running as dovecot/dovecot.

Expected behavior

I expect to see mail_uid and mail_gid set to vmail and uid and gid not returned by user_query or password_query

Fixing those, suddenly IMAP and Webmail work fine. Mailboxes are created and I can access them.

Caveat

This is from my install notes, having installed modaboa with the installer and then testing it. I have not reproduced it (as that's rather a costly exercise at present, but I may do some time and report back - as I'm currently just experimenting with modoboa and if I get it all functional will probably install a clean mailserver from my notes.

Because I have installed it on a play server I have (a sandbox server) there is no guarantee I ran all this on a clear fresh Ubuntu install and may have had a legacy dovecot installation even from an earlier experiment on it. Not likely relevant as I expect the installer to configure it as it needs anyhow (why else would one be running an installer) irrespective of any legacy installs. But I also have no recollection of ever experimenting with dovecot and postgresql before so consider it unlikely.

After tinkering with the request headers for a bit, I've found that the Accept-Language (if it contains a supported and available translated language) will take precedence over the language actually setup in the modo boa profile.

Removing the header will revert this behaviour, which seems to have been introduced by the v2.0.0 interface (which also has the same issue).

Discussed in https://github.com/modoboa/modoboa/discussions/2519

hope this is sufficient, else let me know if you would change something. Bash won't be a login shell but since we clear the enviroment with sudo -i this should not have any meaningful impact

Impacted versions

• OS Type: Ubuntu
• OS Version: 22.04.1 LTS
• Database Type: PostgreSQL
• Database version: 14
• Modoboa: 2.0.3
• installer used: A clone of the repo today. run.py does not convey a version.
• Webserver: lighttpd 1.4.63

Steps to reproduce

Surf to:

https://my-modoboa-site/user/#preferences/

Current behavior

I see this:

Expected behavior

Not that.

Basically landed here after an install because experienced this: https://github.com/modoboa/modoboa/issues/1411 and there it suggested looking at Preferences. But they don't load either.

For what it's worth I used this installer.cfg (redacted):

[general]
hostname = hermes.%(domain)s
tls_key_file = /etc/ssl/mykey
tls_cert_file = /etc/ssl/mycert

[certificate]
generate = false
#type = self-signed

# [letsencrypt]
# email = [email protected]

[database]
engine = postgres
host = 127.0.0.1
install = false

[postgres]
user = postgres
password = XXX

# [mysql]
# user = root
# password = s0FZUMDDfp5e3ASy
# charset = utf8
# collation = utf8_general_ci

[modoboa]
user = modoboa
home_dir = /data/www/hermes
venv_path = /data/venv/modoboa
instance_path = %(home_dir)s
timezone = Australia/Hobart
dbname = modoboa
dbuser = modoboa
dbpassword = XXX
extensions = modoboa-amavis modoboa-pdfcredentials modoboa-postfix-autoreply modoboa-sievefilters modoboa-webmail modoboa-contacts modoboa-radicale
devmode = false

[automx]
# makes configuring email accounts easy.
# Doesn't seem well maintained and hard to find info on it
# https://github.com/sys4/automx
# https://github.com/rseichter/automx2
enabled = true
user = automx
config_dir = /etc
home_dir = /srv/automx
venv_path = /data/venv/modoboa-automx
instance_path = %(home_dir)s/instance

[amavis]
# a high-performance and reliable interface between mailer (MTA) and one or more content checkers: virus scanners,
# and/or Mail::SpamAssassin Perl module. It is written in Perl
enabled = true
user = amavis
max_servers = 2
dbname = modoboa-amavis
dbuser = amavis
dbpassword = XXX

[clamav]
# open-source standard for mail gateway-scanning software
enabled = true
user = clamav

[dovecot]
# The IMAP server
# vmail is a user used by dovecot for storing mails.
# Well described by dovecot here: https://wiki.dovecot.org/VirtualUsers
# and by Arch here: https://wiki.archlinux.org/title/Virtual_user_mail_system_with_Postfix,_Dovecot_and_Roundcube#User
# And IMHO the best HowTo: is here: https://sharkysoft.com/wiki/how_to_configure_a_virtual_user_email_server_using_Postfix,_Dovecot,_and_SpamAssassin#Step_3:_Create_a_system_user_to_own_all_virtual_email_accounts.
enabled = true
config_dir = /etc/dovecot
user = dovecot
home_dir = /srv/vmail
mailboxes_owner = vmail
extra_protocols =
postmaster_address = postmaster@%(domain)s
radicale_auth_socket_path = /var/run/dovecot/auth-radicale

[nginx]
# Not needed, using lighttpd
enabled = false
config_dir = /etc/nginx

[razor]
# spam-catcher using a collaborative filtering network
enabled = true
config_dir = /etc/razor

[postfix]
# The SMTP server itself (MTA or Mail Transfer Agent), an alternative to the classic sendmail.
enabled = true
config_dir = /etc/postfix
message_size_limit = 11534336

[postwhite]
# A script for generating a Postscreen whitelist (and optionally a blacklist) based on large and presumably trustworthy senders' SPF records.
# The Postfix postscreen daemon provides additional protection against mail server overload.
enabled = true
config_dir = /etc

[spamassassin]
# Apache SpamAssassin is the #1 Open Source anti-spam platform
enabled = true
config_dir = /etc/mail/spamassassin
dbname = modoboa-spamassassin
dbuser = spamassassin
dbpassword = XXX

[uwsgi]
# Already installed (running other Django sites)
enabled = false
# config_dir = /etc/uwsgi
# nb_processes = 2

[radicale]
# Free and Open-Source CalDAV and CardDAV Server
enabled = true
user = radicale
config_dir = /etc/radicale
home_dir = /srv/radicale
venv_path = /data/venv/modoboa-radicale

[opendkim]
# OpenDKIM is an open source implementation of the DKIM (Domain Keys Identified Mail) sender authentication system
enabled = true
user = opendkim
config_dir = /etc
port = 12345
keys_storage_dir = /var/lib/dkim
dbuser = opendkim
dbpassword = XXX

[backup]
default_path = ./modoboa_backup/

And for what it's worth:

$ ll  /var/lib/dkim
total 8
drwxr-xr-x  2 opendkim opendkim 4096 Dec 12 13:50 ./
drwxr-xr-x 52 root     root     4096 Dec 12 13:50 ../

and

$ cat /etc/opendkim.conf
# This file was automatically installed on 2022-12-12T15:19:42.629214
# This is a basic configuration that can easily be adapted to suit a standard
# installation. For more advanced options, see opendkim.conf(5) and/or
# /usr/share/doc/opendkim/examples/opendkim.conf.sample.

# Log to syslog
Syslog			yes
SyslogSuccess   	Yes
LogWhy			Yes
LogResults  Yes

# Required to use local socket with MTAs that access the socket as a non-
# privileged user (e.g. Postfix)
UMask			007

# Sign for example.com with key in /etc/dkimkeys/dkim.key using
# selector '2007' (e.g. 2007._domainkey.example.com)
#Domain			example.com
#KeyFile		/etc/dkimkeys/dkim.key
#Selector		2007

KeyTable		dsn:pgsql://opendkim:password@5432+127.0.0.1/modoboa/table=dkim?keycol=id?datacol=domain_name,selector,private_key_path
SigningTable		dsn:pgsql://opendkim:password@5432+127.0.0.1/modoboa/table=dkim?keycol=domain_name?datacol=id

# Commonly-used options; the commented-out versions show the defaults.
#Canonicalization	simple
#Mode			sv
SubDomains		yes	
Canonicalization        relaxed/relaxed

# Socket smtp://localhost
#
# ##  Socket socketspec
# ##
# ##  Names the socket where this filter should listen for milter connections
# ##  from the MTA.  Required.  Should be in one of these forms:
# ##
# ##  inet:port@address           to listen on a specific interface
# ##  inet:port                   to listen on all interfaces
# ##  local:/path/to/socket       to listen on a UNIX domain socket
#
Socket                  inet:12345@localhost
#Socket			local:/var/run/opendkim/opendkim.sock

##  PidFile filename
###      default (none)
###
###  Name of the file where the filter should write its pid before beginning
###  normal operations.
#
PidFile               /var/run/opendkim/opendkim.pid


# Always oversign From (sign using actual From and a null From to prevent
# malicious signatures header fields (From and/or others) between the signer
# and the verifier.  From is oversigned by default in the Debian pacakge
# because it is often the identity key used by reputation systems and thus
# somewhat security sensitive.
OversignHeaders		From

##  ResolverConfiguration filename
##      default (none)
##
##  Specifies a configuration file to be passed to the Unbound library that
##  performs DNS queries applying the DNSSEC protocol.  See the Unbound
##  documentation at http://unbound.net for the expected content of this file.
##  The results of using this and the TrustAnchorFile setting at the same
##  time are undefined.
##  In Debian, /etc/unbound/unbound.conf is shipped as part of the Suggested
##  unbound package

# ResolverConfiguration     /etc/unbound/unbound.conf

##  TrustAnchorFile filename
##      default (none)
##
## Specifies a file from which trust anchor data should be read when doing
## DNS queries and applying the DNSSEC protocol.  See the Unbound documentation
## at http://unbound.net for the expected format of this file.

# TrustAnchorFile       /usr/share/dns/root.key

##  Userid userid
###      default (none)
###
###  Change to user "userid" before starting normal operation?  May include
###  a group ID as well, separated from the userid by a colon.
#
UserID                opendkim

ExternalIgnoreList      /etc/opendkim.hosts
InternalHosts           /etc/opendkim.hosts

and

$ ll /etc/opendkim*
-rw-r--r-- 1 root root 3310 Dec 12 15:19 /etc/opendkim.conf
-rw-r--r-- 1 root root 3310 Dec 12 15:19 /etc/opendkim.conf.old.2022-12-12T15:19:42.630614
-rw-r--r-- 1 root root   94 Dec 12 15:19 /etc/opendkim.hosts
-rw-r--r-- 1 root root   94 Dec 12 15:19 /etc/opendkim.hosts.old.2022-12-12T15:19:42.632340

All looks good on the OpenDKIM front (bar the fact that it's not working and I can't see Preferences at all which may be related).

$ sudo ls -l /var/run/opendkim/
total 4
-rw-r--r-- 1 root root 5 Dec 12 15:55 opendkim.pid